Editor improvements: undo, context menu on hierarchy, shell list, clear warnings…

Posted on

editor-undo
editor-right
editor-rename
editor-warnings
  1. With great thanks to Eugene Loza, we now have a working Undo system for Castle Game Engine Editor!

    • You can undo / redo any action.
    • The undo / redo menu items shows the previous/next operation description.
    • History is trimmed smartly based on approximate size in memory.
    • See the pull request for details.
    • Just try it! It’s bound to Ctrl + Alt + Z shortcut now.

    We want to work on it some more before release: correctly handle transformation changes by gizmos, correctly handle record changes (like TCastleColor) by dialogs (right now these actions will be glued to the next undo; so the design remains correct, you just don’t have the “granularity” of undoing/redoing that you may expect). I’d also like to experiment whether we can assign it to Ctrl + Z when OI is not focused (right now undo is bound to Ctrl + Alt + Z to avoid conflicts).

  2. You can now edit names of components in the editor’s tree view (click or press F2). Also thanks to Eugene Loza!

  3. Right-clicking in hierarchy now exposes a context menu with some useful functions, in particular you can add new component as a child of selected. The credit for this goes also to Eugene Loza – thank you!

  4. Thanks to Andrzej Kilijański, we have a “Clear” button to clear currently displayed warnings.

  5. Fixed deleting a component (deletion should be recursive, previously the children were hidden but remained in memory and prevented from reusing the same Name).

  6. The shell list view is better, with directories.

  7. The dialog to open URLs (e.g. for TCastleScene.URL) by default starts in project’s data directory, to make it natural to choose files there.

Comment on this post ➤

“Escape from the Universe” has been released in Japan for Nintendo Switch

Posted on

Escape from the Universe - one of possible ending screens in Japanese

Escape from the Universe is now available in Japan for Nintendo Switch!

This is a Japanese version of our English (for Americas and Europe) version.

As some of you know, I’m wearing two hats — I’m the author of Castle Game Engine and I’m the CTO of Cat-astrophe Games, an indie game company where we plan to achieve great things with our technical skills, and also cats. Escape from the Universe was developed by Cat-astrophe Games some time ago, ported to Nintendo Switch, and now it has been translated to Japanese — all 100% in Castle Game Engine! The Japanese localization and a ton of testing was done by Worker Bee Inc.

The whole approach to localization is 100% open-source and part of CGE: see the manual section Localization (translation) using CastleLocalizationGetText. I hope this shows that our localization support is fully capable of handling a large, professional project, done in cooperation by 2 companies.

If you have Nintendo Switch, you have now no excuse not to play this game 🙂

Comment on this post ➤

Various engine improvements: lift lights limit, test simultaneous animations, fix changing TLevel.Player, SaveScreenRgba…

Posted on

Zrzut ekranu z 2020-10-22 22-53-57
Zrzut ekranu z 2020-10-22 22-54-04
Zrzut ekranu z 2020-10-22 21-40-10
Zrzut ekranu z 2020-10-22 21-40-27

Here goes an unorganized list of engine features and fixes done lately 🙂 Enjoy, and see if you can find something for yourself in this menu 🙂

  1. You can now increase the number of allowed lights per shape using Scene.Attributes.MaxLightsPerShape. view3dscene has a menu item to experiment with it (“View -> Max Lights Per Shape…”). A test model is in demo-models: gltf/multiple_animated_lights.

  2. view3dscene allows to test multiple simultaneous animations. Just select the checkbox Enable Multiple Simultaneous Animations in the animations panel (Ctrl + A), and now you start/stop the animations independently. The animations are controlled using TTimeSensorNode.Start and TTimeSensorNode.Stop, just like in the example simultaneous_animations_one_scene.

  3. Thanks to Andrzej Kilijański, changing TLevel.Player after the level is loaded is now fixed. This fixes various applications relying on it, like the old “The Castle” game. It is demonstrated by fps_game example, just press F1 to recreate player. It works reliably in all cases, with 1st and 3rd-person navigation.

  4. In code you can iterate using for .. in over TCastleTransform and TCastleUserInterface children.

  5. Fixed opening Lazarus when it is installed from Debian packages (lazarus-ide binary), thanks to Eugene Loza.

  6. TCastleViewport.PositionToRay utility. This allows to get a 3D ray from a 2D viewport position and use this ray to e.g. perform collisions with the world geometry to determine anything you like.

  7. TUIContainer.SaveScreenRgba method allows to grab a screenshot to RGBA image. An example is in examples/short_api_samples/save_screen_rgba/save_screen_rgba.lpr.

  8. Fixed glTF look in case of no explicit material.

  9. Fixed gravity when reading glTF camera (in glTF, gravity is always +Y).

  10. Fixed TCastleViewport.Transparent to ignore X3D Background nodes (it was always documented like this, but got accidentally broken ~year ago).

Comment on this post ➤

Improvements to creatures and items from resource.xml (weapon reloading, automatic pool…), updated resource_animations and fps_game examples

Posted on

fps_game_screen_1
fps_game_screen_3
fps_game_screen_4
Zrzut ekranu z 2020-10-19 02-48-53
Zrzut ekranu z 2020-10-19 02-48-18
Zrzut ekranu z 2020-10-19 02-48-00
Zrzut ekranu z 2020-10-19 02-47-41

A number of improvements and fixes to creatures and items defined by resource.xml were done. Also, our example animations/resource_animations was completely redone, and example fps_game now has a proper gun for shooting 🙂

  1. Weapons defined by CastleItems support reloading, with reload animation, ammo capacity and currently loaded ammo. Demo in fps_game .

  2. Auto-determine pool of animations. For animations not defined by castle-anim-frames/MD3, using pool is most advised, to get performance and animation blending.

  3. Introduced orientation=”..” to resource.xml options. Allows to mix models in glTF, castle-anim-frames and any other formats easily within one project.

  4. resource_animations example is now:

    • designed using CGE editor.
    • it is much simpler, spawning creature “by the book” (using CreateCreature) instead of demonstrating its animations in hacky way.
    • clearly advises the approach “single glTF file” instead of setups with x3d/castle-anim-frames.
  5. The ShootingEye from fps_game with no/poor animations is replaced with a pretty plasma gun from OpenGameArt. The model has been retouched by Michalis and exports nicely to glTF.

  6. Deprecated using different URLs for different animations. See how to define animations in resource.xml. Different file per animation doesn’t match the advised usage (one glTF file with all animations), is not efficient (the same file will be switched back-and-forth to show various animation states, if reused by multiple creatures) and makes animation blending impossible.

  7. Fixed blinking of animation from castle-anim-frames when defined in resource.xml

  8. Fixed changing bounding sphere radius for resources loaded from resource.xml

Comment on this post ➤

Updated online conversion tool to X3D (from glTF, Spine, Collada, others)

Posted on

convert-to-x3d

Our online conversion tool was updated to include all the latest improvements done in Castle Game Engine in the last months.

In particular, you can now use it to convert glTF 2.0 files to X3D (in classic or XML encoding) and the output will automatically use X3D PhysicalMaterial nodes to express glTF PBR materials.

In general our approach to convert glTF -> X3D is documented here. So if you’re unsure how given glTF construction is translated to X3D, this page probably has an answer 🙂

You can open the resulting X3D files in view3dscene or any other engine tool.

Reminder: you can also use view3dscene to do the same conversion (interactively or in batch mode). Use “File -> Save As X3D…” menu item, or command-line as documented here. We provide the online tool just as a convenience for people who don’t want to install view3dscene.

Comment on this post ➤

Andrzej Kilijański joins the development of Castle Game Engine

Posted on

I want to announce, with great excitement, that Andrzej Kilijański joined the development of Castle Game Engine as his part-time job since this October!

You already know Andrzej (and3md on Discord) 🙂 He wrote a number of articles about CGE, and provided many PRs focusing on physics (like settings, triggers, OnCollisionEnter, GetCollidingTransforms), mobile (like time, ASTC compression, admob updates) music (streaming!) and more. So I’m absolutely certain of his experience and dedication for our engine.

As I want our engine to grow, I decided we need to invest. Thanks to this, Andrzej will now be able to spend serious time developing CGE, and we will proceed to develop the engine at unparalled speed 🙂

I want to thank all our Patreon supporters at this point. The money you put in our project is making a serious difference. Please support the engine on Patreon if you like the engine!

Oh, and the tasks we do and their order are public on CGE Trello. That is the place where we coordinate work, and everyone is welcome to join.

Comment on this post ➤

Attach objects to (animated) bones, like weapon in character’s hand, by ExposeTransforms

Posted on

Zrzut ekranu z 2020-10-09 00-47-16
Zrzut ekranu z 2020-10-09 00-46-42
Zrzut ekranu z 2020-10-02 02-42-19
Zrzut ekranu z 2020-10-09 02-17-05

You can now easily attach objects to (animated) bones in your models, e.g. to attach a weapon to animated character’s hand.

This is performed by setting the TCastleSceneCore.ExposeTransforms property. It allows to “expose” transform nodes within a TCastleScene. Transform node is TTransformNode, which in particular represents “bones” animated by glTF and Spine. “Expose” means that we create children TCastleTransform instances, which follow these bones. Subsequently, you can place new scenes inside these children, e.g. add weapons to the hand bone.

It is all nicely visual, ExposeTransforms can be set in the CGE editor using a comfortable dialog box. The children transforms are automatically created and named.

You can also use ExposeTransformsPrefix to avoid name collisions.

See the example application examples/animations/expose_transformations_to_animate_children.

Comment on this post ➤

Upcoming talks about Castle Game Engine at conferences!

Posted on

Screenshot of selection at 2019-02-17 22:01:41
  1. On 9-13 November the Web3D 2020 conference will be held. This year, it is online and completely free! I recommend this event for people interested in the X3D standard, which is an important building block of our engine.

    I will have a short talk (20 minutes) about view3dscene capabilities, esp. in regards to new X3Dv4 features there.

  2. On 19-22 November, MiniDebConf Online #2 “Gaming Edition” will take place. It is also free and completely online. I recommend this event for people interested in Linux, Debian and gaming on these platforms. Actually my talk there will be quite universal, so you’re all invited 🙂

    I will give a talk presenting new Castle Game Engine 7.0 features during the “talks weekend” (21+22 November). It will be 35 min talk + 10 minutes for questions.

I will announce more as we get closer to these dates.

Comment on this post ➤