Direct mode is meant for softer targets and for close encounters. While top down mode is for more armored vehicles and long range targets.

Talked with the design guys if you have the top down mode enabled then the missile is going as it should. You can see that here in this video.

Same as https://feedback.bistudio.com/T130378 this sounds like either a trajectory problem or you aren't using the right mode for the vehicle. Since there is a new fire mode for PCML and Titan.

"What have u done to the rocket launchers?"

This error is very generic. It may be caused by many issues, such as a hardware malfunction, a virus in the computer, but also an error in the game itself. Please try these possible solutions and let us know if it helped.

If you received the error 0xC000012F - STATUS_INVALID_IMAGE_NOT_MZ.

Could you please write in english what the problem is?

Interesting I was not able to recreate this issue on our stable build. Looked at your dumps and found this error

Thank you for the report, we are aware of this issue.

Rockets PCML

• capturing a goal
• choice of the trajectory of attack
• rocket launching

Further everything in this ticket
T130378

In the launcher Arma3 (arma3launcher.exe), under the options, select the platform - 64bit. Tried it?

Now the PCML and Titan missiles have two flight trajectories. Depending on the application of the rocket, select the desired trajectory. The trajectory of the attack from the top down causes great damage. For machines, one missile is enough. Check the game settings, there are keys to change the trajectory of the rocket for the launcher.

Is a bugfix finally in sight for this?

Yup, Oukej said it wasn't intended to use laser designator with this missile. Still would be a good feature considering the wonky target acquiring with this missile. Not to mention for targets in cities.

In T124664#1704168, @Krycek wrote:

So it seems this was assigned since May 2017 but I don't see any fix for this. Still won't lock on with laser designator to this date.

Do you have any Information for when this will be done?

In T129492#1704298, @Wulf wrote:

Hello.

Have you tried contacting the Battleye devs? You can do that here.

I found a feature of this bug. The AI-subordinate will enter the cargo hold only if player vehicle are in the formation status. If the AI does not go inside your vehicle, order your vehicle-driver the command 1/1 (Return to formation) - only after this the subordinates will enter the cargo hold.

0xC000012F - STATUS_INVALID_IMAGE_NOT_MZ

Hey developers, I'm waiting 10 months until you correct this error, but it seems that you do not take this problem seriously.
Your completion settings inside of waypoint does not work only for AI-units, while for the player character it works!, are not you going to fix this bug finally?
 
Please fix, this complicates the setting of all singleplayer missions :/

I submitted a request to BE devs. see how it turns out.

Besides the "bug" with the time all of the other bugs I was not able to reproduce, it seems that they were a one time occurence.

AI can sometimes be a different issue.

• AI will rarely engage on the first pass - sensors don't provide any information about target allegiance, so most of the time AI has to first confirm its target via eyes or ears. You can try https://community.bistudio.com/wiki/reveal to give the AI a head start :) Or there's also https://community.bistudio.com/wiki/confirmSensorTarget. Slow detection of targets by AI in vehicles is still listed as a bug on our side. I can't however promise we'll be able to fix it :/
• AI should be able to engage targets up to the weapon's lock range, even outside of vehicle sensors' range.
• We acknowledge that the diving into attacks is a bad behavior, sadly we won't be able to change that for Arma 3. We're sorry about that.
• We can restrict the diving behavior for orbiting vehicles (helicopters, drones, Blackfish). But since we've got no other attack behavior for aerial units, it may increase their survivability but also limit their ability to engage targets (get into position for a missile launch)

Have you tried contacting the Battleye devs? You can do that here.

Regarding locked characters please contact the servers administrators.

Regarding locked characters please contact the administrators of the specific server.

Oukej, I posted&made two vids here:
https://forums.bohemia.net/forums/topic/200468-jets-custom-panels-gps-camera-feeds/?do=findComment&comment=3295067

This time I was in Sa-Matra King of the Hill, in the AO with OK frames per second, just locked up and crashed with a STATUS_ACCESS_VIOLATION like the other instances. This time, windows didn't warn me of the bad_module_error. I just verified the game cache and it literally downloaded a file 735,2 MB big.

• Current Macer's range is up to 6000 m (there's a plan to increase it to 8 km). That is against standard - MRAP sized - targets. Smaller targets will have a shorter detection range.
• Minimum locking range is 350 m.
• Maximum target speed is 200 km/h.
• The missile has an IR guidance. This means it's limited by object view distance. The range can be affected by weather conditions like fog. Also, primarily, the target has to be heated.
• Macer has never been able to lock onto laser targets.
• You have to use "T" and point the cursor (center of the screen, TGP crosshair....) in the target's direction to designate it. (Cycling targets via "R" is limited to only targets known to the vehicle sensors and their ranges)

This missile is pure junk, I get even shorter lock-on distances than wiki, 1km-500m. Either extend it's lock-on range or scrap it, it's junk in player hands,it's even more junk in AI hands be it UCAV or F\A-181 and so on. Do you know what happens with an AI drone or plane that gets so close to an enemy? It gets blasted to pieces before it manages to lock-on with Macers.
Not to mention it can't lock-on even now on laser designated targets.

So it seems this was assigned since May 2017 but I don't see any fix for this. Still won't lock on with laser designator to this date.

Does setGroupIconParams change the hexagon color, and is it customizable per client or affect the whole group?

2 months have passed, noone even considered this problem, thats quite sad.
in this two months i run all tests i could, here is a quick list of all useful infos i gathered until now:

Same issue happened to me in MP. After that, I could not remain connected to any server because of "Battleye not responding" kicks.

@Wulf

Just a bump. Devs - The community can't find a way to achieve this via a work around. Surely this isn't hard to do?

Oh im on Win7 too

Win7, BE log:

I have exactly the same problem after https://steamcommunity.com/games/arma3/announcements/detail/1664523682540066936

When I try to join any server with BE it gives me this error. I tried anything, Verifying steam cache, deleting BE and then veryfying steam cache again, starting with the arma3battleeye.exe, nothing helps

More checking done and ...

And again, I was on MP standing still and scanning around when stuttering arrived and the game locked up crashing.

Hello
someone found how to fix the worry?

Here we go again, crash on Multiplayer while driving a vehicle and going back and forth from map.

This should be fixed in dev branch.

What a bullshit reply. I'm a steam member since since 2003. NONE of the steam games in my library has this problem. The second I start ARMA3 BOOOM internet gone. You are flodding with multiple connections, ISP thinks you are using P2P -> no more connections. Known problem on YOUR side -> blame Steam. 4 years later... shame on you

I brought this issue up on the forums as well on 1st April and the post seemed to get a lot of support (https://forums.bohemia.net/forums/topic/143930-general-discussion-dev-branch/?page=970&tab=comments#comment-3280362). This feature request would solve a lot of frustration.

No changes so far

Talked to the devs, according to them this is not fixable sorry.

Nope :( The only third party soft which is similar to this which you mentioned is Steelseries Engine 3 for my mouse Rival 300. Also i Have connected mic Samson C01U Pro but I'm not using any softwere besides drivers downloaded by windows.

This is infact not a probem with arma! Its a problem with windows 10 after the creation update. I had the issue myself, and the only way to fix it was to install an earlier version of windows. I ended up getting a free version of windows 8. Infact arma 3 runs better in Windows 8 than 10. The game dosent crash when you tab out, and i seem to get a better framerate.