Jump to content
sw1ne2001

Workbench crashing when opening world files

Recommended Posts

Reaching out to the hivemind. Anyone else having this issue?

 

It seems to only affect the workbench when I try to open world files, particle editor or other tools that use the video driver. The Reforger game runs perfectly fine. Open a world file and crashes every time, occasionally it will run for a second or two and display the world, then it crashes. I was hoping the update today would help but it would seem not. 

 

Anyone got an idea for a workaround? It crashes from trying to illegally write to memory which seems directly correlated with a graphics driver issue (i'm up to date).

Share this post


Link to post
Share on other sites

Yes this is happening to myself as well i was planning on making a co-op mission that i started last night and now cant even access the world editor without it crashing.
this is happening after the Update today.

Share this post


Link to post
Share on other sites

Little update: please see what may be causing the issue, my card / driver should support and is running dx12 but the CLI of workbench is starting dx11? I can't find any reference in a config file or indeed any documentation for switches applied when running the executable from steam. Anyone got a clue? My bold and italics on the last lines of the crash.log

 

Log C:\Users\Q\Documents\My Games\ArmaReforger\profile\crash.log started at 2022-06-08 20:21:02 (2022-06-08 19:21:02 UTC)

------------------------------------
DESKTOP-IPDI99N, 08.06 2022 20:21:02
Unhandled exception

Program: F:\Steam\steamapps\common\Arma Reforger Tools\Workbench\ArmaReforgerWorkbench.exe
Reason: Access violation. Illegal read by 0x7ffacc4c20b5 at 0x28

[NVENCODEAPI_Thunk]: ??? addr:0x7ffacc4c20b5
[NVENCODEAPI_Thunk]: ??? addr:0x7ffacc4c1197
[OpenAdapter12]: ??? addr:0x7ffaccfdfabc
[OpenAdapter12]: ??? addr:0x7ffaccfe2b99
[D3D12GetInterface]: ??? addr:0x7ffabc009d2e
[zlibVersion]: ??? addr:0x7ff6c376edea
[zlibVersion]: ??? addr:0x7ff6c3772bff
[zlibVersion]: ??? addr:0x7ff6c35a5d7c
[zlibVersion]: ??? addr:0x7ff6c369941c
[zlibVersion]: ??? addr:0x7ff6c36e12a6
[zlibVersion]: ??? addr:0x7ff6c3bb68b1
[zlibVersion]: ??? addr:0x7ff6c3bb1710
[zlibVersion]: ??? addr:0x7ff6c364a07a
[zlibVersion]: ??? addr:0x7ff6c364ae1b
[zlibVersion]: ??? addr:0x7ff6c3522bf6
[BaseThreadInitThunk]: ??? addr:0x7ffb11ad7034
[RtlUserThreadStart]: ??? addr:0x7ffb12682651
[RtlUserThreadStart]: ??? addr:0x7ffb12682651


(Press Retry to debug the application - debugger must be attached)


Workbench mode
CLI params: dx11  

 

 

Share this post


Link to post
Share on other sites

Hey man. I'm getting the problem you're getting. Have you got this sorted out? My error looks like yours except at the end of the crash file where it says workbench mode, nothing is under there for me. 

Share this post


Link to post
Share on other sites
On 8/18/2022 at 2:58 PM, TheRealTDog said:

Hey man. I'm getting the problem you're getting. Have you got this sorted out? My error looks like yours except at the end of the crash file where it says workbench mode, nothing is under there for me. 

 

Nope, tried running it with and without -DX12 switch from steam launcher, slightly different error message progression on no -dx12 switch but essentially the same, I can create projects but as soon as I go into world editor, particle editor, sound editor, animation editor it will crash...

 

I can use script editor, behaviour editor, procedural animation editor and string editor without issue leading me to believe that any editor which is trying to render the graphics in real time is causing the crash, common thing is the video and memory as far as I can see. No update from the myriad of crash files sent via the crash tool..

Share this post


Link to post
Share on other sites

You can try going to your project folder, making a complete backup. Then remove all custom particles addons prefabs ect. Add them back slowly and test until you find the file the workbench doesn't like. I had to do that a couple times. If you are lucky you can see the file name that causes the problem in the console log or error log in your profile folder.

Share this post


Link to post
Share on other sites

The tool crash all the time, when you open anything, editing a asset, etc, it's very unstable.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×