slughead
-
Posts
1361 -
Joined
-
Last visited
.jpg.63758642d43f5fd6c35a83f8a7485bde.jpg){kind=avatar}
Recent Profile Visitors
4734 profile views
-
As TFS and I said earlier, with the Quest 3 and its pass-through technology, you can see the WinWing hardware via the headset's cameras and carry on using it. Then use the built-in hand tracking of the Quest 3 and Slugmouse for all the other switches that you haven't got a physical device for. -
You should consult the HTCC website (Home | HTCC). It says the Varjo Aero is not compatible as it doesn't have hand tracking hardware. You would need to add an UltraLeap Motion Controller. I have no idea what "Lighthouse" is.
-
Whilst I haven't tried this myself, I would consider the Quest 3 and use its pass-through feature that enables you to mix VR and the real world. For all other cockpit switches that you do not have physical switches for, use the Quest 3, HTCC and Slugmouse. As I said, I haven't tried this myself, so it would be prudent to seek the views of someone experienced with the Quest 3 and pass-through. Or ditch the Win Wing kit and go Quest 3, HTCC and Slugmouse - fully VR. As I like to fly a variety of airframes, I find that this is the best option.
-
Just one week left of the end of summer sale. If you don’t have your ring size yet, place your order before the end of the month and send in your ring sizes when you have them to secure your Slugmouse order at the sale price.
-
That’s good to hear. What was your solution?
-
Here's a user review...
-
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.
