Backgrounded map = CPU/GPU stress

[jaking]

Systems - various different Windows 10 clients

CPU and GPU usage is much higher when maps are set as background. This becomes a problem where there is a lot of LOS and big maps, weaker PCs can't cope. Putting the map back into a free window fixes it.

[Moon Wizard]

There is a known issue in v4.0.10, where the background map actually is much larger than the tabletop view. As a workaround, if you resize the whole "application" window after sending to background, it will help greatly with this, as well as restoring the panning control in the lower right corner of the background image window.

This is addressed in v4.1 that is currently in beta testing.

Regards,
JPG

[jaking]

Great to hear it's fixed, I'll try to workarount until we update.