I suggest you check your memory consumption of PC and grafic card. Maybe it is constantly rising until the game crashes. You can also try to lower resolution or in game texture quality and see if you can play longer. Saying that, I doubt it is katanga's fault.

Glad to hear the game is mostly working for you. I don't have access to the game at present, so cannot test directly.

As @Cer notes, it's not likely to be a Katanga issue. I know for certain that we don't leak memory in Katanga, because I already profiled that. Check your VRAM and also RAM while playing and see if it keeps growing. It should be stable.

The mechanism that we use to connect to the game enforces a DX9Ex device instead of the usual DX9, and it's possible that this makes the game take a different path and leak memory or introduce a bug. The DX9Ex is the reason some DX9 games don't work in HelixVision.

Would also be worth checking NexusMods to see if there are any loaders or ways to change the game behavior that might help. Sorry I can't be of much help here.

BTW, I'm happy to take a look at the log files after you crash.
%appdata%\..\LocalLow\Katanga\Katanga\output_log.txt
%appdata%\..\LocalLow\Katanga\Katanga\katanga.log

If we are getting some sort of error it will be reported there.

Originally posted by Bo3b:

BTW, I'm happy to take a look at the log files after you crash.
%appdata%\..\LocalLow\Katanga\Katanga\output_log.txt
%appdata%\..\LocalLow\Katanga\Katanga\katanga.log

If we are getting some sort of error it will be reported there.

Here is the log after the game autoquited. This time it lasted only 5 mins:
The output log:
Initialize engine version: 2017.4.26f1 (3b349d10f010)
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce RTX 2060 (ID=0x1e89)
Vendor: NVIDIA
VRAM: 5967 MB
Driver: 27.21.14.5167
Begin MonoManager ReloadAssembly
- Completed reload, in 0.028 seconds
<RI> Initializing input.

<RI> Input initialized.

<RI> Initialized touch support.

OpenVR initialized!
The referenced script on this Behaviour (Game Object '_Stats') is missing!

(Filename: Line: 1758)

UnloadTime: 0.858400 ms
<b>[SteamVR]</b> Successfully loaded 22 actions from action manifest into SteamVR (F:/steam/steamapps/common/HelixVision/Tools/Katanga/actions.json)
<b>[SteamVR]</b> Initialized. Connected to holographic:WindowsHolographic
Awake
CreateSetupMutex
RecenterHMD
UpdateCurve state: 0.5700006
Set environment state: 4
Sharpening state: 1 sharpness: 1.5
Hint state: 1
Start: Command line arguments: F:\steam\steamapps\common\HelixVision\Tools\Katanga\katanga.exe --game-path I:\Need For Speed Hot Pursuit\NFS11.exe --game-title Need For Speed: Hot Pursuit --launch-type DX9
--game-path: I:\Need For Speed Hot Pursuit\NFS11.exe
--game-title: Need For Speed: Hot Pursuit
--launch-type: DX9
CurrentDirectory: F:\steam\steamapps\common\HelixVision\Tools\Katanga
Successful hook library Init
Launch type: DX9 for Game: NFS11.exe
...Launching suspended: I:\Mr DJ\Need For Speed Hot Pursuit\NFS11.exe
LoadAgent
Load GamePlugin
Successfully loaded F:/steam/steamapps/common/HelixVision/Tools/Katanga/katanga_Data/Plugins/GamePlugin.dll
Hook the D3D9.DLL!Direct3DCreate9...
Resume game launch: DX9
Restored Working Directory to: F:\steam\steamapps\common\HelixVision\Tools\Katanga
Launch EndOfFrame
-> Got shared handle: 80000b02
..eyes width: 5120 height: 1440 format: RGBA32
<b>SteamVR Interaction System</b> Headset placed on head
<b>SteamVR Interaction System</b> Headset removed
Sharpening state: 0 sharpness: 1.5
Hint state: 0
<b>SteamVR Interaction System</b> Headset placed on head
RecenterHMD
RecenterHMD
RecenterHMD
<b>SteamVR Interaction System</b> Headset removed
<b>SteamVR Interaction System</b> Headset placed on head
Sharpening state: 1 sharpness: 1.5
Hint state: 1
Hint state: 0
Hint state: 1
Hint state: 0
<b>SteamVR Interaction System</b> Headset removed

Katana log:
Thursday, February 25, 2021 @ 4:57:40 PM UTC


..Unity Native C++ logging enabled.

..Katanga:CreateSetupMutex--> 0000000000000A70

GamePlugin C++ logging enabled.

GamePlugin::OnLoad called
GamePlugin: OpenMutex called: 00000544
GamePlugin: Mapped file created: 03970000, val: 0x0
GamePlugin::OnHookAdded called [Hook: D3D9.DLL!Direct3DCreate9 @ 0x6CE14840 / Chain:1]
GamePlugin::HookDirect3DCreate9
..Katanga:OpenFileMappedIPC Mapped file created: 000001C10D870000, val: 0x0
GamePlugin::OnFunctionCall called [Hook: D3D9.DLL!Direct3DCreate9 @ 0x6CE14840 / Chain:1]
GamePlugin::Hooked_Direct3DCreate9 - SDK: 32
GamePlugin::HookCreateDevice
Returned IDirect3D9Ex: 01241FE0

GamePlugin::Hooked_CreateDevice called
Width: 2560, Height: 1440, Format: 21
-> CaptureSetupMutex mutex:00000544
WaitForSingleObject mutex:00000544, result:0x0
..Katanga:GrabSetupMutex: WaitForSingleObject WAIT_TIMEOUT err: 0x0
..Katanga:ReleaseSetupMutex: ReleaseMutex ERROR_NOT_OWNER
IDirect3D9->CreateDevice result: 0, device: 25DFB600
Create hooks for all DX9 calls.
..Katanga:GrabSetupMutex: WaitForSingleObject WAIT_TIMEOUT err: 0x0
..Katanga:ReleaseSetupMutex: ReleaseMutex ERROR_NOT_OWNER
GamePlugin:DX9 CreateSharedRenderTarget called. gGameSurface: 00000000, gGameSharedHandle: 00000000
-> CaptureSetupMutex mutex:00000544
WaitForSingleObject mutex:00000544, result:0x0
Width: 5120, Height: 1440, Format: 21
Successfully created new shared surface: 25D28E20, new shared handle: 80000B02, mapped: 03970000
<- ReleaseSetupMutex mutex:00000544
ReleaseSetupMutex mutex:00000544, result:OK
<- ReleaseSetupMutex mutex:00000544
ReleaseSetupMutex mutex:00000544, result:OK
..Katanga:CreateSharedSurface called. shared:FFFFFFFF80000B02
....OpenSharedResource on shared: FFFFFFFF80000B02, result: 0, resource: 000001C12008F6D8
....Successful GetDesc on surface - Width: 5120, Height: 1440, Format: 87
....CreateShaderResourceView on texture: 000001C12008F6D8, result: 0, SRView: 000001C1200F7A60

@Hiro: Thanks for the logs. Those look normal up until they are cut off by the crash, so they don't have the usual closing/dispose operations.

Nothing out of the ordinary there. The one thing I would definitely recommend trying- don't play at 1440p. That makes for a 5120 width double wide texture buffer, and there are some limits on textures for DX9 games at 4096. Might not be related but worth a try.

Outside of that, this looks like either a game bug or possibly a bug introduced by switching the device to DX9Ex. Would be worth seeing if other modders have improved game stability, or otherwise alter the game to make this work better.

Originally posted by Bo3b:

@Hiro: Thanks for the logs. Those look normal up until they are cut off by the crash, so they don't have the usual closing/dispose operations.

Nothing out of the ordinary there. The one thing I would definitely recommend trying- don't play at 1440p. That makes for a 5120 width double wide texture buffer, and there are some limits on textures for DX9 games at 4096. Might not be related but worth a try.

Outside of that, this looks like either a game bug or possibly a bug introduced by switching the device to DX9Ex. Would be worth seeing if other modders have improved game stability, or otherwise alter the game to make this work better.

thank for the response. I'll try it. Luckily, with the short duration of each races( usually from 4-8 minutes), it can be bearable with the autoquit annoyance