A demo showing how a game made in Godot can be paused.Language: GDScriptRenderer: Compatibility
Simple demo project for an enemy AI that moves when not seen by the player.
This is a sample project which allows the user to tweak different parameters of a FastNoiseLite texture.Language: GDScriptRenderer: Compatibility
This is a demo for an OpenXR project where player movement is handled with a CharacterBody3D as a base node.This is based on the Character body centric solution as explained in the room scale manual page: https://docs.godotengine.org/en/stable/tutorials/xr/xr_room_scale.html#character-body-centric-solutionHow it works:With modern VR equipment the user is able to move around a large playspace.This is often refered to as roomscale VR.The position of the headset and controllers are tracked in reference to a fixed point within this playspace.This is often a point on the ground at the center of the playspace mapped out by the user when setting up their guardian.In Godot the center of this playspace is represented by the `XROrigin3D` node with camera and controllers being tracked through resp. `XRCamera3D` and `XRController3D` child nodes which can thus not be positioned by the user.The misunderstandings this causes in handling player movement is described in detail in the XR room scale manual page, a highly recommended read before continuing with this demo: https://docs.godotengine.org/en/stable/tutorials/xr/xr_room_scale.htmlThis demo implements the character body centric solution to the player movement problem.Virtual movement by the player (e.g. movement through controller input) in this demo is handled similarly to a non-XR Godot game.Physical movement by the player will result in the character body attempting to move to the players new location.If successful the XROrigin node is moved in the opposite direction of the players movement.If unsuccessful the character body stays behind, the further the player moves the more we black out the screen.Action map:This project does not use the default action map but instead configures an action map that just contains the actions required for this example to work. This so we remove any clutter and just focus on the functionality being demonstrated.There are only two actions needed for this example:- aim_pose is used to position the XR controllers- move is used as the input for our movement"Move" being the hero here. This action is only bound to one of the two controllers, by default making it a right hand option. Godot will always associate the move action with the controller that is bound to it.The code example assumes either controller could trigger the move action. Switching from right to left hand is a separate topic out of scope of this demonstration.Also following OpenXR guidelines only bindings for controllers with which the project has been tested are supplied. XR Runtimes should provide proper re-mapping however not all follow this guideline. You may need to add a binding for the platform you are using to the action map.Running on PCVR:This project can be run as normal for PCVR. Ensure that an OpenXR runtime has been installed.This project has been tested with the Oculus client and SteamVR OpenXR runtimes.Note that Godot currently can't run using the WMR OpenXR runtime. Install SteamVR with WMR support.Running on standalone VR:You must install the Android build templates and OpenXR loader plugin and configure an export template for your device.Please follow the instructions for deploying on Android in the manual: https://docs.godotengine.org/en/stable/tutorials/xr/deploying_to_android.htmlLanguage: GDScriptRenderer: Compatibility
This project showcases optional support for double-precision rendering and physics in action.When using a *single-precision* build, precision errors can be noticeable as soon as you're more than a few thousand units away from the world origin.When using a *double-precision* build, meshes will remain stable even when very far away from the world origin (billions of units away or more).See the Large world coordinates documentation for more information: https://docs.godotengine.org/en/latest/tutorials/physics/large_world_coordinates.htmlWARNING: Official Godot builds do *not* have double-precision support enabled for performance reasons. You need to compile a custom engine build to use double precision support.Languages: GDScriptRenderer: Mobile
A demo for my scrolling backgrounds tool.
A demo showing a GUI instanced within a 3D scene using viewports, as well as forwarding mouse and keyboard input to the GUI.Language: GDScriptRenderer: Compatibility
Layered Sprite is a Godot tool to easily divide a sprite in layers. It can be used for customizable characters.
This CharacterBody2D controller demo was created with the intent of being a decent starting point for Precision Platformers using Godot. Instead of teaching the basics, I tried to implement more advanced considerations seen in the following video: https://www.youtube.com/watch?v=2S3g8CgBG1gThat's why I call it 'Movement 2'. This is a sequel to learning demos of similar a kind.After playing around with the demo, you could potentially just copy over the Player.gd script and form it to your needs. Another option is to take the project as is and add to or subtract from it until you have a complete game.This project is also on itch.io: https://theothetorch.itch.io/movement-2
demo version: Godot 4.4 rc-3 .NETThis tool allow you Import PMX model. And import vmd animation to animate camera and model. This plugin depends on BulletSharpPInvoke.You can get libbullectc.dll from BulletSharpPInvoke's demo. Copy it to project directory. The link is below.https://github.com/AndresTraks/BulletSharpPInvoke/releasesTo compile BulletSharpPInvoke, you can check out my fork.https://github.com/sselecirPyM/BulletSharpPInvokeVideo Tutorial (Chinese):https://www.bilibili.com/video/BV1pKY3e5EHn/
This project shows how to create custom BBCode Tags for RichTextLabelsGoes with my tutorial video here: https://youtu.be/8CZfqdUd3bM
This is a minimal sample of connecting two peers to each other using WebSockets.Language: GDScriptRenderer: Compatibility