Note: these are not necessarily requirements
fc5b5fb
USB SMB HDD
VMC GSM PS2RD PADEMU
Games that support 16:9 dont read the screen ratio setting from browser and boot in 4:3
games should read screen setting
screen setting set in browser is ignored
boot a game that support 16:9 e.g. Burnout 3
But does your game actually follow the display setting from the browser? Not all games do.
OPL does not change the system configuration, so your problem is elsewhere. If you are sure that the game will uses the display setting from the browser, then how are you booting OPL? If you have been involving a modchip in booting OPL, then the modchip's DEV2 code might be incapable of loading the system configuration.
So... Is this a prevailing issue, or is it non-existent?
I tested this with Burnout Revenge and it indeed does not load in 16:9 which I have set in System Configuration.
See Note 21:
https://en.everybodywiki.com/List_of_PlayStation_2_games_with_alternative_display_modes
odd. i played burnout revenge in 16.9 fine a few months ago.
How have you loaded OPL?
Was PS2Logo-Function in OPL on/off (Is there a difference? I suppose there is no difference, but again there could be...)?
freemc boot from mc.
game from iHDD and SMB
logo was off.
@Tupakaveli: Was it a Modchip's DEV-Mode in your case?
Sorry, it was Burnout Dominator SLUS_215.96
Just tested it again with latest build and it is working... I have modchip disabled.
I'm sure when I tested it last time it wasn't working, because I wanted to see if this issue could be closed.
It related to modchip. Its not OPL fault never was. Would be cool seeing OPL fixing this for us, though
@carljtc: Why does it show @V3dita BR ? 馃榿
The issue-list is shrinking! GREAT!
Well, OPL could take care of it just like it does for resetting the SPU2(-Channels?) ahead of starting a game. @sp193 would be the best source to ask, regarding this.
In MY opinion this is indeed the boot-method's job, but I can see the various issues which could happen, if the boot-method simply doesn't take care of it.
However...
I have to criticize the current implementation of it as well, simply because that 'taking care' of the system being 'in the right state' should be done when OPL initializes/starts and not ahead of starting a game (at least I think it is implemented that way)...
Why?
Because implementing it at the start of OPL would take care of it running well on Apps as well (or is that implemented there as well? I thought/think it was not...)?
...and it would be good, if wLE can reset the SPU2 as well, because it is the most-used method to launch ELFs, aside FMCB/FHDB.
I ought to remember, that it had support for the OSDSYS-Init as well, but I am not sure about it.
Most helpful comment
Sorry, it was Burnout Dominator SLUS_215.96
Just tested it again with latest build and it is working... I have modchip disabled.
I'm sure when I tested it last time it wasn't working, because I wanted to see if this issue could be closed.