TonyG

A few of our pilots are seeing it on our dedicated server.

https://discord.gg/d5JFWN

I’ve read though the release page and searched the forum, but I haven’t seen anything that indicates LSO grading results for passes. Currently the Airboss script provides extensive grading information including groove time, which can be output to google sheets in order to create dynamic greenie boards. What is the intention of DCS regarding LSO grading and output formats?

If you're looking for information for US jet bases, alot of info is available on airnav. NAS Oceana departures and arrivals as well as traffic pattern information are on the Airnav page. http://www.airnav.com/airport/KNTU

And it is available in the T-45 Flight Training CNATRA P-1211 under NIGHT FCLP. As far as target airspeeds, it would be exactly the same as day, on speed AoA. 600’ downwind altitude. The bank angles etc are all going to be the exact same. Everything you would do during day FCLPs you’ll do during night FCLPs but there will be more focus on instruments than during the daytime.

FCLPs are conducted at night, same pattern altitude as day FCLP. No crosswind turns until at or above 500’, crosswind turns are called by tower/LSO.

Another VR user....I don’t use NVGs for tanking the Viper at night. Easy to see the lights and make input changes to stay in position.

Yes, more navy Vipers.

MOOSE Airboss is a great solution, and I’m sure ED has looked at the code. We’ve been running it for quite some time and really enjoy the immersion. The carrier steams between the waypoints, and starts CASE I/II/III depending on user input. It then steams into the wind for a recovery period (1 hour) and then returns to the set waypoints. Also avoids islands and other ships. User waypoints by themselves with no ability to steam into the wind would be really frustrating on large scale servers and perpetual servers. If enhanced weather comes along, this would be even more critical. We’re working on running more dynamic weather and this is a critical piece of the puzzle for accurate carrier ops.

That’s a bit of a deal breaker for me. If this issue can be sorted with existing scripting (which it can), that should be standard issue. Turning into the wind for recovery is basic, no crosswinds while flying an approach should be expected.

I’ve done several touch and go’s with the F-16 on the Stennis, just need the hook to complete it. Can’t wait!!

I just recorded my first OK 4.0 from the MOOSE Airboss script, so thumbs up on the stability in this latest patch.

Is anyone running modified beacons.lua file for tacans and icls?

Well done, will definitely incorporate some of these into our squadrons missions. Thanks!

As the need for more tanker resources grows (boom and drogue), planning multiple tankers, each with discreet tacan channels and frequencies, becomes more challenging to input and communicate with clients on multiplayer servers. It would be beneficial to mission designers and pilots alike, if the mission editor was able to collate the tanker altitude, speed, tacan, and frequencies into the briefing page, or perhaps directly into a common kneeboard. Adding AWACs in this format would also be useful. While this may overlap with some of the data/methods used by external scripting, simplification of adding 4+ tankers plus AWACs is a benefit to all. The creation of multiple frequencies, tacan channels, altitudes and airspeeds introduces potential for errors on the design side and confusion on the user side. This would address both those concerns.

I managed to get the tankers to refuel from each other....but that probably doesn’t help you.

You also get the internet award for 2019's Most Necropost.

You just made me preorder....thanks!

I believe Wags mentioned this during the first academic video on the cockpit orientation, that the hook would be there and that undoubtedly people are going to try and land it on the carrier.

Yes, been reported for a long time. Workaround is to step through all the mavs once you’ve rearmed and it starts all of their timers. Would be nice to get this little annoying bug fixed.

I’d bet the mission you have was pre Tomcat release. The 1xx/2xx modex triggers were set up to represent the Tomcat while the 3xx/4xx modexes were set up for the Hornet. Try changing the modex you pick to one of the 3xx/4xx modexes.

This adds ICLS to Nellis as well as a number of other fields in NTTR. https://www.digitalcombatsimulator.com/en/files/3303095/

Rift S Pd 1.4. No problem making out the ball in case i or from ~1.5 NM in case III conditions.

I’ve successfully tanked quite a bit in the F-15 to see if I could do it in preparation for the Viper. The lights are very easy to read, see, use with the Rift S.

https://forums.eagle.ru/showthread.php?t=225972