Game-compatibility: Project Gotham Racing [MS-003] [1.01]

[PatrickvL]

Issues

• Random crashes

_From @PatrickvL on May 5, 2017 22:16_

Reported here : http://www.emutalk.net/threads/56608-The-still-in-progress-emulator-broken-screenshot-thread-)?p=460631&viewfull=1#post460631

Commit ae13a335
Screenshot : http://www.emutalk.net/attachment.php?attachmentid=40016&stc=1&d=1494001148

_Copied from original issue: Cxbx-Reloaded/Cxbx-Reloaded#444_

[PatrickvL]

_From @rexcaptain501 on July 10, 2017 22:22_

I can only get as far as the intro cut scene with pulsing glitchy audio. Once it's finished, an unknown exception code crash error pops up.

1.05: Xbe.txt

Kernel Debug file: KrnlDebug.txt

Intro cut scene:

Crash:

[PatrickvL]

Seems like a patch is not applied, unclear if it's graphics or sound related.

[PatrickvL]

_From @rexcaptain501 on July 23, 2017 23:9_

Tested with Cxbx-Reloaded build 3ca1a35, Jul 23 2017

No audio is being output anymore. Getting similar results to #429 (Madagascar).

[PatrickvL]

_From @RadWolfie on July 24, 2017 0:53_

I'll check this out later this week to see if I can fix the audio part unless someone else will beat me to it. :smile:

[PatrickvL]

_From @RadWolfie on July 28, 2017 0:0_

Hmm... in EmuDSound.cpp at beginning of line 1100 with the code shown below. If removed the if/else check, then audio is playing just fine. Is there some reason for this to be worth keeping? I had checked other playable titles and did not hear any distort or any crash.

    if (pThis->EmuBuffer != 0) {
        *ppvAudioPtr1 = pThis->EmuBuffer;
        *pdwAudioBytes1 = dwBytes;
    } else {
        ...
    }

By doing this, Project Gotham Racing and Splinter Cell Pandora Tomorrow (online.xbe) titles are audible.

[PatrickvL]

@RadWolfie I'm not familiair with the dsound code, so I browsed through it. I still can't determine if your suggestion is right, but it did make me submit a Pull Request for DSound - would you care to review it? https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/pull/537

[PatrickvL]

_From @rexcaptain501 on July 28, 2017 9:50_

Edit: deleted my previous comment. Seemed to be a rendering issue caused by putting video settings to my native resolution instead of auto. This happened with RalliSport Challenge too, but not LEGO Star Wars. Odd.

I hadn't seen this behaviour before. Just for reference:

[PatrickvL]

_From @LukeUsher on July 28, 2017 9:53_

That looks like you set your output resolution higher than 640x480, a lot of titles specifically set the viewport to 640x480, in which case you'd get this result.

Other titles scale to the full screen size automatically, so it's not really a bug as such, just a result of how the game was programmed.

[PatrickvL]

_From @rexcaptain501 on July 28, 2017 9:54_

That's really weird, because on previous builds to aa0c6718 this didn't happen. Edit: ignore this. Context down below.

[PatrickvL]

Problems with wrongly placed and/or un-streched video's is probably due to a bug in overlay handling. I've been messing around with it already, but nothing to show for it yet.

EDIT: Wait a minute - you're saying one build prior to aa0c671 this didn't happen? That's very strange, as this commit doesn't come _near_ graphics....

[PatrickvL]

_From @rexcaptain501 on July 28, 2017 10:5_

I just tried again with an older build I was testing with today and I'm getting the same stretch behaviour. Odd. shrugs

[PatrickvL]

_From @LukeUsher on July 28, 2017 10:9_

This happens with the majority of titles if you set a resolution higher than the Xbox default, it has always been an issue, and will remain an issue until either full LLE (where we can handle this on the GPU level) or we make our rendering functions (eg: SetViewPort) ignore the values given by the xbox title.

The first option is a long way away because of the amount of technical work involved

The second option has a high potential for bugs and upscaling is only a nice to have so it likely will be a time before it is implemented properly.

[PatrickvL]

_From @rexcaptain501 on July 28, 2017 10:12_

Yeah, I just tested with a8033fee (yesterday) and I'm getting the same behaviour as aa0c671, and I'm sure I didn't get this yesterday with the setting at 1920x1080. Oh well, I guess? Hardware Mode looks the same with the stretch behaviour, only rendered to the monitor. 640x480/auto works just fine as usual.

[PatrickvL]

_From @RadWolfie on July 28, 2017 14:37_

@rexcaptain501 When you set a higher resolution, it will mostly "shrink" the output screen because it doesn't perform "fill to screen" process. However dashboard appear to always fill to screen no matter what the resolution is. Plus by design, the "auto" uses 640x480 resolution by looking at the code in the past. I would say it works as intended.

@PatrickvL This is the if/else portion I'm talking about which is now at line 1041. By removing "if" portion, the intro do start playing audio just fine.

[PatrickvL]

_From @zaykho on August 7, 2017 13:50_

@rexcaptain501
Beware that, if you spot an issue with the latest build, and try to load an older one to compare, you will need also to clean the cxbx-r folder in appdata.

In example, Jet Set Radio Future did have some weird issue with a later "test" build, and this issue was still happening when loading an older "clean" build.

I was forced to delete the cxbx-reloaded folder located in AppData\Roaming and reload the "clean" build to be able to compare properly.

[ghost]

Tested with build b4c45cfc (Sep 1 2017). The intro movie plays perfectly with audio. After the movie, the game freezes. It's been like this for a while now in recent builds.

Movie:

Freeze after movie:

Kernel Debug file: KrnlDebug.txt

[hinksta47]

Detected regression with intro video now displaying a white screen, with perfect audio.
The build identified to have caused this is f8f94c0c - "Fix OOVPA's XDK revision to lowest known match".
Last build to have displayed it correctly is e305ff48.

KrnlDebug - e305ff48.txt
KrnlDebug - f8f94c0c.txt

[Voxel9]

From #779 by @SonicThePS4

---

Description

Excellent Intro, But it goes in the black screen when it tries to go to the "Press Start Button" screen.

Dumps

1.01: Xbe.txt
KrnlDebug.txt

Status

Previous behavior:

Current behavior:

Screenshots

Additional Information

[gandalfthewhite19890404]

Latest dev-version - Failed to create Vertex Declaration.

[PatrickvL]

@gandalfthewhite19890404 when?

[gandalfthewhite19890404]

After boot

[Insan1ty0ne]

The intro cinematic plays perfectly with audio, but after that it is just a blackscreen with no audio.

1.01: Xbe.txt

If anyone wants me to log anything specific, please let me know.

[mainzerbe]

Now ingame - amazing job! Huge graphical issues but (basicly) playable.

[ObiKKa]

Thanks for the report above, mainzerbe. One small PR # 2055 two weeks ago on November 29, 2020 and titled "Preserve original IO status block and context for ApcRoutine" solved this game deadlocking after the intro video finished running, and could get to the menus. But this game did manage to go in-game as shown by screens and user comments on GitHub and Discord shortly after.