Black screen when loading game since June 18, 2022 update

[stap]

Every time I start updated PSX Core, BIOS is loaded as usual.
When loading any game, I just got a black screen no matter which game I load. No BIOS is loaded, just a message "Region Unknown->US" and black screen.

The previous version core (May 11, 2022 release) works just fine for all games.

Other testings update:

• The same behaviour is on yesterday unstable nigtly build (PSX_unstable_20220619_083a66.rbf).

• The unstable nigtly build of today (PSX_unstable_20220620_14bd4a.rbf) messes up the core settings on switching any of the toggles and also shows black screen on loading any game.

[stap]

Core settngs (resetting to default won't solve the issuse)

Cheats Enabled: No
Automount Memory Card 1: Yes
Autosave: On
Savestates to SDCard: On
System Type: Auto (Switching to US won't solve the issue)
Pad1: Dualshock
Pad2: Dualshock
Multitap: Off
FPS Overlay: Off
Error Overlay: On
CD Slow Overlay: Off

Apsect Ratio: Original
Scale: V-Integer
Fixed HBlank: On
Fixed VBlank: Off
Dithering: On
Deinterlacing: Bob (Switching to Weave won't solve the issue)
Sync 480i for HDMI: On
Rotate: Off
Widescreen Hack: Off
Texture Filter: Off
Stereo Mix: None

Fastboot: Off
CD Lid: Closed
CD Fast Seek: Off
Data Cache(CheatsOff): Off
Pause when OSD open: On (Switching to OFF won't solve the issue)
Pause when HPS busy: On (Switching to OFF won't solve the issue)

MiSTer.ini video settings:
video_mode=8
vsync_adjust=1 (switching to 0 won't solve the issue)

Using HDMI at 1920x1080@60Hz.

[jca]

What about your BIOSes?

[stap]

Using BIOS v.4.5 for US region and default ones for EU/JP regions (which are downloaded via "bios_updater" included in "update_all" script).
Tried removing those and downloading the default one for US region games. Sadly, no effect.

[jca]

On my system I installed the BIOSes manually before the update script had these so I cannot comment about that but make sure that you installed them correctly.
This is what the readme says:
Rename your playstation bios file (e.g. scph-1001.bin/ps-22a.bin ) and place it in the ./games/PSX/ folder.

boot.rom => US BIOS
boot1.rom => JP BIOS
boot2.rom => EU BIOS

You can also place a cd_bios.rom in the same directory as the CD or 1 directory above, to have it uses together with that CD. This can be used for games that depend on a special BIOS beyond usual US,EU,JP.

If you get a black screen with "ED" overlay in upper left corner, either your BIOS files are corrupt or missing or you have no SDRAM module installed.

[Maxriptide]

I have the same problem described by the opener, the previous .rbf release (22.05.11) works flawlessly. I have my disc images in an external USB drive, I've tried loading an image from the microSD card but it doesn't work either.

[jca]

This is really strange. I never had any problem with this core, I have the games directory on a USB drive, I use HDMI 1080p 60Hz and I have the latest official core.

[Maxriptide]

I solved the problem. I noticed that my main Mister file was outdated, it was version v.220507 although the latest release was v.220529. This is very strange since I update my MiSTer every week at least! Anyway, I downloaded the latest Mister Main file, menu.rbf and Mister.ini from Github, copied them to the root of my microSD card and, after that, the PSX core was working fine. I hope it may be useful for the opener too

[stap]

Thank you!
The issue was the outdated MiSTer file in the SDCard directory. I also find it weird, since I thought update_all.sh was properly updating it. Now I see, that I had version, that wasn't updated since april, so I had to update it manually.

[grantek]

Thanks for the tip! I had this issue too after moving to a larger SD card with a fresh mr-fusion image. I'd run "update_all", but it didn't update the MiSTer Main binary - running the "update" script did though.

Edit: I tried to gather some more troubleshooting info, so I reverted the MiSTer binary back to v220413 from mr-fusion v2.5, and reran update_all.sh and update.sh - this time neither script updated MiSTer, so I assume the first time worked because I was calling the update script directly, but both downloaders had some sort of cache that prevented them seeing the new version.