Flame 2025 Remapping Wacom Area - Rocky 9.3

Flame Flame Questions
1

Rocky 9.3 - Dual 4k monitors. When I’m in the Desktop environment, the span of my Wacom is mapped correctly across both monitors. When I enter Flame I can see in the terminal that it’s mapping my area to 1/2 the size it should be (22400 instead of 44800) so I’m losing 1/2 my tablet’s workable area.

I’ve been using this exact setup in Flame across CentOS, earlier vers of Rocky and many versions of Flame without issue. Now that I’m trying to use it on my new Fury, Flame 2025.0.1 on Rocky 9.3 is not treating the tablet correctly.

Does this ring a bell for anyone (my Gnome scale is 100% btw)? Does anyone know where Flame grabs this info for startup and is it possible to change it?

Executing command: /bin/sh DISPLAY=":1" /usr/bin/xsetwacom --set "Wacom Intuos Pro M Pen stylus" Area 0 0 22400 29600

I don’t see it in init.cfg and have looked a lot of places with no luck.

Thanks in advance for any thoughts…

2

PS - I have opened a case with support, but figured I’d see if this rings a bell with anyone in the community just in case.

3

It is a known issue, and being addressed outside of this forum.
Bug FP-03206.

@Slabrie

4

Thanks Alan,

Do you think this is the same issue? My Gnome desktop is set to 100% (Flame is at 110% Magnification) and I still have the issue.

My only fix seems to be to constantly run the “xsetwacom set” to override the Area to the correct settings whenever Flame forces it back to the wrong ones - Which seems to be whenever some sort of UI overlay is displayed, like clicking on the FLAME menu in the lower left, or context clicking.

5

I’d pursue that with support using the bug ID I gave you. The proper people are well aware of the issue.

1 Like
6

Thanks Alan.

I’ve updated that defect with my notes. Does manually overriding Flame with the correct Wacom setting in Terminal fix the issue on your end?

If so, I wonder if running that command via a script every second or so would create a noticeable hit to performance and might temporarily “fix” the issue until a more permanent solve is found.

7

Hi.

Is there some update of this?. I have same problem. First in 2025.0.1. After update to 2025.1 2025.1.1, I see the issue still there. Rocky 9.3.

Preference is always reset to “Primary monitor”, although I set it to “both monitors”.

I could check how in the preference file /name of user/status/PointerUICurrent.json , where I guess this preference is stored, “pointerTabletMonitors” is always set to ¨1¨ no “matter if both monitor” is selected in preference.

"Settings": [
    {
        "name": "PointerThreshold",
        "value": 5
    },
    {
        "name": "PointerMarginLock",
        "value": false
    },
    {
        "name": "PointerMarginLeft",
        "value": 0
    },
    {
        "name": "PointerMarginRight",
        "value": 0
    },
    {
        "name": "PointerMarginTop",
        "value": 0
    },
    {
        "name": "PointerMarginBottom",
        "value": 0
    },
    {
        "name": "PointTabletMonitors",
        "value": 1
    },
    {
        "name": "PointerUIUseSystemStylusButtons",
        "value": false
    },
    {
        "name": "PointerUseMouseCursorSkinForMouse",
        "value": true
    },
    {
        "name": "PointerUseTabletCursorSkinForTablet",
        "value": true

There is a new (for me) shorcut to change this in 2025 (meta+tab). I am not aware that this shorcut existed for previous 2025 versions because I did not have this problem. But is highly annoying setup this on every flame start.

As an extension of the issue, flame also clear any assignment to the wacom function buttons, (tablet buttons, not pencil buttons) .This reset remains even after flame quits. It only works after a reboot and no starting flame. I would like to use these buttons in flame and for more apps.

8

This issue has been fixed in 2025.0.2.

9

Hi @Slabrie . As I mentioned, I updated to 2025.1.1 , with same issue.

10

From what I see on our side the fix is also available in 2025.1.1, which is different than 2025.1.

11

Ok Stéphane. I updated to 2025.1.1 , not 2025.1.

12

Please open a ticket with our Support team so they can investigate the issue.