You are not logged in.
Pages: 1
I've been using v0.9.11 of Desmume on my Mac OS Sierra, but I've noticed whenever I alter the Desume Window size and close the application; when I reopen Desmume, the application window is back to the default size rather then staying at the size I stretched it too last time. On my older Desmume on my older mac, the application remembers the previous window size when I re-open the program.
Similarly when I load a new rom from the menu, the Desmume application is always on pause by default, resulting in me having to press the execute button to unpause the program. On older versions, it was on "execute" by default the moment a rom was loaded.
Is this a mac issue with the latest version or is there something in the preferences menu I am missing? If its the former, which version of Desmume do you recommend I use?
Offline
there are many newer mac builds on our download page, look harder
Offline
there are many newer mac builds on our download page, look harder
According to the downloads page, the only builds after v0.9.11, are the Official Nightly Builds, which it says use at your own risk.
Offline
I'm using the latest development build and it won't acknowledge my .DSV(save files) and .DCT(cheat files) files that I put in the application support folder for Desmume in the folder .9.12.
Offline
take them out of that folder. boot the game in the new desmume. start a new game and then close it. did desmume put any .dsv files in the application support folder? if not, then you have your answer: that's not the right folder
Offline
take them out of that folder. boot the game in the new desmume. start a new game and then close it. did desmume put any .dsv files in the application support folder? if not, then you have your answer: that's not the right folder
Just had the chance to do that this weekend, I deleted the old v0.9.12 and loaded it up again, it created another v0.9.11 folder in my application support. However this time, I ignored the migration assistant and put the files in manually, it worked.
Notably the same files were put in the old v0.9.12 support folder, how odd?
Offline
I really have no comment except to scoff at artificial intelligent "migration assistant". You think some programmer at mac HQ gives enough shits about something that isn't for sale in the app store to fix their automagic not to break it?
Offline
Pages: 1