Invisibull

Thx GT! Has been great flying over the last couple of days. Hi Plott - You can find them here: WWII Japanese Pacific Theater Naval Order of Battle https://forum.dcs.world/topic/285745-wwii-japanese-pacific-theater-naval-order-of-battle/ WWII Pacific Allied Assets The WWII Japanese Pacific Theater Naval Order of Battle has two links - both are dropbox direct downloads and are the 3rd and 4th links from the top of the first page. Hope to see you there.

Hey folks, I've been really enjoying the Corsair and can’t recommend Hawkeye’s WWII Pacific Allied Assets and Japanese Pacific Theater Naval mods enough—they’ve become essential to my setup. Using these outstanding mods, I’m running a server with a highly realistic Pacific scenario, and you’re all invited to check it out. The server features two controllable aircraft carriers, allowing for dynamic naval operations and carrier-based strikes. There’s also a robust F10 radio menu with features like bullseye tracking, cargo plane locations for escort missions, allied client tracking, and real-time carrier status—all designed to make coordination straightforward and intuitive. For advanced radar situational awareness, I’ve added a custom radar script by GTFreeflyer. The current server name is: IFC PRESENTS: OPERATION STEEL CURTAIN (MODDED VERSION-SEE BRIEFING) | FEATURING THE F4U-1D CORSAIR | ALL SKILL LEVELS WELCOME | P-51s, and P-47s ALSO AVAILABLE VIA DYNAMIC SPAWN Whether you want to test your skills in the F4U-1D Corsair, fly P-51s and P-47s, or take on carrier ops and logistics roles, or just work on your carrier landings, there’s something for every play style. Join us and chat on Discord: https://discord.gg/rW63ScUk7j Looking forward to your feedback, and a big thank you to Hawkeye60 for the incredible mods and to GTFreeflyer for the radar addition that elevates our mission experience. Here's some additional info: FRAG ORDER VF-84 "Wolfgang" USS Bunker Hill (CV-17) Date: 11 July 1944 Time: 0900L 1. SITUATION Enemy Forces: - Japanese forces occupy Rota Island, with established anti-aircraft gun positions, aircraft on the ground at the Rota airstrip, and 155mm naval shore batteries actively harassing Allied shipping. - Japanese warships are operating in the area; their positions are variable and require active search. - Japanese convoys are operating around Rota Island; these convoys are to be located and targeted. Friendly Forces: - VF-84 "Wolfgang," F4U Corsair squadron, embarked aboard USS Bunker Hill (CV-17). - 318th Fighter Group ("Guam Avengers"), operating P-47 Thunderbolts out of Guam. - 21st Fighter Group ("Island Knights"), operating P-51 Mustangs out of Guam. - Allied cargo aircraft conducting regular supply runs between Guam and Saipan. 2. MISSION VF-84 "Wolfgang" will execute the following tasks commencing 0900 hours and extending for five hours: Attack Rota: - Strike enemy anti-aircraft gun positions. - Destroy enemy aircraft on the ground at the Rota airstrip. - Neutralize 155mm naval shore batteries. Surface Search and Strike: - Locate and engage Japanese warships and convoys in the operational area. - Utilize USS Bunker Hill’s SG surface search radar for target acquisition; information is available via F10 Radio menu. Escort Duty: - Escort Allied cargo planes transiting between Guam and Saipan. - Ensure safe passage and protection from enemy air or surface threats. 3. EXECUTION Commander's Intent: - Achieve air superiority over Rota, suppress enemy defenses, disrupt enemy naval and convoy activity, and ensure the security of Allied logistics. Tasks: - Attack Section: Launch at 0900L. Ordnance load per standard strike configuration. - Surface Search Section: Maintain CAP and respond to radar vectors for surface contacts and convoys. - Escort Section: Rendezvous with cargo flights at assigned waypoints and provide continuous cover until mission completion. - 318th FG & 21st FG: Coordinate with VF-84 for mutual support in air superiority and ground attack roles as required. Duration: - Operations will extend for five hours from commencement. Additional Instructions: - All pilots must remain vigilant for enemy bandits in the area. Be on the lookout for hostile aircraft at all times. - Pilots should access The Bunker Hill's radar to keep track of bandits, enemy ships, and Japanese convoys. Radar contact information is available via the F10 Radio menu. 4. SERVICE SUPPORT Ordnance: Full combat load as briefed. Fuel: Top off prior to launch; refueling as required upon recovery. 5. COMMAND AND SIGNAL Command: VF-84 "Wolfgang" CO retains tactical control. Comms: - Main radio frequency for USS Bunker Hill: 124.0 MHz AM - Standard squadron frequencies for intra-flight communications. - Surface radar contact info available via F10 Radio menu. - Coordination with 318th FG and 21st FG via established air-to-air channels. END OF FRAG ORDER

Great mission concept! Very enjoyable. Thx for your help with the script as well.

Thx a bunch for your quick response. Here's a few (of varying quality) I've found so far: "The Corsair’s unique and innovative configuration incorporated engine oil coolers in the inboard wing sections, with the resulting airflow through them making an unmistakable whistling sound, audible over the sound of the engine and firing of its guns." This passage appears in the Background section of the article https://reviews.ipmsusa.org/review/f4u-and-fg-corsairs-part-2-whistling-death "Other wing features included a leading-edge air intake at the fuselage intersection that provided cooling air for the oil system and the engine supercharger inter-stage. Under certain flight conditions, particularly high-speed dives, the intakes created a distinct screaming or high-pitched whistling sound. Japanese ground troops under attack by Corsairs soon linked the sound with the fearsome ordnance capabilities of the bent-wing bird. Because of this, and the Corsair's superior air combat capabilities, the Japanese referred to the F4U as 'Whistling Death.'" https://www.usni.org/magazines/naval-history-magazine/1995/february/designing-bent-wing-bird Guyton, Boone T. Whistling Death: The Test Pilot’s Story of the F4U Corsair. Atglen, PA: Schiffer Publishing, 1994. Relevance: This book, written by Boone T. Guyton, a test pilot at Chance Vought who flew the F4U Corsair extensively, is one of the most authoritative primary sources on the aircraft’s development and characteristics. Guyton directly addresses the whistling sound, attributing it to “the curious high-pitched whistling sound of air being swallowed into its inlet ducts” (p. 7). He notes that this sound was particularly noticeable during high-speed maneuvers, such as dives, due to the airflow through the wing-root air intakes for the oil coolers and engine. While not a peer-reviewed academic journal, this firsthand account from a key figure in the Corsair’s testing phase is considered a primary source with high reliability in aviation history circles Tillman, Barrett. Corsair: The F4U in World War II and Korea. Annapolis, MD: Naval Institute Press, 1979. Relevance: Barrett Tillman is a well-respected aviation historian, and this book is a detailed historical and technical account of the F4U Corsair’s design and combat performance. Tillman references the “Whistling Death” nickname, noting that the sound originated from the wing-root air intakes (housing oil coolers and intercoolers) during high-speed operations, particularly dives. He explains that the inverted gull-wing design and the placement of the intakes caused air to produce a distinctive high-pitched whistle at high velocities, consistent with high-speed dives or fast level flight. This source is widely cited in aviation history studies and is considered a standard reference for the Corsair. Dean, Francis H. America’s Hundred Thousand: The U.S. Production Fighter Aircraft of World War II. Atglen, PA: Schiffer Publishing, 1997. Relevance: This comprehensive study of U.S. fighter aircraft production and performance during World War II includes a detailed section on the F4U Corsair. Dean discusses the aircraft’s aerodynamic features, including the wing-root inlets for the oil coolers and turbo-supercharger, which produced the whistling sound during high-speed maneuvers. The book confirms that the sound was most prominent during dives or high-speed flight due to the high-velocity airflow through these inlets. As a Schiffer publication, it is a respected source in aviation history, blending technical data with operational context. Sullivan, Jim. F4U Corsair in Action. Carrollton, TX: Squadron/Signal Publications, 1977. Relevance: This book, part of the “In Action” series, is a well-regarded reference for aviation enthusiasts and historians, providing detailed technical and operational insights into the F4U Corsair. Sullivan notes that the whistling sound, which led to the “Whistling Death” nickname, was caused by air rushing through the oil cooler and intercooler inlets in the wing roots during high-speed dives. The book emphasizes that the sound was most audible during aggressive maneuvers, such as dives or high-speed passes, due to the aerodynamic design of the inlets. While not a peer-reviewed journal, Squadron/Signal publications are respected for their accuracy and are often used in aviation history research.

I've noticed the whistling sound since updating today and from what I've read, "if the intercooler and oil cooler doors are closed, the F4U Corsair should make less of the characteristic whistling sound or potentially none at all." Also, I'm hearing it when at not very high speeds as well, but have read that "the whistle is most noticeable at much higher speeds, such as during attack dives or when approaching maximum level speed (over 300 knts)." I don't mind it during a dive or when really hauling ass - with vents open, but I'm hearing it with everything closed and at 200 and less knts cruise speed, which seem overdone to me based on the above. I'd be interested in other opinions. Thx.

You are correct in your understanding: if you fly using only the selector on MAIN, the aircraft will draw fuel only from the main (fuselage) tank. The wing tanks are separate and do not automatically feed into the main tank. If the main tank runs dry, you can still have usable fuel remaining in the wing tanks, but it will not be accessible unless you switch the selector to draw from those tanks.

The reserve tank is positioned to ensure reliable fuel delivery during high-demand phases like takeoff and landing. Using the reserve tank in these critical moments helps avoid issues such as fuel starvation or vapor lock that could occur if the main tank's fuel lines or pumps were compromised or if the main tank was not full enough to ensure positive fuel pressure during rapid attitude changes.

Is it currently possible to use navigation homing for an airbase? I've tried manually adding a beacon to Batumi but not joy. Maybe I didn't do it correctly. I know I could place a carrier nearby in the water, but I'd like to be able to do it without resorting to that. Any ideas? Thx.

When not caged, my understanding is that the dial should move to reflect the range to a target based on radar returns. I've messed around with this for an hour and have yet to see the dial move off of 1800'. When I cage it, it goes right to 600', but right back to 1800' when uncaged again, regardless of how far away the target is.

Support Ticket #143755 was put in on 8/27 and so far I've been asked to check a bios setting to see if my RAM was being overclocked (it wasn't). Very disappointing to be completely ghosted by ED on this issue.

I'm still getting this crash, but never when using the non-MT .exe. I have reinstalled DCS from scratch am using no scripts or mods, and I have done tests on my memory and it is fine. Could someone please help? I've attached the latest DCS.log and here is the Windows Crash Report from the Event viewer: Faulting application name: DCS.exe, version: 2.8.8.43704, time stamp: 0x64e3b9dd Faulting module name: VCRUNTIME140.dll, version: 14.34.31938.0, time stamp: 0x023b235f Exception code: 0xc0000005 Fault offset: 0x000000000000165e Faulting process id: 0x4e38 Faulting application start time: 0x01d9d62a3dcb6612 Faulting application path: D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll Report Id: d8dd710f-9880-4cdb-a0d4-5a185a6ec61c Thx dcs.log-20230824-013901.zip

Thx for your reply. I've come to discover that the crash doesn't happen when I'm not using the MT exe. Further, even while using the MT exe it only seems to happen in that particular mission so far. Incidentally, those script errors have been coming up for years in some cases and have never manifested in any noticeable way in the game environment; I don't think they are involved at all. Thx again.

Aircraft used here is an F-16 in MP. Please find relevant logs attached. Thx. null dcs.log-20230606-193242.zip

You're welcome

Yesterday's update has resolved this issue. Thx for all your help, @c0ff

This did not help.

I've always run all DCS.exe's as admin and there is no Debugging Tools folder, so I'm still feeling the pain over here.

I should add that the server will run, but that it takes 3 or 4 hours of "loading" before it will. This was the case even before the hotfix and before I updated Windows.

Updating to 22H2 didn't help.

Trying that now. Thx. I'll report back here when done.

I guess the fix wasn't so hot. So, we wait until the next update and hope for the best?

@BIGNEWY Today's hotfix had no effect on my issue. The DCS Log is exactly the same and the DCS server is still stuck in the loading screen.

Hi, I started by doing all the things you've suggested plus a system restore and none of it helped. I then did a full uninstall, deleted all folders associated with DCS, including the DCS folder within my saved games folder and then did a reinstall from scratch. None of that changed anything either. As far as a "full" log - I provided the entire log in my first post. I'd imagine its brevity is due to the fact that DCS hangs up before a longer log can be generated. DCS is running fine on my PC, but I haven't been able to host a server using the dedicated executable on my server PC since the update.

Best of luck, but reinstalling did nothing for me.

Thanks for your reply. Since I did a full reinstall and others seem to be having a similar issue, I think it's pretty likely that today's update is the cause. Hopefully, there's a fix already in the works.