You are not logged in.
renegade is a romhack. we dont support romhacks. romhacks break games. using savestates increases the opportunity for the game's internal state to get broken. you're screwed. next time save in-game and make plenty of backups
I got as far as moving the player around.
A. your rom is hacked or modified (or corrupted)
or B. you have changed desmume options. Delete the ini file (or otherwise nuke all your files) and try again without changing anything and losing track of it
Of course you may also have problems if youre using a 10 years old version of desmume, but I doubt it.
OK, I guess that's a feeble adjustment.
thanks!!!!!!!!
most likely you have a broken dsv (save) or dct (cheat) file, then. that would get fixed by nuking all your files (make backups first) and rebuilding your emulation environment from scratch
try running other games to collect data, or change config > display method, or delete all your files and start over from scratch (since you're using a hacked rom or have broken lingering cheat or save files [possibly hacked])
so what did you change? did you update desmume? did you change your GPU or drivers? did you change your security software? did you move your files around?
what is the actual problem with the ".desktop" file?
use time machine to recover an older .dsv file
delete your ini file
I mean your windows username. The battery directory doesn't exist because it can't be created. Test the code this way:
1. https://github.com/TASEmulators/desmume … ld_win.yml
2. search for the commit I said would fix it and click it
3. download the artifact which should be linked at the bottom
your username has non-english characters in it, therefore the path the desktop (and the desmume directory and the battery subdirectory) has non-english characters in it, therefore despite 100s of bugs filed and fixed about things like this in desmume, there are still more problems. don't use a username with a non-english character in it (don't use spaces either) and you can avoid a lot of problems with this software and many others.
should be fixed in https://github.com/TASEmulators/desmume … bce32e63dc but only someone unwise enough to use a username with a non-english character in it can test it for sure
I just successfully cleaned a triceratops. what's the problem?
The game freezes, like many others, if you enable the jit and then change the jit size, despite all the warnings near it
just quit doing that
how long does it take to get to a fossil cleaning part? I gave up after I got to the town. can you post a .dsv file?
how did you "put the emulator on 100% volume"
I have no idea why. Nothing changed the fundamental problem which was needing to rejit too much every time the program is written to by the cheat. I am suspicious and worried that something's gone wrong and the cheat processing has broken.
You didn't install desmume. You don't need to uninstall it. You simply dearchived the files. Delete the files.
hope interest from developers will regularly arrive, like old times
ini file [General] BackupSavestateSuppress=1
because the nightly version is built with clang, probably.
I don't care if nobody likes it.
no, there's no help for you. use in-game saves and make many backups.
this is discord's problem, not ours, but you should change config > display method since it will probably be less likely to agitate discord's crusty code
weird. i have almost no explanation for why that would be. but if it happens again can you please note which paths are written in the desmume.ini file? a discrepancy between those and where the files actually are might explain something
I dunno man, make backups of your settings before you mess them up. This happens to lots of people but we have no idea how. They're all hacking or cheating or changing something around. It's also possible you didn't change anything but your save file is corrupted due to computer malfunction or closing desmume while it was in the middle of saving; you should be making backups of your .dsv if it's precious to you, like you should make a backup of any precious file. It's also possible you've been hacking the rom and trying to load the old save file and you've just struck out by creating a hacked rom that creates save files that no other hacked roms can read. We can't guarantee what will happen if you hack roms and try to load data other rom versions created, but white screens at bootup are a likely outcome.