Thank you for the report. I agree that it seems a bit odd, but it does not obstruct the mission in any way. We might revisit this showcase.

Thank you for the report. Please try to re-install .NET Framework 4 with the latest available version (currently 4.7 https://www.microsoft.com/en-us/download/details.aspx?id=55167)

Does this happen even without mods/with mods disabled?

Can I have someone look at this? It has been happening for almost a year now, and is making the game literally unplayable on servers with mods.

Hi,
Not all the time but so far maybe 5 or 6 times

Wulf is this some sort of documented change? It was not like this some months(or years?) ago in my earlier playthroughs, was the rationale explained somewhere? In the past the consumption of your 3 men team is properly accounted for, the bullets they fired were properly deducted but that's the extent of it. Right now up to a dozen 7.62x51 magazine lost with zero actual expenditure every time you leave base is pretty impossible to replace. Adding all the other ammo type lost I think it's impossible to make up for the random deduction even with a full truck load home. If intended I'd consider this a rather peculiar decision.

Thank you for the report. Does this happen all the time?

This does not belong here. This is an issue for the server admin.

I'm on xbox I need to fix this as well

Hope this will help

I solved this by mapping both sliders + & - to Collective Raise (Analogue), albeit a bit confusing, Works like a charm. Thank you all.

I'll do that as well, but it already is a new profile. I re-installed the other day and didn't save anything from the old install.

Hmm. Could you please try creating a new game profile and seeing if the error still ocurs?

Although, I noticed my logging was disabled in the launcher. I don't know how that affects the reports. If need be, I can capture another, with logging enabled.

It's there. I messed up formatting on original post. It's the last thing in the post, after steam.

Thank youf or the report. Please upload your Arma report here. Here is how to do that.

This bug was already fixed.

Make sure you don't have more than one thing mapped to analog throttle or collective. If you do, then the game will take half input from one, half from the other.

2018 and this bug is still live

Ok, had a look at the report. It seems that the OS is terminating the application because it became unresponsive. Try running the system file checker for corrupted files.

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

Please repair fix unit action ["SetTimer,unit,<bombname>];

Thank you for the report. We are aware of the issue.

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

Thank you for the report. The dumps show that you got a UNABLE_TO_INIT_DXGI error. Please, try these possible solutions.

We will have a look at the Mohawk and see what can be done about it.

Good day Devs Please fix this error, do not delay! 4 months there is no progress

Aaah. Now I understand. The armory is shared by the AI with the player. Meaning they also take their equipment from the armory. So whenever you go on a mission they also take ammo and guns so as to simulate how it would work in real life. Even if you are going solo that doesn't mean that other parts of the resistance are being idle they go on their own mission and take ammo and equipment as well.

If you verified that the slider -1 is the only thing mapped to collective raise (analogue) and the slider +1 is the only thing mapped to collective raise (analogue) then try looking in options > controls > controller and disable anything not Logitech, if any. If that still doesn't work then select the logitech and click the Customize button and then Unmap and try again.

In T65252#1737354, @Zectbumo wrote:

Yes, this has been solved. If you are getting 50% throttle then you need to unmap your other analog device. Only map the logitech otherwise it will split the input with the another analog stick (50% + 50% = 100%).

Yes, this has been solved. If you are getting 50% throttle then you need to unmap your other analog device. Only map the logitech otherwise it will split the input with the another analog stick (50% + 50% = 100%).

Has anyone found a solution to this?

@Wulf Please close this ticket :)

Genesis here. This problem still exists

It seemed to me that the problem was fixed but I was wrong. It only works not stable, developers please fix finally this bug

Confirmed on vanilla game. Well, from the vanilla choppers only with Mohawk. And I only tested in plain editor, maybe Zeus adds something else. And in my case the jiggling only affected the suspension, the helicopter body stayed perfectly still and you could take off and land back to the deck and then the suspension/wheel movement continued. So for me it was only a visual annoyance.

I am not sure, but I will ck it out today and report back to you. Thanks for the help.

Hi everyone! I just wanted to say that I'm able to reproduce this issue as well. I'm going to explain what I've done so far:

Thank you for the report. No you don;t need to keep adding comments. The area is just for commenting, further issues that are not related to this one should have their ownv report.

sorry - here is the link to .mdmp

@Wulf, try the Mohawk helo. For me it's guaranteed to jiggle on the decks of both Freedom and Liberty if I place everything via the editor and then play the scenario in SP. I just re-tested today - main branch, vanilla, Stratis, 10 Mohawks placed randomly around the Freedom's deck - 10/10 are hopping up and down. Placing one Mohawk on the Liberty's helipad is also guaranteed to result in either hopping or an explosion.

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

I have tested it. With the vanilla game and the dancing is actually very rare. It happened to me 1 out of 14 times so it is not as severe as it might seem.

Thanks for this Wulf but it appears to be only a partial fix, as the three small bags attached to the pack still have an incorrect 3rd LOD (15m) at distance. and appear bright in colour.

Thank you for the report and dumps. Have you tried the possible solutions listed here?

We re there no .mdmp files?

Thank you. You are very welcome.

Seems to work.
Just skims over the rock. Well done guys!

Please find report files attached (I attached both the .rpt & the .bidmp files as I don't know which one you need)

This issue is no longer reproducible with the latest version 1.84 and should be closed

Ah i see...
I thought this would be a pretty major problem, but i guess it isn't that big of a deal?

http://images.vfl.ru/ii/1535039496/4876abda/23017236.jpg

do I have to keep adding comments? Or is this area for more comments or issues in the future?

Thank you for looking into this problem. As stated above, I have to back out of the game and re-enter to play on other servers, because when the "Tanao" map is running, the system crashes on me and many others. Just google, Trouble with Arma 3 Tanao map and you will see there are others with the same problem.

Thank you for looking into this problem. As stated above, I have to back out of the game and re-enter to play on other servers, because when the "Tanao" map is running, the system crashes on me and many others. Just google, Trouble with Arma 3 Tanao map and you will see there are others with the same problem.

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

Thank you for the report. I tested it and it seems that this only happens in houses/structures that have set pathing. I am unsure wether this can be fixed since going through all of the structures and changing the pathing would be a large undertaking not to mention that it could break a lot of other things.

Apologies for the delay: Tested again (23rd of the 8th) using only default ArmA3 & it seems to either have been fixed or it only happened the first time because we were running addons. Either way problem solved. Thanks for taking the time to check it out.

Still occurs in main branch 1.84.144923. And, as noted by Vdauphin, now also occurs when changing camouflage on the Prowler (Armed) and Prowler (Unarmed), with any camouflage. Oddly, does not occur on the Prowler (AT).