Emulator

Issue 4875 has been merged into this issue.

The issue is still presented for OGL only, DX9 and DX11 doing perfect

Is this still an issue in the tev_fixes branch?

I always took Ghost Valley 2 as a reference and can't recognize the blue box there anymore.

Nevermind, still very noticeable on Wario's Gold Mine.

This issue is there in DX9.

Issue 4875 has been merged into this issue.

And I think that this issue also exists by me in the DX11 version.

I can confirm that this issue affects OpenGL, DX9 and DX11 by me. But you doesn't see just a blue box, but you can also see some variations in that box that matches with what you see in the game. For example a tree. What I mean is that it's not a blank blue box that is showed in the left corner.

Does this issue occur if the IR is set to Native 1X res?

Shows up with any configuration, IIRC it even shows up in the software renderer (could be wrong on that one though)

The only solution is to disable fog (but I think you already know this, because you can find this workaround at the wiki.)

@16 I mean that, as in issue 4875, the screen is here repeated in the left corner and almost 100% transparant.

Can anyone please retry this on OpenGL + emulate format changes? Our OpenGL backend now supports emulate format changes, this could be changes, also the ogl backend is the only one which supports LogicOp correctly

As MaJoR reported that emulate format changes fixes this issue, I think it should be enabled by default in this game ini.

But does emulate format changes fixes this bug for all render engines and not only OGL? I will try this later today and will report back.

It does fix this bug but with a very high cost for speed in this case, i knew it but didn't enable it due to that reason. Same with New Super Mario Bros and EFB to RAM, it fixes the spinning coins but with a very high cost for speed. Both are well known games and "killing" their speed by default creates a backlash. In the New super mario case i actually enabled Efb to RAM by default in the past and had to change it back later after severe criticism about it.
@wickmarkus86 do you want to take the responsibility yourself about it? I just hate the backlash these kind of changes create afterwards...

When I tried it there was zero performance impact on any backend. Of course, my computer is amazing, but I had the framelimiter off and saw no discernible impact. Can you retest it?

Will do, hopefully something has changed in the meantime and it it doesn't impact performance as it did in the past...

OK, i just tested dx9 and it seems that the speed hit is smaller than i remember, just in tracks that had the blue box appear like SNES ghost valley 2 i am experiencing a speed hit from about 160fps down to about 125 fps with the option. Not a huge speed drop but there is, ok i will enable it.

Damn, in Wario's gold mine is down from 170 to 105 fps (that stage also had the blue box always).

Ehm, do you still want it enabled?

-Disabe fog: removes fog and fixes this issue with no speedloss.
-uncheck ''Ignore format changes'': Also fixes this issue, but with speedloss at start of the race and during the race.

I think the best solution would be to disable fog by default. Then you see no fog in-game, but it fixes this annoying issue. And when uncheck ''ignore format changes'' will not affect the speed of the game in the future that much, then we could check ''ignore format changes'' again and uncheck disable fog in the game.ini.

What do you guys think of this?

I heavily, heavily disagree. The goal should be to ACCURATELY emulate the game. I don't think a speedhack that causes the game to look different from console should be by default. If you want to configure it for speed, do that yourself, don't make it default.

@Maarten: We don't enable hacks by default.

@kosta: I still think it's sad that we have no clear policy on what belongs to the game inis and what doesn't. I'm still all for enabling everything that is necessary to emulate games as perfectly as possible, and in this case it even makes sense, given that the blue box shows up in many tracks.

I also saw this big performance drop with high IR, so it's only a gpu slowdown. But as almost all users aren't gpu bottlenecked, I think we should activate it.

@kostamarino: which IR did you use for the performance check?

btw: I don't think we should tolerate a 40% speed drop, but I'm fine with a sqrt(40%) IR drop ;)

@wickmarkus86 basically i used the fractional setting which gives full hd (1920*1080) in my tv-monitor. My gpu is a 560 ti (a middle tier card nowdays).

I have an idea (that someone else needs to implement :-P), what about making an option of utilizing or not the ini files database for the emulator in the general configuration, with it being enabled by default and a strong suggestion to be enabled for compatibility - disabled for personal speed settings that can break a game or certain aspects of it? That way the ini database can be easier focused on compatibility, and a noob can break a game to his heart content for speed and then "restore" it by selecting the option again?

And/or perhaps a second option for personal ini files that will be stored in a different named folder, and will be used when the option is enabled instead of those of the main database.
Something like:
A. Use the gameini database for compatibility.
B. Use the personal gameini database to make your own personal settings (for advanced users).
C. Disable the gameini database completely (not recommended).
The Personal gameini database will be stored in a new folder as a copy of the original and be editable, the original will not be editable, and the whole database could be disabled by selecting the third option. And everyone is covered this way i think?

I don't agree with adding an option for using different game ini databases. Fwiw, option C can be trivially "implemented" currently by simply removing the User/GameConfig folder. Given that this should only be done by advanced users, that's just about as much user friendly as is necessary.

That said, there are numerous things that would allow us to be more "strict" in terms of "trade performance against accuracy" are:

• be more verbose when game inis override the global configuration. E.g. by displaying an OSD message telling the user that stuff may slow down due to config overrides.
• improve the current game-config GUI to be able to easily configure all fields.
• allow for a "local" game ini database so that users don't have to modify the default game inis (so that they can easily revert any of their own changes lateron)

Sounds good to me, the local gameini database is also similar to B, i like it. Now the only thing left is who will actually do the above :-p.

OGL works fine with EFB format changes and VBeam-speedhack *helped me with flickering *

This issue is no more fixed in Directx11 on version 4.0-1312

Congratulations on wasting my time with your erroneous update to this old issue report. The blue box is gone, and if you've read this report at all or the game's wikipage, you'd know that. Instead of giving us your settings, computer, or any kind of information, you just say it's not working.

I verified the blue box is still gone in D3D11.

On the off chance this was an actual bug, you should have provided your actual specs or some kind of useful information.