Working Dreamcast games

[barbudreadmon]

@mitu Sorry, it's not in my habits to sugarcoat my words. Seeing someone who is aware of the bug trackers, aware of an issue, but won't report it, is kinda infuriating, and as far as i can see :

• saying nothing will lead to nothing being reported
• saying things gently will lead to nothing being reported (i already tried)
• saying things harshly will lead to nothing being reported

This is a dead end...

Anyway, sorry for the digression and the insult.

[mitu]

@barbudreadmon said in Working Dreamcast games:

Seeing someone who is aware of the bug trackers, aware of an issue, but won't report it, is kinda infuriating

I understand, but you're sometimes taking it too harsh (and perhaps too personally, on your projects ?). A bug is a bug, don't get mad if it's not reported - the important thing (IMHO) is that is eventually gets fixed.

Thank you.

[barbudreadmon]

@mitu said in Working Dreamcast games:

perhaps too personally, on your projects ?

Maybe, and i consider reicast as one of my projects too, even if i mostly worked on the lr-reicast fork and its naomi support.

[pjft]

Wow, am I late to the party here.

I'll update the list here this weekend, but some games I haven't seen mentioned here that I run include

Virtua Tennis
Virtua Striker (US version - I think. The PAL one is glitchy).

Though indeed both of them suffer from frame skipping, Virtua Striker the most.

I haven't tested the latest build though. Will see if I have the time.

@AndersHP regarding controllers, the only thing I find is that some games require one type of controller and can't be changed, which can be a nuisance. For instance, Ikaruga and Virtua Striker (I think?) don't react to the dpad. That being said, if you map the controls to buttons it should work the same.

[pjft]

@quicksilver and all: do you confirm that the latest Reicast build (after updating RetroPie-Setup) works for you? I'm getting a black screen all over, and glGetError 0x500 (which is equivalent to "can't allocate VRAM"), regardless of whether it's the binary or from source.

Doesn't bother me a lot (as I kept a separate copy of the old binary) but wanted to confirm. :)

Thanks!

[quicksilver]

@pjft I updated shortly after the binary was updated. I have not had the issue you describe. I wonder if something has changed since then.

[pjft]

@quicksilver Thanks. Probably it's something with my setup, which is fine.

Thanks!

[quicksilver]

Just tested Capcom vs SNK2 runs really good overall. Performance wise it feels full-speed to me (I am overclocked). Minor visual glitches when a character stands in front of the windmill background but its not that distracting.

On a side note, does anyone know how to adjust the analog sensitivity or deadzone for reicast?

[backstander]

@quicksilver

On a side note, does anyone know how to adjust the analog sensitivity or deadzone for reicast?

I'm wonder this as well. I think I'm having a slight drift to the left on my left analog stick on my Xbox 360 controller when using Reicast. The one I've been using most I got cheap from a pawn shop so I don't know what kind of abuse it has been through haha. I don't have any issues in any other emulator I've tried. I couldn't find words 'dead' or 'zone' in /home/pi/.reicast/emu.cfg.

@barbudreadmon I like to do more testing before I report a bug to verify it's not something to do with my current setup so I don't waste people's time. I also having played much Reicast in over a year but wanted to give it a go after the update. Last night I got around to playing "Skies of Arcadia" and I was having the same issue of my character moving on his own so now I think it's probably a dead zone issue and not necessarily a bug.

Deadzone Issues bug reported to Reicast devs back in May 26, 2017:
https://github.com/reicast/reicast-emulator/issues/1027

Another tread here about it:
https://retropie.org.uk/forum/topic/10583/reicast-controller-deadzone-setting

[quicksilver]

@backstander problem is that a lot of issues we have with dreamcast, n64, psp and other demanding emulators is that they are unique problems to the raspberry pi. A lot of bug reports I have seen from rpi users are either ignored or you get the shoulder shrug and told to use something else.

[barbudreadmon]

@quicksilver @backstander you should consider switching to lr-reicast, i don't think performances are far apart as long as you properly set core options, and lr-reicast is a lot more active (afaik most improvements in standalone reicast are backports from lr-reicast).

[quicksilver]

@barbudreadmon lr-reicast is not available on raspberry pi last I heard

[barbudreadmon]

@quicksilver retropie needs to update its scripts then, the author of lr-reicast is testing the core on many platforms including the rpi.

[quicksilver]

@barbudreadmon you yourself said in another thread that trying to run lr-reicast on an RPI is "crazy" because standalone reicast doesnt function well. Has something changed recently?

[barbudreadmon]

@quicksilver Maybe a long time ago when there was no arm dynarec, no threaded rendering, no frameskip, ... Or perhaps are you talking about the crazy question everyone asked, aka "The oit renderer will be available on raspberry ?".

Now that all of this is togglable in lr-reicast through core options, there is barely any reason for it to perform worse than standalone.

[quicksilver]

@barbudreadmon thank you for your explanation. Is there a way to install lr-recaist manually? I would be happy to test it's performance on my pi.

[BJRetro]

@quicksilver I would be willing to test too if easy to install lr-reicast. I have had good success with standalone and have two setups so could leave one with standalone so I could pretty easily check how different if at all lr-reicast is with whatever settings are deemed proper.

[hooperre]

This post is deleted!

[mitu]

@quicksilver Since lr-reicast is already a scriptmodule, if you're willing to give it a try, this is what you need to modify

• replace the rp_module_flags with

rp_module_flags=""

• in the build_lr-reicast function, replace the single make line with

make platform=rpi3

Try to install from source, the lr-reicast scriptmodule should be in the experimental section.

At some point, I think the lr core was requiring GLES 3, so that's why it was excluded for the Pi, but maybe I'm mistaken.

EDIT: forgot to say, you'll have to modify the $HOME/RetroPie-Setup/scripts/libretro/lr-reicast.sh file. With the modifications from before, the compilation works (GG NO RE), but I havent' got time to test it with a game.

[barbudreadmon]

Btw, here are the settings that are good for speed :

• Enable Threaded rendering
• Set Alpha sorting to per-strip
• Decrease resolution
• Disable Texture Upscaling
• Disable Modifier Volumes
• Enable Div Matching
• Disable DSP
• Increase frameskip