Memory Read/Write Error - Remix Server Setup

[JP111555]

When Remix tries to boot up 18 Wheels of Steel: Extreme Trucker 2, it throws this error on the server side Exception 0xc0000005, a memory read/write error.

• When I try to boot into the game using Remix. It hooks into the game but the Bridge server refuses to create and crashes immediately causing an eventual Black Screen crash to the game.

• Remix 0.2 - Stable

• RTX 3060

• 531.79 - Game Ready Driver

• Game - 18 Wheels of Steel: Extreme Trucker 2

• Build 1.0 - Steam

Logs To make this easier to reproduce, I will keep all bridge settings and additional files I used in trying to circumvent this at their defaults as they don't seem to impact the outcome of the bug.

• NvRemixBridge.log
• d3d9.log
• extremetrucker_d3d9.log

To Reproduce Steps to reproduce the behavior:

1. Go to 18 Wheels of Steel: Extreme Trucker 2 Config file (Found in documents under C:\Users\USER\OneDrive(if you have it)\Documents\18 WoS Extreme Trucker 2\config.cfg) and paste this in: config.txt Changes engine to DX 9, forces windowed screen and also should set graphics to minimum, however you may have to do that yourself
2. Save config.cfg
3. Go to 'Steam'
4. Click on 18 Wheels of Steel: Extreme Trucker 2, or click on it's .exe file in file explorer
5. Navigate to the game files under 'C:\Program Files (x86)\Steam\steamapps\common\18 WoS Extreme Trucker 2\bin\win_x86'
6. Navigate to the bridge log under .trex folder
7. See error

Expected behavior Upon clicking 18 Wheels of Steel: Extreme Trucker 2, the game will briefly show a white screen before turning black then crashing with no error messages popping up after.

Screenshots

---

White Screen

Black Screen Black Screen does not allow me to take a screenshot. But it comes after the white screen. Waiting times for the screen to appear black vary

[NV-LL]

Hello! Will you please test this on the latest release and let us know if the issue persists? Thank you!

[NV-LL]

Thank you for reaching out. We're going to close this ticket due to an extended period with no response. If the issue persists for you on the latest build, please open a new ticket.