Quote:
Originally Posted by FrodeSolheim
Well, it's a bit interesting if the problem does not exist in 1.0.2 either, but 1.1.x got updated WinUAE code, so the autoscaling algorithm has probably been tweaked a bit. I might have a look at it, but it hasn't high priority now. -And changing the autoscaling code might break other cases.
One possibility, if no other suitable fix is found, is to add a hack to specifically detect this "error" and hardcode a fix for it, since these scaling parameters are not likely to be correct in other situations either. Not a very elegant solution. I'll see what I do..
|
Yes, I think there are more important issues than this one, and maybe it should be adjusted in WinUAE as well in that case to keep the source in sync. At least I know what causes it and there is a workaround. Thank you so much !
Wei-ju