..:: PCSX2 Forums ::..

Full Version: Re: Simple bug with the console reporting.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
This is to continue the conversation from http://forums.pcsx2.net/Thread-Resolved-...-reporting as the thread is now closed.

vsub Wrote: [ -> ]I'm not sure that change to the console was a good idea.Now it's even harder to know which mode you use.

How is it harder now? The only thing that was changed in the console was the message. It went from "Forced software switch enabled." to "Toggling GSdx Hardware/Software renderer". Nothing else changed. You can check it out yourself:
https://github.com/PCSX2/pcsx2/commit/c4...e81b231103

vsub Wrote: [ -> ]but the settings are still not applied correctly when you choose a renderer but that's another problem

I seem to remember seeing this issue mentioned somewhere. Did you report this in GitHub? If not, you should really report it.
Well the word "Forced software switch enabled." kinda tells you that GSdx switched to software mode(which is not always correct because of a bug with the settings not been applied)

This message "Toggling GSdx Hardware/Software renderer". just tells you that GSdx switched to some other mode but which one it is...no one knows.

And about the issue at github,here is the story
This is the beginning
https://github.com/PCSX2/pcsx2/issues/565
Then this attempted fix came out
https://github.com/PCSX2/pcsx2/pull/580
Which resulted in a new bug
https://github.com/PCSX2/pcsx2/issues/584
and the fix was reverted

So there is no fix
1) Except for the fact that as you yourself said earlier, that statement was as ambiguous as the new one since it would show up even if you were starting off with a software renderer and pressing F9 to change to the hardware one. Nothing changed. Both statements are exactly the same as far as not telling you anything.

Don't worry though, ssakash is working on making that statement tell you exactly what renderer you're using:
https://github.com/PCSX2/pcsx2/pull/606#...-113221626

2) Thanks for clearing that up! Laugh
done. https://github.com/PCSX2/pcsx2/pull/617

could I move this additional report to the resolved forums then ?
I have few things to say
1.What exactly is the point now of "Toggling GSdx Hardware/Software renderer" message if you see in the console which renderer is currently active?
2.Could we use some other color or bold text for that info
3.Shouldn't the Enable HW hacks be enabled by default now since the CRC hacks are placed in there....or remove the checkbox and rename the Configure button to HW hacks.

Opening the GSdx settings which still don't sync with the current active renderer but at least the info in the console and the game window is always correct
1/ I think it could be removed.
2/ actually, I Intended on using some colors for that on printf to make it stand out but that didn't work on the sort of terminal log we currently use, I'll look for some alternatives.
3/ I thought CRC hack level is enabled regardless of the the check box status.
(07-05-2015, 09:44 AM)ssakash Wrote: [ -> ]3/ I thought CRC hack level is enabled regardless of the the check box status.

I don't know but having it in another window with settings which are working only if "Enable HW Hacks" is enabled makes you think you have to enable it to enable the crc hacks
(07-05-2015, 08:03 AM)vsub Wrote: [ -> ]I have few things to say
1.What exactly is the point now of "Toggling GSdx Hardware/Software renderer" message if you see in the console which renderer is currently active?
2.Could we use some other color or bold text for that info
3.Shouldn't the Enable HW hacks be enabled by default now since the CRC hacks are placed in there....or remove the checkbox and rename the Configure button to HW hacks.

Opening the GSdx settings which still don't sync with the current active renderer but at least the info in the console and the game window is always correct

(07-05-2015, 09:44 AM)ssakash Wrote: [ -> ]1/ I think it could be removed.
2/ actually, I Intended on using some colors for that on printf to make it stand out but that didn't work on the sort of terminal log we currently use, I'll look for some alternatives.
3/ I thought CRC hack level is enabled regardless of the the check box status.

1. I do feel like printing the toggle message after the current renderer message is a bit strange, but I don't think it should be removed entirely. It's good UX to tell the users when their key press does something, and what that something is. So maybe it would be a good idea to figure out how to make the current renderer message show up after the toggle message.

2. Colors would be good, I agree.

3. I agree that something needs to be done about the CRC hacks option. If it indeed doesn't listen to the "Enable HW Hacks" option, then either that option needs to be removed altogether or CRC Hacks needs to be taken out of there.


(07-05-2015, 10:40 AM)vsub Wrote: [ -> ]I don't know but having it in another window with settings which are working only if "Enable HW Hacks" is enabled makes you think you have to enable it to enable the crc hacks

I agree. This is confusing.

(07-05-2015, 07:04 AM)ssakash Wrote: [ -> ]done. https://github.com/PCSX2/pcsx2/pull/617

could I move this additional report to the resolved forums then ?

Looks like we're still discussing the console messages a bit so don't move it just yet. Smile
3/ (or) make it obey the status of the enable hw hacks.
[attachment=56130]
(07-05-2015, 09:44 AM)ssakash Wrote: [ -> ]1/ I think it could be removed.
2/ actually, I Intended on using some colors for that on printf to make it stand out but that didn't work on the sort of terminal log we currently use, I'll look for some alternatives.
3/ I thought CRC hack level is enabled regardless of the the check box status.

Hi vsub,
I saw a previous thread of yours,could u give me save file of
God of war scus_97399 after pandora's bridge my game is freezing there
Pages: 1 2