vinegarhq/sober

Default cursor disapears with deduplication flag (pointer and text cursor works)

Closed this issue · 1 comments

Acknowledgement of checking existent issues

  • I have checked if my issue has already been reported, and I am certain that my problem has not already been addressed.

What problem did you encounter?

Fair warning: might be nvidia!

Some info to set the scene:
Newest sober version (as of posting) with automatic download selected.

System info:

Kernel: 6.9.12-3-MANJARO
DE: Plasma 6.0.5
CPU: Intel i7-8700K (12) @ 4.700GHz
GPU: NVIDIA GeForce RTX 3060 Lite Hash Rate
Memory: 16Gb

Running nvidia 555.58.02 non-proprietary driver (from nvidia-all)
Running wayland with enviroment values of:

QT_QPA_PLATFORMTHEME="wayland;xcb"

GBM_BACKEND=nvidia-drm
__GLX_VENDOR_LIBRARY_NAME=nvidia
ENABLE_VKBASALT=1
LIBVA_DRIVER_NAME=nvidia

WLR_NO_HARDWARE_CURSORS=1

Working flags:

{
    "DFFlagDisableDPIScale": false,
    "DFIntTaskSchedulerTargetFps": 120,
    "EventStreamBatchSize": 100,
    "FFlagAdServiceEnabled": false,
    "FFlagDebugDisableTelemetryEphemeralCounter": true,
    "FFlagDebugDisableTelemetryEphemeralStat": true,
    "FFlagDebugDisableTelemetryEventIngest": true,
    "FFlagDebugDisableTelemetryPoint": true,
    "FFlagDebugDisableTelemetryV2Counter": true,
    "FFlagDebugDisableTelemetryV2Event": true,
    "FFlagDebugDisableTelemetryV2Stat": true,
    "FFlagFixGraphicsQuality": false,
    "FFlagFutureIsBrightPhase3Vulkan": true,
    "FFlagGameBasicSettingsFramerateCap5": true,
    "FFlagHighlightOutlinesOnMobile": false,
    "FFlagHighlightsIntegratedWithGFX": false,
    "FFlagTextureDeduplicationByHash4": false, #if true = problem
    "FFlagUserHandleChatHotKeyWithContextActionService": true,
    "FIntRenderMeshOptimizeVertexBuffer": 10
}

Steps to reproduce:

  1. Set FFlagTextureDeduplicationByHash4 to true.
  2. Go to any game where you can rapidly change the cursor type (easiest: natural disaster survival, hover over "I'm ready" repeatedly)
  3. Cursor gone.

Bug works in other games too, harder to reproduce.

Workaround so far:
Don't use that flag or set to false.

Roblox Experience link

No response

why are you setting it to true? it was set to false by default to workaround this bug