sgilewicz

Thanks guys. If the script was written to force smoke marking for wingmen, what is the DCS command to attack targets marked by smoke? I don't recall seeing it.

Does marking targets with smoke in SP for wingmen provide any extra accuracy on target versus broadcasting the SPI? I'm running a Maple Flag TTQ mission and the briefing recommends using WP rockets to mark targets for my wingmen. It seems to be an extra step without purpose. Thanks for your observations.

I went through hell several months ago trying to get through this same mission because of the same issues. If I recall correctly the single biggest solution was changing the MFCDs from night to day. I know it seems screwy but I found the night settings were blurring smoke to the extent that targets were completely masked. I have used day settings for the MFCDs ever since. Hope you get it sorted since it kinda sucks doing the same mission over and over when you know you aren't the problem!

"All credits to AlaskanGrizzly for this. This seems a great program to create custom kneeboards and after seeing dburne's entry about working with it in VR, i thought of having a go. However, nothing in the world i do makes this thing work. I'm stuck at creating a profile and i have no clue how to make one (the manual is a bit old because some things seem to have been changed in the software but the didn't make it to the manual yet. One of these things is creating a profile. I managed to set some options (LOL), import a PDF (A-10C manual), created a Custom Kneeboard, select the A-10C aircraft, added a group, moved that over to the Custom Kneeboard and then build a custom Kneeboard for the A-10C. All without a single error, i can see quite some .jpg files in the A-10C which are created out of the A-10C manual pdf but... ... i'm not able to create any profile. If i go there i don't have the same options as in the manual, i have Kneeboard Profiles instead of Kneeboard Settings (what's in a name?) but once in that menu, i can't do anything. I don't have the option the even create a profile, all i have is Modify (greyed out because i obviously don't have one created) and Restore Defaults so i need a bit of guidance because i don't have a single clue on what i'm missing except the fact that i can't follow the manual because i don't see/have what i supposed to see/have." Exactly the same steps and exactly the same problem here! Where is the settings page? MIA on my install.

Okay, 1. A-10C not showing in PTT config UI: License server was down and Vaicom support responded right away and got the server provider on board and my licenses registered. Good on the support team! 2. Appendices not working: Vaicom support pointed out that appendices have very specific commands and sequence: "my target" is not acceptable using appendices. Instructions to flight members specifying weapons and directions must be in the following sequence: recipient__target type__weapon__direction 2__artillery__guns__west - works 2__artillery__west__guns - will not work per Vaicom support since weapons MUST precede direction in the instruction set. I will be spending a lot of time with this but I can definitely see its potential for streamlining comms. It will be time well spent and thank goodness for this forum and thread!

Okay, the Vaicom configuration page indicates that I do NOT have A-10C enabled. A look at the Vaicom troubleshooting video indicates deleting the export.lua from the user\saved games\DCS\scripts folder: Done and setting the path to the DCS install: Done. It still indicates no A-10C in the Vaicom config screen. Obviously this is the reason for appendices not working. Is a reset or an uninstall/re-install in order. Many thanks for any direction you guys can provide. edit: I meant the Vaicom config PTT screen...sorry!

I have Vaicom Pro working but the appendices portion of the commands don't seem to be working (for example: "two...attack trucks from south with guns" in the Georgian Spring instant action A-10C results in the wingman boring straight in from the north and firing mavs). I have extensions enabled in Vaicom config preferences but I noticed that not all modules support extensions. Is the A-10C mod too old?

That is just too cool! Many, many thanks and virtual beers to you!

Got it sorted! Needed to enable POVs in VA joystick settings and assign 4 way switches to them. Just did a test and all is good (I had cleared the DCS radio mappings prior to the problem as you suggested so the issue was VA configuration not Vaicom Pro). Thanks for the response and I can't wait to get proficient with this. BTW do you have a good set of instructions for importing my non-comms related VA commands?

CH Products Hat Switches Not Detected by Vaicom Pro Hi all, I just installed Vaicom Pro and, after watching Hollywood's excellent video plus reading through the manual, fired it up and began configuring the PTT buttons. I have been using Voice Attack for years and have my radios 1-3 mapped to my CH Products Pro Throttle 8 way hat switch. The Vaicom configuration interface is does not see any action when the hat switch is used. The same is true for the 8 way hat switch on the CH Products Fighterstick. All other buttons and switches work without issue. I REALLY want to keep my radio calls mapped as is (since it took me a month back in 2017 to get everything sorted on my HOTAS setup!). These hat switches work fine in Voice Attack stand alone so any ideas why this is an issue with Viacom Pro? Many thanks for any suggestions! And be safe with the pandemic issues.

randomTOTEN, That IS quite painless. I was envisaging re-activations and re-installation, etc. Thanks for the guidance. This will be fun!

Hi all, Currently DCS is on a 250GB SSD (drive letter D). I purchased a 2TB SSD for DCS use only and wish to keep the 250GB drive and its assigned drive letter. The reason is all programs (except Windows 10) are installed on the 250GB and I don't wish to go through re-installation of dozens of programs. Drive C is an SSD used for Windows exclusively. Drive E is a 4TB SSD Hybrid used for all games but DCS. My ideal outcome would be: Drive C: no change Drive D: removal of DCS Drive E: no change Drive F: new drive with DCS only Any tips for achieving this transfer are much appreciated. Cheers!

Guys, I know the IR is for designation only. The issue is when using Mavs, by the time you spot the pointer its usually too late to slave and shoot the Mav unless you do a go around as Yurgon suggests. BTW Yurgon, that worked a charm even though the FE got impatient. Too bad! I called end of vul and just re-established a new vul to finish the job. TTQ12 complete! Yay and thanks!

Yurgon, I think that your philosophy of running in, confirming and then turn around for the Mav launch makes the best sense. I will give that a go. Many thanks! Harzach, if you consider my old 20/2000 eyeballs an upgrade we're both in trouble!

Good points but my issue is the pointer is generally not visible until the Mav is approaching or exceeding its gimbal limit leaving little or no time to lock on and shoot. In other engagements in the same mission the IR pointer is specified and guns or rockets are requested. This seems to make more sense (at least to me) since they are short range and require the Mark 2 Eyeball for guidance.

Like the title says, the JTAC in the second Tactical Training Qualification campaign mission specifies a type 3 engagement using Mavs with an IR pointer mark. Since it is type 3 and Mavs are standoff weapons, the use of IR pointer seems counter productive. Any thoughts? Thanks

OK claw. Thanks for the explanation. I was looking for an easy way to type in the UFC scratchpad but I'll live! Thanks again.

Ok, It's installed and comes and I'm able to type in the window but unable to transfer the text to the parameter of interest. For example: I type in 5000 into the mod scratchpad widow. I then open the DSMS page, open the GBU-12 profile and click on the Min Alt OSB. Nothing happens. Am I missing something? Would love to use this mod since getting data into the various Nav and Weapons pages can get cumbersome especially in flight. I am not using VR just everyday 2D. Thanks for any help!

timo144, Not sure what you mean. I'm orbiting around the IP while setting up the target coordinates and weapon profile that the 9 line and remarks have passed. Once they are set I call "IP inbound" and JTAC will acknowledge with "continue".

I think I have figured out the issue. I have typically placed my ride in an orbit while taking down all the JTAC instructions. Only after replying "remarks received" do I usually begin creating the new waypoint from the 9 line coordinates. I get a "no mark" every time prior to finishing the waypoint. It seems I am too slow with data entry! Creating the new waypoint during 9 line transmission enables me to make an IP inbound call with subsequent JTAC "continue" enabling me to prosecute the target. I have tried it twice successfully so it may be stupid simple on my part. I am curious why the "no mark" when the JTAC laser hasn't even been turned on yet. I could understand if it was on and the user was concerned about burnout but the "no mark" call is made prior to "IP inbound". Not a problem if it is what it is, just like to know the logic. Thanks all!

Thanks everyone. Ramsay, from the link in your first post here: "I believe if the JTAC is lasing for too long they will turn off the laser and say "NO MARK". " I am getting the "No Mark" call long before heading in from the IP and calling "Laser On". Later in the same mission another tank is specified as a lased target and everything works fine. Still confused but I have some things to try and note. I will definitely post back here. Thanks again!

As the title says, the 9 line specifies target marked by laser (code 1688) at UTM coordinates MM823023 in Maple Flag's TTQ Mission 11. The issue is while creating a waypoint with the supplied coordinates the JTAC communicates a "No Mark" instruction. This creates a bit of a dilemma. If I assume the laser mark has been cancelled and set up for self lasing I never get cleared in hot. On the other hand, if I assume that the target is, in fact, being lased then LSS never detects the laser even though the approach is from the proper IP and heading (seems that the instruction is correct). Any ideas? Much appreciated!

Perfect! That was exactly what I was looking for Yurgon. The situation is a mission employing gbu-12 on a tank with jtac lasing. I wasn't seeing the search, detect and track cues on my type. Yurgon, you explained the situation perfectly. Thanks to all you!

Can't find an answer to this one. When a target is being lased by JTAC should the A-10 lasing be enabled? I would think not as long as the TGP is in LSS but I can't confirm this. Thanks!

OK, I can report some success. Following hornblower793 recommendations from the https://forums.eagle.ru/showthread.php?t=239907 thread, I deleted the fxo and metashaders2 folders from my saved games directory (I did NOT do anything else). Launched DCS and started the night mission mentioned in the OP. The difference was quite significant. Although there is still significant smoke, it isn't sufficient to prevent quick and confident targeting. I did try using boat switch center for illuminated targets but the contrast is still lacking. With FLIR working, for the most part, the EO targeting isn't really necessary IMHO. I exited DCS and restarted to see if the changes were persistent and I can report that after 3 restarts the TGP/illumination issue is still manageable. Hornblower793 listed additional steps but the first step seems the trick at least for now and for me. Many thanks for giving me options to try. You guys rock!