ArjinFerman
Tinfoil Gigachad
No bio...
User ID: 626
ArjinFerman
Tinfoil Gigachad
15hr ago
...and just to drive the point home...
EU ties €35bn fund release to Hungary’s break with Orbán era
To unlock the funds, Hungary would need to meet 27 conditions, including anti-corruption checks and a rollback of Orbán-era decisions deemed in breach of EU rules, from the treatment of asylum seekers to ensuring academic freedom.
Which would include the anti-LGBTQ+++ law I brought up with @Stefferi.
ArjinFerman
Tinfoil Gigachad
16hr ago
No, it's not. It's only purpose was to antagonize Christians, and that story was invented for gaslighting purposes.
ArjinFerman
Tinfoil Gigachad
16hr ago
Yeah, but other Republican candidates weren't necessarily better than Kamala, or were perceived as worse than Trump at winning the general election. There's tonnes of these kind of strategic concerns people have when making their choice. Everybody knows this when they're talking about their own side (why do you think the Dems picked a shambling corpse for a candidate that they later had to eject in the las minute?), but conveniently forgets it when talking about their enemies.
ArjinFerman
Tinfoil Gigachad
23hr ago
This comment is my external motivator to finish the scene.
Would you like a weekly ping like I do for Southkraut?
I got back to working on handling of the background textures, and a lot of the time was spent debugging... which with shaders is tricky. No debugger, no text output, so you're left with translating variables into something visual, and playing divide-and-conquer games with your own code. The issue was that the texture immediately under the player worked fine, and the dying bugs got rendered to it, but the ones surrounding couldn't properly calculate the relative coordinates of the bug, and in the end everything was always rendered out of bounds (i.e. not rendered). It turned out to be a stupid copy-paste error where I was using the wrong variable, but the good news is that it works now.
Now I'm trying to handle the player moving around. If you go leftward and leave the background texture immediately behind you, the textures to the right should unload, and new ones to the left should be created (and if you come back, the old textures should be reloaded). Related to this, I'm wondering how to manage memory issues. If the background textures are small, it's easy to zoom out far enough that no background is visible. If they're big they eat up quite a bit of memory (and still don't necessarily cover the whole screen). I found out it's possible to create a compressed Rendering Device texture, and that the compression is quite good on them, but these are read-only. So the current plan is to read the background texture being unloaded from the GPU, create a compressed texture from it, and keep it on the more distant background sprites. After that I might add a second layer of storage, where they get saved to the hard drive, and reloaded as needed.
How have you been doing @Southkraut?
More options
Context Copy link