Emulator

Drawing the graphics involves all sorts of scaling and cacheing and the IR setting is right in the middle of everything.
To me (as non-developer) changing the IR mid-game sounds almost as intrusive as changing the CPU emulation core or the graphics backend mid-game. Anyone would understand that they would be... hard to implement. Yet the IR works pretty well in Dolphin. I mean, you have to often restart normal DirectX-based games only to change the resolution.

I don't know how many users have a real need to change the IR when playing? At least after finding out the sweet spots for the games that they play. Not saying that this isn't an issue at all. And I'm biased as a huge fan of the partial texture implementation, as it is now. I don't understand any of the wizardry behind it, though.

I still think it would be good enough to warn people by adding an OSD line "Changing the internal resolution mid-game can cause graphical glitches" when the hotkey is pressed. Just as we warn people to open the graphics settings when a game is running. Vs. mimimi writing huge amounts of code only to verify that the scaling of the textures is recalculated / maintained after the IR changes in a very limited (?) number of games.

Having an OSD message about changing the resolution causing problems isn't user friendly (and neither is the OSD message about not opening the settings).

I know this is probably still an issue, but, it seems as though changing the IR after the EFB Copies are generated would cause it to use EFB2RAM and thus, be lower resolution... is it even fixable?

Thank you for the explanation, I guess I still don't know everything about this.