Wutex

I have the same problem, if I use the DS4 controller without DS4windows, it works perfectly inside Retroarch. However, if I use DS4windows to make the controller work in Launchbox, only the "X360 controller" created by DS4windows works inside Retroarch, the dinput "DS4 controller" mapped as controller X1 is nonfunctional.

I am always using isocompressor to convert files to cso. Are you sure that from Russia with loves works uncompressed abut not in gz format? I do not see that phenomenon with any of my games. And yes, the delay during the first time start of a gz file is due to the creation of the tmp file, which from then on works as an index to speed up file access as far as I understand.

Those should be CD images of the smaller PS2 Games. Those you can compress to CSO instead, Gzip will not work (as far as I understand).

Hi ZomBeaver, your shader collection blows my mind. But is there an easy way to reduce/remove the vignetting? I can't find it on the shader parameters.

I compressed my whole PS2 collection using that method and all games work. Once the index file is initially created, there is no startup delay at all.

I have the same problem, especially if "update metadata " is unchecked. If I manually check single games for metadata, it's there.

Sorry for the confusion, I did not mean the new version fixes the problem you are currently dealing with. It's just that somebody mentioned that launching games directly using the execuable and the UUID would only work on developer versions, not on stable builds.

Is everybody still using version 2.7.16dev? I switched to 2.8, works flawlessly with the UUID when started directly with the fs-uae-launcher.exe in the programs/windows/x86-64 subfolder.

I confirm that the text in brackets is now ignored when importing with today's beta, thanks Jason!

"preload" is a WHDload argument you can set in the launcher, but not in command line. It preloads the whole disk/image so there is no graphic disruption during disc accesses. For example the Thalion logo won't flicker when loading Lionheart.

I just converted mine to zip and tried it, too. Mabye you hadn't scanned your file database in the launcher before and that was the problem?

My zips contained the Lha files when I optained them. Inside the Lha they have the same Amiga file structure as your zips. So extracting the zips to folder and then compress them to Lha kinda works, but a few games will fail. I suggest you try it out with one file. Just make sure it looks identical inside the lha to your zip (info file in root). Then test if you can start the file from the fs-uae-launcher gui.

Seems like you have a different ROM-set. Mine consists of the original Amiga WHD images in lha archives, yours is in zip format with the amiga file structure. I once tried to convert the zips to lha, but that doesn't work well because some of the files cannot be transferred perfectly (amiga file system vs. windows) At that time I gave up and searched for the lha romset...

Yes, flawless with WHDLoad lha files. If the roms work in the GUI of the launcher, they should work with your program, since it only points to the database entry, not the actual rom file.

I extracted all WHDloads zips, there is less than 1% compression advantage over the lha archives that are in the zips. I that not an option for you @Zombeaver?