Godot VS Cocos2d

I noticed that Godot Engine Apple Vision OS support is merged today. <3

https://github.com/godotengine/godot/pull/105628

Godot + LLM backend

> I failed to fairly evaluate my options at the start of the project.

The more projects I do, the more time I find that I dedicate to just planning things up front. Sometimes it's fun to just open a game engine and start playing with it (I too have an unfair bias in this area, but towards Godot [https://godotengine.org/]), but if I ever want to build something to release, I start with a spreadsheet.

It’s definitely niche, but one of the best presentations I’ve ever seen was done in godot [0]

One of my coworkers copied our PowerPoint theme, built a super basic presentation mode with transitions and used the engine for interactive demos live in the slides running the code.

[0] https://godotengine.org/

If you are talking about this link [0], the person answering is from the Godot team and not Apple.

[0] https://github.com/godotengine/godot/pull/105628#issuecommen...

I don’t think the support depends on distros much, I think the main variable is hardware. If you have a desktop PC bought in the last ~5 years the support should be OK, for the hardware older than that the support is not guaranteed. GeForce GT 730 (launched in 2014) doesn’t support Vulkan, Intel only supports Vulkan on Windows starting from Skylake launched in 2015.

Then there’re quality issues. If you search internets for “Windows Vulkan issue” you’ll find many end users with crashing games, game developers with crashing game engines https://github.com/godotengine/godot/issues/100807 recommendations to update drivers or disable some Vulkan layers in registry, etc.

On Windows, Vulkan is simply not as reliable as D3D. The reasons include market share, D3D being a requirement to render the desktop, D3D runtime being a part of the OS supported by Microsoft (Vulkan relies solely on GPU vendors), and D3D being older (first version of VK spec released in 2016, D3D11 is from 2009).

Another thing, on Linux, the situation with Vulkan support is less than ideal for mobile and embedded systems. Some embedded ARM SoCs only support GLES 3.1 (which BTW is not too far from D3D 11.0 feature-wise) but not Vulkan.

I personally find Go miles easier than Rust.

Is this the ultimate reason,Go is fast enough without being overally difficult. I'm humbly open to being wrong.

While I'm here, any reason Microsoft isn't sponsoring a solid open source game engine.

Even a bit of support for Godot's C#( help them get it working on web), would be great.

Even better would be a full C# engine with support for web assembly.

https://github.com/godotengine/godot/issues/70796

Historically, open-source software has played a critical role in democratizing the development process. Platforms like Blender for 3D modeling and Godot Engine for game creation have revolutionized the creative process, offering free and powerful alternatives to proprietary solutions. By integrating these tools, The Sandbox leverages the robustness of community-driven technology and innovative coding practices that have been refined over years of collaborative use. The decision to delve into open source is not merely about cost savings or accessibility—it signals a paradigm shift. By embracing transparency and community input, The Sandbox is setting the stage for new forms of digital ownership and interaction. These practices lead to more secure, adaptable, and innovative gaming experiences that challenge the norms of traditional game development.

Great updates! Specifically .NET 8 as well as Typed Dictionaries with GDScript.

Really hoping we see web export for C# soon. https://github.com/godotengine/godot/issues/70796

That's all I can really tell you from what you've posted. The original version without the Blowfish encryption is open source (eg. https://github.com/cocos2d/cocos2d-x/blob/v4/cocos/scripting/lua-bindings/manual/CCLuaStack.cpp) , and I don't really understand how why you have so much symbol information available if what you're trying to disassemble isn't also probably open source

As others have pointed out, the biggest difference you're seeing is likely due to the _version_ of OpenGL (and hence GLSL) version. That said, there are still important differences. I'd recommend looking at a comparison between the same shader in a project that supports both OpenGL & OpenGLES. For example, here's a shader from cocos2d-x https://github.com/cocos2d/cocos2d-x/blob/v4/cocos/renderer/shaders/positionColor.vert. Note the only difference in this case is the additional precision qualifier (lowp) for v_fragmentColor. Note too how cocos uses preprocessor macros to handle this, so they don't have to maintain separate shader sources. Depending on your goals, you might be interested in tools like Nvidia cg or nvFX that allow for creating shaders in a dialect agnostic way, but ymmv.

Speaking about markdown files on GitHub, I know that there are some repositories that have very stunning README markdown files, such as this one for Cocos2d-x, whcih includes images in conjunction with text. I might do the same for my repository as well. Considering VS Code have an extension for .md files, this might come in handy when I consider using VS Code to contribute to my game projects.