slughead

This isn’t a script error. This is a fault with the thrustmaster code. Either you haven’t updated the firmware or the target software or both. Search the thread for “filter”. I am not Thrustmaster support and I am not going to respond to these queries in future. If you look back through the posts you will find that all of these questions are related to the installation of the Thrustmaster software, or mismatched firmware and software. Not the script.

All USA customers please note that the Trump import duty is now in effect. All new orders will be subject to a 10% import duty plus handling fee (currently 50 pence) and will be included in the invoice so that the postal delivery duties will be pre-paid. I will absorb this for current orders that are currently in production. Shipping costs are also currently under review and will be updated shortly.

Excellent! Enjoy!

I said earlier that DCS2Target doesn’t use export.lua. The early versions did use export.lua. You should fully uninstall DCS2Target. Remove all of its files and folders. There should be nothing in export.lua about DCS2Target. I would remove both mods and erase export.lua and start over.

Oh sorry. The Data Transfer Cartridge that DCS added recently. I’ve not had a chance to use it yet. Can you provide your DCs.log file from a mission when you have the problem. There may be an error visible in there that identifies the problem.

Honestly I’ve never heard of it. I actually exclusively fly in VR, so I don’t see the lights on the Viper. I wrote DCS2Target for fun and interest as there was nothing else available.

Can you provide a link to DCS DTC? Is it purely software or does it need any hardware, iPad etc? I not going to promise a solution. I am on holiday this week and have Slugmouse orders to manufacture and ship in my return, then folk from the other F-16 simulator that require some software changes. Then I can take a look at this. However, I very much doubt there is anything I can do, about 0.1% chance and my code only reads data. Have you raised this with the DCS DTC developer?

Do you have the latest DCS2Target scripts from my GitHub page?

DCS2Target doesn’t use export.lua. It used to use export.lua until I found a better way with the intention to prevent the export.lua conflicts. Also DCS2Target does do any redirection. It’s a read only program. Perhaps you’re running a very old version of DCS2Target.

That’s great. Whenever there’s a problem always go back to basics. Strip back to just what you need, test, then start adding back one at a time. It’s the same with DCS. Remove all mods and start from the bare minimum. Add mods back until you find the problem,

That would be HTCC and Leap Motion. The HTCC website has details about using the Leap Motion Controller with HTCC: Home | HTCC Hardware: Leap Motion Controller 2 or Leap Motion Controller 1 Software as per the HTCC website instructions: Ultraleap | HTCC

Busy, busy, busy! Two orders shipped today, one will go out tomorrow and four are in the process of being built and are expected to ship this week! As always, all within our typical one- to two-week production schedule.

You’ll need to contact Thrustmaster support to resolve this.

Have you tried any of the Thrustmaster supplied scripts?

Make your own thread please.

I haven’t made the switch to a 5090 yet as I’ve not seen enough feedback about the gains. It’s interesting you say you get 90fps. Could you clarify in what scenario though? I tend to do my tests in a few places. The ramp at Nellis on the missions that come with DCS. A fast flight at 1500ft from the rads on ramp mission in Dubai over populated areas, corner speed turns around the sky scrapers, or flights over Cairo with corner speed turns.

Do double check the firmware in your panel is up to date.

Have I got this right? People complained from the day the AVA was released that it is too wobbly. Thrustmaster fixes this (?) by releasing a new damper and expects the consumer to pay to fix their design flaw? Hmm.

As I have said to people many times, this is a Thustmaster problem not a fault of the script as the script has only gone as far as running standard Thrustmaster code. So I am just suggesting basic fault finding techniques such as, connect direct to PC, install the latest software and firmware, disconnect any other joysticks, etc. Have you updated the firmware in your Viper panel? Have you tried a script that Thrustmaster supplies with the panel/Target software that configures/controls the Viper panel? If you have, you will have exhausted all the basic fault finding steps that Thrustmaster themselves would ask you to do and you will need to take this issue up with Thrustmaster directly.

Are you using a USB hub? This very same problem was reported just one page back.

First post, need help section.

My experience of first line tech support is that they have no clue. You could speak to another and get an utterly different made up story. You’ll only get the truth from the development team.

Ten orders shipped this week! Two more to build and ship and should be going out in the next few days. Orders have been flying out to USA, Hong Kong, South Korea and the UK!

I’m going to assume this has sold. If anyone is looking for a pointctrl alternative, take a look at the Slugmouse.

Have you considered Slugmouse instead? It has no waiting lists and is shipped within one to two weeks.