AvgWhiteGuy

No one ever responded to this post and it just happened to me tonight. All was perfectly fine last night on latest version, now DCS will not load but gives me error screenshot below. I made no intentional changes I'm aware to any files.........FUBAR....!!! Please advise & thank you

@Tomcat-Flyer....got it, thanks. A beautiful addition to the flightdeck

I got the same question, no install instructions and my OvGME just tosses it into C:\......\Saved Games\DCS.openbeta.

I've gone thru @Rudel_chw's 4 missions including the 2 regarding Nav (thank you sir) and it leaves me wondering whether the UH-60L mod has any system TACAN capability to locate/navigate to naval assets (think Carriers)? This is a great mod, a blast to fly but I got a Rum & Eggnog delivery to the CVN-72 for Christmas Eve, and she's sailing somewhere in the darkness just over the horizon. What am I missing? Thanks, and Merry Christmas to all..........

With all this assistance I have sorted most of this out and figured out the source(s) of my dilemma; I had multiple 'profiles' in OvGME. Profile#1 (original) - had DCS on my C:\ drive and I was updating the core DCS\Mods directly...(bad)! Profile#2 - I had moved DCS core to my new dedicated SSD D:\Eagle Dynamics\DCS World OpenBeta BUT was pointing OvGME to ...C\:......\Saved Games\DCS.openbeta\Mods. So it was creating/updating \Saved Games\DCS.openbeta\Mods\Mods (bad)! So i went thru each profile and Disabled ALL mods listed (green) and created the new Dec22 profile pictured above. Now I have the MiniGuns & Crew...success!!! Now I'll try 'Armed Blackhawk' cuz I really need that USCG update below. This brings up some questions that I hope you can answer for a sometimes daft senior citizen regarding Mods. 1) The best Modders present their package with the correct file structure starting in \Mods. I'm assuming that OvGME MERGES this \Mods with the existing \Mods in SavedGames and creates/updates that file structure. This is especially true of a new complete aircraft like the UH-60L. But some Mods aren't packaged like this (Airfield Equipment, Tacan, NavyEquipment, Civil_Objects) and it seems you need to drop them into another SavedGames....\Mods sub-folder directly like Tech. Is this correct and how do we mere mortals know this? 2) If a Mod needs to replace a specific LUA during update, especially a Mod of a Mod as Rudel_chw mentioned above, how/where do we back the original LUA up if we need to remove it later for IC or Multiplayer Server rules? Finally, I've seen many YT videos on Installing-Configuring Mods but virtually all are describing a complete aircraft Mod (UH-60L, C-130, etc, etc.) but I've never found one that explains, shows, tutors us on all the non-aircraft mods like mentioned above. If you know of a good video on this I would love to view. If kept rather generic but explains some of the structure & process involved it would probably save a lot of frustration for Users in the community and be a 'point to' resource in the Forum. Thank you all for your help and input....and @Eduardo...you haven't answered my question from another post....do you ever sleep? Yes, it is a personal preference but not realistic and efficient unless you understand the structure of the file system involved. Users could easily NUKE & FUBAR their whole setup without having a feasible recovery plan.

This whole process of installing Mods is still confusing to me and I'm thoroughly baffled as to why my results suck! I'm trying to install the Miniguns (UH-60L Mod - Version 2.4_3) for the MH-60L Mod and get nowhere, I'm still not seeing anything different in the weapons loadout portion of ME. I'm using OvGME but I'm uncertain if have the correct directories. I have the DCS main installation on a dedicated, separate SSD as in: D:\Eagle Dynamics , NOT on my C:\ drive I have all the Mods in a different file folder as in: D:\DCS Eagle Dynamics Stuff\MODS I have OvGME specifying it's directories as image below. Am I in the right direction here? And what if I were to DELETE the \Mods folder as in: C:\Users\major\Saved Games\DCS.openbeta\Mods ??? Would that mess up everything? For that matter would deleting the entire DCS.openbeta folder from Saved games screw me up completely or will DCS just create another structure there? Might be a fresh start??? If someone can advise and perhaps someone has a doc explaining the structure of the \Mods folder when adding new mods it would be greatly appreciated. I'm losing my mind over this and at my age it doesn't take much.

Oh Yeah....love to have that USN Rescue with the winch.... But on another issue, has anyone been able to get a simple basic TRK file? I can't get even a 30 second TRK of short rolling lift off, 5 sec hover and landing. Always falls over to the left side no matter what I do.

@Rudel_chw...you left just enough breadcrumbs in your Trigger image above for me to figure part of this out; got all doors (except Pilot) open via Triggers. I found those door Commands referred to in the Keyboard Lua (3406-3409). Then seeing your last piece of GOLD (missioneditor.lua) post left me more puzzled as there doesn't seem to be a similar reference, but then I continued reading the thread referenced and found your use of Trigger > Set Command....and Voila! And thanks for the missioneditor.lua info...that will definitely come in handy

Ooooh, didn't think about that, thanks I have an Orbweaver keyboard so I'm thinking about creating a macro to Open/Close at anytime...not necessarily the Pilot/Copilot. Has anyone noticed any/much aerodynamic effect of flight with the sliding doors open vs closed, especially during takeoff, hover and landing? I heard years ago it could be significant for some helos, particularly the UH-1. Can you give me any clues as to where you found the 'Cockpit Device' and 'Command' settings, is there some doc with this info? Thanks again @Rudel_chw....don't you ever sleep

Anybody tell me what the method is to have the door set open from the mission start; is this all with keybinds while LIVE or are there preset options?

And I'd love to have a 'cloaking device' below 7,000ft. but..... This topic has been discussed and discarded over the years as not IRL and impractical when you consider that 'tracers' are loaded every XX round and for a GAU-8 it would be pretty stupid for XX to equal <= even 60. Additionally, I copy/paste a comment I made over a year ago for your consideration. Posted June 11, 2021 **** The the logic behind a tracer round is to trace the bullet flight path and make necessary ballistic corrections for drift & drop over range to target. As much as tracers might be an awesome sight to see, especially at night, I can't see it's practical application in a real war zone with an A-10C GAU. a) ground impact is pretty visible, day or night regardless of the rounds fired. b) HUD visual 'cueing' tells me the range and impact area. c) it's not like you can 'swing the barrel' XX° degrees like an M249, .50-M2HB0 or even the GAU on a AC-130; you'd need to steer the whole plane. d) the visual effect would probably be a detriment to the pilot's vision, especially at night, leaving him/her with temporary blind spots...at 300kts heading downhill !!!! Even a 'subdued tracer'; one that delays burn for a hundred or more yards downrange, combined with gun barrel exhaust would create a visual impairment. The only benefit I can see is the tracers use to 'mark the target' for other friendlies, whether air or ground forces. Oh, and the obvious self-induced 'chubby' from watching the spectacle. ***** ..and remember this ain't a video game, this isn't ARMA.

Sure, I'll give anything a try, and thank you. Is there any suggested Axis setting for this with a Warthog HOTAS Stick & Throttle? I'm referring to Dead zones, Saturation, or Curvatures

@Rudel_chw, can disregard the issue right now, I started a whole new simple mission removing all other potential variables and got the UH-60L as I hoped. I figured out the first 2 attempts were giving me the UH-60H (AI) model. SO all good so far. Now I'll set up some TM Warhog bindings and try a startup. Then maybe I can figure out how/where to install the UH-60L_Pilots-Miniguns_v2.4_2_1 Mod for this mod. That always f#cks me up. Thanks very much...

On the way......... dcs.log debrief.log

Is this NOT correct? null

The excitement is killing me after reading all this thread...and I can't seem to get it work. Mission Planner has the Blackhawk Cold at Batumi but the mission starts at Ext views of another airfield. I cannot get an F1 position in the aircraft; only F2 and other views. The mission starts with the APU cranking up although I have NO settings or bindings. In other words, I have no default position as Pilot.

CONFIRMED as FIXED in v2.8.0.32937 for AI [F/A-18] launching AGM-141 TALDs, used same settings as image above EXCEPT switched 'Weapon' from 'Guided' to 'Decoys'. I'll test same mission with multiple salvos tomorrow. Thank You ED

Thanks [ED]Obi, I just receive a note from Redkite on latest update and d/l'ng now. I did see 'Decoys' in the weapon selection for Waypoint action but it didn't work on my v2.8. I'll give it a test in the next 24hrs. Do you know if the settings in above image are correct other than selecting 'Decoys'? Cheers

In v2.7..... I used TALDs deployed by an AI F/A-18 flight, then I followed up with HARMs & AGM-154 once the airspace was active & saturated. Since upgrading I can't seem to get the AI flight to release the TALDs. Bugged or some settings were change? Image is from Redkite YT video that worked for me before

My opinion on this VAICOM issue as a SINGLE pilot/player on a retired fixed income; Many thanks to Hollywood for adding such immersion over the years, and additional thanks for the decision to hand it on to others to further expand and support. We all owe a debt of gratitude to him for that. He didn't get rich doing this, do the math on 'Revenue x Licenses'; it was a passion. A possible future of VAICOM product development & support without a license fee, balderdash...continue charging for the product! It takes effort, talent, time and some passion to build/maintain this, TIME is MONEY. For those of you that may complain because you've already bought a license...it was well worth it. Divide that license fee by the number of hours you spent flying with such immersion....do the math; damn well worth it! How many beers, cups of Starbucks, packs of cigs, bags of Tostidos was that. Sorry, but you should be embarrassed by even whining about that small, token license fee. Continuing a license based product ensures a future for it, especially with a larger team and a growing community. Be happy Finally, upgrading to the 2.8 version??? I was considering rolling DCS back to 2.7xxxxxx latest version out of frustration. Then MAXsenna gave me simple instructions to d/l and install new Vaicom DLL. It took a whopping 3 minutes to complete and I was back on the tarmac 'requesting engine start' in my A-10C, F/A-18 and F-16. Thanks again MAXsenna! So please, stop the whining, do the upgrade (doesn't even hurt), praise Hollywood's contribution to our community, and go drop a BOOM or FOX an adversary...be happy.

Damn MAXsenna, that was really complex, tough exercise...about 3 minutes after d/l...brilliant. No rolling back. All my A/C are back flying again, thank you very much.

Thanks guys, I got to figure out the path to least insanity... IF "new community fixed version" fixes problem, even if it just resolves the '\' and or HOTAS Mic issues so I have COMMS menu that seems reasonable; at least I can get clearance to crank the engines. IF rolling back to v2.7.16.27869 is faster, easier and I can find an updated Skazillas Updater GUI (mine was ancient), that would give me pleasure as well. @Horns, see images regarding 'hooking'

Lost COMMS & COMMS Menu - All Aircraft Updated to latest version last week, all seemed good. Yesterday lost all COMMS menu but had made NO changes. Keyboard ' \ ' (Open COMS Menu) does nothing Warthog HOTAS MiC switches, I hear Clicks and I see there is a proper response on VoiceAttack/Viacom but it does nothing. VoiceAttack/Viacom recognizes commands...but something about 'nobody available' OrbWeaver Keyboard mapping does nothing. Batumi BLUE, No Ground Crew, No ATC MY A/C affected include ALL A-10-c models, F/A-18, F-16, P-51 I'm patient and I would be happy to role back to previous stable DCS Beta 2.7xxxxx if someone could direct me to the proper DCS_Updater CMD. I know you folks will solve it soon but need DCS during COVID lockdown in Shanghai. Anybody got an idea...please

@MAXsenna.....In the meanwhile, can I retreat to the last 2.7xxxx Beta version?

Lost COMMS & COMMS Menu - All Aircraft Updated to latest version last week, all seemed good. Yesterday lost all COMMS menu but had made NO changes. Keyboard ' \ ' (Open COMS Menu) does nothing Warthog HOTAS does nothing OrbWeaver Keyboard mapping does nothing. Batumi BLUE, No Ground Crew, No ATC Voice Attk-Viacom recognizes commands...but something about 'nobody available' @Primetime Casual...sound similar...everybody on strike or in the <profanity>ter? Anybody got an idea...please @Moderator...sorry about <profanity> but it is a US Military term, along with FUBAR