godot-google-play-billing VS godot-proposals

There's no post or pre processing stack. You cannot access world normals, motion vectors, depth buffer and such. You can only access the color, by creating a viewport.

Multiplatform support sucks. Mobile official plugins are dead [0], the package size is way heavier than Unity, you've got performance problems and nothing can assure your game will even be approved in Google Play. Android dev heavily requires plugins (Admob, Play Games), so unless put your game at a fixed price, you're not accomplishing anything. There's also no console support.

But wait, the Godot leaders made a company called W4 to fix these issues! They'll bring in console support, official mobile plugins, hosted multiplayer and such. But it's an investor funded company, and they stated that they will sell the stuff. Sooo, the "it's free and open source!!!!" advantage over Unity that everyone loves doesn't seem that great now.

I could talk all day long about Godot issues. But let's just sum it in "It's just Gimp, if compared to Photoshop". It's NOT a "It's just Blender, if compared to Maya".

I've lost all hope on the project, it's stil years away from reaching feature parity with, at least, Unity 5. But I hope Bevy does better!

[0] https://github.com/godotengine/godot-google-play-billing

https://github.com/godotengine/godot-ios-plugins and https://github.com/godotengine/godot-google-play-billing

Hello, I have downloaded the plugin from https://github.com/godotengine/godot-google-play-billing/releases and I have placed it in res/android/plugins but I don't believe it is working. I am testing it with the following code which never gives any output:

Godot was fine, for the most part, it's a good engine for small games. The main issue was around working together and resolving conflicts with git (Godot isn't really working and constantly kept changing IDs in resource files), and it kept losing data in scenes when the code changed so we had to rebuild things several times. On previous test games we also ran into huge performance issues in the editor when we wanted to do too much work in scenes, so we had to switch to doing most of the work in code.

The worst part was when I had to rip out a bunch of testing code that used @tool for release as it seemed to cause issues when doing a release build. The engine is generally not great when you want to follow clean software engineering (e.g. dependency injection is not possible, I opened a proposal to that end here[1]).

[1]: https://github.com/godotengine/godot-proposals/issues/8850

If we had a Mask2D, this would be super easy and straight forward.

So if that's what OP meant, clip_children property won't work. Instead OP needs to use a CanvasGroup parent and the Line2D (with CanvasItem Material in Subtract mode) and TextureRect as siblings, or any of the other methods explained here until we have a Mask2D node.

There is an open proposal to have a compile option for a LibGodot, as a Library https://github.com/godotengine/godot-proposals/issues/6267

Yes, there could be the option to open at least 2 tabs at the same time, when working with scripts. This has probably already been suggested in: https://github.com/godotengine/godot-proposals

I cannot tell exactly where the jitter is from the video, but if it is what I'm thinking of, it is a known issue, see here. There is a proposal to fix this, with tons of discussion here. Try some of the workarounds mentioned in these two links. Game looks great by the way!

It's in the release notes. Here is a link to the pull request, based on this proposal.

Currently not possible: https://github.com/godotengine/godot-proposals/issues/7213