<i>parseArray is expected to be a much faster dedicated command.</i>

I don't see how that could be possible. parseNumber probably just calls atof, this proposed command will have to understand SQF grammar to correctly interpret the contained data types.

I made a mistake in the initial description of this ticket.
It is the "Armed Assault Showcase" mission, NOT the 'Combined Arms Showcase'.
I updated the ticket accordingly.

Please note I tested it again without the mods installed, I can keep replicating this issue.

Thanks for your remark though as I would otherwise not have noticed I mentioned the wrong showcase before.

Try removing all mods and report if you can still reproduce the issue. Otherwise close the ticket.

I can confirm that this issue still exists in version 1.10.114.700 of Arma 3.

L-159 actual specifications support in-game cannon

How about comparing it to the L-159's actual info?

http://en.wikipedia.org/wiki/Aero_L-159_Alca#Specifications_.28L-159A.29

http://www.zvi.cz/en/products/20-mm-gun-pod-plamen.html

Also I would recommend to increase the Gatling Cannon round count to around 580 rounds, as the F-18 has a standard round count of 578 rounds.
source: http://en.wikipedia.org/wiki/McDonnell_Douglas_F/A-18_Hornet#Specifications_.28F.2FA-18C.2FD.29

duplicate of http://feedback.arma3.com/view.php?id=16485

Mass-close of resolved tickets not updated in last two weeks.

This bug is in all kinds of missins, in Single Player Missions, too. If you take command of any unit, you can not order them to take up any equipment. Example: during the mission "Combined Arms" you get command over a Grenadier, Machine Gunner and a Medic to destroy enemy AT capabilities behind the next hill. Those soldiers do not pick up any equipment since the last update.

Yes, that would be ok too, as long as the intent of new and old functions is clear unlike the current case of the comments littered in dirTo and relativeDirTo.

It's a point of view thing.

My counterargument would be, how many authors are not aware that their scripts are broken because they expected a 0 to 359 output but never checked?

Also, for the purposes of scripts that use setDir, which accepts -90 or 270, it won't make a difference.

Additionally, I think it's a mistake to use it in a script if you are aware that it returns values that were not intended by the author.

If you weren't aware that it returns values other than the ones it says to expect, then it will fix things rather than break it. As is the case with relativeDirTo.

Resolved according to CL.

Or you can always leave it be because there are people that use it as is and instead create a duplicate BIS_fnc_dirToReal that would return 0-360

This function is so old that rectifying it now will lead to many broken scripts.

Confirmed. It certainly does not do what the author of that script expected it to do if we go by the comments for that function:

"Returns the compass direction from object/position 1 to
object/position 2. Return is always >=0 <360."

Line 25 of BIS_fnc_dirTo is:
_ret = _ret % 360; //ensure return is 0-360

Changing the line 25 of BIS_fnc_dirTo to:
_ret = _ret - (360 * (floor (_ret / 360))); //ensure return is 0-360

Would fix the problem and return a value in 0 to 359 range as the author of the script intended.

Duplicate of #0002325.

No any updates after all this time? Seems such a small thing to fix, for such a big annoyance.

This is at least on the changelog of 1.48:
Fixed: Switching optics mode resets zeroing
http://dev.arma3.com/post/spotrep-00045

Now to test if it's actually fixed.

Zeroing is also retained for each fire mode (single/auto)

Actually, this also happens in Arma2. So I hope if it can be fixed in both games when they find the problem.

I have experienced it while playing TAW Domination multiplayer on Arma2.

+1

if you would like any attention from BI... i strongly suggest a repro mission.

many thanks

fixed....

Which mission? Which buildings specifically?

Yes, since alpha, most of the players don't even know about this but are complaining on random dying all the time ^^

This is happening since the alpha days. I'm not sure but it seems to be dependant on some used scripts.

No reaction for more than a month. Closing as resolved.

Should be fixed in current version of dev build. Could you place check it and let me know if you still able to reproduce it? Thanks

Mass closing tickets marked as resolved more than 1 month ago.

If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.

I don't like the idea. Arma is a game with lots of diversity. If you want a ranking system you will need standarts to rate, which means that there will be less freedom for mission designers.

@tyl3r99: Thank you for your questions. 1. What does fog have to do with my problem? 2. No need. 3. It doesn't matter.

It has to do with sloppy RV4. When you start putting TERRAIN in VIDEO OPTIONS bellow ULTRA you can start to see stuff and rocks floating. If this will ever be fixed it would required major overhaul of engine imho, and I doubt that will happen unless BI proves otherwise.

This happened to me with a friend. We had a sniper war because he was talking too much ermm... anyway, the only reason he spotted me is because i was hiding on a dirt mound. He saw through the dirt mound and started shooting me. I'm there watching his bullets impact the dirt on the other side, frustrated, because he wouldn't have seen me otherwise. Not sure if this could be a solution, but sub pixel rendering, object draw distance/aggregation.

did you have fog enabled?
can you produce a repro mission?
what are your view distance object distance settings

thank you

So I updated the issue, the problem stays the same only the information was updated.

My friend and I we tested it a bit more thoroughly and I updated the info because I founded the information not clear enough.

Problem also exists in not armoured vehicles, and is indeed very annoying

yeah seems ok

I'm assuming this did not reoccur in the last couple of months?

Okie dokie