Shadoga

Sweet contribution to this community, thank you! Releasing a Hornet UFC soon should work out well for you. Plus, I'm not recommending to have a Viper UFC ready when the F-16C hits DCS - instead I'm shure the BMS folks would embrace such a unit for a reasonable price anytime already now.

From 1975 on, it was rather the F14A for the Navy anyways. So, for classic Cold War scenarios, the Tomcat-A is a realistic adversary for MiG-19/-21/-23 as well. For balancing, you can still ban the Phoenix from your server and use AWACS types that don’t datalink with the Tomcat. Of course it‘s sad that the Phantom gets delayed indefinitely, since it has so much appeal to folks from user-nations around the world. But until then, I consider the F14A as a legit placeholder.

Clients need to purchase a license, server software is for free.

Were yesterday's server hung-ups/crashes caused by LotATC server.exe?

With all this done by a single core, I'm so gonna get single-digit fps in MP... - love the evolution you're pushing anyways.

Good news, the LOtATC reactivation! Last time I missed it by half a day, tonight I‘ll check it out. Any special test items to look out for or to try out as a client, or is it only LOtATC‘s server .exe that needs to prove not causing harm for the game server?

@Kirkey: not helpful, since Nealius references this vid and seems to have watched it very closely. It is my understanding that you can enter the Case1 stack overhead the boat at your assigned level from any position by flying towards the TACAN and prior to reaching it by aligning with either BRC or the arc in any other senseful way. To leave the stack for the Initial, you fly a racetrack pattern by extending the outbound course (opposite BRC) until abeam or past abeam the 3NM-Initial. While outbound past abeam the boat you start your descent to 800ft and accelerate to 350kt. The inbound turn towards the Initial then requires more bank/G. I don't know if it is common for formations larger than 2-ships to open up the outbound course by 10-30° in order to facilitate the following inbound turn for the formation, requiring less bank/G. It might also be possible to delay the speed increase to after passing the Initial or to being established inbound Initial/BRC... - for the run-in it might suffice to be at 350-400kt when reaching the boat overhead/abeam position. SME advice required here. My follow-on question would be regarding vertical separation in the stack: Lex states lowest Case1 stack altitude as 1500ft and 1000ft steps for separation upwards. Since I know holdings only from civ. IFR procedures being at straight 1000ft levels (A6000-7000-8000 or FL200-210-220): is it correct that Case1 carrier stack is flown at 1500-2500-3500...?

Huge thumbs-up! Finally having somewhat realistic radar coverage will be a game changer for human GCI/AWACS operators and their customers. I just hope the integration works well for 104th Public Dedi, technically & rules-wise!

Where comes that Jester name from for the GIB-AI feature anyways? Wasn't it Viper who told Mav in his garden that he would fly with him - and Jester the one, when questioned by Viper before if would wanna fly with Mav, who replied: Dunno??? I mean, c'mon, who would wanna share a pit with Michael Ironside and his portrayal of Jester? Why not Merlin or Goose (yeah, ok: RIP) or Sundown or Viper the godfather or lend Slider from Ice or whatever? Sorry for haven't watched the movie yet this year if I got the above wrong, saving the re-view for a Heatblur release...

3rd one is still out there as well:

No, the LSO audio will be triggered automatically when flying through certain positions. You only need to contact the boat‘s AI ATC if you want to activate the ship‘s lights at night.

Awesome work again, Chuck, thank you so much for your huge contribution to this community! I'm not yet through in depth, but so far came across the following: (re.: Rev.21/06/2018 ) - I was looking at the Carrier Ops Parts 5&6 and couldn't find the carrier takeoff weight trim table. I found it on p.72 in the Start-Up Procedure where it makes sense as well - but maybe you could add it repeatedly or at least reference it in Part 5. I know the relevant pages are already cramped, but personally I wouldn't consider it bad form to just copy the whole p.72, give it a new header and repeat it completely somewhere between p.77-80. - max. trap weight 33.000 lbs should be mentioned somewhere in Part 6. - p.91 2.: No Landing Lights at all and no other ext. lights during daytime in carrier ops! - p.93 9.: You correctly state to forget about airspeed later in p.95 Pic.10 - but in consequence, you shouldn't mention "140-150" kts when discussing on-speed AoA here. Being below max. trap weight will always give you less than 140 kts, maybe better leave any speed values out completely here. - p.97 bottom right: "AoA Indexer and the Meatball both telling you that I am too fast." correct: AoA Indexer telling you are too fast, Meatball telling you are too low. Meatball can't tell anything about speed, only about glidepath. - p.99 14.: reads as if selecting full MIL was the only standard practice. I think in the lecacy Hornet there were many cases and good reasons to go full AB upon touchdown, e.g. turbulence (possible windshear) or slower acceleration due to increased drag by external stores (empty tanks & racks). Maybe change it to read selecting "at least" full MILL or go AB, depending on circumstances. - Somewhere in Part 6 you maybe should mention the importance of wind speed across deck for carrier landing ops. A new user or server host setting up his mission with stationary ship and no wind will run into trouble because some of the concepts (e.g. start turn abeam Rounddown or aim for Crotch) don't apply in this case. Youtuber Lex Talionis mentions a desirable wind speed across deck of 25-30 kts through accumulated wind and ship speeds.

Great flying guys and thanks for the mission! I almost exclusively get to practice traps online on your server where the set moderate turbulence has my stick and FPM all over the place. Guess I gotta practice more in straight winds as well to get the controls technique down pat before taking on the turbulences...

Can confirm for multiplayer on public servers, TACAN station ID is missing since today's update.

Even Microprose's Fleet Defender, the only legit ancestor to DCS: F-14, had a dragon flying around as airborne object in some missions...

@falcon 120: AWACS on both sides are placed rather far back, so besides kills, crashes & disconnects of your previously called closest bogey, they might have dropped from AWACS radar contact due to terrain masking. Playing hide&seek in the hills of Oman peninsula is very popular for a/a fighters on 104th these days in that mission. @Badlego: Happened before occasionally, usually some script kiddo joins and drops a hacked nuclear weapon. If 104th members are present, such a person is usually kicked and perma-banned right away.

On the SRS Client Window's "General" tab, there is a "Speaker Boost" slider. I had to set it to 24dB.

Thx BIGNEWY, Nvidia drivers are actual, will give reinstall a try!

Today's update brought me game crashes, all in the F-18 in multiplayer on 104th server, couldn't finish even one flight. Checked drivers, repaired DCS, deleted fxo & metashaders folders - all to no avail. Will now try other servers and singleplayer. Since I'm in VR, I can't click "OK" in the crash dialogue for an automatic send of the log compilation. Attached are the last two archives, I had to delete the tracks due to upload restrictions. dcs.log-20180613-194104-noTrk.zip dcs.log-20180613-201542-noTrk.zip

Good call!

Thanks, that explains it...

TACAN's are bugged in that they switch themselves on and off, at least in multiplayer. For VOR nav in the Hornet, you cannot navigate their radials but you can home on them by dialing them into one of your comm radios and then get a bearing needle by selecting ADF 1 or 2. Unfortunately, you cannot navigate the many NDBs on the maps with the same ADF function because your comm radios can't tune NDB frequency ranges. Doesn't make sense, but that's what stingy customers wrote into the Hornet's requirement book... So basically, VOR nav in the Hornet works like classic NDB/ADF navigation and it occupies one of your two comm radios.

The Hornet in it's current limited state is a pain in multiplayer air-to air but has already become the main DCS strike aircraft for me. The ability to edit your waypoints / build your own route and fly them with precise TOT, laying CCRP retarded bombs from an <200ft AGL / >550 KT attack run and not having to do it in the weirdo-computer metric Viggen cockpit is my personal groundpouner love. Missing Digital Integration's Tornado so much...

Hi fellows! Since last week, I noticed a weird increase in ping times for overseas servers. I'm located in southern Germany and while nearby continental Europe server pings have remained stable, transatlantic pings have risen by over 100ms. Examples: - ACG Cold War: steady 32-45 - Buddyspike Blue Flag: steady 40-55 - 1st Fighter Program (french): 50-65 whereas: - 104th Phoenix: from 130-150 up over 260 - DDCS: from around 160 to over 270 and so on. I already checked and reset and updated everything I could on my side: PC, router, switch, cable modem, cables. Everything normal, bandwith tests show nothing indicating that my provider changed anything. Has anyone else experienced something like this? What could it be?

Where's your new sever located? On the ACG Cold War I have a ping of 35-45, on your new Cold War it is over 150.