Kotor 2 T3M4 Black Screen bug

[austinmackinnon]

Title

https://xemu.app/titles/4c410014/#Star-Wars-Knights-of-the-Old-Republic-II-The-Sith-Lords

USA version

Bug Description

T3M4 stuck on Peragus Black screen bug. Quote from reddit post that was made about this issue on Xbox Series X "Ok, well, Im as T3 on Pegasus and trying to open the hatch so my char and anton can come down. When I finally open it, the game goes to a quick sequence with T3 and then fades to black... then the screen stays black and never comes back.

However, I can go to my main menus, so I do, save my game, load my game, and there is my main character, a few feet away from where T3 was. So I look around and realize Im in an area closed off by forcefields, except for the elevator which brings me back to where T3 came from. I go in teh elevator, and when taht area loads... Im back to being T3 without the main character in my party. To top it off, T3 is frozen in place with a big red X through his portrait."

From what I can find, this issue only occurs when the game is run off of an xbox hdd, whether emulated or no. The game works fine off of a physical disc. I'd really like xemu to be able to run the game without dealing with this bug as it can't run the game off of the xbox disc directly.

Expected Behavior

After T3M4 gets blasted in the cut scene, the game is supposed to load back in your character in the peragus administration level. There are some other instances in the game where it switches locations that the issue can occur as well.

xemu Version

N/A, this is a bug that shipped with the game and is present on an actual xbox console.

System Information

OS: Batocera 36-dev-464802256a Disk Format ext4 OpenGL 4.6 (Core Profile) Mesa 22.3.4 CPU AMD Ryzen 3 PRO 2200GE 8 GB DDR4 3200

Additional Context

No response

[ArdentMoogle]

I was able to resolve this issue by changing xemu to use the debug memory setting, ie. 128 MB instead of the default 64 MB.

[coppermine733]

This is a known issue with the game in general and happens on a real Xbox. I believe it's a scripting issue that results in a race condition. It only presents itself when the game is played from fast media, such as a hard drive, instead of the DVD drive.

[MasonP57]

It is March (not April lol) 30th 2024 and I would just like to add that on Xemu v0.7.120 this issue is still occurring. Based on the previous post here by ArdentMoogle I checked, my emulator was already on the 128 MB memory setting. I have toggled between both the 128 and the 64 while quitting and restarting the program and neither seems to work.

This issue seems to be a complete blocker for the game at present.

[iamdark24]

What are the lotto numbers? Jk, but it’s March 30th.

I’d suggest using an older version of Xemu for now until it’s fixed in a new release.

[ArdentMoogle]

It is March (not April lol) 30th 2024 and I would just like to add that on Xemu v0.7.120 this issue is still occurring. Based on the previous post here by ArdentMoogle I checked, my emulator was already on the 128 MB memory setting. I have toggled between both the 128 and the 64 while quitting and restarting the program and neither seems to work.

This issue seems to be a complete blocker for the game at present.

It worked for me once, but I guess it was a coincidence. I wasn't able to replicate this, and the only way past the black screen for me was reloading my save a ton. But later in the game the bike races are just black screens.

This game really just hates fast media. It's maybe possible for someone to artificially throttle the read speed in xemu's code, and that could fix the issue, but really this game is just dead in the water because of the previously said race condition.

Someone modding the game to fix the race condition is really the only good fix, otherwise buying the PC version through Steam is unfortunately the best option.