Might be related to: https://feedback.bistudio.com/T128002

Sorry for the late reply. We will have a look at it and see what can be done about it.

No, no we already fixed it. :)

Ok, thank you for letting us know.

Hello greepi1.
We have moved the character for you and it should not be stuck any more. In case there are any issues with the character still, please let us know under this ticket.
Regards,
Geez

hello, thank you for the response.

Unable to reproduce on RC 1.82, everything is working fine.
Try downloading the 1.82 RC and testing the issue.

The issue remains for me in both the RC 1.82.144547 and Dev 1.83.144562 builds.
7.1 USB wireless head set.

Use Arma3Update182RC as beta code in steam

In T124112#1671489, @TheMasterofBlubb wrote:

Hey guys can you try the dev and RC build. I yesterday played with a friend and he was sure he had not the bug anymore

Ok I replayed mission & no problem experienced, maybe a glitch. Thanks

http://steamcommunity.com/profiles/76561198151286714/

Hey guys can you try the dev and RC build. I yesterday played with a friend and he was sure he had not the bug anymore

Not to point out the obvious, but the problem still stands. I know this is obviously a very complicated problem as this has taken over a year to try to solve but the least we could get is an update :/ Or at least advise us in whether or not we will have to play 32bit for the remainder of the game's lifetime into ARMA 4

I’ve just got latest update and this issue seems to have now been resolved.

Interesting I tested this in our internal, dev build and the RC and without any errors. Are you sure you did not do anything specific?

In T127963#1671324, @Wulf wrote:

I just tested this in our Dev Branch and it works could you please test this in the Dev Branch if the issue is present? Also did you use set waypoint or a different command?

Thank you for the report, we will have a look at it.

Just tried it on the current dev build and it didn't work. Assuming that it's been fixed.

Thank you for confirming.

Just to make sure about the severity of the problem, as soon as you "properly" turn in (wait until the end of the animation) then turn out, everything is back to normal.
the problem occurs when you turn in >then< before the anim is done, turn out.

"Seems evident that you are just here to wind people up"

@Nordic_Harold the system in Vbs 2 would be cool. But for real digging (with shovel) Arma 3 maps are made of triangle so you would always dig giant triangles

Ok, closing. :)

In my opinion, the same keys could be used for adjusting the bipod legs as those for adjusting the turret height (which are also used for adjusting the periscope height on the Strider, for example). In the View category of the Controls configuration, scroll to the bottom and see "Raise turret" and "Lower turret".

The US Army field manual FM 3-50(90) has charts of electro-optical systems and the types of obscurants that defeat them.

The improvements to the DayZ animation system with "proper turning animations" seem very promising for accomplishing a fix to this issue in Arma 3.

VBS2 has had "ground cutting" for years. See this demo video. So this is possible on a technical level.

I confirm , it's now fixed

Does not appear to be present anymore :)

Has many duplicates -> T79285 T83321 T77860 T76277

1 moment

Either that or the positioning of the player is different in the internal build. Is the player's bipod on a slope that declines toward the enemy position and the player's body on a slope that declines away from the enemy position? Maybe you could record a video of how it looks in the internal build?

Desert_Foxtrot, though it seems evident that you are just here to wind people up, you did actually inadvertently help me by directing me, (through other facetious comments in other topics), to one of the other reports for the same issue, that is with actual helpful information from Wulf.

Nope can't reproduce this issue. It just always go where I point with the Vorona.

I just tested this in our Dev Branch and it works could you please test this in the Dev Branch if the issue is present? Also did you use set waypoint or a different command?

Could you please upload here the test mission you used?

Dev Build 1.83.144553 the issue seems to have been fixed. Can you please confirm it?

Have you already tried the possible solutions listed here?

You do realize that you are binding the same control to 2 different things and expecting it to work separately, right?

Hmm tested it and they seem ok. PCML locks as always, the only reason the Nyx and Titan wouldn't lock is that the target couldn't be detected by the IR trackers that both have. Will have a look at it further.

Aaah sorry my bad.

Tested it again. It seems that this issue is fixed in our internal build, will have to wait for the next Dev Branch and test it again if the issue persists.

Vitdom,
I did try to verify game content through Steam, nothing got detected. I re-installed arma 3, nothing changed. I've checked for pc updates and made sure Arma 3 is up to date. Is there a specific update I should check? I never overclocked my pc, I had built the pc myself. I used to be able to play Arma 3 without any problems, the last time I played Arma 3 was like 3 or 4 years ago on the current pc with the current pc parts. I have just tried a couple different MPs, it would load the game, I would select what team to be on and click start, got the error. The first MP I tried, I would walk a few feet and get the error. The second MP I tried, I spawned beside a heli, got in it, started the engine and got the error; it did like a small lag then the error popped up.

the mission should be in the additional information part, either way here it is again https://www.dropbox.com/s/kvelqqakewzn5j4/bis_pip_error.VR.rar

Here is a video demonstrating the problem. I took my hand off the mouse (so that I didn't accidentally change the direction that the player was facing), pressed the key to go prone, pressed the key to deploy the bipod and then held Alternate to look at different angles. Clearly the player is hovering in the air, supported only by the bipod.

Hey, thanks for the report! The compass/veh.radar has been removed as a part of sensor overhaul. You can get the heading information directly from diegetic elements or from the info panels (GPS panel, Radar display) - those can be displayed by left or right square bracket [ ].

The AT Nyx,
The Titan short
and the PCML

I think some kind of player controlled setting would work.

Thank you for the report, we will have a look at it.

Thank you for the report. We are aware of the issue, however this was done for performance reasons. The game was more unplayable with overdraw distances knocking the FPS down as much as 10. This was introduced as a way to combat that, we are aware it is not perfect. Perhaps some tweaks may happen in the future though can't promis anything.

Couldn't reproduce on the RC of 1.82.

I have tested it in your attached mission and I was not able to reproduce the issue. Could you please provide a video of the issue so that I might figure out what I am doing differently?

Thank you for the report. Could you please upload the mission you used for the test?

In T127981#1671229, @Vitdom wrote:

Were you presented with any error message when Arma 3 crashed?
Did you verify game files through Steam?

Were you presented with any error message when Arma 3 crashed?
Did you verify game files through Steam?

Same goes for AcinPknlMwlkSrasWrflDb

Still reproducible as of 1.80.

No addons!

CPU: E3-1230 v2
Graphics card: Nvidia GTX 1060 6GB
RAM: DDR3 12GB