it says this everytime STATUS_ACCESS_VIOLATION.
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Arma 3 Activity
Sep 19 2021
hi it is doing the same to me and i have tried all recommended steps but still with same error
o and im new to this game so i cant even continue the campaign
Sep 18 2021
I believe this was introduced with Contact. My impression is that the cause is the physics hitbox of the wreck model being extended well below the visual model and clipping into the ground - you can also find the wrecks appearing to float in some circumstances.
Bug still exists in the latest version
This is caused by the following line:
Sep 17 2021
I'm really sorry you are not happy with the fix we applied in 2.04, I haven't seen any complains except yours, so this was unexpected. I have re-downloaded 2.02 to compare, and while it is true, when optics are brought up, the movement is artificially restricted to stay within the screen boarders, this was the culprit for initial issue of unusable deadzone. At the moment the free swing is constant between all types of optics and sights, meaning, if you find 2 objects at a distance deadzone apart, the range of the barrel free movement before your body starts turning will be identical whether it is no sights, iron sights, optics or zoom in any of the above. This makes it consistent and usable. in 2.02 optics and zoom movement was limited to the screen borders, so if you would point your weapon at an object at the edge of deadzone and then zoom or bring up the optics, your aim would jump towards the screen center and you end up aiming not where you were pointing. After 2.04 you actually are aiming where you pointed.
This was fixed in 1.84. (With a citation of this very ticket! https://dev.arma3.com/post/spotrep-00081)
Sep 16 2021
but there was no reason as everyone is free to adjust it to their liking
As intended. You can move deadzone slider to about half. I could have forced lowered it more so that the sights would never leave screen, but there was no reason as everyone is free to adjust it to their liking
Sep 15 2021
Should be fixed since rev 148197
Cannot repro
Sep 14 2021
fixed in rev 148195
AH-64D Apache mod dev here, agreed this would be great! I am currently in the process of moving our mod across to this, and the 50 values is definitely a tight squeeze for us too - we aren't able to move all of the parts of the pages across to the new method because of this and are working on a hybrid approach, and multiplexing the different MPD pages so we can reuse values.
game keeps crashing cant get it to work no matter what i do.
Sep 13 2021
plz help cant figure out how to fix
Sep 12 2021
I’ve passed your ticket to our config person let’s see what they say
If set last value in envelope[]={}; config entry less or equal to 1 it will not climb. But there is still "bump" at 125% maxSpeed. It will descend but rate will be less than at 120% maxSpeed. Also speed display will not turn red.
Hi, Ive just tried with katiba in mp and sp, no problem, firemode stays full auto when getting out. Could you post detailed steps how to repro the bug please?
Indeed, at small downward angle after max speed reached the UAV starts rising. Interesting bug but it is burred deep in physics simulation so not fixable at this time.
I wanted to add that standing on top of rock objects in particular seems to really tank FPS.
Sep 11 2021
If you read my original post, I have tried everything under the sun aside from a full system restore..
Thank you for your report, we'll look on it.
my game crashes on startup
Seems to me that these are working fine, thanks once again :)
Your game display resolution might be misconfigured
Sep 10 2021
rev 148193
I've just found one more tunnel in the hills, and on that one I observe the same behavior on the south entrance (Grid ref 109-100)