2017-07-27, 03:35
Thank you so much! I'll check your appointment. And sorry for Google's English.
(2017-07-31, 18:21)SimonC Wrote: First, huge thanks to Zach for creating such an excellent addon!
Small problem. When I originally setup everything I just used the default download path, "\addon_data\plugin.program.iarl\temp_iarl". Today I went and changed it but for some reason my favorites (named "- Favorites") does not use the new path. In fact, looking at it's XML file it clearly has the new path in place but continues to download to the default. The other (non-favorite) listings are correctly using the new path. Maybe a bug?
I am perfectly OK with just re-creating a new favorites (assuming this will fix the issue) but there does not seem to be a method to actually delete a favorite. Is the best method to simply delete it's XML file?
Thanks again for such a great addon!
(2017-08-01, 16:07)SimonC Wrote: Ran into another interesting snag.
I originally setup the video driver in Retroarch for OpenGL, which worked fine, until I setup the PS1. The PS1 core I am using is beetle hw. This core is not compatible with OpenGL, so I thought I could use the "Save Core Overrides" in Retroarch. This however does not override the video driver. I ended up changing my default video driver from OpenGL the vulkan driver. Everything works fine until I tried loading Dreamcast games. I am using the Redream core, which does not work with the vulkan display driver.
Is there a way to work around this issue with cores requiring particular video drivers? I looked at external_command_database.xml to see if I could use -C "new configuration file" switch in Retroarch but did not find a launch command for the redream core. Of course the drawback of going down this road is any updates pushed I will have to keep editing the XML file. Any suggestions?
(2017-08-01, 17:04)zachmorris Wrote:(2017-08-01, 16:07)SimonC Wrote: Ran into another interesting snag.
I originally setup the video driver in Retroarch for OpenGL, which worked fine, until I setup the PS1. The PS1 core I am using is beetle hw. This core is not compatible with OpenGL, so I thought I could use the "Save Core Overrides" in Retroarch. This however does not override the video driver. I ended up changing my default video driver from OpenGL the vulkan driver. Everything works fine until I tried loading Dreamcast games. I am using the Redream core, which does not work with the vulkan display driver.
Is there a way to work around this issue with cores requiring particular video drivers? I looked at external_command_database.xml to see if I could use -C "new configuration file" switch in Retroarch but did not find a launch command for the redream core. Of course the drawback of going down this road is any updates pushed I will have to keep editing the XML file. Any suggestions?
I have this same exact issue with my setup. For PS1 I use the HW core and have a config file specifically to load the vulkan driver. I've just used the Manually Entered Command Line to add the -c argument, copying the rest of the standard command.
Anytime the XML is updated the settings will have to be updated. The only saving grace here is I don't expect most of these to change much (except for maybe MAME, which has an ever changing romset), the user has the option of not updating if they dont want to, and settings changes really only take a minute to update.
I'm always up for suggestions on how to make it better though!
(2017-08-01, 19:53)SimonC Wrote: Here is a copy of what I tried, did not work:
"%APP_PATH%\retroarch.exe" -L "%APP_PATH%\cores\remednafen_psx_hw_libretro.dll" -c "%APP_PATH%\retroarch_vulcan.cfg" "%ROM_PATH%"
Not sure if its the use of "" or the placement of the -c switch.
(2017-08-02, 00:01)zachmorris Wrote:(2017-08-01, 19:53)SimonC Wrote: Here is a copy of what I tried, did not work:
"%APP_PATH%\retroarch.exe" -L "%APP_PATH%\cores\remednafen_psx_hw_libretro.dll" -c "%APP_PATH%\retroarch_vulcan.cfg" "%ROM_PATH%"
Not sure if its the use of "" or the placement of the -c switch.
I'm not at my gaming computer right now, but I recall it took a while to figure out. I recall the original issue I had was that save config on quit was set, so it always reverted to the last setting. I think your append config needs to turn that off.
See here: https://forums.libretro.com/t/different-...ore/9617/9
(2017-08-02, 00:14)SimonC Wrote:(2017-08-02, 00:01)zachmorris Wrote:(2017-08-01, 19:53)SimonC Wrote: Here is a copy of what I tried, did not work:
"%APP_PATH%\retroarch.exe" -L "%APP_PATH%\cores\remednafen_psx_hw_libretro.dll" -c "%APP_PATH%\retroarch_vulcan.cfg" "%ROM_PATH%"
Not sure if its the use of "" or the placement of the -c switch.
I'm not at my gaming computer right now, but I recall it took a while to figure out. I recall the original issue I had was that save config on quit was set, so it always reverted to the last setting. I think your append config needs to turn that off.
See here: https://forums.libretro.com/t/different-...ore/9617/9
In my retroarch_vulcan.cfg, it's already turned off. I don't even get to a point where RA even loads.
If your running on a Windows system, did you need to setup environment vars? I am assuming that IARL is handling the usage of APP_PATH and ROM_PATH.
(2017-08-02, 00:44)zachmorris Wrote:(2017-08-02, 00:14)SimonC Wrote:(2017-08-02, 00:01)zachmorris Wrote: I'm not at my gaming computer right now, but I recall it took a while to figure out. I recall the original issue I had was that save config on quit was set, so it always reverted to the last setting. I think your append config needs to turn that off.
See here: https://forums.libretro.com/t/different-...ore/9617/9
In my retroarch_vulcan.cfg, it's already turned off. I don't even get to a point where RA even loads.
If your running on a Windows system, did you need to setup environment vars? I am assuming that IARL is handling the usage of APP_PATH and ROM_PATH.
I'm on LibreElec, but I don't think that should matter. The usage of APP_PATH and ROM_PATH should work just fine. If you turn on debug log you can search the log after trying for "IARL: External launch command" and see what command IARL is sending to actually launch the game. This is the same command you could just paste into a cmd prompt, so you can try it directly from the cmd prompt as well (and even add --verbose to the end of the command to get more info from retroarch.exe) to see where the potential issue lies.