Thinking about it now, it might be that being both regressions back to versions older than 5.0.0 beta/RC cycle they may not belong to this particular thread if that's the case please accept my apologies and tell me about so I can replicate this post into the main support forum.Īnd once again, thank you so much and all the best for WinUAE 5!ĮxecutePostDisk=uae-configuration cachesize 128 cpu_speed real cpu_throttle -420 cpu_memory_cycle_exact true cpu_multiplier 2 immediate_blits true Regression goes as back as 4.4.0, the last release where such an useful setting doesn't produce this effect.
Regression is 4.9.1 where it doesn't happen at all.Ģ.) 'Lionheart' main menu appears corrupt when using 'remove interlace artifacts' display option to get rid of interlace hell both there and in main game background effects. Always using QuickStart profiles, of course. I'm using 5.0.0 RC4 right now:ġ.) Intro screens in 'Agony' OCS/ECS appear completely distorted under ECS Agnus (or Full ECS combining Agnus and Denise). Now, I'd like to report a couple issues I've been noticing as of late. I'll see if I can isolate that code, but I'm out of time for today.įirst the first, thank you Toni for all the work you've been investing in such a milestone as 68000 cycle-accuracy is when it comes to proper Amiga emulation. The BTS demo triggers it when a particular AGA video state with 8 planes is enabled.
When the screen goes green, I can see all kinds of packed-pixel garbage and chunks of the display moving all over, so it appears to be some kind of DirectX buffer corruption going on and it's definitely not a problem on the Amiga side. If you switch between DX9/DX11 mode or software/hardware mode on-the-fly, the display is partially resolved, but there is still something internal that is messed up sooner or later the green comes back. It's apparently a DX9/DX11 issue, and it happens in both software and hardware mode. Just disabling whole program optimization in the FullRelease build resolves the issue.
Debug builds don't have this issue, and almost all optimizations (O1/O2) changes nothing. The "Whole Program Optimization" (/GL flag) seems to be solely responsible for triggering the green screen bug. I've found that this is related to the compiler optimizations. I found out some things about the green screen bug. BTS and Fantastic Dizzy AGA all green bug.
0 kommentar(er)
