Uzii

Increase the C-130's weapon and ammo cargo space... 3 weapons and 20 mags? It can carry tonnes(literally) for goodness sake, but not a box of magazines? And I'm sure this has been mentioned, but for my piece of mind, fix the negative scoring when getting kills in an enemy vehicle. How did that get past testing?

@ahmedjbh Thats weird. I used GUER on my mish, and it worked OK too. Huh...

@ahmedjbh GUER is the independent side. The other bug is when you respawn markers and Boot_hill are too close to the players. Norrin, my good man, I have a problem, actually two. I'm using a HALO drop to begin with and it all works fine, but JIP is heavily bugged. The units who HALO in are instantly killed when a player joins, and they spawn at Respawn_west. I think its the HALO sqf from the game that's messing it up, but I can't figure out how. I've sent a copy of the mish to you, thanks again for all your work. Also, the spectate script never seems to follow anyone other than the downed player, can't figure what I've done wrong with that one. Same thing happened on my last mission too. Edit: I was using an older script, but none of the fixes mention my problem. (0.2i I think)

This seems to be universal for HALO drops, I did it just last night on Domination, moments before being shredded by a Tunguska. Steep hills seem to cause this.

Like the ones from Domination and Evo? Or an actual area of visible fog, say in the bottom of a valley, that you can see from the hills?

In the condition area put: taskCompleted TASKNAME1 AND taskCompleted TASKNAME2 AND taskCompleted TASKNAME3; Edit: The TASKNAME# being whatever you've named your objectives in the briefing.

Yeh, I think you just need to delay the dropspawn.sqf. In an init it must not run correctly. The trigger condition can just be 'true' with a 1 second timer if you want the C-130 at the beginning. Off to work now, good luck.

It happens with the Ammo trucks too. If a vehicle is totally empty, they won't refill. I wasted a few hours on this too, so don't worry ;)

http://rapidshare.com/files/253839102/TEST-c-130drop.Chernarus.zip.html Ok, there it is. Its a US ordinance ammo box, so the script has been altered slightly in 2 places. One for the attach to the parachute, ammo boxes need to be slightly higher attached, else they sink into the ground when they land, and the planes takes longer to be deleted, I felt it was too short, you could noticeably see and hear it just vanish. Something did occur to me too about yours, you haven't got any AA or enemy in the area you are dropping into, have you? That seemed to cause strange behaviour when I was messing around with this script a week ago.

This is getting weird. Right, I'll try and get a working example.

I tried it out of a chopper, still the same effect. I'm going to tear up some other missions that use a HALO drop... see what I can find.

The position is where the C-130 will drop the goods. But using the invisible H should still work, the method you were using should be the same, getpos drop1.

Have you tried the same script, but from a trigger? So it doesn't fire from the init of an object, but when something is triggered. Or, even a true trigger, just delay its effect by 5 seconds. There might be trouble running it from an objects init.

Its probably that, but also, you didn't change any of the values in the script, I had a similar problem when I changed the starting distance of the C-130.

http://forums.bistudio.com/showthread.php?t=77831 Last post, I thought it sounded familiar, it was me :P Might need a re-up. I think you can only have 10 D/Ls from that link. Is there a way to upload a small file on the forums?

Yep, that's it. It means that if its not(!) the dedi server running the script(isServer), it exits without running the rest(exitwith{}). There will only be one server running it, so only one C-130 will spawn. The problem is that every player was each running the script so there would be a C-130 for every player. I think that's it.

http://forums.bistudio.com/showthread.php?t=76641 Third post down looks like the thing you need. Just get the class names of the weapons you want from here.

Thank you, your continuing help on this thread is much appreciated.

I was merely surprised that is all. And I doubt I'm the only one ;)

Got the same problem too. Can't check right now, but does this occur if you start the unit in a heli, then force eject?

So you can test things by yourself... whatd'ya know...

Ah, how would I go about that? At the moment, I've got it activating when a trigger is err... triggered. Edit: Found this little piece on the wiki, would this at the beginning of the script work? ?(!isServer): exit

I imagine thats a very basic way to do it. You REALLY need to search a bit man, this isn't the first time. Look at this thread: http://forums.bistudio.com/showthread.php?t=77308. The second page has some good stuff.

In the "description.ext" file, you need these lines: class Weapons { class G36a {count = 12;}; class G36C {count = 12;}; class G36_C_SD_eotech {count = 12;}; }; class Magazines { class 30Rnd_556x45_G36 {count = 200;}; class 30Rnd_556x45_G36SD {count = 200;}; class 8Rnd_B_Beneli_74Slug {count = 200;}; }; Just edit them to what weapons and ammo you want which can be found here.

_bomb attachTo [_chute,[0,0,2.3]]; That seems to line the box up with the ground pretty well. Think it might change slightly with other size boxes. As for multiple drops, not sure, just above my level. Might be able to loop the spawn vehicle action for the drop, or copy it and put a little wait between each one so it drops 3 crates in a row. Not sure though, Tajin is the man for this one ;)