Jump to content

pappagoat

Member
  • Content Count

    60
  • Joined

  • Last visited

  • Medals

Community Reputation

6 Neutral

1 Follower

About pappagoat

  • Rank
    Lance Corporal

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. There is also this module, needs updating but A-1H and F-100 CAS are still functional:
  4. 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.
  5. 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
  6. 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
  7. 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.
  8. 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.
  9. BIS_fnc_initVehicle does otherwise work. I have tested it using the name assigned to a vehicle, ie "jet1"
  10. Ok first part works great, second part gives me an error 'expected object' as if its not returning the config name as the answer.
  11. 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;
  12. pappagoat

    GX Addons v2

    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.
×