I do noticed a small bug on the splash sprites showing fully when looking farther away from the water fall vs closer.. maybe a bug on the engine itself?
Viewing post in Stress Test for Copperlicht.js comments
Hi, yes, there is an alpha sorting issue with the Copperlcht cubemapped Water in WebGL, with anything else using Alpha transparency, when viewed from a certain angle. Not much I can do (other than to position things in a better way that prevents such viewing angles). You can also see it on the viking boat, sometimes the part that's under water appears over the water. I wish this was the only bug ^^ but this one is not my contribution. Anyway, Copperlicht is still the most practical, sleeves up hands on WebGL approach in terms of porting Blitz3D syntax to WebGL, which is the actual goal of this exercise. It's not so much the syntax, but the set of tools that made it so easy to write games in Blitz3D.
For instance you wouldn't believe how complicated it gets when I want to linepick in the line of fire. First I have to check whether a line intersects with an npcs bounding box. Then I have to check with an other linepick command where my bullet would hit the world (but it will go trough the npc mesh). Then I have to calc the distances between impact and actual player-npc distance, and if the impact distance is shorter, I can assume the bullet has hit an obstacle in between. To wrap that all up and put it into a LinePick() function that returns the picked entity is so troubled - I already wrote the alternative linepick for Copperlicht, however it does not take into account dynamic rotation - I'd have to add a bunch of matrix stuff in there. Yet, when one uses a cylinder parented to the npc for linepicks instead, it's probably slightly inaccurate, but the function in itself is pretty fast. Right now I got 5 npcs in a working shooting scenario, including Coppercube Linepicks (as described first) between me, the npcs and anything with collision in between (terrain, tree trunk boxes, buildings, rocks) and while the framerate was still kind of playable before I added this simple game logic, it is now getting really slow. Anyway, the whole approach with such a big terrain probably was just a bit too ambitious. Then again, most people have faster graphics than I do. Wasn't there some other Blitz3D to WebGL attempt? Blitz3D NG or something? If I can save myself all the work, let me know.
I never looked closer into MiniB3D, but kind of remember it was pretty limited. Esp. when compared to copperlicht, that has a lot that even blitz couldn't offer, like realtime shadows or render to texture. Also, loading B3D with lightmaps, for instance exports from Terabits Decorator. It made it a pretty ideal candidate to simply wrap copperlicht commands in Blitz syntax, the rest is then only Basic to Javascript, that I've done to some degree with the BB2JS converter already. Also, the mini3Dsoundengine.js is ready to be added. Copperlicht lacks some stuff, but some of it can be written and added in html5 directly, and some things must just be hackamulated together, like for instance Linepicks. However, most ikely one will always have to follow some special procedure in writing for Blitz3D in a way that such a converter could process. Things like EntityPickMode that sets the pickability, must add this mesh and its triangles to a dynamic list of geometry that should be checked at all, just as an example on how things can get complicated quickly, as here you'd also have to parse the meshes recursively for child meshes (eg NPCs), which may be the wrong approach due to speed in WebGL anyway, so you would use invisible boxes attached to the NPCs to check linepicks - the conditions differ so much that these special proceedings were kind of necessary.
Copperlicht,js is the WebGL engine that the visual editor CopperCube uses when exporting for the WebGL target. Copperlicht.js can be scripted directly without the help of Coppercube, but Coppercube offers some convenient features, like a world editor that imports a nice range of formats and can put all assets into one CCBZ file that you will distribute (except textures and sounds). You can then also load this CCBZ file by script and or mod the html page that CopperCube exports.
CopperCube can also export for other targets such as DirectX, OGL, Mac, Android, if I'm not mistaken, but I'm only interested in WebGL.
There's also Vortex2 which has more features and shadows, but has a bug with the skeletal animation system so it diverted to vertex morph animation which is not good and practical.
Btw, I assume you already saw this, so you should join the site challenge for the waterfall entry as I think you will already win by default (only entry so far). Mark (markcwm) has now taken over and sponsoring this contest with a bit of reward or prizes will be given.