TonyG

All the answers you seek are within this. https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Ops.Airboss.html It works great with SC, grading is almost exactly the same and it provides marshalling in CASE I ops as well. Is it integrated? No, but on day 2 of EA, it does exactly what you're looking for.

Works brilliantly. /end thread.

Can this be increased? If you're trapping on a busy MP server, it disappears while you're still working to taxi out of the wires. 15-20 seconds should be sufficient. Even better would be an Event that output this so it can be captured for dynamic greenie boards, but for now an extended message duration would be appreciated.

How? I was using it last night, seemed to be working OK.

Yes, the stacks are not reverting. I think we missed a step on the recovery, as we all got LSO: GRADE: NC : No proper communications but it seems like it didn't take us out of the stack. Just kept adding to it. I can't remember how Airboss purges the stack, but maybe that needs to be added to SC? Partially user bug, but at the same point there should be the ability for the system to reset itself.

Pretty sure this is a bug but wanted to see if anyone else had experienced it in MP. Three of us came back to the Roosevelt last night. Called in and were given 7000/22, 8000/23, 9000/24. Strange issue because there was no one at 6000/21. I landed and took off again. When I called into marshal, I was assigned 10000/25, but there were no other aircraft in the miz with me. Anyone else experience issues with case III marshal?

We’ve been using both. We ran CASE III ops last night but the marshal altitudes assigned from SC didn’t match the altitudes given by Airboss, and I know the Airboss ones were correct. Need to do more digging. For us, the grading provided by Airboss is still superior, as we can grab the output csv and convert it to these graphs.

Pikes and Franky updated Moose on May 16th to accommodate the SuperCarrier. The latest release works. I can tell you from extensive testing today that it not only works, but continues to grade passes fairly accurately despite the dimensional difference between the Stennis and SuperCarrier. We’re running both carriers under Airboss control, can turn them independently and get grades out of either.

You have to relink it to the carrier everytime. And then you can move it. Rinse and repeat. It’s a royal pain and I imagine this is a bug.

The ED LSO grades are present in the DCS.log.

This would be highly desirable.

It is, I see it all the time on our groups server.

Unless you’re in a mission solo. It would be more than a bit annoying to have to hop out of the plane after every pass to turn the lights back on and then spawn into another jet and go through all the setup again to fly 1 more pass, then hop out and turn the lights back on etc etc etc.

You can get them to disappear through moose scripting. Making them reappear particularly on a moving carrier is another problem which I don’t think has been solved via scripting. I use scripting to ‘disappear‘ aircraft parked on the fantail of the Stennis at beginning of missions.

Throttles are constantly in motion. Flying an ICLS is fairly straightforward, but you should be switching to visual (ball) by 3/4 mile anyhow. Lots of anticipation needed because we're missing the seat of the pants feel that you have in RL. I think a properly flown CASE I approach has more challenge to it than a properly flown CASE III approach in the sim. CASE I is far more dynamic, requiring a lot of config changes in a short period of time. CASE III, you've got a 10nm run in to get things configured and trim sorted out before the descent at 3nm.

Placing chocks and removing them seemed to dampen the amount of bouncing for me on the Stennis.

That’s another great point. Case II poor weather or Case III in brutal weather, the lights should come on during the day. I’m not convinced it works like that now.

Same here. Both on dedicated servers and regular game servers.

Currently (when it's working) the Stennis only lights up at night. In VR, the deck is quite hard to see in dawn/dusk lighting situations for lineup. Will the SuperCarrier be able to have its lights turned on for dawn/dusk flightops?

That's a pretty solid summary on how not to do things. You'll be fighting the FCS the whole way, and I'm confident your landings look like controlled crashes. The guy is asking for advice on how to do it properly, which is trimming and learning to work the throttle to control you glideslope. Walking the throttles instead of making huge input changes will help keep the AoA under control.

There is a discrepancy in the modelling of the carrier. The ICLS and the meatball don’t line up like they should. Fly the icls and you’ll see a low meatball all the way. Fly the meatball and you’ll be high on the icls. https://forums.eagle.ru/showthread.php?t=225991

I run this MOOSE script at the beginning of a mission (300 seconds in) to disappear a bunch of static Hornets from the fantail of the carrier. All of the Hornets names start with zDS_. I think it was Hardcard that helped me figure it out. local HornetSet = SET_STATIC:New() :FilterPrefixes("zDS_") :FilterStart() local function HornetDestroy(HornetUnit) HornetUnit:Destroy() end HornetSet:ForEachStatic( function(HornetUnit) timer.scheduleFunction(HornetDestroy, HornetUnit, timer.getTime() + 300 ) end )

As mentioned MOOSE already done this as part of the Airboss class. I’ve got a rescue helo, a low tanker in a close orbit and a high tanker (could be swapped to an AWACs) in a higher wider orbit. https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Ops.Airboss.html

I used this in a SP mission as part of a checkride. This is targeted at a particular unit number in the mission. This was done with MIST. if Unit.getByName('747') then if Unit.getByName('747'):getFuel() > 0.6 then trigger.action.outText('Congrats your fuel load is greater than 60%', 30) trigger.action.setUserFlag(1, true) end end Here's the mission it was used in, it is a night AAR and land ICLS recovery mission in either the Tomcat or the Hornet. Hopefully there's better suggestions that will follow, but this worked for me for a limited scope. Edit to add - i chose 60% as I started the aircraft with low fuel and there was a landing to be done after refueling. You can change the 0.6 variable to whatever you desire. BFQ6.miz

If you’re in AG mode, you won’t be able to cage the HUD. Presumably if you’re using the FLIR, you’d be in AG mode.