Continuing.
Custom Textures could be moved to Enhancements Tab preferrably, but maybe spacing issue, then General is the only other place that make sense, with existing numbers of tabs, unless default sizes for the graphics window are adjusted.
Log Render Time To File feels more like it fits into the Utility groupbox in the Advanced tab
Also, borderless fulscreen is a standalone thing right, not something used ontop of "Use Fullscreen" ?
Also if (now by default) Custom Fullscreen Resolution is set to AUTO and Use Fullscreen is enabled, than it is upscaling/downscaling whatever IR is set to and the "Auto Adjust Window Size" has no effect. That right?
I was trying 3xNative without fullscreen and with auto-adjust and it looked almost the same as 4x, which was a few pixels larger, I have 1440p and 3x (1920x...) definitely shouldn't take 95% of the screen. (Vulkan, Qt)
Metroid Prime Trilogy: 2x Native (1280x..)
Actual with EURGB60: Width 1604x..
Actual without EURGB60: Width 1924x..
Same thing with Wx and D3D11
Understood, I wish there is something we could do about that, you think ubershaders have room for improvement at all?
Custom Textures could be moved to Enhancements Tab preferrably, but maybe spacing issue, then General is the only other place that make sense, with existing numbers of tabs, unless default sizes for the graphics window are adjusted.
Log Render Time To File feels more like it fits into the Utility groupbox in the Advanced tab
Also, borderless fulscreen is a standalone thing right, not something used ontop of "Use Fullscreen" ?
Also if (now by default) Custom Fullscreen Resolution is set to AUTO and Use Fullscreen is enabled, than it is upscaling/downscaling whatever IR is set to and the "Auto Adjust Window Size" has no effect. That right?
I was trying 3xNative without fullscreen and with auto-adjust and it looked almost the same as 4x, which was a few pixels larger, I have 1440p and 3x (1920x...) definitely shouldn't take 95% of the screen. (Vulkan, Qt)
Metroid Prime Trilogy: 2x Native (1280x..)
Actual with EURGB60: Width 1604x..
Actual without EURGB60: Width 1924x..
Same thing with Wx and D3D11
(05-09-2018, 10:21 AM)mstreurman Wrote: 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.
Understood, I wish there is something we could do about that, you think ubershaders have room for improvement at all?