Working Dreamcast games
-
@backstander You understand that emulators are generally coded by 1-3 persons in their spare time, and that there is no way they would have time to test all games on the platform by themselves ? So when you find a bug, don't be stupid, report it on their bug tracker...
-
@barbudreadmon Wow thats a pretty harsh reply. You make it sound like @backstander was being ungrateful or entitled and I didnt get that at all from what he said.
-
@quicksilver said in Working Dreamcast games:
@barbudreadmon Wow thats a pretty harsh reply. You make it sound like @backstander was being ungrateful or entitled and I didnt get that at all from what he said.
No, i just don't understand why there is no trace of this issue on github (i checked both reicast and lr-reicast) while @backstander apparently found this issue some time ago already. That's not how this issue will get solved, and as an author of those projects it is kinda infuriating to see issues reported on the retropie forum instead of the rightful place.
-
@barbudreadmon Some users don't use Github or even know there's such a thing - they use RetroPie (or other frontend/image) and that's it. I think you overreacted - as @quicksilver said - and calling your users 'stupid' is not the way to encourage them to add proper bug reports on the project's page.
-
@mitu said in Working Dreamcast games:
@barbudreadmon Some users don't use Github or even know there's such a thing - they use RetroPie (or other frontend/image) and that's it. I think you overreacted - as @quicksilver said - and calling your users 'stupid' is not the way to encourage them to add proper bug reports on the project's page.
Maybe "stupid" was too much, however i'm right, there is no way a bug will get solved if the author is unaware of it.
Also, let me be clear, @backstander is not someone who is unaware of github, or the fact that emulators have their own repository (i checked his history before my harsh comment), so your statement doesn't apply here.
11 hours after my harsh comment, i see people tagged me as a bully for saying the truth, but still no report on github... -
@barbudreadmon said in Working Dreamcast games:
Maybe "stupid" was too much, however i'm right, there is no way a bug will get solved if the author is unaware of it.
Nobody is disputing that .
Also, let me be clear, @backstander is not someone who is unaware of github, or the fact that emulators have their own repository (i checked his history before my harsh comment), so your statement doesn't apply here.
I also checked his profile, since he's a longtime user, but that doesn't excuse your insult.
11 hours after my harsh comment, i see people tagged me as a bully for saying the truth, but still no report on github...
No, they tagged you as bully because of you insulting a forum user, not because for saying the 'truth', and that includes me. As I said, if you want to encourage people to report problems - here or directly on the project's Github page - you might consider not insulting them first.
-
@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.
-
@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.
-
@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.
-
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.
-
@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!
-
@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.
-
@quicksilver Thanks. Probably it's something with my setup, which is fine.
Thanks!
-
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?
-
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/1027Another tread here about it:
https://retropie.org.uk/forum/topic/10583/reicast-controller-deadzone-setting -
@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.
-
@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).
-
@barbudreadmon lr-reicast is not available on raspberry pi last I heard
-
@quicksilver retropie needs to update its scripts then, the author of lr-reicast is testing the core on many platforms including the rpi.
-
@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?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.