DraStic (Nintendo DS emulator) OUT NOW for pi2/3!

lilbud

@mediamogul My stylus just stopped working, it moves, but clicking it has no effect

PokeEngineer

Try reinstalling DraStic.
For the other issue, you have to edit something in the DraStic GUI first to get the .cfg file to show up...

PokeEngineer

@lilbud

I have never experienced that issue...

Linkseo

@RetroPieNerd
Thank you. I've tried uninstall and reinstall but the cfg file is simply not there. only a drastic.cf2 file is in the config folder. weird. anyway you can share your .cfg file so I can add it to my folder?

lilbud

@RetroPieNerd It was working, but now all it does is move around

PokeEngineer

@Linkseo

If you go to the options in the DraStic GUI and edit something then save, the config file will be created.

Linkseo

@RetroPieNerd This is the problem. I get a black screen when I go into the gui by pressing M.
No sound no picture. just a black screen. I can hit esc to get back to the game but cant see the gui.
Someone else with a 4:3 monitor said they have the same black screen when going into the gui. not sure if it has something to do with our 4:3 monitor or not

backstander

@Linkseo

not sure if it has something to do with our 4:3 monitor or not

I bet it does...well it's closed source so we don't know what it's really doing.
Anyways could you plug your RPi into a 16:9 monitor and press M for the menu and save for the config file?

Or maybe someone else could post their config file to pastebin with default settings and the exact filename and location they found it in?

PokeEngineer

@Linkseo

Just tested it with my old 4:3 TV (my main display is 16:9), same issue...
I guess it has to do with not having enough room to display the GUI on 4:3 monitors...

Linkseo

@RetroPieNerd Thank you. I now know im not going crazy :)
I'll try plugging into a 16:9 monitor to create my drastic.cfg file. edit it there I guess. once its created I can always edit it through ssh. Would be nice to see the gui but until the problem is fixed, this will have to do.

jcarhat

Got a strange issue. It instalols fine, runs games fine, but when I rebooted my rpi3 and launched a game it too k me to the run command, asking me to select am emulator like last time. there was a '1' option, but drastic was not listed. instead it was blank.

launching the game like htis booted me back to ES. and reinstalling drastic didnt fix the issue. how odd.

backstander

@jcarhat
What's in your /opt/retropie/configs/nds/emulators.cfg

Mine look like this:

drastic = "pushd /opt/retropie/configs/nds/drastic; /opt/retropie/emulators/drastic/drastic %ROM%; popd"
default = "drastic"

Also when I installed DraStic, I didn't have NDS in my ES menu. I even installed lr-desmume from source thinking it would add it but it didn't so I just added it manually.

/home/pi/.emulationstation/es_systems.cfg

  <system>
    <name>nds</name>
    <fullname>Nintendo DS</fullname>
    <path>/home/pi/RetroPie/roms/nds</path>
    <extension>.nds .zip .NDS .ZIP</extension>
    <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ nds %ROM%</command>
    <platform>nds</platform>
    <theme>nds</theme>
  </system>

backstander

@Linkseo

BTW...here is my default /opt/retropie/configs/nds/drastic/config/drastic.cfg from my RPi3 for those who have a 4:3 monitor and want to created it.

Here's what a game looks like:

Also here's what the menu looks like:

jcarhat

@backstander

so i reinstalled drastic, it worked, and then i rebooted thge system and got the same error. I checked that cdg file with notepad++ and this is what I found...

ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
default = "ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ"

That cant be right...

jcarhat

@backstander

I think im just going to wait for a stable release, it hanged when booting up a game and corrupted my SD. whihc is unfortunate.

hopefully the kinks get worked out soon.

backstander

@jcarhat

That cant be right...

Yeah that's odd. Something is corrupting that file. Maybe delete that file and then make it again with my config I gave before.

I think im just going to wait for a stable release

Or that also might be a good idea. I just hope it's not corrupting other files in the process :(

jcarhat

Yeah I did just that, which is what then caused the system to hang on booting up a game.

Lucky I just made a backup of my image a day ago.

Although I have a strange issue with my backups. three of my games, always, and i mean ALWAYS end up corrupted whenever I re image from a back up. As in they dont work and I have to re-copy them onto the pi. and they are always PSX games.

maybe backing up files of that size leads itself to data loss/corruption? who knows.

backstander

@jcarhat

maybe backing up files of that size leads itself to data loss/corruption? who knows.

One question: Do you have your SD card reader overclocked on your Pi?

That can cause some weird random unstable corruption of files.

Also having a power supply that's not 5V 2A can cause this.

And last, having a knockoff generic cheap microSD card can cause this as well.

You might already know all this but I just wanted to cover all the bases.

jcarhat

All of those bases are covered, except im not too sure about the first one. I havent changed any settings related to the SD card so I think I'm safe.

It'sjust odd because the games work. I shot down the system, back up my image, current image still works fine, but when I re image the pi certain psx games dont work. so the issue I htink has to be with the way im backing up my image, but cant narrow down the problem because the process is so simple.

backstander

@jcarhat
I guess it could be the software you're using to backup your SD card or it could be the card reader you're using on your PC/Mac.

I'm use Windows for this and I've heard that it's best to first format the SD card before flashing an image on it. I use SD Card Formatter 4.0 and then after formatting I use Win32 Disk Imager to flash the image to the SD card.

Also if you have another SD card reader, maybe try that one and see if you have the same issues.

It's usually a little trial and error before we discover the culprit ;-)