pappagoat

Hello Chaps, A few static line observation if I may: - Game Observation: Sometimes I have seem canopies bounce up into the aircraft after deploying, or when the game is laggy the chute deploys before the jumper has had time to fall, but the result is that the aircraft starts trying to gain altitude to avoid colliding with the stream of parachutes opening up near it. - Suggestion: Not sure, disable collision for the parachutes? - Game Observation: By my calculations paratrooper parachutes are descending at appox 12 m/s (much faster than the in game air crew parachutes). - Real World: Both the US T-5 and UK Type-X Parachutes had an approx descent speed of 7 m/s. - Suggestion: Reduce descent speed of parachutes,reduces ground collision injury issues, is more accurate, and gives more time to enjoy the game jump.

Hello, I'm using BIS_fnc_ambientFlyBy to spawn aircraft that fly a set route. I am trying to find out how to get the unit name of the aircraft so that I can then do things to the spawned unit, such as limit its speed, set velocity and teleport AI into the aircraft. Does anyone have any ideas?

No, I know what it is and I wanted to use flyby. It''s for a repetitive AI paradrop.

Hello, I'm making some airborne related missions. Can you chaps look at changing the descent speed of the parachutes? They are far too fast. The T-5 and X-Type had descent speeds of about 7 m/s. This will also remedy injury/death incurred in game when landing.

Trying to get a trigger to be activate whenever certain types of aircraft enter the trigger area. I have tried the below, as well as isKindof for just a single aircraft config and nothing has worked. Any ideas? Trigger Condition: (bluefor present) this && ({ _x in thislist} count ["uns_f100b_CAS", "uns_f100b_BMB"] > 0) The second part is I then want the trigger to execute a script upon the aircraft that activated the trigger, something like the below, hoping the _x denominator carries over from trigger condition to On Activation: On Activation: result = [_x, "uns_f100_silver", nil] call bis_fnc_initVehicle;

Result! Great. Works perfectly.

I've been using this for CAS. It needs updating but calling in A-1H and F-100 still works. I did try editing it but can't get it to repack - keeps on kicking back errors or not packing correctly. Unsure why at the moment.

Gents, Love the progress on this, strong work. A few things I've noticed: AC-47 SEA camo texture and bump-map don't seem to be fitting the model properly. F-105 silver textures not with right gloss map? silver appears dull grey. CH-34 & (C)H-21 still have issues where they cannot maintain a consistent altitude when pilot by AI, keep on nosing up and gaining altitude. Radio Module: I may enter only AC-47 as the only CAS but A-1H CAS still becomes available.

There is also this module, needs updating but A-1H and F-100 CAS are still functional:

Interesting, will try. Yes basically for my missions want to make it so that certain aircraft (F-4, F-100, F-105) spawn with with their pre-SEA camo textures if the year is 1965 or before (I already added the year part to the trigger conditions). Trying to use it with the GX support module as its the only module that I've found that supports UNSUNG aircraft for CAS, but as I mentioned there are issues with it not working on all aircraft when calling in CAS with more than one jet at a time.

Yeah both work when I test with two static aircraft, but when interacting with the air support script only the first jets skin changes... humph

Tried this in the activation as well and it gave the same result, only first aircraft skin changes... wondering if it is to do with the air support script im using

Nope.. that didn't work, looped it but it still just changes the first F-100 when several are spawned at the same time or in rapid succession. I do have repeat on in the trigger, so once the trigger zone is empty and they spawn again, again the texture of the first one changes.

Hmm actually, if more than one F-100 is spawned at the same time, only the first one has its texture changed... maybe that is more to do with the way the trigger is activated. Maybe I should put the second part into a loop.

Works beautifully, thanks!

BIS_fnc_initVehicle does otherwise work. I have tested it using the name assigned to a vehicle, ie "jet1"

Ok first part works great, second part gives me an error 'expected object' as if its not returning the config name as the answer.

Thanks.. why -1?

Have not been able to get hold of them thus far. At present no releasing anything, just seeing what can be done... but none of that matters because of the errors when trying to repack.

Drop the folder names @GX Addons into your main ARMA 3 folder. Then in the ARMA3 loader go to the addons tab and click '+ local mod' at the top to add it.

Updating the script but for some reason it is not re-packing into PBO correctly.. Anyone want to help?

In Vietnam the USMC used the UH-1E, not the D. The E is basically a B adapted to USMC specs. The USMC also did not use the CH-47, but I imagine you might have that in place as there is no CH-46 yet. I did find a CH-46 for ARMA3, however it is a very incomplete port, but could be a start point: https://steamcommunity.com/sharedfiles/filedetails/?id=1457539426 It would be really good to see a UH-1B/C/E slick as well.

Thanks, got it all working in the end.

Trying to make a script so that after a parachute jump, once all team members are on the ground, any that are 150 meters from the player after a certain time leave the players group. I've made the below but have been getting errors I have not been able to resolve: waitUntil {{_x isTouchingGround;} forEach units group player}; sleep 45; {if ((player distance _x) > 150) then ([_x] join grpNull; _x groupChat "Unable to RV with you, proceeding independently."; sleep 3;) } forEach units group player;

Yes