libretro
[Feature Request] M3U support
Like in others computer emulation cores, M3U would be a great improvement. I have a bunch of multi sided tzx games i can't use because i can't switch media at runtime.
This has been already reported at #72, i don't know why this issue has been closed seens this FR has not been adressed. That's why i create a new one here.
specifically 452.06 and above
Meaning https://github.com/libretro/flycast/issues/968 isn't the only regression from those recent nvida drivers ? Or are you maybe using vulkan with 4GB pixel buffer ? If so, using 2GB fixes this ?
Used both Vulkan and GL, set it to any of the pixel buffer settings, as well as set it to "per strip" and "per triangle" options, and the problem still occurs
Also crashing for me. Tried to use an older build from july 2020 and the problem persists. I recently updated Windows 10 to 20H2. Using latest nvidia drivers from 2020.10.7 with my Core i3-7130U, GeForce MX130 laptop.
I will check if the problem is present when trying with an Intel HD Graphics 610 laptop and a GTX950 desktop. Flycast settings set to default, RetroArch video driver set to glcore.
Also crashing for me. Tried to use an older build from july 2020 and the problem persists. I recently updated Windows 10 to 20H2. Using latest nvidia drivers from 2020.10.7 with my Core i3-7130U, GeForce MX130 laptop.
I will check if the problem is present when trying with an Intel HD Graphics 610 laptop and a GTX950 desktop. Flycast settings set default, RetroArch video driver set to glcore.
Flycast DOES NOT crash with my Intel HD Graphics 610 laptop neither my GeForce GTX950 desktop (also updated to latest 456.71 nvidia driver). All my systems are running Windows 10 20H2, RetroArch with glcore video driver, flycast at default settings.
Only crashing system is my MX130 laptop.
That's gonna be a real tough nut to crack if it only happens on certain models, my gtx960 doesn't seem to produce this crash either. We'll need some backtrace from someone with a faulty model.
nvidia seriously screwed up there...
~~Just updated the core and it's not crashing anymore after changing game!~~ Nevermind. It happened again.
Still happens with the latest Nvidia drivers, and also happens with the most recent PCSX2 core.
I also have the 3070 card with latest drivers and it's crashing. I will try to get a backtrace tomorrow.
I updated to 20caf3f, and looks like it's able to swap games without crashing at last.
Swap Dreamcast games works fine sure, but unloading Flycast is what still crashes.
Swap Dreamcast games works fine sure, but unloading Flycast is what still crashes.
Works fine here (GTX 970).
It took a while to figure out but I finally discovered that Flycast crashes upon exiting content if Retroarch's global video driver is set to Vulkan, it doesn't happen with gl/glcore. This happens regardless of whether Flycast's driver is set Vulkan or GL/GLcore. Flycast also crashed for me for having devreorder's dinput8.dll in the Retroarch root folder. Once I deleted dinput8.all and set Retroarch's driver to glcore it stopped crashing and terminated as expected.
~~While the above didn't fix it for me, updating to the latest nightly of RetroArch and Nvidia's 461.92 drivers did! Works with both GL and Vulkan as well.~~
Oh interesting, I tried voorunde suggestion, changing to glcore globally, then creating a vulkan override for the core and yeah, no crash anymore on close content. Updating to latest Nvidia drivers didn't fix it for me however.
Steps to reproduce if anyone is interested:
- No content loaded, set video driver to glcore.
- Restart RetroArch (or else the "fix" won't work properly).
- Start a DC game, change driver to vulkan and create a core override.
- Close content.
- Launch the game again, it should be using vulkan and it shouldn't crash anymore on close content.
Another fix for me was to downgrade my Nvidia drivers to 451.48 (version mentioned by Tatsuya on Discord) using the "clean install" option or whatever it's called.
Tested by running RetroArch from MinGW, because for some weird mystical reasons if I launch RA from Windows Explorer and if I get Flycast to crash a couple times it doesn't crash anymore but I'm getting a ton of weird stuff: https://github.com/libretro/RetroArch/issues/11940
Well apparently it only 'fixed' itself because Windows decided to add a register key that would prevent the core from unloading when RetroArch runs... Without it, it will crash on close content, regardless of video driver.
I updated to the latest Nvidia driver from March, 30th, latest bios (which adds Resize Bar), latest Windows update and latest RA+Core nightlies from today and the issue seems to be resolved.
I'm in Vulkan globally fyi.
Have you tried loading up another Dreamcast game after closing the first one and see if the second game behaves incorrectly? Because Windows 10 likes to sometimes add a registry key when Flycast crashes too many times, which will prevent the Flycast core .dll from unloading, which 'fixes' the crashing, but introduces a whole new list of bugs, including a second Dreamcast game not loading properly, to stuff like random crashes when trying to load another core.
Have you tried loading up another Dreamcast game after closing the first one and see if the second game behaves incorrectly? Because Windows 10 likes to sometimes add a registry key when Flycast crashes too many times, which will prevent the Flycast core .dll from unloading, which 'fixes' the crashing, but introduces a whole new list of bugs, including a second Dreamcast game not loading properly, to stuff like random crashes when trying to load another core.
Tested everything, no problem whatsoever !
Bit of a sanity check, but if you open Regedit, and navigate to [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers], do you see an entry with the data description "$IgnoreFreeLibrary<flycast_libretro.dll>"?
Bit of a sanity check, but if you open Regedit, and navigate to [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers], do you see an entry with the data description "$IgnoreFreeLibrary<flycast_libretro.dll>"?
Nothing :).
Is the bug fixed for other people ?
I started using RA on October '20 or so, and I've always had this problem, regardless of video driver, threaded rendering setting, GPU drivers for GTX 970. Haven't tried other GPUs yet. I don't have the registry entry mentioned above. I'll be trying this out on other GPUs when possible.
If I change RA to glcore and not customize the cores back to Vulkan, it works without issue for me. If I change Flycast itself back to Vulkan however, it appears to work as it doesn't crash when I close a game, but it will crash when I try to load another core's game. So it's basically the same thing, you could load different Flycast games before if you didn't try to close the current first.
Oh well, it's all good with glcore! At the moment at least. GTX1080/latest Win10/updated everything, drivers included.
No idea if one of the backports fixed it or if it's really by updating the Nvidia drivers, but I don't have the issue anymore, no crash on close content, no registry key created anymore, no weird behavior on next loads, etc.
edit: downgraded both the core and RetroArch, still no issue so I guess the Nvidia drivers fixed it indeed! Thanks for the heads up @Immersion95 Also not sure if it matters but I checked the "make a clean install" box while updating drivers.
Using latest drivers (465.89) with up to date Flycast (0.1 de6ccff) and RetroArch (1.9.1), and it still crashes on close content for me.
Using latest drivers (465.89) with up to date Flycast (0.1 de6ccff) and RetroArch (1.9.1), and it still crashes on close content for me.
Latest RA nightlies ? Maybe it's only fixed for Ampere....
Maybe it's only fixed for Ampere....
No, I'm still using a GTX 970 and it started to work properly again today after updating Nvidia drivers. @ds22x have you checked the "clean installation" during drivers update? Like I said I checked it, but it could be completely unrelated... worth the shot I guess?
Could be something else tho, like a Windows update? 🤷
Checked latest nightly, still crashes. Did clean install those latest drivers after first reverting back to default, still no dice. Still using a GTX 1650 and running W10 20H2.
So weird, in my case it's clearly the drivers that fixed it, I just downgraded to 461.92 and the crashes are back, re-installed the newest 465.89 and no crash or anything weird anymore.
I also noticed there was a Geforce Experience update, are you using it? Is it up-to-date (3.22.0.32)?
And while typing this I just got a notification saying a new version for the drivers (466.11) is available :p