-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gsdx: set the new renderer in ini file after a F9 switch #588
Conversation
I think pcsx2/MTGS.cpp also needs changed as well? Needs a
|
Yes that console writeline can be modified now to show what the renderer actually is, like people wanted :p |
Will this make it so the F9 toggle is permanent? Or will remain a temporary switch like before where GSdx will switch back to the renderer you have chosen in the UI when you open PCSX2 again? @refractionpcsx2 YAY :D Will it also let us print it to the title bar? That'd be useful for when we're troubleshooting end user issues on the forums. |
Hm that is a concern, writing it to the ini will keep it that way for the next time you'll boot PCSX2 again, not sure if we want that |
I guess gsdx could be told to clear it out of the ini when it gets told to close |
You'll have to store the initial value you had at boot and restore it when closing |
First is the file really updated in windows? |
What do you mean is the file really updated on Windows? Ofc it is :p |
@refractionpcsx2 I believe it was mentioned in one of the GH Issues that it wasn't writing the value to the .ini file. I can't remember who mentioned it or in what Issue though. XD EDIT: |
So I propose another idea. Set the renderer before enter the GUI instead of after toggling it. |
This way, the gui is aligned with the renderer but it doesn't save the value if you don't open the GUI
9ec2621
to
ead0301
Compare
I updated the branch. Tell me if it behave better. The renderer is only set before calling the gs option. |
Tested after rebasing this on master (7135867) and capitalising renderer. This makes the renderer settings when you open the config panel confusing and doesn't fix the issue. My test: To fix the behaviour requires changes to the core. The core has the assumption that users always start off in hardware rendering mode and does not know whether the user is in hardware or software rendering mode. That's why a GSdx only fix won't work. If you don't mind, I can probably fix it. If so, do you:
Note: because the core assumes users start in hardware rendering mode - The "Switch to GSdx software rendering when an FMV plays" gamefix and some other stuff in the code (disable Vsync in software mode) is actually broken when the user uses a software rendering mode to begin with. |
Switching to software mode should change the main renderer imo, not have a sub/temporary renderer mode, if you change to software, it should change that in the config as well, at least then you know if you change it in the config, you're getting hardware mode if you chose it. There's no real reason to make it a temporary setting. |
So an F9 toggle would be a permanent switch? Gregory's previous fix would have worked in that case (it'd break toggle on the older plugins if that matters). I suppose it doesn't matter too much whether it's permanent or not now that the title bar tells you what's being used. |
I still think that at the end of the play through GSdx should go back to the setting it initially was (before any F9 toggles) except if you modify it via the GUI. This way if I eg test a game and toggle 10 times, I won't have to check every time where it ended up for my next play through |
Then the F9 toggle needs to be reset if the renderer is changed. PCSX2 doesn't know if you're in software mode, so resetting it in GSDX should be fine. If we did know, PCSX2 wouldn't have to say it's swapping renderer without being precise :P |
Thinking again, it can be mostly solved in GSdx without touching core and keeping it temporary. If you save the last state of the F9 toggle and compare it with the current flags it should work. Something like this in GSOpen2:
|
I agree with @bositman, I still think that the toggle should not be permanent. |
Tentative fix for #584