(05-09-2018, 09:26 AM)Renazor Wrote: Round 3 I guess:
Does the damage of missiles get changed when using Skip Drawing? (I thought it wa part of ubershaders I guess not)
Does Samus get correct number of missiles from ammo pickups when using Skip Drawing?
Does MP3 experience random errors or crashes and shows signs of loss of stability during Skip Drawing?
If all the answers are no and the game shows no difference compared to when it's running at the most safe options then the option Skip Drawing would be able to be considered "purely graphical inaccuracy" which is a much lesser category IMO.
That's technical opinion, but the users could be different, the question is then how much do people care about such things, whether it's really important to them, would a user treat something that has purely graphical inaccuracy as hard as a gamplay inaccuracy or stuttering or crash even?
If the users have strong opinions then there's no choice but to treat these as if they were serious gameplay inaccuracies, but I hope otherwise. I do understand it's tricky because it's per-game, and some games have on thing where a graphical thing is required for gameplay as you mentioned, which means that it's just not possible to do it widely, this categorization would have to be done per-game.
The GUI can't have so much text to explain things per-game, that's when this comes in.
Not saying this is an important thing, it's just a side idea, but it would be like this, each game (realistically only select popular ones) would have a table in the the wiki with all the relevant GUI editable options listed, along with the category they fall into, INI overriden, comment, etc, along with a semaphore indicator, kinda green, blue, yellow, orange, red ... most definitely the red ones are also going be marked as INI overriden.
Ofcourse in the beginning most of the table would be undefined, because something like this takes quite a load of time to populate and a maintainer too to keep it updated.
This goes hand-in-hand with the default ini overrides, testing done for this would actually help find potential options which weren't overriden in game INIs before but should be if the evidence supports that.
EDIT: Then you or me aren't using the term accuracy right, so dolphin officially doesn't put graphical stuff into the "accuracy" category or what?
Is Samus able to look through objects/walls until the shader is compiled? YES! Can she shoot or walk through these objects that she cannot see yet? NO!
Does this directly have to do with accuracy? NO... It has to do with how a PC GPU works in emulation.
FIRST OF ALL: *Remember you are emulating the console not the game*
This means that your PC's GPU has to pretend to be the console's GPU and the emulator has to translate the instructions given to the consoles GPU by the game to something a PC GPU can understand. The problem lies here: The instructions can only be interpreted by the emulator and given to the PC's GPU when the console's GPU receives them from given game(the emulator can not look into the future). So your PC's GPU can only start compiling shaders once they've appeared on the screen.
Native PC games can compile all shaders before they are even used once since the game can let the GPU know "Hey in the future I am going to use the following shaders so please have them ready when I ask for them" so the PC's GPU can compile ALL shaders while the game is loading.
Check my profile for up to date specs.