NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix
[Runtime Bug]: Access Violation in nvngx_dlssd.dll During Call to NVSDK_NGX_SetInfoCallback. Crash on 3D Content Loading.
@nv-ajaus is already working on this.
Since Aug 14, 2024.
- Dominant language
- No language data
- Stars
- 1.7k
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.