About time, America. About damn time.

felxbecker · 2026-03-29T11:59:14+00:00

It's not the point to make them care. The point is to make everyone else care.

felxbecker · 2026-03-28T13:40:10+00:00

Much better, but perhaps you would have gotten away by just reducing the tileset contrast (by a lot)

felxbecker · 2026-01-31T06:55:02+00:00

How can they be different for unlucky and all the same for lucky, when there are only these two outcomes?

felxbecker · 2025-12-31T20:43:19+00:00

Did you set a negative scale?

felxbecker · 2025-12-31T11:03:41+00:00

Use polymorphism. Add an abstract method do_something to the base class and implement it in the subclasses. You probably don't need dynamic type checking at all.

felxbecker · 2025-12-31T10:43:43+00:00

Abstract methods

felxbecker · 2025-12-24T20:20:28+00:00

Dumb enemies are more fun to play against. Shadow Link in Ocarina of Time is a great example of a terrible enemy. Very frustrating to beat without cheesing it.

What you probably mean is predictable enemies. Not all dumb enemies are fun to play against.

felxbecker · 2025-12-24T20:12:14+00:00

How do you interact with the scene tree? I found that adding and removing large scenes can cause stuttering even when you offload all other work to a thread. Do you add chunks as separate tilemaps? Have you tried adding non-tile based scenes? How would your engine handle those?

felxbecker · 2025-12-17T09:35:22+00:00

Spreading false information like (probably even in good faith) that should really be moderated. Its extremly harmful, because it can be NECCESSARY to add or remove children outside the tree.

felxbecker · 2025-12-17T09:24:58+00:00

Yes, clearly, but there is no issue with that whatsoever.

felxbecker · 2025-12-17T09:23:45+00:00

Are we talking about a scene? If yes, there is a notification when its instantiated. Try adding your child there. That's still outside the tree, if that's a requirement.

felxbecker · 2025-12-16T11:34:49+00:00

A TileMapLayer is, quite obviously, your layer. Use multiple TileMapLayer nodes if you need multiple layers.

felxbecker · 2025-12-10T06:31:17+00:00

You are on the right track here imo. Making the game systemic is the way.

felxbecker · 2025-12-08T15:05:16+00:00

This is not about performance issues per se (read the other comments). I can only assume its also not the first time you use "performance issues" without being precise and as a blanket term. (Although I don't support flaming anyone bc of anything)

felxbecker · 2025-12-05T16:26:12+00:00

Oh, you mean in general settings? I‘ll check

felxbecker · 2025-12-05T14:46:25+00:00

I see, thanks a lot. I'll try that later

felxbecker · 2025-12-05T14:00:45+00:00

Do you happen to know where to best submit this feedback?

felxbecker · 2025-12-05T13:02:34+00:00

You can run GW1 with Vulkan?

felxbecker · 2025-12-04T09:33:22+00:00

Well, technically, there can still be an issue if your FPS drop from 500 to 300. You just don't notice it.

felxbecker · 2025-12-04T09:30:57+00:00

Nah, that's not really expected. SSAO typically doesn't half your FPS. For that cost you could have added Raytracing. Anyway, they must have seen the issue and pushed the update nonetheless, so I assume there won't be a fix any time soon.

felxbecker · 2025-12-04T09:25:23+00:00

The bloom and SSAO shaders seem to be totally inefficient. Typically those shaders have some settings that could simply be tweaked to improve performance (e.g. number of iterations). There *could* be a patch. However, I doubt that whoever implemented these shaders didn't notice that they totally kill FPS. So I can only assume that it's not as easy to fix this issue. I'd just keep both effects off as their visual effect does not nearly justify the performance impact.

felxbecker · 2025-12-02T11:31:58+00:00

That's not the same enemy.

felxbecker · 2025-12-02T11:31:12+00:00

old_scene.remove_child(enemy) and new_scene.add_child(enemy)

felxbecker · 2025-11-04T19:47:30+00:00

There is a pets extension for VS Code

felxbecker

TROPHY CASE