To measure the distance use the key, the default is "T".
Works everywhere, where there is a distance sensor.

Already tried that, nothing changes.

Try to assign both + and - Z axis inputs in the analogue thrust, you should be then able to use the thrust stick with its whole range

Pretty much everyone on Olympus is upset about the new 3rd person heli camera and wants it to be reverted to the old one.
Please go back to the old helicopter camera.

I did not consider this a problem until the release of Tanoa. My first message on this ticket is after the release of Tanoa on DEV.
http://steamcommunity.com/games/arma3/announcements/detail/831295479358001897
Height adjustment is not the only bipod problem. There are a number of other problems that need to be addressed. For this reason, I allocate all major tickets for the bipod.
https://feedback.bistudio.com/T81982
https://feedback.bistudio.com/T123368
https://feedback.bistudio.com/T85691
I think these issues should be solved in the aggregate.

This was a problem before tanoa as you can see the time i created this ticket apex was not released.
I understand Tanoa has more vegitation and grass so your view may be obstructed more on Tanoa.
But, the terrain on altis and other maps will have the same exact problems.
As i said this isn't a major issue that would effect the gameplay that greatly so no, i do not think this will effect any of the popularity of missions on Tanoa nor any other map.

In T82167#1607504, @Shields wrote:

Lex, as the status of the ticket says "Acknowledged, Wishlist".
The developers have this on their to do list, its just not very high priority.
They have more important stuff to work on, bumping this ticket every few weeks will not help at all.
If they add this feature, i'll be grateful. If not, i'll live with it. Trust me i understand that this issue is annoying, i made the ticket so i know.
But its not game breaking, it doesn't make bipods completely useless or the game unplayable. You, me and everybody else is just going to have to live with this.

In T82167#1607294, @Lex wrote:

?????????????????????

Super! Thanks!

Lex! they make next DLC, don't bother them! Lol!

Also, thrust to weight ratio is waaaaay off.

Thrust to weight ratio is waaaaay off.

Same problem. Using Saitek x52 Pro. Tried clean vanilla install, with and without DLCs and even Devbuid with no change. Also one of the axis (twisting/YAW) is registering in game only as absolute 0 or -100 or +100,making flying pretty much impossible. I checked saitek controll program and there its registering correctly as analog.

thank you for the feedback.

thank you for your feedback.

@razazel any word on a timeline for a fix. Or even where the problem stems? We have a huge dedicated and tech savvy community that I'm sure would be happy to lend some ideas.

?????????????????????

@Burrito57 We are aware of this ;)

?????????????????????????

????????????????????????

Combine questions on RPG-7

Combine questions on RPG-7

Combine questions on RPG-7

Combine questions on RPG-7

Combine questions on RPG-7

Close ticket, no problem

@SuicideKing Thank you. Close ticket, no problem

Hey, thanks for the report. I'm sorry but we will not add manual guidance to AA Titan variant. It's been deliberate to have it IR only.

Are devs aware of this? I mean, on top of this post it says "Assigned to: None"
If not, we should make them notice.

The action can be found under Controls, Weapon - "Lase Range"

Actually, there is. For example, we have a custom FOB for our unit. Instructors have access to Zeus, as well as regular Zeus. Since they have automatically added all objects (simple objects are excluded) they can delete those objects (accidentally or on purpose). + if you have too many objects (we have 9746 objects, of which are 5587 simple (could be more, but now I can't set it)). Zeus loses tons of fps because all of these icons + he can delete all non simple objects (which I don't want to be deleted). I really see no point of removing this from 3ditor and having this option enabled for few objects only.

Still does not work.

Yup, I have the same issue but with every UNSUNG map. The client crashes randomly and the crash report spams the following (several hundred times): Unsupported format palette 8 // Bad texture format in GetPixel{F60336}

Duplicate of T124837

Logitech Attack 3 USB Has an axis with negative and positive values. A similar problem. A small change in the position of the axis Z + \ - sharply changes the thrust from 0 to 100%.
I changed the keys in places, and it all worked well.

Duplicate of T124920

could you please send me (describe or screenshot) your thrust configuration in the control settings?

Thanks for the heads up, should be fixed in next Dev branch update

Back again... or not solved. Place any civilian helo with this code (init field). start and restart the game, or just make the helo respawnable. That doesn't work.
_veh setVariable ["color",X]; where X is a correct value within the number of skins, doesn't work neither.

The launch Titan AA has a small angle. You can not shoot at the target, when the target is as close to you as possible.

Good game support , 5 days and still no answer on steam support, 2 weeks and no answer ... i keep in my mind to not buy any more of your games.

Looks like it has been fix in the last released 1.70
Good job guys!

I have tried with and without Dynasound 2 but unfortunately I hear/see no improvement.

+1 change it back to it`s old Performance, please.

+1, change it back please revert it, would love to play old AT, now there isnt much fun with the new one, flies very slowly, almost impossible to wireguide.