lr-duckstation - Experimental new PlayStation 1 emulator
-
-
@iga said in lr-duckstation - Experimental new PlayStation 1 emulator:
@dankcushions
/opt/retropie/configs/all/retroarch.cfg
/opt/retropie/configs/psx/retroarch.cfgbingo. both of these are non-default, which tells me you've adjusted retroarch settings in the menu, and saved, and now are running sub-optimal settings. for example
audio_driver = "alsa"is a (much) slower audio driver than the current retroarch default, which is
alsathread, which it will default to unless you override it in your config, which you have done.i suggest you reset to defaults:
- navigate to
/opt/retropie/configs/all/and check if you have anretroarch.cfg.rp-distfile. if so, delete (or rename)retroarch.cfgand renameretroarch.cfg.rp-disttoretroarch.cfg - repeat in
/opt/retropie/configs/psx/
- navigate to
-
@dankcushions said in lr-duckstation - Experimental new PlayStation 1 emulator:
audio_driver = "alsa"
-I've already tested with alsathread too - same effect!
And i am sure - i don't changed audio driver by myself - alsa was default after retropie installing...
Ok, i will try to rename current configurations cfg.rp-dist and try again
-
@iga said in lr-duckstation - Experimental new PlayStation 1 emulator:
And i am sure - i don't changed audio driver by myself - alsa was default after retropie installing...
correct, i didn’t say you did, and you’re right it was defaulting to alsa in earlier versions of retroarch, and then changed to alsathread in later ones.
the point is, by going into the RGUI and adjusting any settings, and then saving that config, you make ALL the current retroarch settings permanent, so any changes to the defaults by retropie or retroarch would have no affect. you’re now the owner of the retroarch settings and are basically running your own retropie spin-off.
for this reason i would not recommend changing retroarch settings via the RGUI and instead use https://retropie.org.uk/docs/Configuration-Editor/ - this only inserts the single setting you change to the config rather than setting EVERYTHING.
-
@dankcushions good to know, i never used the Configuration-Editor and made all changes via RGUI over the years :/
So i am running also my own retropie spin-off, i guess i will start to create a new setup in the future (Pi5) .Good luck: i never had problems.
I also had to change to ALSATHREAD by myself (did that in RGUI as well), but everything works great.
I also tested "NFS IV: High Stakes" yesterday evening and played a couple of rounds on "Landstrasse". No problems at all. -
@dankcushions said in lr-duckstation - Experimental new PlayStation 1 emulator:
correct, i didn’t say you did, and you’re right it was defaulting to alsa in earlier versions of retroarch, and then changed to alsathread in later ones.
well... i firstly download retropie in January-February of this year - it was 4.7.1, and then immediately did update - so, i ve supposed that use latest current version...
And i don't changed in retropie-setup gui anything else by my own, I've make changes in game process in retroarch -> quick menu->options or controls. In first "settings" retroarch menu i am only make visible fps in left corner and applied it to all cores. That's all....
-
@iga said in lr-duckstation - Experimental new PlayStation 1 emulator:
@dankcushions said in lr-duckstation - Experimental new PlayStation 1 emulator:
correct, i didn’t say you did, and you’re right it was defaulting to alsa in earlier versions of retroarch, and then changed to alsathread in later ones.
well... i firstly download retropie in January-February of this year - it was 4.7.1, and then immediately did update - so, i ve supposed that use latest current version...
the alsathread change didn’t happen until June-ish
And i don't changed in retropie-setup gui anything else by my own, I've make changes in game process in retroarch -> quick menu->options or controls. In first "settings" retroarch menu i am only make visible fps in left corner and applied it to all cores. That's all....
that’s enough to do it. any settings change via RGUI where you need to make a config save creates the massive config files you have, and stops you getting any updates to the defaults.
-
@dankcushions said in lr-duckstation - Experimental new PlayStation 1 emulator:
and stops you getting any updates to the defaults.
what kind are the updates? - on the site in download section is still same 4.7.1 from November 4, 2020. And maybe we could see changelog...
Аnd how to make updates now? - format and reinstall?
On the other hand, (after formattng )apply all my own personal settings again (which I maybe even could not remember) is too hard\lazy to make nfs work.... ((
-
@iga said in lr-duckstation - Experimental new PlayStation 1 emulator:
@dankcushions said in lr-duckstation - Experimental new PlayStation 1 emulator:
and stops you getting any updates to the defaults.
what kind are the updates? - on the site in download section is still same 4.7.1 from November 4, 2020. And maybe we could see changelog...
config default updates. i suppose following retroarch and retropie on github would show you the changes, but they’re amongst a lot of other things.
Аnd how to make updates now? - format and reinstall?
i already told you how to reset the config to latest defaults.
-
@dankcushions Ok, thank you!
But by this logic, after next any changes ( change key mapping or increase sound volume for example) you will lost ability to next updtes?
-
@iga said in lr-duckstation - Experimental new PlayStation 1 emulator:
@dankcushions Ok, thank you!
But by this logic, after next any changes ( change key mapping or increase sound volume for example) you will lost ability to next updtes?
my advice above was to use the configuration editor for such changes, but it is less user friendly. to be honest, i have never needed to increase sound volume - just raise the master volume in ES. key mapping shouldn't need a config save via core input remapping, which is a seperate file and doesn't cause these issues.
-
@dankcushions It's all sadly, cause have ability to change some settings for your own needs and don't do it it's ... hmm 50\50... don't know :-/
in addition to turning on the fps counter, which I definitely use to understand if it works correctly, I like to use a rewind that is also turned off by default and this will already make a change in the original config. Also, some emulators may have bilinear filtering enabled by default or some other filters, disabling which will again lead to changes in the config. And I'm silent about all sorts of tweaks for n64 cores.
.... so i suppose that have access to options could be very useful, but in general, I understood the whole idea, so thanks again! -
@iga i am quite unsure too, i doubt that everything i do via RGUI would be possible to manage via the configuration-editor.
Here is a summary of my must-have-changes via RGUI:- enable analog axis on controller P1 & P2
- setup Retroachievements, change to "Hardcore Mode"
- lr-flycast: enable access to NAOMI/Atomiswave service-menu
- lr-duckstation: change memorycard-saving to *.srm
- change audiodriver from "ALSA" to "ALSATHREAD" in all lr-emulators
Can i do all these changes via configuration-editor?
-
@sirhenrythe5th said in lr-duckstation - Experimental new PlayStation 1 emulator:
@iga i am quite unsure too, i doubt that everything i do via RGUI would be possible to manage via the configuration-editor.
since it allows the text editing of the config file, yes effectively everything can be done by configuration editor
Here is a summary of my must-have-changes via RGUI:
- enable analog axis on controller P1 & P2
what option specifically?
- setup Retroachievements, change to "Hardcore Mode"
yes
- lr-flycast: enable access to NAOMI/Atomiswave service-menu
- lr-duckstation: change memorycard-saving to *.srm
these are both core options - nothing to do with retroarch settings.
- change audiodriver from "ALSA" to "ALSATHREAD" in all lr-emulators
as discussed in the OP, this is the retroarch default for pi4 now. no need to set it if you're using retroarch 1.9.5 or later. the only reason people need to set it manually is if they're running non-default config settings files...
we are now wildy off-topic. i don't want to turn this into a general retroarch support thread
-
I read the topic about F1 2000 game, and i try to test again F1 2000, F1 2001, F1 Arcade and now they are working fine.
These games wasn't working properly with the previous version of lr-duckstation and lr-pcsx-rearmed.
-
Love that duckstation updates.
Ran into some issues playing Xenogears. If there is a better place to capture these issues, let me know.
GAME: Xenogears
VERSIONS TRIED: SLUS00664 (ISO), US-PBP, Undub 2.0 (PBP)
HARDWARE: PI4 8GB r1.4, VL805
Settings: Defaults, no cheats, no shaders
ISSUES:- Freezing when using fast forward and attempting to open a chest
- Freezing/crashing during last dialogue box before leaving the blackmoon forest
NOTES: Tried playing around with video settings to lower the resolution; adjusted read and write speed settings; made sure alsathread settings were selected -- Nothing fixed either of the issues above.
Latest version of pcsx-rearmed doesn't encounter these issues so it doesn't appear to be a problem with the rooms.
-
If you can, share the save file/state so i can try it, thanks
Without the fast forward the game crashing? -
@fd I've played xenogears up to the point of reaching the town of nisan but haven't touched it since then because tales of arise got me hooked. I've never encountered any crashes since I've played it from the start up to the point that I've stopped, so probably the fast forwarding might be causing the crashes. I also have the xenogears 2.0 but in chd.
-
I can't remember if duckstation save states are captured in the same .state file that pcsx-rearmed uses or if they are stored in the ldci file. I have linked to both below:
Thanks.
*Also, I have tried playing through the same section in blackmoon forest without fast-forward. No luck. (Not using fast-forward when opening a chest does seem to work though)
-
Are you able to combine discs into a single chd file(ala pbp) or are you selecting a disc at a time?
Also, I want to say that I saw similar PBP crashes at similar times on PSP and it required a specific popstation version. So maybe the issues are tied to using PBP files.
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.