[Runtime Bug]: Unreal engine gets stuck resizing window

[mmdanggg2]

Describe the bug

When resizing the game window it can often get stuck in a loop resizing back and forth between the previous and new size/resolution.

How do you reproduce the bug?

Run an Unreal engine game with a dx9 renderer, such as D3D9Drv or D3D9DrvRTX Get it into windowed mode and drag to resize the window around.

What is the expected behavior?

No response

Version

0.5.1+c099b404

Logs

NvRemixBridge.log d3d9.log UnrealTournament_d3d9.log

Crash dumps

NvRemixBridge.exe_20240814_194453.dmp

Media

https://github.com/user-attachments/assets/6f18e7ab-9419-4991-8cd2-fbe2751e6fc9

[NV-LL]

REMIX-3448 for tracking

[lvengesanam]

Few changes were added to fix issues similar to this last month.

@mmdanggg2 Could you test with bridge-remix binary from https://github.com/NVIDIAGameWorks/bridge-remix/actions/runs/10013926678 to verify if the issue persists.

[mmdanggg2]

Yes, that does seem to be ok with that version. Although after resizing for a little bit memory usage (RAM+VRAM) steadily increases and it becomes more and more laggy/unresponsive until it crashes.

[lvengesanam]

Could you test to verify if it causes a crash with dxvk-remix binaries from https://github.com/NVIDIAGameWorks/dxvk-remix/actions/runs/10426232995 which resolves issues with recreation of device and swapchain with change in resolution?

Noticed your fix under - https://github.com/NVIDIAGameWorks/dxvk-remix/pull/77. Could you verify if using binary from https://github.com/NVIDIAGameWorks/bridge-remix/actions/runs/10013926678 fixes the issue that you were trying to address?

[mmdanggg2]

Just tried it with those versions of dxvk and bridge. Still crashing after resizing a few times:

https://github.com/user-attachments/assets/9de4e99b-5f57-4d66-a11e-2db52c4baf59

NvRemixBridge.log d3d9.log UnrealTournament_d3d9.log

Interesting that is seems to end in VK_ERROR_DEVICE_LOST Also see this in event viewer:

Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Ampere, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: fc80ca55-f50b-42e4-bafd-be9184c7861b

Problem signature:
P1: 141
P2: ffffa30bc3139010
P3: fffff805509dfd80
P4: 0
P5: 45f4
P6: 10_0_22631
P7: 0_0
P8: 256_1
P9: 
P10: 

Driver 560.81 on W11 23H2 22631.4037

The crash when minimising from fullscreen seems to also be fixed but now introduced issues with double cursor and I'm unable to interact with the menus properly afterwards:

https://github.com/user-attachments/assets/a30dbe99-e9da-4e95-8a36-6d7aa40d9b2e

I think the game may be registering 2 clicks each time instead of 1.

[lvengesanam]

Thanks for validating with updated binaries.

With respect to the crash on resizing: Have noticed this issue several months ago on certain system with stock dxvk too wherein several rapid changes to resolution were made. Could you confirm if this occurs with stock dxvk ?

Will get back to you on the double cursor issue.

[mmdanggg2]

Had a go with dxvk 2.4 and it was happily scaling nice and smoothly for a while until I got bored so, safe to say not an issue there.

[lvengesanam]

Thanks for confirming. We are still looking into this issue.

With respect to double cursor seen, could you try setting 'client.DirectInput.forward.mousePolicy' to '0' in 'bridge.conf' to verify if it fixes the issue?

[mmdanggg2]

That helps but the issue comes back after minimising and opening it again.

https://github.com/user-attachments/assets/31e2fec5-1eb5-472f-a473-8cfc15ed1f2a

UnrealTournament_d3d9.log d3d9.log NvRemixBridge.log

[lvengesanam]

Thanks for all the tests. Double cursor issue with minimizing seems to be a new one, could you please file a separate bug for that.

We will be looking at both the issues.

[mmdanggg2]

Submitted that here: #591 Seems like the client.DirectInput.forward.mousePolicy = 0 option actually made no difference, just the newer bridge version.

[lvengesanam]

Thanks for creating a separate bug.

To confirm the newer bridge version resolves the double cursor issue prior to minimizing right?

[mmdanggg2]

That was not a problem before either, with 0.5.4, it works fine but crashes when minimising.

[lvengesanam]

Thanks for the confirmation. We will be looking into this.