Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

I think its because you have it on an external disk.

Oh yeah !
That was it dude !
I dl it on my C disk and it works !

Finally. I hope that I'll can help somebody with it :)

Yeah I try to dl it on my C disk, I'll add a note tomorrow, thanks for the reply / note

#prayforit

format has a maximum size limitation, so it won't work correctly for this purpose.

A command for escaping strings would be nice, but not sufficient.

str does more than just serialize strings. It traverses the entire data structure you pass in, and serializes it.

All I am asking is for it to play nice with strings :-)

str has other problems, for example, a null object will be serialized as:

<NULL-Object>

obviously that's not valid SQF, why couldn't the devs just serialize it as objNull ...?

In anycase, <NULL-Object> is easily parsable, you can simply use a regex to match it, and replace it with the correct valid SQF objNull.

I know that breaking backwards compatibility is probably out of the question, even if the old behavior was bad.

At the moment, my work-around for being able to serialize stuff correctly, before passing it into an extension is to recursively traverse the structure ... and convert strings using toArray. However, both the traversal, and the toArray command add a lot of overhead.

Finally, consider this ... a lot of the time the contents of the variables being passed around is beyond the control of the developers (player names is one such example).

EDIT: I see, compile does fail.

It seems all str command does is it places "" around the argument, that's all.
Because str deals with double quotes only you can use single quotes

_value = '--->""<---';

to work around the problem, or use format and form the string you send to extension exactly the way you want.

I doubt this is going to change as this is ancient command and it may break too many scripts. What needed is new command, parseString that would correctly parse all escaped " within.

Added a couple of examples in the repro steps

Looks exactly like it should, what were you expecting the result would be?

When the argument to the str command is a variable (or literal) of "STRING" data type ... the str command wraps the result with double quotes.

That's not enough. Simply slapping double quotes around some text does not make it a syntactically valid string.

Any other programming language that has a "stringify" function would escape the nested string delimiters, when stringifying variables of "STRING" data type.

So in this case I would have expected str to produce:

"--->""<---"

This doesn't seem to be happening anymore.
Could you please verify?

Are you sure it isn't about the shotgun model you are using? or have you tried with different shotguns from different mods?

The shotgun only directly uses the ammoconfig from BIS config so no changes there. But it may be that BIS want to have it like "explosive shotgunshells" like to the AA-12

Duplicate of and related to http://feedback.arma3.com/view.php?id=9875 , http://feedback.arma3.com/view.php?id=12555 , http://feedback.arma3.com/view.php?id=13971 , http://feedback.arma3.com/view.php?id=16403

Since there are selectable colors for the Ghosthawk and the Huron this would be great. A "color-selector" in the create object window would be ideal for this, so that it doesn't block up the vehicle list.

A nice thing would be if the Blackfoot had a black skin too, like every other NATO helicopter has.

This seems to have been fixed.
Tested on 1.41.129399 Dev.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

it looks fixed in devBranch 1.35.128021

I have just realized that it is possible to get cyclic input already: https://community.bistudio.com/wiki/inputAction/actions

It still begs the question, why is there a collective RTD command when you can already get it through inputActions?

I am still unable to fine a method to set input controls via scripting a this time. I am still requesting this ticket stay open.

That is an already known issue since the dev branch release of the DLC: http://forums.bistudio.com/showthread.php?149636-Development-Branch-Changelog&p=2798992&viewfull=1#post2798992

Interesting, when I read that post initially, that message wasn't there.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Even better way is to update Killer drivers, crashes then disappear.

Hello,
Thank you for reporting the issue.
We need crash dump files from this folder for solve your problem.
C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package please?
When the archive is smaller than 5000k, you can attach it here. When it is bigger, please use some free sharing service and post link here.

How to find correct crashdump file:
Try to make the crash happen
Look into crashdump folder
Upload crashdump with latest date in name (crashdump is rpt + bidmp + mdmp file with same name). Please try to provide as many crashdumps as possible, it helps us investigating the problem in a big way.

Thank you.

http://feedback.arma3.com/how-to-user.html

Bullets penetrate just fine...

An important detail for the simulator! I think it should be implemented.
I would add a random penetration of only a some percentage of bullets. For example 30 -35%
For heavy calibers (Sniper rifles) I would increase this value up to 70-80% through-penetrations

closing in favour of duplicate #24048

Seems to be resolved since dev-branch 1.45.130815 according to http://forums.bistudio.com/showthread.php?149636-Development-Branch-Changelog&p=2939180&viewfull=1#post2939180

I tested this out today, I wanted to try the TARU, but not having really used it I decided to switch to the regular flight model, I tried lifting a Zamak first and although the sling load worked fine implying that it wasn't overweight I broke the ATRQ Rotor at about 40% throttle. So I went down to a hunter, then a quadbike, and then ammo box and every time the ATRQ Rotor broke during take off. I use an x55 HOTAS, so I have a very precise throttle and was ascending at less than 1 mp/s, so there's really no way to be more gentle than that, and increasing throttle would just increase the stress on the rotors and make them more likely to clip, but this seemed different, if the rotors hit both should die. I tried it again later with the advanced flight model and didn't have any trouble at all, it just takes a lot more throttle on take off at which point you are able to take off and land and even turn really hard if you want.

A friend and I tried to lift an ATV with the lift variant of the Taru, and it broke almost immediately. Another time I was able to carry an Ifrit several kilometers and it only broke when I started to slow down to drop it off. Almost lost the Ifrit and the Taru, but managed to get them both on the ground with minimal damage. This is content people paid extra for, and this thing can't perform the operation it was designed for. Lifting is the only reason for this chopper's existence. Can we please get some info as to the status of this bug?

It's nice how people reporting this issues problems are getting closed with reference to this issue which is by all indications dead to the devs. They can even be bothered to give us a post to say ANYTHING about this. I know the marksman system part of the DLC is the new hotness and Tarus are old news. But we did pay money trusting to get what we paid for. I cannot speak for others but this kind of thing discourages me to pre-purchasing any other DLC from BI. I can no longer expect that they will deliver on their promises.

I have a solution for some people.
When you use the advanced flight model there is no ATRQ Bug. I tested it very long and it never broken.

But BI must also fix the easy model!!!

Yep. Xeno Taru Pod Mod fix this problem

yeah cool a mod that doesnt work on all servers

It's not fixed. Does anybody know that the Xeno Taru Pod Mod fix the problem?

I think it is fixed since version 1.40, I recently tried it in 1.42

FIX NEEDED...
I cant do sht with this heli, useless piece of metal shit.

DEVS? Y U LET US BUY CONTENT THAT DOESNT ECEN WORK?

Really needs to be fixed. I can´t even lift the pods which are made for the Taru without breaking the ATRQ.

Please fix this bug immediately !
It's a very old bug and you dont do anything against this.
Please fix it in 1.42

It has been 5 months since this was reported. Almost 4 months since it was assigned.
This is a Key feature of Paid content. The TARU is a DLC heavy lift helicopter that cannot lift even light items without damaging the helicopter.
I have an issue with this bug having no priority and no apparent care from the Devs.
We paid for this feature and should be able to count on you to make it work in a reasonable amount of time. Or at least to give us some hint you are looking into it.

Related to http://feedback.arma3.com/view.php?id=22551
and http://feedback.arma3.com/view.php?id=22659

Video: http://stuzer.link/s/sztRF

Some information would be nice, because you can throw the Taru in the Trash if this does not get fixed...

I seconded that.

Go in a taru, slingload a pod (fuel pod for the test) fly and there is a moment your Atrq will be severly damaged.

Or with zeus, direclty spawn a taru and a pod, put the pod under him for slingload without slingloading it, go in the taru put the engine on and almost always the ATRQ will break.

Tested in latest dev build and normal fly mode.

https://www.youtube.com/watch?v=D7WKsRXUVC0&feature=youtu.be

In facts seems that the hitpoint HitVRotor be the problem.

Another problem seems that it cant be damaged by firing on the rotor too...

Hello,
Thank you for reporting the issue.
We need crash dump files from this folder for solve your problem.
C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package please?
When the archive is smaller than 5000k, you can attach it here. When it is bigger, please use some free sharing service and post link here.

How to find correct crashdump file:
Try to make the crash happen
Look into crashdump folder
Upload crashdump with latest date in name (crashdump is rpt + bidmp + mdmp file with same name). Please try to provide as many crashdumps as possible, it helps us investigating the problem in a big way.

Thank you.

http://feedback.arma3.com/how-to-user.html

I've included my ARMA3 crash RPT file, and also my DxDiag file.

Please help!!