CatMI666 / example-3d

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Cocos Creator 3D Example cases

demo01

  1. scenes/helmet: PBR material showcase, skybox
  2. scenes/jellyfish: animation, transparent material, simple prefab instantiation
  3. scenes/knight: animation, light
  4. scenes/particle-compare: various particle effects
  5. scenes/sponza: multiple render target, particle system, lights
  6. scenes/tangents: glTF tangent space data conformance test
  7. scenes/winter: particle system, emitter editing

demo02

  1. scenes/ambient: ambient lighting
  2. scenes/audio: audio system baseline test
  3. scenes/collision-detection: simple collision detection
  4. scenes/custom-effect: custom shader
  5. scenes/pbr: PBR baseline
  6. scenes/physics: rigidbody physics simulation
  7. scenes/shadertoy: simple example on importing shadertoy resources
  8. scenes/shadows: planar shadow demo
  9. scenes/skin: pre-integrated SSS demo
  10. scenes/toon: NPR baseline

simple-fps

A really simple and lame FPS shooting game demo

Contribution

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 be.

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.

About


Languages

Language:TypeScript 100.0%