Captain Orso

I understand completely. I worked in service and support for nearly 40 years. I know the routine Yup, Synchronize Cockpit Controls with HOTAS... has the checkmark.

ctld.lua and moose.lua are both written to call STTS (Simply Test To Speech) from SRS. Looking back at the messages (you never said where they are appearing - I'm not clairvoyant enough to ascertain that) but it looks like from DCS.log, inserted by ctld.lua along with the messages showing that the JTAC input is garbled. When I open 'JTAC-Test Academia-Caucaso-Range-SIN-ATIS.miz' in the ME... I was about to chastise you for not doing the JTAC call properly, but I realized I was only looking at the call in the trigger actions list, and when selecting the action, I see that it is correct--although the drawing on the map indicating freq 1680 is wrong - insert Kermit drinking tea meme here What I did note is that after calling each script file, you have no pauses. So let me explain. I learned that when loading scripts like moose, mist, ctld, etc, you load the first one in Trigger Type -> 4 Mission Start. All subsequent scripts are to be loaded in Trigger Type -> 1 Once with -> CONDITIONS = TIME MORE 2 (I've used 'TIME MORE 1' also without issue too - YMMV). TIME MORE x is how many seconds since mission start, so for each subsequent script being loaded, you need to increase the TIME MORE parameter. EG: 4 Start Mission -> Actions = Do Script File(mosse.lua) 1 Once -> Conditions = Time More 1 -> Actions = Do Script File(mist.lua) 1 Once -> Conditions = Time More 2 -> Actions = Do Script File(ctld.lua) 1 Once -> Conditions = Time More 3 -> Actions = Do Script File(another_script.lua) 1 Once -> Conditions = Time More 4 -> Actions = Do Script File(yet_another_script.lua) This is to insure that all scripts are actually loaded and ready, before any calls can be made on them. Since your triggers run one after the other as fast as they can, and all with 4 Start Mission, it might be that the JTAC call is running into a not completely loaded ctld.lua script and things go awry. I'd suggest giving that a shot and see if it helps.

I have a toggle switch assigned to CMWS ARM/SAFE, CMWS/NAV, CMWS PBYPASS/AUTO. and to the safety cover for the JETTISON switch. I tested with both hot and cold starts, with all the switches both ON or OFF. Only the CMWS ARM/SAFE switch synchronizes with my HOTAS. CMWS/NAV always starts in the CMWS position. CMWS PBYPASS/AUTO always starts in the AUTO position. And the JETTISON safety cover always starts closed.

You're getting all over the place now. If JTAC-Test Academia-Caucaso-Range-SIN-ATIS.miz is the mission with the JTAC issues, the JTAC call is missing all of the information. I noted that some of the many lua scripts you are loading may be calling SRS. I'm very bad at lua so I'm not going to try to debug anything--just a waist of time on my part. Look into the scripts you are using and their requirements.

Absolutely not. You just set the unit(s) name(s) and frequencies and anything else I'm forgetting and it works. At mission start you get an on-screen message that the JTAC unit has taken up service, and if it has a target, it will tell you the type (T-72, SA-8, whatever) and if the status changes it well be reported. From the moment the message is posted, the JTAC is lazing. The only issue I know, is that the JTAC tends to lag behind moving targets, which can be a problem if the targets are fast.

idk there were a number of updates since I've noticed this issue. And since I have this issue already, and I can either somehow go back to a previous version or press on forward, I installed the update that just arrived today and am now on 57.0.0.254.153. I have yet to test how well switching out to Dash works, or how long it takes until it doesn't--sometimes only minutes.

Many thanks for the reply, Lange_666. I have 56.0.0.193.155. I have no idea what I had before and when changed from what to what. I'm thinking of going a complete reinstall.

Am I the only one who every experienced this issue? I opened a case with oculus and spent hours testing, trying and gathering log and dump files and they never gave me an answer as to what the issue is or what I can do. It is a MAJOR issues if you cannot switch out of DCS if you have touch anything outside of DCS on your PC. If you use a Rift CV1 and regularly use the Remote and the Oculus button to switch from DCS to the Dash board, let me at least know that it is working for you - Always - Nearly always - Sometimes - Never - What are you jabbering about, are you on drugs? Many thanks in advance.

Every aircraft I own I tested to see if the Nav or Position Lights are forced on during hot start, even though I have "Synchronize Cockpit Controls with HOTAS Controls At Mission Start" selected, and a HOTAS physical toggle switch assigned to each ON and OFF positions, and the switch set to OFF. I am always forced to turn the lights off after spawning into the cockpit. Happens on the carriers and SC as well with Hornet and Harrier, although it is prohibited to use position, anti-collision, and landing lights on the decks of these ships, at all. All these aircraft tested. P-51D, all variants Spitfilre, all variants P-47D, all variants Mosquito UH-1H Huey AH-64D AV-8B-NA A-10C A-10C II F/A-18C F-86

It seams that to get DCS to behave that it doesn't leave you with migraines you need independent 3rd-party tools with secret information, and asking to have the deficiency at least recognized, you get told everything works as it should and that I, as the customer, am at fault, but I can ask the manufacturer if they might update their product to fit to my unreasonable expectations. It seems a twisted world we live in. Many thanks for the Infor, MAXsenna. I believe from the forums to have read, the source for up-to-date info and access to downloads for VIACOM is thru their Discord channel. Is that correct?

I would surely like to know how that is possible, since VoiceAttack is only a voice interpreter with an hierarchical scripting framework which only outputs menu point activations. If through VIACOM you can say, "refuel me chief" for "top her up, chief" it can still only access the comms menu -> crew chief -> refuel & rearm - or do you know something of which I am completely unaware? I would sure love to know what it is.

The DCS App erases the data I spent a relatively large amount of time and effort to input and control for correctness for no reason. That is a bug. Even if I dropped every bomb on target and flew back and got a new set of GBU-38's, the JDAM programming in the internal computers should in no way be erased. The system has an OSB for doing that if the pilot decides it is necessary. It can hardly be any more obviously a bug.

The title pretty much says it all. I'm on MP server. Enter F/A-18C hot. Rearm & Refuel, adding 8*GBU-38 and a centerline fuel tank. Start GBU alignment and go into the kitchen and come back. Timer is gone. Program all 4 stations with different targets for each bomb, using PP1 and PP2. Double check every Station and PP1 & 2 to be sure everything is programmed. Because I've been sitting on the ground for god knows how long, with the engines running, while I program everything, I call the ground crew to refuel--of course I cannot tell them to only refuel, because I am retarded like a snakeye. I'm watching like a hawk, the DDI display with the SMS page -> JDAM View -> MSN (left where as it was after STEPping thru every station to check each one). Right when the crew chief says rearming complete, STA8 and PP1 disappear and along with it the programming displayed below has also disappeared. Stepping thru every station and looking at PP1 & 2 for each shows that ALL PROGRAMMING HAS BEEN ERASED!!!! Curse words uttered omitted for brevity.

The maps are just getting better and better Imagine getting the Caucasus map in this quality...

I'm not going to hold my breath until the Huey get's a nice DCS-MLU... *sigh* But DCS does seem to be working strongly toward the Cold War period, and what aircraft represents the period better than the Huey... or maybe the Phantom II... or Tomcat... Mig-21..... but with regards to helicopters, it's the good ol' UH-1 Huey! Please, pretty please, let's have the Huey massaged and oiled and made to fit in with the airframes DCS and Friends are putting out today, so that no one would guess that it's been around for so many years already. I'll even gladly play for the upgrade, like when I purchased the A-10C II instead of paying the full $79.99, because I already owned the A-10C basic, I only paid $9.99(!!). I would pay more for an Huey upgrade! You hear that ED? Free money for the taking!

Many thanks for the reply, Sedenion. At least according to my phone's OS the Google Authenticator has no permissions to look at my phone number, SIM card, or IMEI. Of course, that is assuming the Android OS itself is not spyware. But then simply owning any mobile phone opens one to being spied on, even if you use a 'burner' phone, you leave a trail. Just one not so easily followed to you as a person. With the number of forums and even large corporations being hacked and having personal data stolen - especially email address and passwords from forums, I view TFA as added security, but I also use a password generator and encrypted password database. Since ten years the world knows without a doubt how much data the US's security agencies collects on all of us, even though it is highly illegal in the US itself, and yet there was no huge wave of protesting the government or telecommunications providers who cooperated with the government. The US public in general is in that sense and albatross around or necks. What each person does with that information is and individual decision with no perfect solutions available. Thanks again for your reply, Sednion.

Hi Sedenion, thanks for the update to OMM Could you point me to information about TFA and digital-identification? I'm never heard of any concerns with TFA and use it with many accounts. Thanks in advance.

Yes, but it behaves exactly as before. If you press too long, if flips off again. It acts like: short press = [Boxed], and long press = Unboxed . All other VAR's are simply press/click any length of time = toggle state: Boxed<->Unboxed.

I want to add a Waypoint TSD -> Point(B5 -> Add(L2) -> WP(L3) -> IDENT>(L1) If you hold L1 for longer than about 1 second the Box at IDENT flips off again and on the KU IDENT is removed and you cannot enter the Waypoint identifier. This happens whether you are left-clicking with a mouse or have a key assigned to press L1 and are pressing the key. Happens on both the left and right MPD.

So true, sorry.

You will have to be much more specific, exactly what doesn't work, and how to repeat it.

Follow the link in my previous post and read.

Draken35 is the author of the plug-ins, and IIRC was also the one who pushed for Scratchpad to be plug-in compatible at all. Here's the link to the post with his latest content:

No, that is not correct. Without plug-ins to delete old data, mark it with you mouse and press <Del> {delete}. <Esc> causes Scratchpad to rescind the focus so that pressing keys passes them on to DCS and not to writing into the open scratchpad. If you implement the 'QWERTY_KB and Load Coordinates' plug-in you will get a [CLR] button to click, which will clear all content of the current scratchpad page.

I'm just thinking functionality. I'm not worried about the looks of the apps.