ekianjo
Hardcore Member
That's mentioned in the README for Drastic too...You need the three firmware files put into the appdata/Drastic/system directory.
That's mentioned in the README for Drastic too...You need the three firmware files put into the appdata/Drastic/system directory.
I was under the impression that I didn't need any additional files.Q: Why does DraStic need BIOS files? Other DS emulators don't need them.
A: It doesn't as of version 2.1.3p, since it comes bundled with alternatives.
This isn't high level emulation but BIOS replacements written by us. But if
the Nintendo BIOS files are present they will still be used. Please let us
know if you find a compatability problem that requires them, so we can fix
our BIOS.
The firmware is also no longer strictly necessary as of version 2.1.0p,
but if you have problems you can still use one downloaded from a real DS.
You can use this homebrew program to dump the BIOS and firmware files if you
have a flash cart:
http://library.dev-scene.com/index.php?dir=DS/Hardware(Firmware) 07/DSBF dump/
Note that as of version 2.1.0p your settings will always be taken from the
emulator's internal firmware settings and not from the firmware. I might
release a program to convert DS firmware settings to DraStic's configuration
file if there's a lot of demand.
Note:I was under the impression that I didn't need any additional files.
My guess is some games do not play well without the official bios.The firmware is also no longer strictly necessary as of version 2.1.0p, but if you have problems you can still use one downloaded from a real DS.
I have no idea what that means, but it looks like an error of some sort.auplinklink.c:223: AUFS_CTL_PLINK_MAINT: Inappropriate ioctl for device
Very rarely at best. That's not the problem. Something else must be wrong. That IOCTL error probably isn't a hint either, it happens after the emulator returns.My guess is some games do not play well without the official bios.
It's an error to do with the way PNDs are mounted - it seems to happen sometimes on most PNDs, but it doesn't seem to be the harbinger of any sort of doom.I have no idea what that means, but it looks like an error of some sort.auplinklink.c:223: AUFS_CTL_PLINK_MAINT: Inappropriate ioctl for device
It's also not supposed to happen on latest firmware though (doesn't happen for me).It's an error to do with the way PNDs are mounted - it seems to happen sometimes on most PNDs, but it doesn't seem to be the harbinger of any sort of doom.I have no idea what that means, but it looks like an error of some sort.auplinklink.c:223: AUFS_CTL_PLINK_MAINT: Inappropriate ioctl for device
Yes.@Exophase:
Did you read the Nintendo Ds Documentation from the maker of No$GBA? Its very detailed: http://problemkaputt.de/gbatek.htm
maybe within a few weeks.
Rotated output is possible still, maybe. notaz told me how to do it, but I haven't really looked at the impact. It's probably not that bad.
I'm not a big fan of having a vertical mode with a gap because the screens are already so tiny in vertical orientation even when scaled up to fill Pandora's screen. But I'll consider it. I doubt I'll ever support scaling to below the actual DS resolution, that'd be pretty miserable. But DS height is 192 pixels, so unscaled there's still up to 96 pixels of gap (480 - 384, an entire 50% screen height). Looking at my DS Lite, the gap is about 2.2 cm in the fully extended position, which is about 47% of the screen size. So there's just barely enough pixels to approximate that if you can accept the very tiniest screen size w/o downscaling.
I know there hasn't been an update in quite a while (a lot of the stuff Lordus and I work on doesn't really apply to the Pandora version) but it's probably a good time for one soon.. maybe within a few weeks.
IF we get good OpenGL ES support on Pyra with low overhead I think we'd like to just do a free-form layout editor w/shader support like on the Android version. But that's a pretty huge if right now. I'm honestly not really sure what our options will be on Pyra.
I just found a strange behaviour with Drastic 2.3 and latest SZ. When playing Chrono Trigger i noticed a sudden drop of frames (it was after about 10 mins of gameplay). This happened both with frameskip set to none and auto 4 with my Rebirth Pandora clocked to 800 Mhz. Looks like Drastic is skipping frames even if it is told to not, maybe broken vsync? I also tested other games (Contra 4, Mario and Luigi PIT) and the same issue occured so definitely not a Chrono Trigger only related problem.