Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Arma 3 Activity
Jun 19 2023
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
I have 32GB RAM
and 11GB GPU mem
wiki error.
There is no viewDistance server config setting, nor in difficulty.
Tested in singleplayer, local hosted MP (where I am host and player) and dedicated server.
All the same.
Can you actually reproduce this without mods?
I tried with a prowler gunner, I get kicked back out to zeus after the unit is dead, but I have no problem after that, movement still works fine.
Well the log files aren't useful, they just stop, no actual crash report 🤔
There are only two log files in that report, and both show that you have been playing just fine without any crash.
I don't know whats happening here, if I see it right its a crash inside Microsofts own code.
You can launch the arma3_x64.exe from game directory manually.
Memory allocation failure? maybe ran out of ram?
Please pack mdmp's as .zip files, it saves alot of space.
Selected Audio Output: Øretelefon (6- Arctis Pro Wireless Chat) - Channels: 1, Freq: 48000
Thank you, it was bad remoteExec script code loadfile (fom\" + "ttt.txt")
and a missing check in diag_stackTrace
"EZFRD64" I don't know what that is, but its crashing you..
Its not part of our game, you can try googling that name, it will be some software you have installed.
This is a old crash that we've been tracking for a while. We have no idea why it happens and we cannot reproduce it, it seems to only happen randomly after a long time of playing. Which makes figuring out the cause extremely hard.
Crashed in Microsoft's XAudio2_7 code. Not much we can do about that
I know this bug and we've been tracking it for a long time, but we are unable to reproduce it or figure out why it happens.
It happened in this case during drawing map icons and loading their textures.
This seems to only occur rarely and randomly, very hard to track down.
Well the RPT spam is not new 😢 That code is atleast 5 years old.
GPUName was removed due to privacy concerns.
Arma units was offline on the weekend, that happens somewhat regularly.
Jun 18 2023
Jun 17 2023
In T170533#2414297, @dedmen wrote:13:16:50 DX11 error : CreateTexture2D failed : DXGI_ERROR_DEVICE_REMOVED
13:16:50 DX11 - device removed - reason: DXGI_ERROR_DRIVER_INTERNAL_ERROR
13:16:50 DX11 error : CreateTexture2D failed : DXGI_ERROR_DEVICE_REMOVED
13:16:50 DX11 - device removed - reason: DXGI_ERROR_DRIVER_INTERNAL_ERRORSomething is wrong with your graphics drivers or graphics card.
Try updating your graphics drivers.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Jun 16 2023
both are max zoom in
issue https://feedback.bistudio.com/T158796 seems to be directly related, if not exactly the same problem which causes this.
Found some pertinent information about the strange performance limitation present in our Huey fleet:
Jun 15 2023
Jun 14 2023
Seems to be affecting say3D as well:
https://forums.bohemia.net/forums/topic/239226-say3d-distance-issues-playback-stopping/?tab=comments#comment-3462730
wrong animation, wrong side of ejection, wrong 3d model it has the safety engaged
Jun 13 2023
The update did not fix the above "MUTE" voice protocol error.
"Players" use American English, they are not silent.
If it's not possible to fix it, maybe just remove it and give all Asians the VIE voice protocol? VIE is working fine.
Issue 1 is fixed in 2.13/2.14 150692
Also next profiling branch build, probably early next week
Issue 1:
Issue 2:
To explain what we're doing and why the error is happening:
Looks like you have a config error.
You have magazine both in "player" and "close/short/medium/far" modes of a weapon.
Just stop doing that?
What a bummer nobody ever fixed this. Guess there's no chance now.