Burnout 3/Revenge/Black - Missing sky texture

[karasuhebi]

-PCSX2 version: 1.3.1-382

-PCSX2 options: Defaults.

-Plugins used: GSdx32-AVX2, SPU2-X, LilyPad, cdvdGigaherz, the rest of the plugins were null.

-Plugin settings: Tested GSdx D3D9, D3D11 and OGL, both hardware and software renderers. Used both native and upscaled resolutions. Also tried with AF off and AF 16x.

-Description: The game's sky box appears black. Switching to software mode won't fix the problem. The issue is fixed if you boot into the game with a software renderer.

-How to replicate: Boot the game and play it. The issue shows up in any race.

-Last known version to work: Unknown, probably never worked.

-PC specifications: CPU: Intel Core i5-4670K @ 4.10GHz GPU: Sapphire HD 7950 w/Boost 3GB OS: Windows 8.1 Pro

-Other comments: If you boot into the game after already having played another game (in my case, DRIV3R), the missing sky box will be filled with garbage data, possibly from the previous game.

Screenshots:
http://imgur.com/a/0JhH9

Bonus screenshot of the blur effect in the game being broken (turned into ghosting):
http://i.imgur.com/sNTUBoY.png <- Look on the right side of the car.

[ssakash]

GS dump is needed to debug the graphical glitches,

[bositman]

The game has CRC hacks so you should also disable CRCs in GSdx to actually see all that is broken (and it's a lot :P)

[karasuhebi]

Ah yes, GS dump is probably a good idea. Thank you @ssakash. @bositman brings a good point though. @gregory38, would you like a GS dump with all CRC hacks disabled?

[gregory38]

Just do the dump in sw mode.

[karasuhebi]

https://dl.dropboxusercontent.com/u/6425650/gsdx_20150529031828.bmp
https://dl.dropboxusercontent.com/u/6425650/gsdx_20150529031828.gs

[gregory38]

Did you try with

UserHacks = 1
UserHacks_DisableCrcHacks = 1
UserHacks_AutoSkipDrawDepth = 0

Lots of effect are disabled. And depth textures aren't read back. I can't reproduce the issue but I think it would be better to fix all effects with known issue first.

The sky issue could be related to 16 bits / 32 bits conversion. A 32 bits 640x480 target is equivalent to a 16 bits 640x960 target but guess what, gsdx still uses 640x480, and half of the screen is potentially garbage...

[karasuhebi]

I did not try disabling CRC hacks, no. I will do so now.

[gregory38]

And try also to disable the texture cache (if you know how to recompile gsdx).
Config.h, => use this line

#define DISABLE_HW_TEXTURE_CACHE // Slow but fixes a lot of bugs

[karasuhebi]

OMG, without CRC hacks:
http://i.imgur.com/FQZLj2O.png

[gregory38]

yes I said various effect aren't emulated correctly ;)

[karasuhebi]

So why did you want me to try without CRC hacks? Did you need me to provide you with a GS dump of that?

Anyway, I'll disable texture cache in a minute and get back to you.

[karasuhebi]

Yeah the sky is still missing with hardware texture cache disabled.

[ssakash]

what about the ZeroGS plugin ? was the sky still present ?

[karasuhebi]

ZeroGS: http://i.imgur.com/jqTGLX4.png

FWIW, ZeroGS doesn't even let me see the menus. It shows me the Loading progress bar when the game first boots and then you see NOTHING until you get into a race. Then you get what you see above.

[karasuhebi]

Would someone mind booting some random game and then booting into Burnout 3 using full boot instead of fast to see if the garbage textures are still there or if they get flushed??

Thanks!

[escape209]

I full booted into Burnout 1, played a race and then full booted into Burnout 3. Then the game was suddenly on acid:
http://i.imgur.com/6xNQ08u.jpg

It seems like the textures ARE THERE, but the coloring is wrong. However, notice how the far right of the sky is just grey. This is on OpenGL, by the way. I'll see if D3D is any different.

[karasuhebi]

Doubt D3D11 will be any different. That's the same issue I was having. I just wanted to see if doing a full boot did anything to flush the garbage textures that stick around from the previous game.

Thanks!

[karasuhebi]

@gregory38 Should I test this game now with the latest build?

[ssakash]

I think it'd be nice to check whether bug is present with Preload data frame option.

[joder666]

@ssakash Yes, sadly it is still present.

[FlatOutPS2]

The issue is fixed if you boot into the game with a software renderer.

You don't need to boot the game with software renderer, just loading a track in software mode is enough.

If you've loaded a track with a hardware renderer and get black skies, then switch to software mode and exit back to the menu in software mode, then switch back to the hardware renderer and use that to load a track, the sky textures will also be there, but the sky will be white(the blue sky color won't get loaded).

[marios237]

what is that can anyone help me ???

[MrCK1]

@marios237 This isn't a place for general support. If you have a question, please make a thread at forums.pcsx2.net instead.

[tadanokojin]

Issue is as follows (for Revenge):

Game is rendering sky texture (note rendering, no EE write) to buffer at 0x2c00. However, actual sky data is offset +32 pixels in the x direction. This happens once as the game is in the loading screen.

Later, game will sample 0x2c10 for sky data with no offset. Since the cache is not designed to deal with this situation, it results in a miss. This issue is similar to the notorious Jak Eye issue. Texture inside rt will alleviate this but it will also result in some bugs dealing with reflections on the cars.

I'll work with @iMineLink for a solution.