The Powder Toy

jacob1

@Thatreactordude (View Post)
That is strange, it happens for me too on Windows 10, but not on Linux which I usually use.

For now, I recommend turning off "Change Resolution", use fullscreen without that. The window will be slightly smaller with black bars above and below it, but at least the bug won't happen.

Personally, I never use fullscreen, I'm just so used to playing TPT with the smaller window.

DrThing

I liked the custom gravity, you can use it on the destructable city, the legendary save, do destroy anything, also a question, is heated air affected by gravity?

LBPHacker

It is.

tessarion

Does anyone know when the flatpak install will be updated for Linux? I tried downloading it directly from the site, but whenever I click on the executable, it tells me that it can't run because it's not associated with any known program. I'm running Linux Mint 20.3.

LBPHacker

We don't maintain the flatpak version. This is the repo for it, and it seems dead. As for your issue with the official executable, you'll have to set the execute bit on it and possibly launch it from a terminal. File managers seem to be bad at launching executables.

KiwiSky

@jacob1 (View Post)

Hello! Since version 97.0.352, TPT crashes whenever trying to save a world on my system. The program fully crashes as in the window closes and the process is exited. I have provided my system information and details on this crash below.

Post was too long to fit here, please use this link instead: https://pastebin.com/SzNuUQVT

jacob1

@KiwiSky (View Post)
Are you using the official download from the website, or getting it from some other source? This bug was reported last week on an unofficial AUR build of TPT, but not on the vanilla release.

If this is a self-compiled build, then make sure you are compiling with this commit applied.

Jakav

That's probably the issue I was having. Sadly though, I can't click on the link for some reason.

jacob1

@Jakav (View Post)
I probably typoed the <a href= part of the link. Fixed now.

Now I want to know, where were you having this issue? A self-compiled build? A Linux build? Someone else's build? Just curious.

Some compilers are over-eager to throw that exception, even if the code isn't doing anything wrong. The vanilla builds shouldn't do that, or else we would have realeased 97.1 already. We could do a 97.1 anyway but 97.0 has been extremely stable so far, there's only 3 commits since then and only 2 are bugfixes (the other I could call an improvement more than a bugfix)

Jakav

It was my own self compiled build (version of my mod), using MSVC I believe if that matters. Windows 10. It seems like the exact same thing.

Edit: Apparently that isn't the commit that fixed it, as I haven't synced it yet. Maybe the build number commit fixed it? Perhaps something else.

Official Game Feedback