findings:
1. "View Map", Main BG3 always show correct image without the corruption.
2. If you open "View Map" & Main BG3, click auto update then uncheck fog, there is no corruption on the image.
3. If you uncheck fog, you get corrupted image, then open "View Map" and Main BG3, click auto update then check fog, still corrupted image but "View Map" always show correct image.
Problem between "View Map" & fog option?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Weird fixed frameskip issue with this game. tested on clean r3109 :
start game with different fixed frameskip 0-9
case 1: (start emu)
use fixed0to2 - ok, then fixed3 - hang at 1st screen, then fixed4 - ok, then fixed5 - hang at 1st screen, then fixed6 - ok, then fixed7 - same hang, then fixed8-9 - ok.
case 2: (start emu)
use fixed3then5 - ok, then fixed7 - same hang, then fixed3 - same hang
case 3: (start emu)
use fixed0-4 - ok, then fixed5 - same hang, then fixed6 - ok, then fixed7 - same hang, then fixed8 - ok, then fixed9 - same hang
case 4: (start emu)
use auto1-9 - ok
tried the same scenario with Wizard of Oz & order of phoenix - ok.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
this game needs fog enabled for proper graphics display.
the random & temporary lockout for fixed frameskip is still there but can be bypassed by choosing another frameskip value if happens or use auto.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
for the record, those shapes are used for occluding models (anywhere you can go behind the art, these are used to make your character disappear). I have no idea why they use fog to implement that though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
well they didnt know what youd be able to go behind depending on the camera angle, so they probably added occlusion anywhere they thought you might could even slightly go behind something maybe depending on if the camera was lucky.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
you can download savestate from http://www.sendspace.com/file/lxmq4w
findings:
1. "View Map", Main BG3 always show correct image without the corruption.
2. If you open "View Map" & Main BG3, click auto update then uncheck fog, there is no corruption on the image.
3. If you uncheck fog, you get corrupted image, then open "View Map" and Main BG3, click auto update then check fog, still corrupted image but "View Map" always show correct image.
Problem between "View Map" & fog option?
Weird fixed frameskip issue with this game. tested on clean r3109 :
start game with different fixed frameskip 0-9
case 1: (start emu)
use fixed0to2 - ok, then fixed3 - hang at 1st screen, then fixed4 - ok, then fixed5 - hang at 1st screen, then fixed6 - ok, then fixed7 - same hang, then fixed8-9 - ok.
case 2: (start emu)
use fixed3then5 - ok, then fixed7 - same hang, then fixed3 - same hang
case 3: (start emu)
use fixed0-4 - ok, then fixed5 - same hang, then fixed6 - ok, then fixed7 - same hang, then fixed8 - ok, then fixed9 - same hang
case 4: (start emu)
use auto1-9 - ok
tried the same scenario with Wizard of Oz & order of phoenix - ok.
no more weird frameskip hang with r3110.
this game needs fog enabled for proper graphics display.
the random & temporary lockout for fixed frameskip is still there but can be bypassed by choosing another frameskip value if happens or use auto.
for the record, those shapes are used for occluding models (anywhere you can go behind the art, these are used to make your character disappear). I have no idea why they use fog to implement that though.
it is found in alot more places like stairways and even the game toilet etc (not just places where you can travel thru' the art pieces).
well they didnt know what youd be able to go behind depending on the camera angle, so they probably added occlusion anywhere they thought you might could even slightly go behind something maybe depending on if the camera was lucky.
(also if any other game entity might ever go behind it they may have occluded it)