McShetty

Also, I can't find the cockpit button to drop the center fuel tank. I've bound it to a joystick button which does work.

I'm trying to use Uncontrolled and ActivateUncontrolled. Is there a way to make aircraft spawn in certain spots rather than just randomly all over the airport? i.e. Spawn 4x F/A-18s and always have them to come up in spots 5, 6, 7, 8. This also makes sure client spots are not blocked. I just want them to look organized before they go off on their flights.

Yep, I can see that. Seems like it should just re-pack them every time saved is pressed. Or do a diff or timestamp to see if it's been updated. But it fine now that I know how it works.

Oh wow. I've done a few time consuming mistakes in the last couple days I won't soon forget. Thanks!

How do I actually use RESCUEHELO.SetAltitude() or similar? I have this which works. I'm new to this... clearly. :lol: -- Rescue Helo @ USS John C. Stennis. local rescueheloStennis=RESCUEHELO:New("USS Stennis", "Rescue CH-53E") rescueheloStennis:SetTakeoffAir() rescueheloStennis:Start() -- Rescue Helo @ USS Tarawa. local rescueheloTarawa=RESCUEHELO:New("USS Tarawa", "Rescue SH-60B") rescueheloTarawa:SetTakeoffAir() rescueheloTarawa:Start() -- (Optional) Make carriers patrol their route indefinitely. UNIT:FindByName("USS Stennis"):PatrolRoute() UNIT:FindByName("USS Tarawa"):PatrolRoute()How do I implement? Neither of these work. I think it should be the latter, but when I add either to the script the helos do not spawn. RESCUEHELO.SetAltitude(40) RESCUEHELO.SetOffsetX(10) RESCUEHELO.SetOffsetZ(50) RESCUEHELO.SetRescueOff() rescueheloStennis.SetAltitude(40) rescueheloStennis.SetOffsetX(10) rescueheloStennis.SetOffsetZ(50) rescueheloStennis.SetRescueOff()

No way, really? That explains why it did update once in a while since I kept checking if I had done something wrong with the trigger. Well OK. Super thanks for the help!!!

I don't know, maybe this is old news. I'm editing scripts and then testing and it has become apparent DCS is not using the current version of the file. I very carefully made sure I was saving the script and then even went to exiting the script editor and DCS yet I still see things in the logs that do not exist. "RAT_C-17A" does not even exist. I changed the name to something completely different. I opened ~mis00006C25.lua and it is in fact the old version of the script. I also deleted all the temp files and the issue persists. Script is in Users\myusername\Games Saves\DCS\Scripts\ 2019-02-19 20:37:48.293 ERROR DCS: Mission script error: : [string "C:\Users\micha\AppData\Local\Temp\DCS\/~mis00003B5E.lua"]:22279: SPAWN:New: There is no group declared in the mission editor with SpawnTemplatePrefix = 'RAT_C-17A' SpawnTemplatePrefix = 'RAT_C-17A' stack traceback: [C]: ? [C]: in function 'error' [string "C:\Users\micha\AppData\Local\Temp\DCS\/~mis00007FF2.lua"]:22279: in function 'NewWithAlias' [string "C:\Users\micha\AppData\Local\Temp\DCS\/~mis00007FF2.lua"]:50022: in function 'New' [string "C:\Users\micha\AppData\Local\Temp\DCS\/[color=Red][b]~mis00006C25.lua[/b][/color]"]:1: in main chunk

A rescue helicopter would follow carriers. Unfortunately they can't do CAS.

Wow! Just being unlucky enough to be in the way. Super thanks. Noted. I was concerned about the mods I added. I just wasn't sure what to do about it.

It happens every time at the beginning of the mission. It's almost comical at this point. trk attached. ROE = hold Immortal = on Frienly Fire.trk

For an airshow plane so many systems are likely not in a functioning state and possibly removed that more compressed air could be stored. I don't know the number but say the original system had enough air for 3 LG cycles, it might be determined this is insufficient safety factor and larger air capacity was mandated.

Another trick I use that seems to help a lot is to keep it trimmed perfect so I'm not fighting any pressure at all. It seems to make it easier to lock-in the speed and decent rate. Too low or too high can be adjusted with very small speed changes. It should be almost hands off on final. Also, you're setting up a mission where you're already in flight and just turn something like 90 deg onto final and land. So you can just do it quickly over and over.

That was deep. But how can I be the wind if I'm already the ball?

It's 6 switches plus a throttle nudge. Battery. Right side forward. Both fuel pumps. Behind throttle. DECS Switch. Next to seat-back left side. Fuel shutoff. Same place. Engine start switch. Right side forward. Once the engine gets to 9% bump the throttle forward and pull it back. This moves it from cutoff to idle. There's a few post-start items but this will get the engine running.

Same for me.

Hey thanks! This is great.

Damn I need to learn to read. Actually dyslexic so I really did see "off" but I don't like making excises so we can just go with, "I'm dumb." Thanks. :thumbup: Side note: Being dyslexic is fun sometimes because signs can say odd and entertaining things. Gotta roll with it.

Best kind of bug. The ones that fix themselves. :thumbup:

It's expected to try to turn into the wind. Been a while since I've read it but the manual states no VTOL in crosswind over some limit. So in a strong wind you're facing into it or you're not VTOLing. But then it also states no taxi with canopy open but there's youtube videos of that too. Damn Marines with their forearms hanging out and their sleeves rolled up looking all cool.

350 is way too fast and almost certainly result in bouncing back into the air. I've had very good success landing at 300 kph, very shallow decent as usual. Bad part is that you can't see over the nose. Looking around the side works a little. What I've done is to initially come in at a little steeper angle and 10-20 kph faster to keep the runway in sight and then bleed off the speed, increase the AOA, and shallow out the glide slope at the end. But just make sure the glide slope is stable before touchdown. This has prevented all bouncing. 95-100% throttle is normal. It can fly level at ~220 kph and 30 deg AOA so landing slower than 300 is likely possible but maybe a tail-strike.

You can turn it off in the settings. I don't do A2A much in any plane and find them distracting too.

I noticed the Mig-15 does this too but to a much smaller extent. So I'm expecting the Mig-19 to be somewhere in the middle. Otherwise: 1) Turn on the stabilization. 2) Keep it trimmed all the time so you don't have much, if any, pressure on the stick while trying to fly straight. High speed, takeoff, landing, whatever. Constant trimming. This is also a trick in other planes for refueling. 3) Fly it A LOT.

I'm curious about when the A model will be out. I kind of like things that are underdogs or rough around the edges.

The attached mission picks a random number associated with a pre-defined group and then just picks again until it finds one that hasn't already been spawned. Oddly this doesn't work all the time and will just "spin" occasionally and I haven't figured out why yet. When it does work it can take more than what I think is an acceptable amount of time because as more spawns happen the chances of randomly picking the same number goes up. Is there a better way to do this without getting overly complex? I know there are other ways which would require setting up a much larger number of flags but I'd like to avoid that. Just trying to keep it simple. Thanks. Random Spawn.miz

It also seems you can't click 3-position switches quickly. You have to wait for the animation before the 2nd click. This seems like a fun update: Chaff, canopy, switches. I'm not mad and can wait for fixes but seems like a lot of odd shit slipped through.