Missing redraw or missing configuration in my rio config

[mcctuxic]

Hi,

I open rio fullscreen. Then I open another application with a window...say xterm...which starts as a small window on top
of rios window. If I resize of move the xterms window, I got something like a "mouse trace" ... or better: "window trace" drawn
on rios window, which does not vanishes automagically and remains static.
Pulling rios window to the upmost layer on top of everything else, the traces are removed by a window redraw.

Did I need to adapt my configuration - for example for haveing a certain video card - here...how can I avoid this effect,
which does only appear in conjunction with the usage of rio?

Cheers!
Tuxic

[TheusHen]

Hi,

I don't think this is related to having a specific GPU or to a missing graphics configuration.

From the behavior you describe, this looks much more like a redraw/exposure issue: when xterm is moved over Rio, the area underneath it is exposed again, but Rio apparently does not repaint that region immediately. The old contents of the surface then remain visible until another event causes a full redraw, which would also explain why bringing the Rio window to the top clears the artifacts.

Rio uses a GPU-rendered surface and its Linux rendering path has had a few changes specifically around damage tracking, occlusion and redraw scheduling. In particular, X11/Wayland now have a vsync-driven redraw path instead of relying exclusively on terminal output to trigger frames.

As a quick diagnostic, you can also try:

[renderer]
strategy = "game"

That forces continuous rendering, so if the trails disappear completely, it would strongly suggest that the problem is in the repaint/invalidation path rather than the GPU itself. It does use more CPU/GPU, so I would only use it as a test/workaround.

I would also recommend testing with the latest Rio version, since the rendering/event-loop code has changed considerably between older releases and the current codebase.

If the problem still happens on the latest version, the most useful information would be:

• Rio version
• X11 or Wayland
• Desktop/window manager and compositor
• GPU + drive
• whether strategy = "game" changes the behavior

The fact that the artifacts disappear as soon as Rio is redrawn makes me think this is worth investigating in the X11 repaint/exposure path rather than as a hardware requirement.

Cheers!