Well I only play on 1 server, so cannot say about other servers. But it happens to others too on that server.

In the VR after I moved from the first waypoint where targets pop up when you reach the waypoint.

@Wulf any updates on this issue? It has been in the wild for some 6 months now.

When exactly during the Bootcamp did the crash occur?

Interesting your dumps when it comes to MDMP there are none. Does this happen only on a specific server?

This is not an Arma 3 issue. Will move it to DayZ.

After some testing. Seems that the loiter waypoint is causing this issue, we will have a look at it.

Is that possible for to downgrade Arma 3 to a version prior to DLC Tanks ? (I mean the exe + datas) So I can test If I crash on this previous version ?

Since it's been more than a year now, is there any fix for this problem yet?

Thank you for the report. That is odd what specs does your computer have? Also, if you are experiencing crashes please send us your Arma report. Here is how to do that.

Another crash, same circumstances, same server, same mods, only this time the missile might have hit the vehicle.

Thank you for the report, we will see what can be done.

This would be more than useful, i am actually surprised that something like this was never included in the game.

Switching memory allocator to the default windows one (bad performance) seems to clear the error, but it keeps popping up after I switch back after some time.

@GRIDEFORT I support you. In general, lighting in the game - all flashlights and headlights is are useless. It will not light beyond 5-8 meters

Please create a folder with the suffix Altis and put the file in it. Thank you.

Getting bad_module_info error again.
Here's the log{F203276}

Please upload the whole folder not just the sqm. Thank you.

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

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

Could you please send us a new report with current dumps? We want to know if the issue persists even after the last update.

Should be fixed in next update.

Would be great to be able to edit missions as a group at the same time.

Hello, just wanted to note that the "Puppeteer" achievement is still bugged. Opened the editor, started a scenario with end trigger, selected a unit, right click, "Play as Character", played the scenario up to the end. But nothing. Game version is 1.82.144647.

Still no change with 1.82. I'm adding this post just to show the developers that this bug is still a significant pain for MILSIM practicioners.

I've incorporated the script from my mod into the mission...

Gladly! But before I do that, the script I'm working on is currently in the form of a mod. Is it alright if I upload separate PBOs for the mission and the mod along with repro steps, or would you rather I try to integrate my script into the mission?

Hmm. Could you please upload your mission here so that we might have a look at it?

Still seems to happen post 1.82, although I've had at least one mission where the markers did NOT disappear for me, but they DID for another player.

Respectfully, it doesn't. I've tested my script without the flyInHeight line and it still completely ignores the flyInHeightASL command. The result of...

This should be fixed in the next update.

@dmorchard if you remove _plane flyInHeight 100; it will work.

Yes and many little discrepancies with the usual experience in AAA games. Let us say, in infantry mode It is impossible to move diagonally in proportion to combining the signal from two axes. This is not a strong problem. I am most intolerant of cyclic collective adjust flexibleness. It should be a little nimbler: like would it now after first second of hold of button, just after pressing.

mas acontece de travar no meio da missão tambem

geralmente quando eu termino uma missão e começo a outra, assim que termina da missao o carregamento o jogo trava

Thank you for the report, I tested it and it should be fixed either in the next or the one after that update.

@madpat3 this ticket about UAV Darter which can't reach a traveling point.
For other problems with UAV Darter it is necessary to create other ticket with steps of reproduction of a problem.

Still broken.

Yep, just tested with dev branch 1.83 :

Tested it out with a joystick, still not able to reproduce the issue. Could you please send me a screenshot of your camera and vehicle settings?

Thank you for the report. We will have a look a it.

Thank you for the report, we will have a looka t it.

Thank you for the report, we will see what can be done.

So, if I understand right zous az that Xbox 360 controller has less sensitive X,Y view?

Please remove the -noLogs parameter so that we can see what is going on in the rpt files. Thank you.

Thank you for the crash dumps, but could you please tell us when does the crash occur?

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

Odd. Tested the mission in dev and stable version of the game. No crashes occured. Does the crash occur to you when you switch to the dev branch?

Thank you for letting us know.

Finally got a FIX!

P.S: Not running any mods, just Vanilla ArmA, I've done the Steam option to fix the files, Did nothing.

Update, i Think the problem is linked to my joystick when i have it connected. Might be interfering with zoom in button i have linked on joystick, i have zoom in binded to shift+q and e (zoom in and out), seems to be interfering with the Ctrl + Q and e (turn in and out). It shouldnt be affecting eachother but seems like the ctrl or shift input first doesnt do a difference so it becomes problematic. Or if its a problem connected to joystick throttle im not sure but its defenetly connected to joystick somehow. Maybe you could test it out that way. This should be the problem.

by the way in the vehicle looking around looks fine.

Should be fixed by the recent surface overhaul (changes in maxSpeed, friction and restitution of the surfaces and in maxSpeed effect - now it's only a speed limiter and it doesn't affect PhysX thrust input)

As expected, seems to work in 32 bit for this simple mission and the teammate mission (papi dans les orties V3).

NOTE : I crash also on several other mission that don't necesserally have boat, so it is not the fault of the boat, but since i can easily reproduce crash with this very simple vanilla mission, maybe it will help hunt the bug.

OK, I work on this issue all afternoon.
I get back to the original and first mission that make me crash : papi dans les orties V3

Thank you for attention. I bind axis correctly. My problem in that to look around with (xbox360 controller autoschemed) three times more agile than to look around with xbox360 controller from list of customizable mapped, mappedup by xbox360 controller scheme.

This is still an issue for me. Can reproduce it every time with the Razer virtual surround. It does not seem to clash with the windows spatial surround emulation though.
x64 only.

@GambaDendy i think you mixed somthing up. The 100 is how much % your joystick has moved from 0 to full on 1 axis.
So it cant be more than 100.
What can be chang NOW is the way how it raises till 100 , how much you actually need to move your joystick and the deadzones aka how much you atleast have to move for anything to happen.

Max value 100 is too small. Need a coefficient of applied to controls. By default, the schematic (xbox one controller) applies the stronger force to aiming. Or need acceleration for axis. Sorry if is a offtop. Sorry for my English.

Just did some extra checking. Left gunner shoots at a Quilin (open topped car, doesn't matter if it is armed), so in the case of ifrits and striders the problem might be that the gunner either doesn't see the driver/passengers or "knows" that he shoot at him effectively.

Looking farward too it :)