TWC_Alamo

Also the Leap uses the PC processing power as I understand it. Neural nets are great for image recognition. The Youtube at about 6:20 shows the nVidia Deep Stream Application running on the Jetson Nano tracking multiple objects at 30 FPS from 8 simultaneous H.264 video streams.

This $99 Jetson Nano neural net development seems like the perfect platform to develop a finger tracking system for VR. Based on the image tracking examples shown in the YouTube video below, it seems that it would be possible track ten finger tips from multiple cameras in real time and map them in 3D to the clickable areas of a virtual cockpit. It would unload the heavy duty image recognition and tracking from the game PC and then just pass the 3D coordinates to DCS through a custom mouse driver or perhaps even DCS bios. Since neural net learn, seems like you could train it for the different DCS cockpits and it would improve over time. https://www.youtube.com/watch?v=RpO_a10QmLk Hey Miles how about a "Touch Control II using Neural Nets"?

That is correct. However you can still click and scroll the item your looking at with the mouse’s buttons and wheel even with “use mouse” unchecked. I have an 18 button mouse that I use its 12 key keypad to control views and other sim functions, so my right hand is often on the mouse when I need to flip a switch, so I click with the mouse. I really like DCS’s “Look” and “click” option in VR.

HF’s profiles work great in VR. In fact I don’t want to fly in VR without them. You can choose to use the trim hat (H1) as the mouse buttons and wheel. There is an option to use H1 for the mouse functions as a shifted press ( using the S3 button as the shift key) and use it for trim unshifted or vice-a/versa. The trigger zoom isn’t working for VR, but you can emulate it by also mapping the VR zoom in the GUI to the first stage trigger. Also VR zoom and VR recenter is mapped to H1 using a long press or double tap. You should definitely check it out.

Does anyone know how to create a Voice Attack command to return Windows' focus on DCS. I run multiple monitors on my system and although I have the "CONFINE MOUSE" box checked in VR, I often wind up with unresponsive flight controls because I inadvertently bumped the mouse and shifted focus somewhere else.. When this happens I have to lift the HMD and ALT+TAB back to DCS. It would be great to have a Voice Command to be able to say "Return Focus on DCS" and have Windows make it so.

Madrus, I'm not sure of the exact terminology. I think the "Microsoft Store" may be a physical store like we have in a local shopping mall, whereas the "Windows Store" is the app that comes in Windows 10. Anyway take a look at this video on how to uninstall the "thing" in Windows 10 that was causing my problems. May not work for you.

Take a look at kneeboard builder. It allows you to put a PDF on your kneeboard and view it in the cockpit or in VR. www.dcskneeboardbuilder.com

Madrus, I was having similar issues. In my case, the root cause was Windows 10 not disconnecting the real TM devices when TARGET initiates the Virtual TM Controller. The result is that DCS will have an axis mapped to multiple devices. One quick way to see if this is the case is to check DEVICES in CONTROL PANEL. If after you launch a TARGET PROFILE you see NO caution flags on your TM stick/throttle AND MFDs and the presence of the TM VIRTUAL CONTROLLER, then you have this problem. On my system it also was related to how long my system set idle before starting TARGET. If I fired up TARGET immediately after booting, I would most likely not have this problem. You might check that as well. Obviously, not everyone is having this problem, but it seems to effect some system after a recent update to Windows 10. My system was didn’t have this problem until about 3 months ago. It is related to conflicts between TARGET and the WINDOWS STORE. Removing the WINDOWS STORE solved this problem for me. Take a look at this thread for a solution: https://forums.eagle.ru/showthread.php?t=232737 Hope this helps

Problem Solved! I think I have stumbled across a solution to this problem. It appears to be solved by removing the Windows Store. From a post on the BuDs discord server, "Windows Store was interfering with TARGET when target tried to disable the controllers in order to create a new virtual controller. Windows Store wanted to use the new virtual controller and didn't like it, so it locked it. I ended up with 3 joysticks in the list." Anyway I removed the Window Store using the method described in this YouTube video (https://www.youtube.com/watch?v=ZAWJ73If6OM). I have tested it by letting my computer set for tens of minutes and the running TARGET. The profiles now run quickly.

Sokol1, Thanks for posting this as it is very timely. I was about to try doing my own 3D printed CAM follower type joystick mechanism in Fusion360. I think I'll first try this one and see how it works and if I can improve on it.

I think this is it: https://forums.eagle.ru/showthread.php?t=218874

Too be able to edit a mission without having to take down multiple instances of the dedicated server.

How to launch multuple instances of the dedicated server? Great Utility! I looking for information on how to use DUU to run multiple instances of the dedicated server. On the Dedicated Server Setting Screen it looks like there is a provision for setting only one alternate write directory. So how do you designate multiple write directories then launch each separate instance? I am not understanding something about launching the dedicated server. Seems like it would be great addition this screen to provide radio selection buttons for up to four servers, each showing their respective write directory and each with a launch button.

I didn’t receive the PM. However, I am #88 on the list and ready to place my order as soon as my unit is available. My HMD is an Odyssey Plus.

Nothing like being 3/4 of the way through a long tutorial (like the F14 cold start) and have an interruption occur. Would definitely +1 the need to make the last tutorial text reappear! Seems like sometime ago I came across a series of YouTube videos where some enterprising content developer took the time to record himself going through the tutorials and amplifying the steps. I found it useful to follow along, pause and even rewind some segments and then compare results on the tutorial giving me difficulty. Maybe someone will do that for the F14?

Okay, I misunderstood. I am using HomeFries's Target Profiles and tried looking for similar code to what you reference. He is using the TM virtual controller that combines the Stick, throttle and 2 MFD's into one controller. I need to do some more digging. Thanks.

Thanks Snake_iis. I have manually (in fact "early and often") gone through all the USB Hobs and HID listed in the Device Manager and disabled the power management feature. I have not tried the RegEdit, but will give that a try. I have been down this path before trying to solve an issue with Windows, and my computer resetting TRACKIR. I once saw a post on a ED forum about also changing a Group Policy regarding the USB power management. If set wrong, it will override all the manual USB settings, but I haven't been able to find that again and my Google search has found it either. Alamo

Svend, Thanks for the suggestion. Is your hub USB 2.0 or USB 3.0? I did the same with a new fairly expensive hub, but still have the same issue. Alamo

Thermal, How do you do this? Alamo

Panther, I have done this but still having problems. I just wished Windows wasn't so damn motherly! Alan

Thanks for the suggestion. I'll give it a try and report back. Which file exactly are you editing?

I am having an intermittent problem with TARGET virtual combined device. After the computer has been idling for awhile and I start up the T.A.R.G.E.T. GUI to create a virtual joystick that combines the throttle, stick and two MFD's into one device, Windows (or TARGET) doesn't disconnect the physical TM stick and throttle and MFD's. In the DCS controls setting pages both the Virtua Combo Device and the physical devices are present with the buttons and axes doubly mapped. This causes havoc with the TARGET profiles. Also the Windows->Control Panel-> Devices and Printers , show the TM virtual combined device and the physical devices, but without the yellow "caution signs" Window normallydisplays when the TM Virtual Combo device is running correctly. I can tell when things are going to go wrong by the time it takes the TARGET Profile to load. If it takes 2x or 3x as long as normal, then I will have the problem. Restarting TARGET does not solve the problem. However, if I launch a TARGET GUI immediately after a reboot, it starts always starts normally. I suspected Windows power management might be suspending power to the USB and HID devices and causing the problem. I went into the device manager and made sure the "Allow the computer to turn off this device to save power" option was UNCHECKED for all the USB Hubs and HID devices, but this seems to have no effect on the problem. A Google search fails to turn up anything about this problem. Has anyone else encountered this and if so have you found a solution?

Thanks for the suggestion. No, I’m not running TS3, but ...Discord is running. I changed power management setting to inhibit Win10 from suspending USB devices, so we’ll see if that has any effect.

Windows and TARGET fist fighting? TARGET PROFILE USERS: I am having an intermittent problem with Windows 10 (1809) and TARGET. Sometimes after the computer has been idling for awhile and I start up a TARGET profile, Windows doesn't disconnect the physical stick, throttle and MFD's1&2. DCS's controls setting show the Virtual TM Combo device and the aforementioned physical devices. Also the Windows Devices and Printers, so the TM physical devices, but without the yellow caution signs Window normally shows when the TM Virtual Combo device is running. It has the effect of making the axes extremely twitchy and button pressing problematic. I have CLEARED CATEGORIES for the TM physical devices, but the axes still jump around like they are double mapped. I can tell when this is going to happen by the time it takes the TARGET Profile to load and announce the "selected" aircraft. If it takes 2x or 3x as long as normally for the profile to start, then I have the problem. Switching profiles or restarting TARGET does not solve the problem. If I launch a TARGET profile immediately after a reboot, it starts normally. So I suspect it may have something to do with the USB power management. Someone mentioned something similar in a few posts earlier but in connection with the COM switch. Has anyone else encountered this and if so have you found a solution?

Broken links Could you possibly update the links to MissileTrainer Information, if the documentation is still available? Thanks.