I made a new demo of water using Castle Game Engine. The demo is available in demo-models repository, in the water/simple/ subdirectory.

Open it with any viewer using the latest Castle Game Engine code, for example use the “daily build” of view3dscene. Here’s a movie:)

1. The next issue of Blaise Pascal Magazine will contain a nice long article I wrote about Castle Game Engine! 20 pages, describing how to use the engine from absolute basics, showing how to construct a simple cross-platform 3D game using TCastleWindow, TCastleScene, TCastleTransform, SoundEngine features. I am quite happy with it 🙂

   I will also make the article available for all Patrons of Castle Game Engine at the end of this month (September). If you would like to support the development of CGE, now is the time 🙂

   The article is accompanied by a public example code and data.

2. I will also be present next week an the Lazarus Professional Conference in Bonn. You can meet me on Saturday (22 September), during Community Day, when we will be showing Castle Game Engine.

   Please drop by to talk, or just to say “hi”:)

Since a week, Michalis is a Professional Member of the Web3D Consortium. These are the people who make X3D specifications, see also our documentation how X3D fits within Castle Game Engine. By being a “professional member” I will have some extra access (e.g. to see draft specs of upcoming X3D versions) and some influence to take X3D into interesting places 🙂

My vision and goals for X3D is documented publicly in my “x3d-tests” wiki. This wiki contains an overview + lots of details what I would like to see in X3D standard. Many of the ideas revolve around bringing X3D more “aligned” with glTF 2.0 feature set. Which is of course closely tied with getting glTF 2.0 into Castle Game Engine, as an X3D scene graph. I believe that this is a solution in which everyone wins, i.e. we will have an engine with perfect interchange format (for which glTF 2.0 is now better, although X3D tries to catch up) and a perfect scene graph (where X3D shines already).

We have a number of engine improvements to announce:

• A new way to access data files is to use a special protocol castle-data, like this: castle-data:/images/my_image.png. This is exactly equivalent to using ApplicationData('images/my_image.png'). During development, it will simply load a file data/images/my_image.png from your project.

  The “data” directory is documented in a new manual page. It is also listed on a reworked manual page about networking, downloading and URLs.

  The advantage of the castle-data protocol is that it can be used easily from other data files, like X3D or xxx.castle-user-interface created by Castle Game Engine Editor or Lazarus .lfm. The CGE editor already automatically uses this protocol if you open an image or 3D model within the data subdirectory of the project.

• We use AMD Compressonator, cross-platform and open-source, instead of old ATI Compressonator / AMD Compress. See the documentation how to automatically compress your textures.

• New manual page nicely summarizes supported model formats.

• The editor keeps improving. You can add, delete components, you can start a new file from any root (so e.g. you can start building user-interface rooted in TCastleUserInterfaceRect, or TCastleSceneManager), you can see the effect of the UI scaling, we automatically detect when you open a file in project data (and use castle-data protocol), you can easily add a scene with a primitive (like a box or plane, using PrimitiveGeometry underneath).

• Our Jenkins (Cloud Builds) includes a macOS machine now. The Linux build now makes Linux/x86_64 builds.

• Performance fixes for CustomRenderingPass and weSilhouette.

I’m proud to present first public screenshots from the upcoming Castle Game Engine Editor!

The goal of the editor is to allow you to manage CGE projects (create, build, run…), visually design hierarchies (of user interface controls and 3D/2D models) and browse project assets. Yeah, just like those other big game engines:)

A more precise list of features is in the README at the editor source code. And this is all following my plan for editor in 2018.

What does actually work now?

• You can create a project from a template, or open an existing project. Project is just any directory with CastleEngineManifest.xml file.

• You can compile / run / package / generate textures and do other usual operations on the project. The output, like compilation output, as well as program log (regardless of the OS) is displayed at the bottom. The editor calls the build tool for these operations, which in turn calls FPC and other tools.

• You can open and save a designed user interface (anything descending from TCastleUserInterface, formerly TUIControl) and 3D/2D game models (anything descending from TCastleTransform). They are serialized using Pascal RTTI (JSON format produced by FpJsonRtti). The editor, as well as your own game, use CastleComponentSerialize unit to do this. The files have extensions .castle-user-interface or .castle-transform and can be loaded with functions UserInterfaceLoad or TransformLoad.

• You can edit the published properties of the selected component using the object inspector on the right. It’s all updated “live” in the middle window of course. If you save the edited file, and run the project, you will see that it’s actually using a new design.

• See the screenshots for the initial stuff:)

Of course, many things are missing now, including some crucial things to make it actually useful for real applications. E.g. dropping new components on the design is not yet implemented. And dragging the UI controls, and TCastleTransform, visually (in the 3D window) is not possible yet. Well, there’s work ahead!

I’m really pleased with the result so far 🙂 P.S. If you like what I do, please consider donating to help in the development of the engine. Thank you!

We got excited and we decided to build our own Asset Store:) Initial plans are here.

While it’s being created, I suggest we upload models to opengameart.org and mark them by placing [cge] in the title. This way we can build the content for our asset store today 🙂 We have a persistent link to all models marked [cge], make sure your models appear there.

• The point of the models tagged with [cge] (and later in our asset store) is to be available in formats that Castle Game Engine can handle. Like X3D, castle-anim-frames, Spine JSON. See the exporting documentation about how to export from various software.

• Of course, just like all opengameart.org submissions, the assets must also be clearly marked with an open-source license. And, like all opengameart.org assets, you are strongly encouraged (but not required) to upload also a “source” model version (in Blender, Spine etc.), to allow people creating derivative works from it.

• It is best to test your models in view3dscene (you can use stable view3dscene version, or view3dscene snapshots from the latest GitHub code). Run the animations to see they are OK too, using menu item Animation -> Named Animations (this calls the familiar method PlayAnimation in CGE).

Note: The assets I upload will also be available as part of CGE demo-models repository, in subdirectory opengameart.org-submissions. So you can also get them from GitHub, and you can submit pull requests to add/modify them. But that’s just my choice, you can host your models in any way you like, just make sure to upload them 🙂

New stuff in the engine 🙂

1. More comfortable control over headlight using TCastleSceneManager.UseHeadlight property. This allows to easily turn headlight on/off regardless of the MainScene existence and it’s contents.

   See also TUseHeadlight type docs. See also new TCastleSceneManager.HeadlightNode property to customize headlight shape.

   A new demo showing how to control the headlight is in examples/headlight_test/

2. view3dscene has a new menu option Print Current Camera (Viewpoint) (Pascal) that outputs a suitable Camera.SetView(...) Pascal code.

3. The engine includes a simple time usage profiler (TCastleProfiler, Profiler singleton).

   It is automatically used by various CGE loading routines.

   Simply call Profiler.Enabled := true, and you will get in the log profile of the TCastleApplication.OnInitialize execution.

   Display Profiler.Summary at any point, in any way, in your application, to show the currently gathered profile.

   See the TCastleProfiler docs for more.

   Sample output:

   -------------------- Time Profile begin
   Profile (speed of execution).
   Each line shows time, followed by [time spent in this process], followed by description.
   Lines are sorted within each group, to show the most expensive operation at the top.
   
   7.35 [7.35] - TCastleApplication.OnInitialize
   > 1.65 [1.65] - Loading .../character/soldier1.castle-anim-frames (TCastleSceneCore)
   > 1.49 [1.48] - Loading .../level/level-dungeon.x3d (TCastleSceneCore)
   > 0.78 [0.78] - Loading All Sounds From .../audio/index.xml (TRepoSoundEngine)
   > > 0.71 [0.71] - Loading .../audio/dark_fallout.ogg (TSoundFile)
   > > 0.00 [0.00] - Loading .../audio/flaunch.wav (TSoundFile)
   2.07 [2.07] - Prepare Resources .../level/level-dungeon.x3d
   -------------------- Time Profile end
   

1. Sound engine improvements:

   • Easy additional simultaneous music tracks, for easily playing looping sounds, using the new LoopingChannel property.

   • Added a <group> element to group your sounds in “sound repository” XML files. See the manual about “Sound”.

   • We auto-detect extension (.wav, .ogg) if no URL is specified for <sound> in “sound repository” XML files (previously we assumed .wav).

2. The paper Tornado statistics in Ukraine based on new data is using Castle Game Engine for visualizations!

3. Our xxx_compile.sh scripts now just call the build tool. See this commit log for numerous reasons why this is better.

4. Our website is now protected by Cloudflare. In case of outage, you will see a cached version.

Sorry for being so quiet lately, lots of work! A big announcement about a big new feature is on the horizon, but I am not ready yet. 🙂

1. ClipPlane allows you to define custom clipping planes.

   See our documentation of nodes, X3D documentation of ClipPlane, and a simple demo or very complicated demo.

   Remember that this node can be specified in an X3D file (which you can open using e.g. view3dscene or load to TCastleScene), or it can be added and changed using Pascal code (use TClipPlaneNode class).

   While we already had this feature in the past, it was broken in the modern shader pipeline. It is fixed now, and will work both in modern OpenGL and on mobile OpenGLES 🙂

   • in OpenGL >= 3: use built-in gl_ClipDistance

   • in OpenGL < 3, keep using gl_ClipVertex,

   • in OpenGLES: use own castle_ClipDistance, discard in fragment shader.

2. We also have a new example showing how to use TInputShortcut and save it to a config file.