3.5.2 MS Windows The Output 'Window' starts flashing if the output window is moved/dragged.

[tracyscott]

If I drag my output window (which has an ISF shader rendering to it normally), it flashes and jumps back and forth as if it is still being dragged from the starting position to the ending position of the drag even after dropping it in a final position. i.e. It sequentially redraws itself along the old drag path while flashing. It doesn't even require a scenario to be running. My laptop has dual graphics cards and the behavior is the same for both. I also have my display zoom set to 100%.

3.4.1 Seems to be working correctly.

[tracyscott]

Just an update on this. When running in 3.5.2, even without moving the window, once I start playing the scenario, the output window will intermittently resize in a flashing fashion. I tried 'Reconnect' on the device thinking it might be some bad initialization state and reconnecting does fix it. Reconnecting after moving the window also fixes it.

[tracyscott]

Another note, moving the window by the 'position' property doesn't trigger the behavior.

[jcelerier]

well that's the first time I see this. Can you share the file you have ? You are on win 11?

[tracyscott]

Yes, Win 11. It doesn't require any specific score file. I can trigger it on a new project with only a Window device added. I just add the Window device and then attempt to move it around. I just tested resizing the window and that also triggers it. It is like the window starts glitching and constantly resizing itself to all the sizes it experienced while dragging. Like the drag data points are accumulated somehow and constantly played back. The cpu usage goes from 0.4 with a normal window to 6.8% while it is constantly resizing the window.

[jcelerier]

could reproduce on windows, it works fine on other OSes. I don't have access to a win32 machine until next weeek to try and fix it, will look at it then