CrossWiseRanger

BLUF: Use looping waypoints to restart sound. PROBLEM: Radio Beacon in UH-1H stops working when a call is made to or received from ATC. This issue can be seen in the Elbrus Rescue mission. Actually in any mission with beacon usage. Radio Beacon works until either transmit or receive on any UH-1h radio. Not a problem with the simulated radio chatter that is coming in as a message; can tell a message as radio volume does not impact the chatter. Waypoint radio transmission is a Perform Command which activates immediately. The loop requirement continues the audio until another radio transmission bumps from playing. No provision for automatic restart of the transmission. SOLUTION: Have the infantry RTO move between two waypoints. Using the Elbrus mission. For WP 0 delete the "Hold" and add "Perform Command - Go To Waypoint - 1." Create Waypoint 1 with "Perform Command - Go To Waypoint - 0." This creates the loop. Radio transmissions will still stop the beacon. However, the beacon will be restarted when loop returns to WP 0. Adjust the distance between waypoints and speed in WP 1 to determine time interval. In my example (below) distance is 17 feet and speed is 2 kts giving a time between WP's of 5 seconds. Times 2 results in beacon reset every 10 seconds. Once you have your desired time in WP 1, set that speed in WP 0. Comments on Elbrus Mission -- interject some realism for those interested. 1. The mission has radio chatter and beacon on same radio, the ARC-131 with Homing. Not possible; either voice or beacon. Assuming the team either has an ELT or using the Russian helicopter one, they could communicate via ARC-51BX on Guard of AM 243 Mhz with voice since ADF not functional in DCS. 2. Service ceiling for UH-1h is 12,700 ft. Mission requires 18,500 which is not happening. 3. Max of 30 minutes at altitude of 12,500 before oxygen required. Having been a Special Forces Halo team leader flying around multiple times at that altitude; your performance degrades rapidly. And all we had to do was get off the ramp. The AF would pass an O2 bottle around for us to take draws off of. One hit and it was like someone turned the lights on in a dark room.

Beacon Loss with ATC Call -- Solution Had the same problem with Elbrus Rescue mission. Actually any beacon usage. Beacon working until either transmit or receive on any actual radio vs the simulated radio chatter that is coming in as a message. (Can tell message as radio volume does not impact the chatter). Solution is to have the infantry RTO move between two waypoints. For WP 0 delete the "Hold" and add "Perform Command - Go To Waypoint - 1." At Waypoint 1 include the same "Transmit Message" as in Waypoint 0. Then send as above from WP 1 back to 0. Radio transmissions will still stop the beacon. However, beacon will be restarted at next WP. Try with two different sounds to see that is actually changing. Issue resolved.

Target - Cease Fire Bingo BuzzU. Logged in and $9.99. Additionally, wasn't familiar with the "miles" and got it for no cash. Thanks.

When Discount Applied I'll ask a different way. Non beta, have C version. The E-shop has the II listed for $79.99. Also has this disclaimer: "Warning! This product cannot be refunded or exchanged in whole or in part, regardless of the payment method." Added to my cart, proceeded to check out. No change in price. When is the discount actually applied?

Where is the Magic Buy Button? So, if we are not running beta, how do we purchase the II now so as to get the discount? I have the A-10C, but have not found a way to purchase on the site.

Cgjunk2 - thanks for the tip. Didn't work. Signed out and back in. Turned module off and trashed - though Spitfire folder did not go away. Deleted Spitfire folder manually. Ran repair, again. Restarted computer. Reloaded Spitfire module and turned on. FINALLY - the Spitfire Icon is back in the bottom list and module working again.

My Spitfire module is now missing. Had been working perfectly. Also, the module icon no longer shows on the start page with the others along the bottom. Module shows as loaded in module manager. Ran repair. Deleted module and restarted. Module still shows as loaded. Renamed the Spitfire folder in Mods / aircraft. Still shows as loaded. After renaming, deleted module in manager again and restarted. No joy. Running 2.5.6, latest version. Any ideas on how to get the Spit working again?

BuzyBee, Thanks for the quick reply. Me error was in not realizing that only the elevations are automatically included. That is working.

How Download Maps Where or how do I download the Normandy and Caucasus maps into TacView? See references to them being available with 1.8.2. Thanks.

How Reference Unlisted Tokens With DCS running, upon launching VoiceAttack, the following information appears: Nearest ATC: Tbilisi-Lochini. Player Rebel entered module UH-1H Huey, unit callsign Uzi11 DCS mission | UH-1-IA-Free Flight ------------------------------------------ Plugin 'VAICOM PRO 2.5' initialized. I am already using the published tokens such as: {TXT:vaicompro.playerdata.currentmodule.name} How can we access those items such as "Nearest ATC", "Player", etc. These are not listed in the latest manual of March 2020. Thanks.

Still No Joy Found nothing that appeared related to V in dcs.log. On loading, will list: player x entered module UH-1H Huey unit call sign y. {TXT:vaicompro.playerdata.currentmodule.name} is not working. Logs "----" instead of aircraft module such as UH-1H. Same with .cat and .version. It does work occasionally. Have found no relation to when start V versus DCS. Are there any settings that could be effecting this? Thanks.

{TXT:vaicompro.playerdata.currentmodule.name} Not Working Running Vaicom Pro 2.5.10. {TXT:vaicompro.playerdata.currentmodule.name} is no longer working. Logs "----" instead of aircraft module such as UH-1H. I use this to tailor keys to aircrafts types. Worked great in the past. Anyone have a solution or this same problem?

Issue Resolved ***** Yurgon -- you are an Ace. Thanks. Just tried with static objects. Laser works as expected and as you reported. Nothing else is detected. Resolves my issue. Though disappointing that the laser doesn't actually work map wide. That would seem to indicate that the only targets DCS wants us to engage are static objects. I on the other hand like to fly around and see if I can hit random objects. Gives me a better understanding of the systems.

Update with video linked - worked in past This video by ExcessiveHeadspace at the 8 minute mark shows TGP laser employment. Can clearly see the TGP coordinate change when lased as well as having the mark point with a different coordinate from the lasing. Can someone confirm or deny that the laser is ranging? 1. If you can confirm working, then it is something I am doing wrong. 2. If can confirm not working, then how do we get this bug reported?

Updated problem with images Image 1 shows the TGP at the base of the building. Image 2 shows the same face location of the building except at the top. Image 3 shows a long range view of the building. Notice TGP in point mode, easily within range, and laser on when latch the laser. The coordinates of image 1 and 2 (base of the building and top) should be the same with the altitude different by about 180 feet. Can view the coordinates in the images. I remember when flew over a year ago that toggling the laser on immediately showed the change in the TGP coordinate. The TGP point at the top of the building is reporting the coordinate to the slant point which is behind the building, approximately 210 meters away. Also, both points are showing elevation of 16 feet. Could someone please try their laser and see if it is working for ranging?

Clarification Yurgon, Guess I wasn't clear enough. Trying to lase a building. The TGP shows the ground coordinate behind the building. Lasing, the coordinate does not change. Can you lase a building and get a different coordinate than originally shown by the TGP?

Cannot get the TGP laser to provide a coordinate. It has been over a year since flew the A-10C, but I cannot figure this out now. This worked great before. Followed steps on several tutorials. TGP SOI, laser on, "L" flashes while marking coordinate. Location result is same as without using laser. Laser marking INOP; or, what am I missing? Thanks.

I have done that and everything Oculus has ever suggested. Works fine except for DCS.

Started as a problem occurring every several weeks. Now occurs after finish a DCS game. When go to start DCS with VR, the Rift cables are no longer connected. Per Oculus, the solution has been to completely uninstall and reinstall Oculus. This works temporarily. Requested support from Oculus, but they have not provided a solution to date. So, a graphics card configuration question. I have an ASUS GeForce GTX1080 and a multisynch display running via Direct Link cable. Both the display and Rift are connected to my graphics card. Is this the proper setup? I tried running the display from the motherboard Direct Link port but this crashes DCS, though Rift cables stay connected. All drivers and software are up-to-date. Anyone else have this problem -- or have a solution? Thanks.

P-51D-30 Toe Brakes Effect Stick Your answer was close -- and led to solution. I had the -30 folder at that location. It contained all the files as the -25 except for the Saitek rudder pedals. :thumbup: Once added the rudder pedal file, worked perfectly. Thanks

On the -30 version, using toe brakes causes the stick to jump around making unflyable. When this first happened, I checked controls and axis commands were mapped correctly. Using Saitek PRO Flight Combat Rudder Pedals. I also tried deleting and reloading profile. No change. Can create a mission with -25 and everything works fine. If subsequently change that mission to -30, error occurs. Changing back to -25 does not eliminate the error. Also, if create a mission with -30 the error is there from the beginning. Conclusion: -30 has a bug that over maps toe brakes to stick.

Rift flying in UH-1h, version 2.5. Modified a mission to add wind to see how the wind effects tracking with ILS and NDB's. First noticed that the ILS was not working. Then that the NDB's were also not operational. The only setting changed between a functional and non-functional ILS and NDB is the setting for wind speed @ 33ft. Any setting not 0 gives inop nav. What is not working specifically. The UH-1h CDI vertical and horizontal pointers do not move. Shows flags for GS and LOC. Morse code is heard. On A-10C, the ADI Course Warning and Glide Slope Warning red flags are showing. Bank Steering Bar not moving and Pitch Steering Bar not visible. No morse code is heard. Tested on Kutasi and Senaki airports. Tested with an old mission and a newly created one. Also tested with both the UH-1h and A-10C. Problem replicated across all scenarios. Bug?

What do you want FFB to do? Have looked at the possibilities of force feedback for a flight stick several times. The original idea was a stepper motor for each axis. Would be simple to implement. There are two primary drawbacks. 1. The amount of force applied in the leverage of the stick exceeds what the stepper motor can handle. 2. The step size was too large for accurate control. The last few days have been trying to understand the trim system on the A-10C. There are approximately 20 increments for nose down and 40 for nose up. One of the main concerns I have with the trim system is that it requires two simultaneous actions. Activation of the trim and then an unrealistic repositioning of the stick to offset the trim input. Once I could observe what the trim was doing and then remembering my private pilot days it occurred to me that I have been looking at FFB from a wrong perspective. So I'm going to ask a somewhat silly question. What are you trying to achieve with a FFB joy stick? My concept is to feel the loading of the elevator and aileron in reference to the set trim position. That would allow for trimming of the aircraft by feel. Your thoughts please.

How do we get the In-game Console as referenced in the DCS User Manual? Example: COCKPIT INDICATION TEXT IS EQUAL TO (requires console).

Maybe Asked Wrong Question Grimes - thanks for the info. Disappointing news that cockpit actions cannot be done from a script. So for repetitive training, who wants to manually reset all of the controls each time restart a mission? For example, flying with NVG's would take a lot of time just to reconfigure the lights. This is a disincentive for playing complicated missions. Also wastes time while doing training for a specific task to AGAIN reconfigure the cockpit on start. So, maybe I asked the wrong question. Once I have all of the cockpit triggers set in a mission, how do I transfer that "set" for use in another mission? For example a set of triggers that changes the cockpit configuration between "Day", "Night", and "NVG" mode. I use one of the spare buttons on the UFC to trigger the change. Surely the answer is not to manually reenter the data in a new mission; or, even to start that as a mission shell for aircraft trigger setup!