Dolphin different behavior Virtua Striker 3

[trihy]

Hi guys, not sure what can be happening here.

Some Dolphin builds, when you start this game, let you select 50 or 60hz.

Other Dolphin builds dont show that part of the game and stays at 50hz.

With the latest builds it doesnt show.

Not sure which versióon show the hz selection screen, cause this was random among Dolphin builds among the years, but most of them show the screen.

Now seems latest builds doesnt. 

Any ideas why?

[mbc07]

Enable Progressive Scan in Graphics Settings, then hold B button while booting the game. That will bring the prompt you're mentioning and the selection you make will be saved in SRAM...

[trihy]

Enable Progressive Scan in Graphics Settings, then hold B button while booting the game. That will bring the prompt you're mentioning and the selection you make will be saved in SRAM...

Hi, tried but doesnt work. Im using GC bios. Hold B during bios animation and still hold while game starts, hz selection screen wont show.

On other Dolphin builds screen Will appear everytime no matter what hz you choosed before.

[mbc07]

Try to do that with Skip BIOS enabled...

[trihy]

Try to do that with Skip BIOS enabled...

Hi tried with skip bios and could enter to hz selection screen.

Then enable bios and Hz selection screen shows even when not pressing B.

And now everytime I boot the game the hz selction screen appear.

Any guesses of this erratic behaviour?

[mbc07]

After enabling Progressive Scan and setting the desired Hz once, I also always get the selection screen when booting. That's the case all the way back to Dolphin 4.0 era, so I think it's intended behavior...

EDIT: if you want the Hz selection screen to be gone, you can disable progressive scan OR you can delete SRAM.raw in User\GC and let Dolphin regenerate the default file on the next run...

[trihy]

Hi. Will try to delete sram. Probable was generated a couple of years ago.

Im ok if hz selection sceeen always show. Problem is when wont show and game will be locked to 50hz. But now i know some workarounds if that happen again.

Thanks