- scenes/helmet: PBR material showcase, skybox
- scenes/jellyfish: animation, transparent material, simple prefab instantiation
- scenes/knight: animation, light
- scenes/sponza: multiple render target, particle system, lights
- scenes/winter: particle system, emitter editing
- scenes/ambient: ambient lighting
- scenes/audio: audio system baseline test
- scenes/collision-detection: simple collision detection
- scenes/custom-effect: custom shader
- scenes/pbr: PBR baseline test (tbc.)
- scenes/physics: rigidbody physics simulation
- scenes/shadows: planar shadow demo
A really simple and lame FPS shooting game demo
For future contributer and maintainers, please apply to the same rigorous examination and documentation style as we have established so far.
It is the only way for us to reach far.
If some bug is forcing you to do some hacking, workaround, or any kind of strange logic that is not immediately comprehensible, be sure to add clear explanation comments at obvious places nearby.
Every 'unpleasant surprise' encountered along the road is a big deal:
Either something is not working, or some designed feature is far less intuitive than what the designer thought it would.
So make sure to do all the followings:
- try to classify the problem: is it editor-related or engine-originated? Which module(s) were involved?
- file an issue to the relevant team
- If it is a bug, clearly document it in code (usually near your temporary workaround) with the issue number.
- If it is a feature(or lack of one) and looks/feels strange/awkward no matter how you design the relevant system, make sure to write it down in the issue ticket with detailed explaination on your design decisions and why the engine API is not a good fit.
- Remove all the workaround or temporary designs once the bug is fixed or new feature is introduced.