Fully functional turrets added to the Bethesda!

The turrets act like attachables, moving with the craft and there shouldn't be any craft-turret collision issues. They also gib when the craft is destroyed and despawn when the craft leaves the field.

The turret I'm using is semi-WIP. I'm likely going to keep the gun but change the sprite. I'm also going to resprite the craft so it matches coalition colors better.

Some code and lots of advice courtesy of Abdul Alhazred. Thanks much!

Wow, I guess the bump was a good thing after all. I am 100% behind this little nugget's revival.

Very nice, just a few issues that might have been stated already:
-Ship is too fragile.
-Gun turrets are too weak in fire-power. Change them to Coalition Auto Cannons.
-Gun turrets get destroyed too easily.
-Ship lags for some reason.

1: Going to work on that. The engines are going to get external armor and I'm going to update the hull a bit so it can take some punishment.

2: The turrets are on the Bethesda for defense. This thing is a dropship first. That said, I think I either need to add clipsize or range to these guns. More firepower will come with the next project I use this code in (hint; it will include many more turrets)

3: I'll experiment with this.

4: I just tried it and it really does! The regular dropship produces almost no footprint but the Bethesda causes a marked linear increase in processor load (wtflag!?) I tried messing with the engines, but they don't seem to be the culprit. Even with the LUA off, it is still very laggy. Does anyone have any ideas why this could be happening?

What is the lifetime of the particles it spits out?

The same as the vanilla dropship's. I've even tried reconstructing the code form the vanilla dropship's ini. Same laggy result (even with less particle emissions.) I wonder if it could be the sprites rather large size?

How many attachables? Attachables are laggy.

Only two, the two arms the turrets sit on, plus the two engines and two doors, like other dropships.

It might just be that the drop ship is so big that the atom group is large enough to lag.

That's probably it. Though, I tried switching out the sprite for the DSMk1 sprite.

All the same, it would explain why theres a linear CPU time increase, an atomgroup for each seperate spawn of the dropship. I guess it can't be helped

Anyway, did a big respirte of the ship. Shal I release with gibs or no?

As long as you'll make gibs eventually I think you should just go ahead and post it now.

Sweet Jesus, yes, it's back. Possibly my favorite dropship ever made <3 The new planned out features sound great, hope you can get around to them pretty quick Aaron. Not to rush you, just excited about the whole thing

There's a problem that if you deploy the ship as enemy(I did in the scene editor), the turrets will still be on your team.

@goid: I'll see what I can do with that. Shouldn't be hard to fix. Just some code in the create(self) function to match the turret creator's team.

In other news; slowly making gibs. It is hard work. I am also swamped with my new job.

I like this ship, and I'd like to share my personal experimentation with it. The Bethesda can, if not comfortable, then at least reliably carry a dozen MDC-brand Tactical Nukes, and can hold as many as twenty and still be moderately controllable in its death dive (and what a glorious death dive it is). Each of said nukes weighs 100 kg.

Just try to wrap your head around how much thrust this thing's putting out.