VR: Michalis has access to Oculus Quest since the beginning of 2022. Port most likely using OpenXR (to include the widest possible range of devices using a single cross-platform API).
AR: most likely using Android / iOS built-in frameworks, as these make AR widely available on modern phones.
We should read meshes in a way that keeps binary layout of data in glTF, so that it is ultra-fast to load, and it is loaded almost straight from glTF to GPU.
Some modifications to CGE may be required here (CastleGeometryArrays will have to be made more flexible for this). New X3D nodes should be introduced, like
BufferGeometry (same as X3DOM?).
We should also perform skinning fully on GPU, avoiding
CoordinateInterpolator done on CPU.
More physics engine integration:
Physics behaviors in editor (ALMOST DONE - PR IN REVIEW - by Andrzej Kilijański).
Auto-size for colliders (ALMOST DONE - PR IN REVIEW - by Andrzej Kilijański).
Visualize colliders in editor
Joints (IN PROGRESS - by Andrzej Kilijański).
The details are listed in the manual about physics.
Using FPC + WebAssembly, new target announced at the end of 2021.
Some parts may also be done using pas2js. Done most likely just "wrapper", and the majority can be done using WebAssembly.
This is already in-progress by Trung Le (Kagamma).
Official Steam integration in CGE, see https://trello.com/c/RNDjQhqe/71-steam-headers . We already used it for The Unholy Society, we want to either “just publish that approach” or propose a new, improved (without an intermediate “wrapper” library) approach.
We should also upload CGE as app to Steam.
This is almost done, thanks to Jan Adamec. We need to release it :)
Associated with glTF, X3D and other formats that the view3dscene (and Castle Game Engine) handles. Available in the App Store / Google Play Store. For free or for 1 USD (not sure yet; but definitely without ads, I really dislike ads).
Easily design a height map (X3D
TElevationGridNode node, with trees, rocks, grass). Saved and loaded as an X3D file.
Implementing this feature will most likely be split into a couple of small releases:
Edit the heights.
Edit the grass and trees and rocks.
Efficiently render huge amounts of grass and trees and rocks.
Implement nice shaders to show it, like this BareGame example.
What we have now: The engine includes a unit
CastleTerrain to generate terrains in various ways (most notably, from smoothed random noise). We have
examples/terrain/ demo to play around with it. We have the "Wyrd Forest" game that also uses
CastleTerrain, and also includes a simple editor of terrain settings.
What we need: Visual, interactive editor for the
ElevationGrid (the thing you get from
TTerrain.Node call). To make hills, valleys in a comfortable way. And comfortably plant there stuff (rocks, grass, trees…).
Allowing to trivially get multi-playter functionality in your games.
We have a simple example code that shows how you can start a new renderer: see examples/research_special_rendering_methods/new_renderer_skeleton/.
This would make the whole TCastleViewport.Items a single graph of X3D nodes, allowing for more sharing in code. The TCastleTranform would be just like TTransformNode, but a little diferently optimized (but it would become toggable at runtime).
be simpler to users, as the engine will be "one single application" for macOS users.
avoid troubles resulting from Apple translocation. It right now prevents the CGE editor from detecting CGE path.
avoid current duplication of
castle-editor/data in distributed package, thus making it smaller by ~60 MB.
This will allow to run CGE editor on macOS by just double-clicking it, out-of-the-box.
We should also enable developers to easily sign their own applications packaged with CGE build tool.
These 5 units (CreatureCreatures / CastleResources / CastleLevels / CastleItems / CastlePlayer) expose a high-level API, that sits on top on existing classes (like TCastleScene and TCastleTransform). But I am not 100% happy with their API. Reasons:
The API is too specialized at some points (3D games with creatures / items pickable),
It is confusing how it maps to API underneath (e.g. TPlayer somewhat controls the TCastleNavigation).
Gradually I will want to express their features in different ways, in ways that are more closely and obviously connected with TCastleScene / TCastleViewport / TCastleNavigation. Basically, I’m very happy with current API of TCastleScene and TCastleTransform, and I want to make it more obvious how it is related to creatures/placeholders and other concepts introduced in CastleLevels and CastleCreatures and CastkeResources. Currently they use TCastleScene and TCastleTransform inside, but the relationship is non-obvious.
It’s not going to happen any time soon, but it will happen gradually, over the course of next 1 or more years. That is, some of the features of the 5 units mentioned above will become available in other ways too (more flexible, and more obviously connected to TCastleScene).
I know this sounds vague, because I have not yet clarified these plans in my head:) These 5 units are useful, they provide various features on top of TCastleScene. I’m not going to just "ditch" them or even deprecate them, before I made a better API that also has these features. For example:
New TCastleScene.Load should be able to take a callback (or some class instance) to easily perform the "placeholders" functionality of
TLevel.Load in a flexible manner (user can decide what to replace with what).
There will be TCastleSceneView that provides part of the functionality of T3DResource (multiple TCastleSceneView share a single TCastleScene but can show different animation frame of it), but without some often-unnecessary "baggage" from T3DResource (like refcounting of T3DResource, and it’s special Prepare/Release methods).
It should be possible to add an A.I. (like TWalkAttackLogic) to any TCastleTransform instance.
I know I want to go in this direction. Based on the questions (including on Discord) I see that the API of these 5 units is not clear to people. It wraps TCastleScene / TCastleViewport / TCastleNavigation, but in ways that are not obvious, and that is something I want to improve.
Again, bear in mind that it will not happen any time soon :) You can safely and happily use these units, probably for a few years to come.
But it is something I think about for the future, and it may explain some of my decisions. E.g. that is why I don’t plan special integration of TCastleCreature with castle-editor. Instead I want to enable you to add future TWalkAttackLogic to any TCastleTransform one day. And thus we will have "easy creatures" in CGE but with more flexible API.
We can make 3D modeling of realistically-looking stuff much easier by reusing libraries of realistic materials.
Explore possibility to support USD – Universal Scene Description format as a first-class citizen, alongside glTF and X3D, in CGE.
To improve this documentation just edit the source of this page in AsciiDoctor (simple wiki-like syntax) and create a pull request to Castle Game Engine WWW (cge-www) repository.
Copyright Michalis Kamburelis and Castle Game Engine Contributors.