Advanced Castle Game Engine features - forms, 3D generation, shaders, customizing editor
0 likes13 views
The document discusses the capabilities of the Castle Game Engine, including 3D generation, shader effects, and customizing the editor. It outlines various features like modifying 3D worlds, creating custom components, and offers examples and documentation links for further guidance. The engine is compatible with Delphi versions >= 10.2.1 and supports UI scaling for cross-platform games.
Advanced Castle Game Engine features - forms, 3D generation, shaders, customizing editor
- 1. Advanced Castle Game Engine Forms, 3D generation, shaders, customizing the editor (and more) Michalis Kamburelis
- 3. Engine on FMX form (Windows, Linux; other Delphi platforms coming)
- 4. BTW, Delphi Linux (on FMX) P.S. WSL rocks for Delphi+Linux (lightweight, comfortable Linux inside Windows), thanks Jim McKeeth
- 6. Editor or not? ● You can design things in CGE editor. Or not, create all by code. ● You can use TCastleControl (FMX, VCL, LCL) or TCastleWindow. ● These are independent decisions. ○ All 4 combinations make sense :)
- 7. Use CGE API from FMX events
- 9. 2023 Generate (or modify) 3D worlds
- 10. Build or modify worlds ● build (or modify) ● 3D or 2D content ● using Pascal code ● use-cases? ○ visualize some external data (like a real-life 3D machinery or statistical data) ○ procedurally generate 3D worlds ○ fix / enhance existing 3D models
- 13. From where, to where? ● You can start from: ○ nothing (just create empty TX3DRootNode) ○ or any imported model (X3D, glTF , Collada, STL, …) ○ (you can combine multiple models too) ● Do what you want on nodes' graph in memory ○ Build and modify ○ Render ○ Process animations, interactions (touch sensors) ● You can save to: ○ X3D file (perfect representation, no loss!) ○ (Coming soon: also save to glTF)
- 16. Enhance the look of ● Shapes ● Groups of shapes (maybe whole model from glTF , X3D etc.) ● Lights ● Textures (maybe write reusable texture generated in shader) ● Screen (post-processing effects) using your own GLSL (OpenGL Shading Language) code.
- 17. Examples ● Volumetric fog ● Water ● Screen effects ○ Escape from the Universe, on Nintendo Switch: https://www.nintendo.com/us/store/products/escape-fro m-the-universe-switch/
- 18. Volumetric fog (sample 3D texture with noise)
- 19. Water ● render texture for mirror https://castle-engine.io/x3d_extensions_mirror_plane.php ● perturb normals from animated noise
- 20. Chromatic aberration screen e ect (aka post-processing e ect)
- 26. Custom components ● Specific to your project ● Reuse some necessary graphical designs and logic ○ E.g. a button for consistent game UI, with key on PC, with keypad on consoles ○ E.g. a 3D object, like a machinery part, with configurable size / layout / attachments etc. ○ Maybe model with a shader effect from previous section ○ Maybe 3D thing procedurally-generated from previous section
- 27. Design-time Special design-time operations: ● Use component editors, as in Delphi (context menu on component) ● Use property editors, as in Delphi (special editors for some properties, even with dedicated forms) ● Override CGE editor special methods to enable extra design-time in CGE editor, like mesh editing
- 29. Example: Castle Lines 2D https://github.com/KumurTash/CastleLines2D (by Korchazhkin Sergey) Design-time lines and polygons editor! Note: use version from branch, https://github.com/KumurTash/CastleLines2D/p ull/3
- 34. Delphi versions supported ● All Delphi versions >= 10.2.1 ○ These are Windows and (to be confirmed) Linux requirements ○ For mobile, a bit stricter requirements: Delphi >= 10.4 ○ Always recommended latest Delphi stable, so 11.3 now ○ Tested with Delphi 12 beta of course :) ● Delphi Community Edition is OK too, we specifically test it ○ Note the need to build from Delphi in this case, F9 from CGE editor cannot work as Community Edition doesn't have command-line compiler. ● https://castle-engine.io/delphi
- 35. Engine can optionally scale UI. ● It can follow DPI scaling. ● Or it can follow some hard-coded window size (like 1600x900) "fit" or "enclose" your screen. ○ This is like Unity UI scaling, easy to use and effective for cross-platform games (where UI size doesn't have to match other apps). ● To make it work OK, you must use anchors. ● Effectively, you can pretend that you always have the same window size (like 1600x900), hardcode all the positions and sizes, set proper anchors, and you're good. UI Scaling