slughead

I currently use this one. It works for me. I won't guarantee it would work for you. Who knows how well they are built from unit to unit or how they will react with different appliances connected? You'll just have to try it out for yourself. But first, have you connected directly to your PC to make sure the hub is the problem? https://amzn.eu/d/7SQ8Zf6

Sure. I’ll see what I can do.

Did you mean to post that here or on some other topic?

All orders that were placed this week are shipping out tomorrow!

Always connect directly to the pc when fault finding. Not all usb hubs are equal and many cheap ones are poorly constructed and are electrically noisy. Connect direct to the pc then see. If it works, get a better hub or usb pci card.

Are you using a USB HUB?

Returning to this to say that in one of the recent updates it appears that AI behaviour has improved massively. At least in my test flight. AI pilot appears to manage fuel better, or perhaps he's been given more fuel. They're not crashing into hillsides and they are maintaining close formation better than I have noticed before. I've not managed to test their bingo state and whether they eject when they call bingo.

Thank you.

Thanks for the link. However, that thread has gone far off-topic about cost. I specifically said that cost is not a relevant factor for me, and I'd like to cut to the chase. I also asked specifically about use in DCS VR. Hence, I posted in the VR section of the forum, not the hardware section. Not all VR users look in the hardware section, but all DCS VR users are more likely to look in the VR section. But mainly, I couldn't find a single person in that thread who has made the upgrade. Maybe I missed it.

Has anyone upgraded from a 4090 to a 5090, and if so, what is the performance difference in VR? Ignore cost, that's for another topic of conversation. This is purely about performance concerning DCS in VR. Conjecture of performance is also not relevant. First-hand experience replies with the two cards only please. Youtube videos are also not your first hand experience and I can search youtube myself for that thanks.

All current orders are packed and will be shipped out this week, including a complete replacement (FOC, of course) order that the couriers managed to send to the wrong continent on the opposite side of the world. C'est la vie! Would love to see dome photos or videos of you all with your Slugmice!

Formal release Added F-18C gear handle lamp and mapped to flash Warthog user LED1. F-18C speed brake remains on Warthog user LEDs 1 through 4, with LED1 shared with gear handle lamp. Fixed F-18C issue where console lights would remain on for subsequent cold starts when the battery switch is set to OFF when entering the cockpit. Fixed the behaviour of lights when missions are restarted and aircraft are shutdown. Corrected LED test when script starts. LED test on mission end removed. Warthog console lighting and all indicators extinguished on mission end. Ethernet port number moved to a random port in user port space. DCS2Target is now at version: 1.0.11 TMHotasLEDSync is now at version: 1.0.8 Other versions of dcs2target/tmhotasledsync are not compatible with this release. You must only use the versions listed above. For support issues, read the first post thoroughly, then follow the "Need Help" section before requesting support.

From the log: Error:InitSocketServer failed with 0x00002740 : Only one usage of each socket address (protocol/network address/port) is normally permitted. I expect that indicates that either two copies of the script are running or something else on your system is already using port 1000. If you reboot your PC and try again, that should eliminate any duplicate execution of the script you may have managed to do. If that doesn't solve it, try turning off all other software except the script and see if it works. If it does, you know something else is using port 1000. Then, shut down the script, turn on one of the programs you shut down previously, and start the script again. Repeat until you find the culprit. If that fails, your firewall might be blocking the Thrustmaster software, and you will need to enable it in your firewall, probably the Windows firewall.

Excellent. Thanks for your thorough testing and clear reporting. I will try to get a formal release out this evening. Enjoy!

@CM2024 Try these. led_utils.tmhTMHotasLEDSync.tmc

Yes. That’s an easy one. Perhaps just turn them off altogether instead of doing the LED test? Just leave the LED test for when the script starts on the Thrustmaster side.

@CM2024 Could you try the following patches please? Place this one into your dcs2target folder fa-18c_hornet_lamps.lua And this one where you TMHotasLEDSync files are led_utils.tmh Both files replace existing ones. This should solve the problems you raised and also improved LED test on start and end of mission plus the Warthog backlight will be turned off when the mission ends.

Right ok. Thanks for the thorough test and explanation. I will have another look at this.

That’s usually the result of the DCS side not sending enough bytes. So it would sound as though you may have missed some files or forgot to update the DCS scripts. Both the hooks and dcs2target folders. Can you check and let me know how you get along.

This has now been added. Warthog user LED1 will flash when the gear handle lamp is lit. The speed brake still uses LEDs 1 through 4 with LED1 combined with the gear handle. This should be fixed. Please use the latest dcs2target.zip (v1.0.11a) and tmhotasledsync.zip (v1.0.8a) This is a pre-release. Please let me know how you get on so I can formally release it should there be no new problems.

Thanks for the report. I'm just sitting down to work on the F-18 script now so that was good timing.

I’ll see what I can do! Maybe combine the bottom led with the speed brake. I might at some point design an indicator panel for landing gear lights, APU etc that connects via USB or Bluetooth and make it available as a product.

Graphics. HUD Symbology affected by engines heat blur effect - fixed The team must be running out of things to do! It's nice to have this finally done though.

What’s in your export.lua file? Post it and I’ll take a look. dcs2target stopped using export.lua a long time ago.

Please follow the troubleshooting section in the first post of this thread.