slughead

I can't say that I have noticed this.

Update! The tool has been renamed to DCS2TargetExport. Why? Well, it now supports the Warthog as well as the Viper Mission Pack... and now the Viper Panel too - or at least I hope it works for the Viper Panel. Wait, there's more.... it also supports many more aircraft. Er, but don't get your hopes up. The F-16 indicators are only shown in the Viper Mission Pack / Panel. Other supported aircraft only show the speed brake position on the Warthog. I'm open to alternative suggestions for the Warthog LEDs and those of the Viper Mission Pack / Panel. Please put your suggestions in a comment below. The links to the updated files are in the first post which has also been edited to show the new features and limitations. Enjoy! The next update will support control of the Warthog backlight level from the relevant cockpit control.

There's the reason. The Viper Panel is not supported in the build that you are using. Within the hour, I will upload a new version that should support the Viper Panel and the Warthog plus other aircraft. I say should because I do not have a Viper Panel to test with. You will be my guinea pig.

Can you provide the dcs.log and the output from the console window of the script editor please? What aircraft are you flying? Only the F-16 is currently supported.

You're going to need to provide more information if you want anyone to help. My crystal ball has a very limited range and can't see your settings.

Update: The speedbrake position is now indicated on the left column of the programmable LEDs display. The updated links to the files are in the first post. Both files are required.

Feature Requests ViperTQS Specific: Two Columns of LEDs: Speed brake - show the amount brake is open/closed Radar/Missile alert: Radar lock - all LEDs lit. Missile launch detected - all LEDs flash. Warthog Specific: Column of Five LEDs: Speed brake - show the amount brake is open/closed Gear: Gear Up - bottom four LEDs illuminated Gear down - bottom four LEDs off Gear warning - top LED flashing I can’t think of a way to allow more than one of the above. I also do not feel it worthy to reproduce indications that are already visible in the cockpit and/or have audible alerts. The speed brake is probably the most sensible one to implement in my opinion. I would also like to link the brightness of the backlight to the actual aircraft control. This may be possible on the Warthog but I am not aware of a way to do this on the ViperTQS. Please discuss/throw your ideas into the pot.

I believe I have fixed all of the issues raised so far. Please use the following thread to report issues and to get the latest updates.

Update... Fixed: Now working with multiplayer. Detects when aircraft is destroyed - LED states on the ViperTQS will be set to OFF. Script race conditions that cause the scripts to fail (crash). Removed FarmStick detection from TARGET script. Fixed case where the sync with the ViperTQS would not work if the mission does not start in a jet. Updated files are in the first post.

I have only spent two days on this. So it's quick and dirty. There is plenty of refinement to do. I'll take a look at resetting the LED state when the user drops out (eject/die/etc).

"Godlike" is 3072x3216. Most of us using Link run at a much higher render resolution for clarity. This explains why DCS is running smoothly for you - it's just not working as hard. As for the quality/clarity being as good as running at a higher render resolution, I guess beauty is in the eye of the beholder. I've not tried it myself to give any judgement.

I believe I have fixed the problem with starting a mission without entering an aircraft. Can you give this script a try? The script should ignore any aircraft other than the F-16C_50. Export.lua

Ah ok. I believe I have replicated this using the formation trainer mission from d0ppler. Once the mission starts, you are given a list of aircraft to jump into. None of the lights get activated. So I think I can use that script to debug and enhance the export script. Whether that will fully address multiplayer I can't say at this time.

Forgive my ignorance, I have yet to use multiplayer. How can you not be in an aircraft when the mission starts?

I suspected that might happen as others who have tried to export data have had this happen too. I don't know what the solution is, sorry. If anyone does, let me know! I wonder how DCS-BIOS does it.

Have you tried the scripts with multiplayer yet? It may not be compatible at all with multiplayer.

Good catch. I don't run any other exports so I haven't run into this problem. Yeah, this is something I need to try to work on. Not sure how though at this time. I will investigate. When you say fly again do you mean respawn without returning to the mission debrief screen? Possibly. I was wondering what to do with these LEDs. You're very welcome and thanks for the feedback. Right now I am working on an export for the "other F-16" simulator to do the same thing. Once I've done that, I'll come back to this although I may break away and fix item 3 in your list.

We pay 20%. Double the price isn't an extra 5% in VAT. What is the price on Amazon in Denmark?

It's £730 on Amazon in the UK. That's about half the price in Denmark I think. Meta Quest Pro - Advanced All-In-One VR/MR Headset : Amazon.co.uk: PC & Video Games

What Is DCS2TARGET? With the recent release of the new Thrustmaster Viper Mission Pack and Viper Panel, many users have shared their dismay that the landing gear and other indicators are not working/integrated with DCS. This isn't a fault of the product or Thrustmaster, as there are far too many applications, each with its unique style of exposing simulation data. It isn't fair to expect Thrustmaster to support all of those applications, and this is where the community fills the gap. Along with TMHotasLEDSync, you will also need dcs2target. Together, they enable the LEDs on the Viper Mission Pack, Viper Panel, and Warthog to relay the indicators in the DCS cockpits. There is a caveat, though, as I will explain below. For the Viper Mission Pack and Viper Panel, some LEDs can relay the indicators of the F-16 landing gear, the landing gear handle and the threat warning auxiliary panel. It also has two columns of five user-programmable LEDs. However, the LEDs in the threat warning auxiliary switches do not fully mimic those of the real aircraft. Specifically, the "altitude" switch can either be illuminated red or green on the Viper Mission Pack / Panel as opposed to "LOW" in amber and "ALT" in green. Also, the ACT/PWR switch can only be illuminated fully instead of individually for "S" and "POWER". Therefore, we have to accept some compromises regarding how the indicators of the F-16 can be shown on the Viper Mission Pack / Panel. For the Warthog, there is only a column of five LEDs for the user to configure. How It Works: The dcs2target.zip file contains a set of lua files that interrogate DCS and send the relevant lamp data to the Thrustmaster TARGET software running the TMHotasLEDSync.tmc script. The data is sent via TCP only if it changes. The TARGET script handles each packet through an event. Thus, it is fairly efficient and should not introduce any significant load on your CPU. The DCS simulation data is interrogated every 100ms (ten times a second). It’s not too taxing on the system yet fast enough so that we humans shouldn’t notice any lag. The TARGET script does not configure your HOTAS throttle for use with DCS. It merely controls the LEDs of the HOTAS throttle. If you use another TARGET script to map your device to DCS, I advise you to use DCS to map the axis, buttons and switches instead. However, if you wish to use a target script to map your HOTAS throttle to DCS, you’ll have to try to figure out how to combine this script with yours. Please don’t ask me to help with combining scripts; you’re going to have to figure that out yourself. Installation: The dcs2target.zip file contains two folders: Hooks and dcs2target. Extract the folders and save them in the "%HOMEPATH%\Saved Games\DCS\Scripts" or "%HOMEPATH%\Saved Games\DCS.openbeta\Scripts" folder or both if you use both stable and open beta builds. Your "%HOMEPATH%\Saved Games\DCS\Scripts" and "%HOMEPATH%\Saved Games\DCS.openbeta\Scripts" folders should now have two folders: Hooks dcs2export Unzip the TMHotasLEDSync.zip file to a folder of your choosing. Links to Files (GitHub Repositories): dcs2target TMHotasLEDSync Current Build Versions: TMHotasLEDSync.zip 1.0.10 dcs2target.zip 1.0.12 How To Use: Start the Thrustmaster T.A.R.G.E.T. script editor. Open the TMHotasLEDSync.tmc script from the folder where you extracted TMHotasLEDSync.zip. Start the script. Start DCS. Supported Aircraft: The following aircraft are currently supported: Aircraft Exported Parameters Supported TM Hotas Throttle A-10C Speed brake position, gear warning, cockpit unlocked and console lighting. Warthog A-10C_2 Speed brake position, gear warning, cockpit unlocked and console lighting. Warthog F-16 Gear, gear warning, TWA indications, JFS RUN, MAIN GEN, STBY GEN, FLCS RLY, EPU RUN and the speed brake position. Viper Mission Pack, Viper Panel FA-18_Hornet Speed brake position, console lighting*, APU RUN and GEAR HANDLE lamp. Warthog JF-17 Gear, gear warning, gear transit, master warning and the speed brake position. Viper Mission Pack, Viper Panel Su-25T Speed brake position. Warthog Su-33 Speed brake position. Warthog *When the F-18C, A-10C or A-10C_2 battery is set to "On," the TM Warthog console lighting level will be set to level 1, i.e., minimum illumination. This is a compromise to ensure that the column of LEDs will illuminate to reflect cockpit lamp states, such as the APU Run lamp, even though the console lighting dial in the cockpit might be set to off, or the generators may not be producing power. I expect to support other aircraft, such as the F-15 and F-14, as and when I purchase them. You are welcome to contribute to the project by adding to the scripts through the GitHub projects. Suggestions And Feature Requests: Feel free to make any suggestions for improvements as a comment below. Need Help? First, ensure you have installed the v3.0.23.1003 or later of the Thrustmaster TARGET software. Most problems are due to people running old Thrustmaster TARGET software and controller firmware versions. If that doesn't solve your problem, raise an issue in the comments below. Include your dcs.log and full TARGET script editor console output in your message (you can select, copy and paste directly from the TARGET console output using your mouse). If you are using a USB hub, try removing the hub and connecting your controller directly to your PC. If it works, you will need to consider replacing your USB hub with a better-quality model. Contributors: @slughead @Tigershark2005

No, not as yet is now... yes. I have written a Thrustmaster target script to handle TCP packets exported from DCS via an export.lua and associated utility scripts that I have written. Take the files in f-16c_50_lamps_export.zip and put them in your Saved Games\DCS\Scripts or Saved Games\DCS.openbeta\Scripts folder or both if you use both stable and open-beta builds. Unzip the ViperTQSLEDSync.zip file and run the ViperTQSLEDSync.tmc file in Target. The target script must be running before you start your mission in DCS. This script does not take control of the ViperTQS so you use it as normal in DCS without needing to reconfigure DCS. Only the LEDs on the ViperTQS are controlled by the script. However, if you use a target script to map the ViperTQS to DCS, well you'll have to try to figure out how to combine this script with yours. Please don't ask me to help with combining scripts, you're going to have to figure that out on your own. I chose to use TCP rather than reading and writing files as it's less demanding on the processor and it will not wear out your SSD/HD prematurely. The export script only sends an update packet if one of the lamp indicators has changed. On the other side, the target script will only handle a packet if it receives one. So in that way, it's efficient. However, on the DCS side, it is polling for changes every 100ms. The CPU effort involved is minimal so it should not affect the performance of DCS. Ideally, I would want to trigger an update when a parameter changes rather than polling the parameters periodically. However, I don't think there is a mechanism by which this can be achieved. So it is what it is. One thing you will notice is that Thrustmaster has not properly emulated the RWR lights. For example, the ALTITUDE LOW and ALT are either both green or red at the same time. You can't illuminate one or the other. So a compromise had to be made in that when LOW is detected, the LED colour is red. When LOW isn't detected the LED is green unless the RWR is powered off. Similarly, the ACT/PWR button is either all green or off. I do not think you can illuminate the A or POWER individually - it's just one LED for the whole button. So that's quite a let down in my opinion. Although I only fly in VR so whilst I've gone to the effort of doing this, it's the 2D flyers that will reap the rewards and be a little miffed at the same time. ViperTQSLEDSync.tmcf-16c_50_lamps_export.zip

The latest DCS open beta was released (yesterday) with a profile for the Thrustmaster Viper TQS. Alternatively, when I first got mine, I just went to DCS options, controls, select HOTAS in the search drop-down box and then for each throttle hotas action, double click on the cell that aligns with the ViperTQS and the action, then press the button / move the switch to that setting and the mapping for that action should be created. Repeat for all buttons. Do the same for axis. Make sure you save the config so you can reload it incase you need to reinstall / something goes wrong in the future.

Just saw your post on the PTC v60 thread on atmeta. Sounds good. I won't be rushing over to PTC as once bitten twice shy with the older reports of huge PTC issues and bricked units. Keep us updated please. Out of interest, are you running any custom settings in the ODT?

Start a new thread and put a screen capture of it in there.

I would suggest starting a new thread in the performance section of the forum. The major stutters, and by major I mean pauses of seconds and so not micro stutters are present in 2.8 as well but not as frequent. Give the single-threaded binary a try. If you have the same stutters in that, then it isn't due to core parking. Either way, best to generate a new thread as I don't think that this has anything to do with Oculus configuration.