Emulator

Turn on EFB2RAM

JMC4789 wrote:

Turn on EFB2RAM

I don't have it on my dev build unfortunately

Setting EFB copies to RAM is the same as turning off "Store EFB Copies to Texture Only".

JosJuice wrote:

Setting EFB copies to RAM is the same as turning off "Store EFB Copies to Texture Only".

Ohhh..in that case, i've already on, but it didn't do anything unfortunately.

Maarcis12 wrote:

JosJuice wrote:

Setting EFB copies to RAM is the same as turning off "Store EFB Copies to Texture Only".

Ohhh..in that case, i've already on, but it didn't do anything unfortunately and turning it off didn't fix anything.

if you look closely at the pictures in the top left and top right it seems like it is loading a wrong texture (one that is actually used for multiple objects)

I think maybe a FIFOlog will help... If I have some time tonight and I can reproduce the error I can record one, but not sure if I have FIFA Street 1 or 2...

Using the attached fifolog on real hardware shows the same issue, so this is probably an issue outside of the graphics code.

Does this issue happen when dual core is disabled? I ran into an issue where nondeterministic behavior happened when using dual core with a fifolog with one of the FIFA street games (unfortunately I'm not sure which), including the wrong textures being used for the HUD. It seems to be something along the lines of the game putting the vertices for the HUD into memory at one location, then drawing it, then waiting for the draw to finish, then changing the coordinates at the same location in memory, then drawing, then waiting for it to finish, for each HUD element, and dual core is breaking the wait step so it tends to use coordinates for a later draw with the texture for an earlier one. However, I'm not sure if that's specific to the fifoplayer or not.