[Runtime Bug]: Access Violation in nvngx_dlssd.dll During Call to NVSDK_NGX_SetInfoCallback. Crash on 3D Content Loading.

[lotexiu]

Describe the bug

A bug occurs where the game Pangya (Anime Golf Game) crashes when any 3D content is loaded after startup. Initially, the game starts, and the login screen with its content is rendered correctly. However, after logging in and reaching the game menu, any action that involves changing 3D elements causes the game to crash.

The way I installed rtx-remix in the game was to download the zip file releases and extract all the files in the game folder where the game's ProjectG.exe executable is located.

To make d3d8to9 work you must rename it to d3d8 and to get the game you can access this link, it is not official but a pirated one. The game is not paid but it is a dead game, which had its website and server closed in 2016

In any case, below in the next comment of this issue, there will be a step by step guide on how to download, install rtx-remix in the game and in any case how to create an account in the game. comment

Bridge-remix issue for more details https://github.com/NVIDIAGameWorks/bridge-remix/issues/13

How do you reproduce the bug?

Start the game. Complete the login process. Click on the "Family Mode" option in the menu.

What is the expected behavior?

The runtime should handle 3D content changes seamlessly without causing the game to crash.

Version

0.5.4

Logs

exception.log d3d9.log ProjectG_d3d9.log NvRemixBridge.log

Crash dumps

NvRemixBridge.exe_20240810_201752.dmp exception.dmp

Media

With D3D8TO9 + D3D9.DLL

https://github.com/user-attachments/assets/c09e5d0e-a594-4130-bbf3-400c8dbf2c3f

Only D3D8TO9

https://github.com/user-attachments/assets/94e04fca-0bb4-42a9-9119-9ae38f0bc86e

[lotexiu]

Tutorial Pangya download and RTXRemix

Game Tester Account TestPlayer 123456

[nv-ajaus]

Hello @lotexiu , I made a change to fix an issue where a crash in dxvk-remix can crash again during DLSS deconstruction, which masks the original issue, leaving a NvRemixBridge crash dump file (.dmp) that we can't use to track down the original crash. I noticed that the dump file provided with this GitHub ticket seems to show a symptom of this. If and when you can, please reproduce the crash you previously reported using the latest dxvk-remix release build here (https://github.com/NVIDIAGameWorks/dxvk-remix/actions) or the build for the specific commit I made https://github.com/NVIDIAGameWorks/dxvk-remix/actions/runs/10118513607/artifacts/1745781365 , and upload a newly generated .dmp file.

Thank you!

[lotexiu]

@nv-ajaus Hello, I will perform the test now with the latest version you mentioned and with the commit you made to see if it occurs and send the dmp file. Thank you for your help.

[lotexiu]

Version: 33e8c58-619 (Last version) d3d9.log exception.dmp exception.log NvRemixBridge.log ProjectG.exe-up.txt ProjectG_d3d9.log

Version: 53b0bdc-599 (Commit version) d3d9.log exception.dmp exception.log NvRemixBridge.log ProjectG_d3d9.log

[lotexiu]

uhmm, do I need to do anything else or do I just need to keep waiting? I'm testing the new ones and seeing if some will work

[NV-LL]

Hi @lotexiu - thanks for the logs, and we apologize for the wait. We've opened REMIX-3533 for investigating this issue.

[lotexiu]

Alright, if you need it i can make tests here. And where i need to go here to find the Remix-3533? its in the actions tab? beacuse i dont see into the branches, releases or the actions

[NV-LL]

The Remix number is for our internal ticket tracking purposes; it's not public-facing. We'll definitely let you know here if we need any re-tests done or have any other questions for you! Thanks!