Powder Toy Menus Glitching/Freezing

  • nuke-a-cola
    7th Mar 2016 Member 0 Permalink

    It was snapshot 29 for me, 14 simply refused to open, however, I'm running Mavericks, if that may make a difference.

  • jacob1
    7th Mar 2016 Developer 0 Permalink
    @nuke-a-cola (View Post)
    Right ... I don't think snapshot 14 worked at all on macs and I didn't fix it until later

    I will try compiling some versions with different flags or other settings later. So check back in 1-2 days maybe (or maybe I will do it tonight, not sure)

    @motaywo (View Post)
    Very unlikely since the game doesn't know what has been on front page. If it is a random occurrence though, it might just be confusing to notice what really causes it.
    Edited once by jacob1. Last: 7th Mar 2016
  • yoelleoy
    7th Mar 2016 Member 2 Permalink

    I can confirm that my Mac also doesnt work. Same problems as he said before

  • AutoExplode
    7th Mar 2016 Member 0 Permalink

    I also have the same problem as everyone else here. however the consle commands i put in are not saved and i am also on a mac, is this meant to happen? I am on OSX yosematie 10.10.2.

  • 22minnis22
    7th Mar 2016 Member 0 Permalink

    @jacob1 (View Post)

     Yeah, I can confirm this is a problem on OSX, working on Windows 10, but on all OSX computers I have tested, attempting to open any save using v91 additions results in the one of the following: save opener menu flickers away and game freezes; game freezes; entire game flickers and an "Unexpected program abort" bluescreen; or just straight to the "Unexpected program abort" bluescreen. Is there any way to generate a log file? If so, it may help to understand what's going on

     

    EDIT: I said v91 additions, but from testing on my desktop, it seems more specifically that any saves involving CRMC will invoke the crash

    Edited 3 times by 22minnis22. Last: 7th Mar 2016
  • motaywo
    7th Mar 2016 Member 0 Permalink

    Also, I've just noticed this: The console works fine mostly, but if you input an error (like if you type an element wrong or use an invalid property), it crashes and goes right to a "Mermory read/write error" bluescreen.

    As far as I can tell there's no screen flicker when that happens, so it might be related, or it might not.

     

    EDIT:

    @22minnis22 (View Post)

     I'm not sure - I just did a test and saved a save with chunks of crmc in it. I closed TPT and reopened it, and the save opened and loaded normally with no problems.

     

    @jacob1 (View Post)

    Okay, I've just done an experiment - It seems that saves that have recieved +1 votes crash the game, but saves that still only have the 1 default vote are fine. (It appeared that downvotes don't have a impact, but as I only tested one save with 1+ down and 0 up, it's probably just a fluke)

    Edited 2 times by motaywo. Last: 7th Mar 2016
  • jacob1
    7th Mar 2016 Developer 1 Permalink
    @motaywo (View Post)
    That is incredibly weird O_o. Thanks though, since it could be possible that that is the issue (there was a similar issue a really long time ago where saves that had no votes at all, not even the default vote, caused a crash. I guess we didn't think there were any saves like this)

    Are you getting any crash reports? I will definitely do some testing tonight (and hopefully not just play minecraft all day :P), might have to launch my laggy OS X vm.
    Edited once by jacob1. Last: 7th Mar 2016
  • Ivniinvi
    8th Mar 2016 Member 0 Permalink

    I have also been experiencing the same problem, it is forcing me to force quit powder toy and when I click a save icon, the info page starts becoming transparent in the bottom half.

  • jacob1
    8th Mar 2016 Developer 0 Permalink
    Can you all test the latest snapshot? I think I might have fixed the issue:
    http://starcatcher.us/TPT/Download/Snapshot%20mac.zip

    I didn't try narrowing it down, because it's another extremely compiler / compiler flag dependent bug. Apparently if you compile with -O3 (or O2/O1), the crash happens. None of the other optimization flags seemed to have any effect, and also the resampler code that gets run when looking at a save didn't have an effect either.

    So I just removed -O3 from the compile flags and it seemed to fix it for me.

    In the future I might try using a newer cross compiler. The one I have is really old and doesn't support C++11 or anything. It might also be time to bump the minimum required version to OS X 10.8, which would allow for more optimizations using this new cross compiler, and also fix some compile warnings, and potentially allow C++11 in the future. But for now, this temporary fix seems to work.
  • monkeyboy214
    8th Mar 2016 Member 0 Permalink

    @jacob1 (View Post)

     The new snapshot works fine. No glitches/crashes.