WineCape

Yeah, only problem is, that Beta aint available yet. But thanks for the clarification.

I get the same update error less then 2 minutes ago: In essence, ERROR: Unknown module FA-18C So if there is no BETA update (My known, latest beta is 2.5.2.17559). -- I guess we have to await then a later pushed Beta; later then the above then ....

Do remember to update DCS to the latest BETA version BEFORE you download the Persian Map.

And what size will this monster be? 16GB+?

Thanks. Worked like a charm your advice earlier! Keep up the excellent work!

SkateZilla's Nifty "DCS Updater Utility": To force branches into another directory? SkateZilla's DCS Updater Utility (DCSUU) seems a useful GUI front-end utility to keep updated branches of DCS World apart and to roll back/update certain branches without bothering with exe. command prompts.. - and to run branch builds side by side Here's the question: I installed DCS just before DCS World 2.5 was released as an "RELEASE BUILD" and installed it under the folder directory E:/Games/DCS World OpenBeta folder Subsequently I updated DCS World to the 2.5.1 (UPDATE/OpenBeta), but I dumped the latter into the SAME E:/Games/DCS World OpenBeta folder, which is not prudent, as I would rather dump all future BETA's into another directory so that SkateZilla DCSUU can be pointed to these separate folders - and keep the RELEASE BUILD separate from in case I need to roll back to a RELEASE BUILD that "works." Anyone here know how to "force-move" the directory structure now, or maybe in the future, so that any OpenBeta future released DCS builds are kept away from the same directory as the RELEASE BUILD, given that all game files (Release and Beta builds) currently are now in a single directory called \....\DCS World OpenBeta\ folder? Do I simply point the DCS Updater utility under the "CUSTOM #1 BUILD fields" - see attached pic - - to the same E:/Games/DCS World OpenBeta folder for now and use that build/original folder structure, for now, as my official release build? And IF so, will the utility itself then create a separate directory (copied?) folder structure, away from the original OpenWorld Beta folder structure? -- See 2nd pic - so that I can run the RELEASE and Beta's side by side, or do I have to do a possibly cut/paste of some folders instead to make this happen?

Relevance? As one pilot of the F18 mentioned already, the latest single engine cutting edge plane was already a compromise between the AF's requirements and escalating cost and the eventual Navy's "watered-down" want for a 2-engine variant. There was a very valid design reason for initially wanting a 2-engine craft for the Navy's purpose, not? If cost was taken out of the equation, I venture to believe that reliability alone of any single engine would not have swayed the designers to stick with a single engine future design for the Navy's purpose.

I get that. The "boy" in any navy pilot dictates he will be very eager to get his hands on a cutting-edge fighter, single -engine or not. ;) I was actually referring to the new design for both a 1 and 2 engine fighter, pilot input paramount in design. Cost not being a factor in such designs choosing between 1 or 2 engines for aircraft over big ponds... Alas, it usually is a compromise between higher risk for the pilot and less costly design methods. Supposedly the higher tolerance standards and MTBF's of single engine craft has increased. And they have. Much like having a modern single HDD; having zero redundancy on backup when your Western Digital/Seagate spiffy new drive fails ... ;)

Simple; ask any pilot if he prefers a 2 engine or 1 engine if his plane is to fly over oceans. I venture to bet that almost all pilots would choose a 2-engine fighter; Cost of plane design notwithstanding, including (supposed) MTBF of 1-engine designs.

Care to say what did fail, where and when? :)

Article: https://www.stripes.com/news/us/navy-retires-f-a-18c-hornet-from-combat-as-f-35c-nears-operational-status-1.522981 (dated 20 April 2018 ) So I guess the Super Hornet wont be simulated - or declassified - by ED until the E/F's are, too, close to retirement from active military operations..?:noexpression: