Desynced map

[Dominus41]

It seems that during gameplay if you pull up the map in the pause menu and look around before going back to the game, you'll find the map did not reset and is now partially desynced.

This issue is easy to reproduce and I also quickly found a workaround. To fix it, simply go back to the map screen and scroll through some points of interest use the toggle command before going back to the game, the map should be back to normal.

[LittleBitUA]

Nice repro, the screenshots make it obvious: the HUD minimap is showing wherever you left the big map panned to, not the area around York. The map viewer's scroll offset is leaking into the minimap and only gets reset when the map re-centers (which is what your point-of-interest toggle does).

One question that decides where I look: does it happen with a gamepad too (pan with the left stick, back out), and with 60 FPS off? If it's mouse/keyboard only, it's on my side - the recomp maps WASD and the mouse onto the sticks in menus and something may be left behind on exit. If it happens with a pad as well, it's the game's own map state and I'll reset it when the map closes. Either way it's fixable, just want to fix the right thing.

[Dominus41]

So first I guess I should mention that I'm using a french keyboard with an AZERTY keys layout as opposed to the more common QWERTY one. I did modify my keybinds accordingly, ZQSD as opposed to WASD.

Now for the follow up tests, I wasn't able to reproduce the glitch using a Xbox One gamepad but then I also started having more and more issues reproducing it altogether, even with my keyboard. When I first discovered it, I could trigger it pretty much with a 100% success rate (out of like 3 attempts before I decided to report it), but since your latest hotfix patch (1.2.1) its become more and more finicky to trigger. It's now come to the point where I've simply not been able to get it to happen in my last 2 boots of the game.
I also tried to switch between SLD and Ximput, but that didn't to have any impact.

I did however get to witness a brand new glitch while testing, I don't know if it's related to the map screen - although it would often happen after fiddling in it - but I'd sometimes get theses random glitchy flickering flashes on my screen, sometimes for minutes on end or until I restarted the game. It even filled my whole screen once.
I should also note that since these glitches have started, I haven't been able to desync the map.

EDIT: forgot to test it at 30 fps, might try it tomorrow.

[LittleBitUA]

Thanks for going through all that, the pad result and the "can't repro anymore" both help more than you'd think.

The flickering green boxes are a different (and more interesting) bug than the map. Those boxes sit exactly where UI panels get drawn, and the dithered rainbow edges are the signature of a render target being read back with the wrong pixel format: the game renders the scene in a 10-bit HDR format and the UI in plain 8-bit over the same memory, and the emulated GPU has to convert between the two when the game switches. The default "ROV" render target path does that conversion with some bookkeeping of mine, and when that bookkeeping loses track you get panels blended over garbage. Not your AZERTY layout, not SDL vs XInput.

Two things that would nail it, whenever you get a chance: in the launcher, Graphics → Render Target Path → RTV (compatibility), and see if the flashes ever come back (that path uses the emulator's own conversion, so if they're gone, it's mine to fix in ROV). And if you catch the flicker again, the log from that session (logs\deadlyprem_XXX.log) would be useful.

The map desync I'll keep watching; if it only ever happened with keyboard panning, it'll be something in how the recomp feeds WASD into the map's stick input.