kfarley215

Seems the HMCS doesn't cross over to the side monitors with TrackIR and 3 Monitors set in Options. This doesn't make HMCS very useful w/ 3 monitors because it is stuck on the middle monitor when your eyes are on the side monitors.

I have played through TEW3 once and really enjoy it. As a relatively new DCSer I can probably play through it 3 - 5 times on different difficulty levels as it is very interesting. In this case, TEW3 M03 I had the following issues which I will be glad to try to help trouble-shoot. Mainly, I would like others to not have to experience them: 1. ATC Request Startup - I was on the correct freq and used Comms menu but ATC would not give me direction. However ATC always caught up with what I was doing after the fact. 2. I successfully hit all of the requirements for WP1 - WP4 and had my TOT and AGL validated for success over WP4. Once I reached WP5 and connected with Hunter to move to WP6, my flight went radio silent. They would not respond to "Echelon Left" commands given numerous times. 3. Once I got to WP7 and began engaging ground targets, my Flight was off the air and would not respond to Engagement commands. They simply flew around doing nothing. They eventually went Bingo and ejected. 4. Once I completed the mission by myself and got AWACS confirmation to RTB, while my flight was all gone, I actually got radio messages triggered from my flight even though they didn't exist. Still a fun mission, but with no flight support it is unrealistic to eliminate that many ground targets. I know it is virtually impossible to keep Campaigns operational with the constant DCS changes so this is feedback as an FYI. If I can help debug, tell me what would be helpful. Thanks, Looker

Thanks for confirming! After saying it 60 times with infinite variation I got it to recognize the pattern. Whew! :thumbup:

I can get Jester to recognize "Radio Mode AM" and recognize "Radio Tune" or "Tune Radio" but when I supply the digits and even get a confirm beep, the radio freq does not change. Can someone please list the exact phrases they use to get the AM Freq tuned to the digits required? Thanks!

Working now, thanks. Given Airio is for F-14s only, we also get the Navy chatter which is ok, but it seems to be shorter and more repetitive and almost all traps vs. the NATO chatter. I understand we can select which Chatter we want in the options if we don't want the default. Any plans for broader Navy chatter soon?

FYI - Here is a set of Kneeboard files with commands for Airio: https://www.digitalcombatsimulator.com/en/files/3304381/

F14 Rio Plug-in not working after going through manual steps So, when I activate the Airio option in Vaicom Pro configuration, as expected, the Jester menu goes away. But I can't get Jester to respond to voice commands even though I can get a beep hit on the Vaicom voice recognition (although recognition is painful). I have followed the instructions to export the plug-in data and import the Airio file to VA and then copy to Vaicom Pro for DCS profile. Also, when I run the Plug-in Configuration Editor it shows 850 Key Words. When I press the Test button, it shows 365 missing aliases. Is there something I need to do to resolve the 365 Aliases? What other debug steps should I follow to understand why the Airio plug-in is not working?

Ok. I have spent a couple hours ensuring SRS and Vaicom are mapped correctly to the matching PTT radios etc and so SRS is working and Vaicom is activating the correct channel with the Warthog HOTAS Mic keys. The Menu behavior has gone away. I still can't get RIO working but I'll start a new thread for that.

Vaicom Pro generating unwanted keystrokes I have Vaicom Pro licenses and with A-10C everything was fine. I just got the F-14 and the RIO plug-in but Vaicom is now generating spurious keystrokes so that the Comms Menu (mapped to \ in DCS) keeps showing up or disappearing. This happens in the F-14 but not in the A-10C. When I close VoiceAttack or simply disable the Vaicom profile the issue goes away. I have triple checked all the key mappings and I don't see anywhere keys could be generated, but Vaicom is generating keystrokes that trigger the comms menu somehow. Any thoughts?

Thanks! Got it working and understand directory structure now!

I have this working now. User/DCS/Mods/tech S the home for Mods while User/DCS/Liveries is the home for Liveries. In the case of Mods, each mod should have a subdir with an entry file declaring itself a plug-in for Mod Manager. In the case of VPC Objects, this needs a patch available in in google drive. Also the subdir in the original zip file for VPC declares itself main and has numerous subdirs. Change this to VPC bjects for clarity. Each mod author tends to create their own peculiar dir structure in their zip file. Some think they are adding to ED nstall folders instead of the standard Saved Games folder. Some think artifacts go under the Bazar directory. All of this leads to confusion and mods or liveries not working. I’m told that mod managers help with this. I will research them and learn more. For now I hand tune my Saved Games folder for each mod or livery (and fix the unit name references to match ED standards) and now everything is working.

I checked the Mission Editor and I see that in the Payloads tab for a Unit you can view and edit the Paint Scheme. I see that some Livery creators are not following standard naming conventions and so their Liveries will not be found until it is registered under the correct unit signifier (in this case "F-18C"). I do have Liveries loading now, thanks for your help!

Ok. Makes sense. Liveries go in their own folder outside of /Mods/tech. Now, when downloading the latest liveries I'm seeing various folder names and even aircraft type information in the description. Example: 'VFA-97 300 (CAG)' contains description file starting with livery = { {"f18c1" While the ED notation is folder 'f_a-18c' and the description file uses: livery = { {"F-18C_Texture1", 0, "F-18C_Texture1_NSAWC_25", false}, I checked the Mission Editor and I see that in the Payloads tab for a Unit you can view and edit the Paint Scheme. I see that some Livery creators are not following standard naming conventions and so their Liveries will not be found until it is registered under the correct unit signifier (in this case "F-18C"). I do have Liveries loading now, thanks for your help!

Good info, all! Understand that placing User content in Saved Games will keep ED content clean and manageable. It was the original VPC Object Zip that created the confusion. It has a deeper directory structure than the others and it used 'main' as its placement under /Mods/tech instead of using /Mods/tech/VPC Objects. So the lesson for me or anyone downloading mods is, a mod is best managed as a Folder in /Mods/tech and will declare itself a plugin in an 'entry.lua'. But I see a bunch of Liveries with various folder structures. Some have /Bazar/Liveries path. Do Liveries go to Saved Games/DCS/tech/Bazar or do they go to the actual ED install folder Bazar/liveries?

As I learn to install missions with mods, I understand that mods are generally intended to go to <Drive>/Users/<user>/Saved Games/DCS (or DCSOB)/Mods/tech However, each mod has its own peculiar directory structure ultimately containing LUA, EDM or DDS files. Are we supposed to preserve a directory structure for Mods/Skins etc or are we supposed to place the files in Mods/tech/main/Liveries; Mods/tech/main/Shapes; Mods/tech/main/Textures? I ask because I don't seem to get any mods to load when I just unzip into /Mods/tech Thanks!

Because I am having this issue with missions from different authors (preacher316 & habu_69) although I have yet to get any mission loaded with either VPC or USN, could I ask you to tell me a mission that works for you and list your User/DCS/Mods/tech and your User/DCS/Mods/tech/main directory structure. All these zip files seem to have assumptions that are not 100% clear and I don't see in a log where a file is not found with a directory name included. This way I can discern whether the Mod Installation or the Author has the bug. Thanks!

Am I correct in figuring that these Mods are not supported in DCS 2.5? There are a number of missions created in 2018 and 2019 with these Mods but after hours of research and fiddling I can't get them to load in DCS 2.5.

I am having trouble getting TacView configured for OpenBeta whilst it is working in stable build (as well as SRS). I have cloned my scripts directory in Saved games for DCS.openbeta compared to DCS and reviewed file paths. Interestingly the DCS Saved Games folder points to a mods/tech/Tacview folder that does not exist for DCS but does exist for DCS.openbeta. Anyhow, here is my error log that illustrates how OpenBeta has numerous complaints loading additional plug-ins: 2019-12-24 14:15:38.449 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/dcs-srs/dcs_manifest.x86_64 2019-12-24 14:15:38.449 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/tacview/dcs_manifest.x86_64 2019-12-24 14:15:38.449 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/us navy equipment/dcs_manifest.x86_64 2019-12-24 14:15:38.449 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/vaicompro/dcs_manifest.x86_64 2019-12-24 14:15:38.450 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/main/dcs_manifest.x86_64 2019-12-24 14:15:39.774 ERROR SECURITYCONTROL: Manifest size check failed for file './Scripts/Database/db_countries.lua' 2019-12-24 14:15:39.868 INFO Scripting: OBSOLETE mount_vfs_sound_path() used in ./CoreMods/aircraft/AJS37/entry.lua 2019-12-24 14:15:39.869 ERROR SECURITYCONTROL: Manifest size check failed for file './Scripts/Database/db_countries.lua' (The countries error reflects my attempt to get a plug-in working for an F/A-18 mission that won't load due to NavyFighters and other plug-ins reporting errors). 2019-12-24 14:15:40.285 INFO Scripting: plugin: SKIPPED 'DCS-SRS': not authorized 2019-12-24 14:15:40.285 INFO Scripting: plugin: SKIPPED 'Tacview by Raia Software': not authorized 2019-12-24 14:15:40.285 INFO Scripting: plugin: SKIPPED 'USN-Deckcrew': not authorized 2019-12-24 14:15:40.285 INFO Scripting: plugin: SKIPPED 'VAICOM PRO by 315 Interactive': not authorized 2019-12-24 14:15:40.285 INFO Scripting: plugin: SKIPPED 'VPC Object by voc & virpil.com': not authorized How are others getting OpenBeta configured to support all Tacview and content plug-ins? Thanks!

I purchased F-14 via OpenBeta My Error log shows: 2019-12-24 14:15:40.163 ERROR EDCORE: Can't mount coremods/aircraft/f14/textures/lns_f14_exterior. Drivers errors: 2019-12-24 14:15:40.163 ERROR EDCORE: EDCDriver: there is no directory coremods/aircraft/f14/textures/lns_f14_exterior.edc 2019-12-24 14:15:40.163 ERROR EDCORE: FSDriver: there is no directory coremods/aircraft/f14/textures/lns_f14_exterior 2019-12-24 14:15:40.163 ERROR EDCORE: ZipDriver: Can't open zip archive coremods/aircraft/f14/textures/lns_f14_exterior.zip. 2019-12-24 14:15:40.871 ERROR EDCORE: Can't mount mods/aircraft/f14/textures/color/dynamic. Drivers errors: 2019-12-24 14:15:40.871 ERROR EDCORE: EDCDriver: there is no directory mods/aircraft/f14/textures/color/dynamic.edc 2019-12-24 14:15:40.871 ERROR EDCORE: FSDriver: there is no directory mods/aircraft/f14/textures/color/dynamic 2019-12-24 14:15:40.871 ERROR EDCORE: ZipDriver: Can't open zip archive mods/aircraft/f14/textures/color/dynamic.zip. 2019-12-24 14:15:40.873 ERROR EDCORE: Can't mount mods/aircraft/f14/textures/chromecatlegacy. Drivers errors: 2019-12-24 14:15:40.873 ERROR EDCORE: EDCDriver: there is no directory mods/aircraft/f14/textures/chromecatlegacy.edc 2019-12-24 14:15:40.873 ERROR EDCORE: FSDriver: there is no directory mods/aircraft/f14/textures/chromecatlegacy 2019-12-24 14:15:40.873 ERROR EDCORE: ZipDriver: Can't open zip archive mods/aircraft/f14/textures/chromecatlegacy.zip. Is everyone getting this?

I heard Axman, responded, we hopped over to the new channel and I got the Bullseye coords and then vectored in. I had already overshot his location by the time I had the new waypoint so I had to turn around. I got within 1 mile of his location and sent the message that I was on target (the only available message) and from there it was radio silence. My inference is that I did not arrive within a time window and so the triggers did not fire. What are your parameters once Axeman has given his vector to Dodge 1?

I just completed mission 4. I killed the insurgents, got the Axeman assignment, got the Bullseye vector and went to those coordinates and couldn't raise Axeman after repeatedly circling his coords and reaching out on the new Guard frequency. I have the Log and the Trackfile. I'm interested in which triggers or timing I missed. Kudos on the great writing, audio and thoughtful campaign design! Just curious how I could have handled it better as I ran the mission 3 times and this last time had the coordinates and entry points fairly optimized..

I just got the Mi-8 and see there is an updated Mimino campaign for 2.5 in Russian. Is there some way I could help to convert it to English for those of us looking for new Mi-8 missions? Thanks!

Any new info on ILS at many airbases? I have run A-10C missions out of Batumi and Nellis and neither have ILS working while I am dialed into the latest info on ILS frequency and runways from other threads.

Fixed - Oculus Rift S driver issue with Beta You triggered a reminder that based on another recommendation for VR performance that I set the Oculus software settings to use Beta drivers. When I set that back and triggered a full re-install of drivers for Oculus, the mouse came back! Thanks for the thoughtful, generic advice! ;)

I was successfully using Rift S during the last 2 months but this week the Mouse in cockpit disappeared. Before you reply with all of the stock answers, I have spent considerable time changing all the VR mouse settings, trying the VR pointers (which are ok but you can't tune radios) etc. This was working even as late as Tuesday and Weds the mouse went away and I have spent about 6 hours trying all possible permutations. (VR Panel mouse on/off, capture mouse cursor on/off etc.). I can actually see the cursor in a frame but it disappears when it comes into the bounding box of the cockpit. I have also experimented with display configuration for different resolutions and # of screens (I run a 4 monitor setup with 2 Nvidea GPUs). As an aside, my recently built rig is as high performance as they come and still my FPS with dialed up setting is 20. When I use the default VR performance settings I only get 40. Whereas in 3 monitor Ultra quality configuration with every setting maxed out I get 170FPS. Clearly, ED needs to assign some VR performance engineers. Thanks for any thoughtful, knowledgeable suggestions about Mouse in VR. Please don't provide generic answers because I have already tried about 50 different permutations. I'd be happy to hear if anyone else has this issue. OriginPC Millenium, Intel i9-Octo-core 32GB RAM, Nvidia RTX 2080Ti (11GB RAM), NVidia GTX 1080, 2 1 TB SSDs, 4 Asus Monitors (1 4K, 3 HDR), Oculus Rift S, TM Warthog Hotas.