November/December engine improvements:
-
We no longer use the GtkGlExt library on Unix. It was not necessary (we had a code to initialize OpenGL directly using glX on X11, and it is simpler). And this way user has one less library that needs to be installed before our application can be run.
-
Loading optimizations: The TCastleTransform resources are no longer freed prematurely in some scenarios. You can also define
CASTLE_SLIM_NODES
to have a little faster node creation. -
You can specify in CastleEngineManifest.xml to build using lazbuild. This way our build tool and editor run under the hood lazbuild instead of “bare” FPC. It’s quite useful if your application uses some Lazarus packages (like LCL). For caveats see the documentation of
lazarus_project
andbuild_using_lazbuild
. -
New version of model_3d_with_2d_controls example shows how to use CGE editor within Lazarus (LCL) application. We design CGE UI in CGE editor, and then load it into
TCastleControlBase
on a regular Lazarus form. -
Reimplemented TCastleInspectorControl, it is much more useful now to inspect the UI hiierarchy. Just add it to your window like
Window.Controls.InsertFront(TCastleInspectorControl.Create(...))
. Toggle visibility with F12. -
I’m working on introducing PBR to X3D specification, and then to CGE! We’ve talked a lot, and my pull request to introduce it into the Web3d specification is in-progress. We also have some initial examples how it will look like. In short: there will be a new node
PhysicalMaterial
. -
Log file location changed on Windows: We cannot assume we can write into the directory of the exe (because we cannot, e.g. if exe is in read-only “Program Files”). Instead we write into the log in user config directory. You can use LogOutput to print this value. See the new, extended manual page about logging.
-
Container.Focus fixed.
Start the discussion at Castle Game Engine Forum