How are you guys adjusting your shader settings for this core? When I bring up the F1 menu, I have a black screen and I can’t see adjustments that I’m making. Is there a trick to it?
Aside from that… I wanted to say that I’ve been playing it for a couple days and it is very rock solid. Compared to where it was at just a few months ago when we first saw it, it has made some really great progress. The retroarch guys have done a really awesome job on this core. Thanks, guys. 
What i need to know is, am i the only person who has noticed frame pacing issues with PAL games in this new core? So far nobody else has confirmed this.
The old core supported VRR and the 50fps PAL games were smooth. This one doesn’t.
things like framerate issues are often very subtile, and PAL and VRR is not that common i guess.
Why not just output 50 Hz as the original Hardware would do?
Because i don’t want to manually change the refresh rate of my monitor every time i want to play these games. There isn’t a 50hz option either way.
It’s the VRR’s job to keep games run smoothly and in every other core it works, except this one. Plus, the old PS2 core was also working fine, which makes it feel like a regression to my eyes.
It would be enough for me if someone else acknowledge/confirm the issue. Because if there’s only one person having this then it will never get fixed.
Sadly my system does not support vrr. Otherwise i would Look for it
I was going to check into it and then realized I don’t have a single PAL PS2 game.
Having some problems with Tomb Raider Anniversary. It’s like this in game as well. Changing the video renderer doesn’t fix it, software rendrer activly crashes the core. Only the Tomb Raider games are affected so far. I’m on a 7000 series AMD GPU with internal graphic.
[edit] Why is the default for memcard saves the System folder and not the Saves folder?
Just started using LRPS2 instead of my standalone PCSX2, and every time I take a screenshot, it shows up black. Have you ever found a fix for this?
this is normal, unfortunately. You’ll need to use an external screenshot utility.
@George.Spiggott we haven’t gotten saves fully ironed out yet. Once it’s squared away, we hope to have it use the normal srm save mechanism. Re: Tomb Raider, I don’t have that game, but if it’s doing it with all of the renderers, there’s probably something wrong internally. Does it do it with all default core options (probably easiest to just move/rename your *.opt file so it creates a new one with default values)?
Unfortunately on my system LRPS2 is not really usable so I’m back with the stand-alone pcsx2. I will keep an eye on it and try “my luck” every once in a while…
hunterk, are the screenshots just borked until further improvements come or there’s no way they could ever display right, like other cores?
I just want to confirm that the game Tomb Raider: Anniversary works fine on my system (on a dedicated AMD GPU using praLLEl-GS renderer). So its not a problem with the game itself. Maybe the Rom image is broken or maybe it has something to do with the Bios file? And sadly its true the screenshot is black for me too. But it was working with the old core version.
I’m sure it’s fixable but nobody’s actively working to track it down, so no ETA.
Deleted the .opt and all the cache files, opened the core with GLcore (it wouldn’t open under Vulcan) then reopened the core under Vulcan. All works fine now, thanks.
I’m going to try importing my saves from PCSX2 now, they look to be in the same format.
[edit] Yep they work fine.
Hunter, is this the same issue as the screen being black while paused/editing shader parameters?
I don’t know if it’s the same, but it’s probably at least abstractly related.
I’m using LRPS2 as my default emulator now though I’m still using standalone RPCS2 for games that don’t work well with it.
So far I have come across.
Soul Calibur II - slow compared to standalone. Soul Calibur III - slow compared to standalone. Global Defence Force - transparency issue (bridge on level 1).
I guess not worth to file bug reports related to natvie internal resolution either for the time being? E.g. 240/288p isn’t correctly recognized. Although, for some reason the software renderer does render scanlines on non-interlaced low res, but the internal res in the RA scaling settings doesn’t reflect it.
hmm, i think you could file an issue about it, sure. Worst thing that could happen is someone closes it (which we don’t usually do anyway, hence >2k open issues for RetroArch).
