TWC_Alamo

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.

HomeFries's TM Target Profiles for the Warthog and Cougar accomplish all items quoted below and more. They work great in VR and I never have to take my hands off the HOTAS while flying. They are available for almost all DCS aircraft---even the A4E Community Mod. Each joystick button can have several different functions. https://forums.eagle.ru/showthread.php?t=116454

Mifur, Didn't you mean that your video card has only one HDMI port? The picture shows your video card has 3 X display ports, 1 X HDMI (which appears to be to your existing monitor) and 1 X DVI connection. I bought several of these DisplayPort to HDMI cables. https://www.amazon.com/gp/product/B01HXOU4Y2/ref=oh_aui_detailpage_o05_s00?ie=UTF8&psc=1 I have used them for connecting the Odyssey+, Vive and multiple monitors and 55" TVs to several computers. These work well at 4K, whereas others I've tried haven't. They are available in various lengths and cost about the same as the the adapter previous mentioned, but avoids you also having to buy another HDMI to HDMI cable to connect the adapter to the device. If your monitor has a DVI port, you could also use a DVI to DVI cable to connect it to your video cards DVI output.

I would not mind having that in my real airplane, but except possibly for the display unit, the sensor suite and ADS-B receiver would have no use in a sim. Even with the display unit, you would still have to interface it somehow with data from the sim. It is physically so much smaller than any of the huds in DCS, I don't think it would be worth it.

I had this problem yesterday with the Odyssey Plus. I had been experimenting with SS in IL-2 and fpsVR. I launched the latest DCS OpenBeta and encountered this "white box of death." I thought it might be related to the OpenBeta update, so tried the release version and encountered the same thing. I then reset Super sampling back to 1, rebooted and it was fine. I was able to reset SS back to 2 and all appears normal. Based on the Vive thread, apparently the problem is not confined to just the O+ . However, I didn't try this with my Vive, but will the next time it happens.

HoneyBadger, I am in complete agreement with Hansangb assessment. I have yet to try the O+ in room scale as almost all my VR is in flight simulators.

I guess that depends on a lot of factors. I've been a pretty die hard Vive user since launch and bought the Odyssey + on kind of a whim, thinking it would be cool to have another VR setup available when friends come over so, we could fly together. Received the O+ on December 1st and haven't put on the Vive since. With the clarity tweak mentioned elsewhere on this forum, the gauges and MFDs in the cockpit are clearly readable and there is no screen door effect. Head tracking may not be as precise as the Vive and the fit might not be as comfortable, but it is good enough for the much better view. I'll keep the Vive for my guests, but the O+ is now my primary HMD. But as they say, your mileage may vary.

I am a proponent of "look and click" as it seems the most natural in the cockpit. I don't like reaching for the mouse, so I have the "USE MOUSE" box unchecked in the VR setting. I use HomeFries's free Target profiles for TM HOTAS, which allows multiple functions for each of the HOTAS buttons. https://forums.eagle.ru/showthread.php?t=116454&highlight=target+profiles His VR profiles maps the trim hat to the mouse buttons and wheel as shifted function (or not). The only downside is the small cursor that tracks your vision. But the most annoying problem I have in VR if I do happen move the mouse, is loosing focus out of DCS, which results in the controls freezing. I run multiple monitors and even with the CONFINE MOUSE box checked, I still end up with my system focus.

I am a new plus user who has transitioned from the Vive. I have retired my Vive to my backup system. I can't see flying any sims in the Vive after using the plus.

Sign me up too.

Thanks Don!

A solution To help others having this same problem, I will share what worked for me. I found and followed this thread on REDIT: I downloaded and manually installed WMR for Win10 1803 from here: https://docs.microsoft.com/en-us/windows/application-management/manage-windows-mixed-reality#enable When I tried running WMR, I received an error message that I needed to run Windows Update before it could proceed. This was something new, but maybe progress! Windows Update tried installing KB4467682 2018-11 cumulative update, but failed with error 0x80070002. A web search found this page: https://allthings.how/windows-10-version-1803-update-failed-to-install/ common error I had to force Windows to UNINSTALL the failed update and then did a manual install as described in the above link. After rebooting and updating, WMR runs and I played around in the WMR tutorials. Success! :):):) Only about 5 hours wasted in fighting with Windows.:mad::mad::mad: Next step is getting steam VR for WMR installed.:book:

I did but the Windows Update Troubleshooter didn’t find any problems. I also tried the sfc /scan now. It reported repairing some corrupted files, but WMR still will not download. Many of the “fixes” from my Google search seemed to apply to earlier versions of Windows 10. I’m currently on 1803. Not sure what to try next. I hate to have to reinstall Windows.

Just received my $299 Samsung Odyssey Plus from the Microsoft store and have run into problems installing Windows Mixed Reality. The computer passes the compatibility checks, finds the head set and pairs the hand controllers and proceeds into setting up the play space area. But then I get a message "We couldn't download the Windows Mixed Reality Software." When I hit "retry", the download runs to 100% and the error reappears. I have tried many of the "solutions" suggested from a web search of this error without luck. It appears to be a Windows Update issue, but all my window updates are up to date. Anyone else run into this error and find a solution?

What is WT?

HomeFries, I hope you had a great Thanksgiving Holiday. Any chance that you could put together a quick profile for the A4E? I am so used to the keys in your Target Profiles it is very odd flying the A4E with the buttons not in the "right" places. Thanks, Alan

Has any one tried using this card to connect the Vive to the GTX 2080?

How to activate Alternate LSO Views? Jar, Thanks for keeping this updated. The mission has really helped my carrier landings go from constant disasters to occasional disaster. I am trying to understand how to activate the various LSO viewing positions. Comments in the first post indicate there are alternate LSO view folders that you install: "View is set to VR PLAT CAM view by default but you can change this by editing the John C Stennis lua or installing the various COREMODS folders contained in the "Alternate LSO Views' folder." I've been through PLATCAM 1.7.ZIP file and can't seem to locate the alternate LSO view folders. Can you give a little more detail on where they are and how to activate them? Thanks

Take a look at these---they are "<free>" https://www.thingiverse.com/thing:2603527 https://www.thingiverse.com/thing:939047

Thought that was the case, but the FAQ's are a little confusing on the topic and I hate loosing activations. Thanks

I am doing a major hardware upgrade and need to deactivate my modules. I understand how to deactivate the old STARFORCE PROTECTED modules using the DRM button in the module manager, but how do we deactivate the newer modules like YAK52, FA-18C, AV8B, Persian Gulf and Normandy Terrains? There is no DRM button or UNPROTECT.EXE in the MOD directory. Does the new system track activations and deactivations like the old copy protection system?

Thanks Panther. That helped, but the images are still blurry, but more readable. I tried reducing the settings further (i.e. 0.3 and 0.1), but noticed that began effecting the DDIs and AMPCD on the main screen.

Hey Maestro72x, Based on your recommendation, I thought I would give simvc a try before diving into Helios and Capt Zeen. It appeared to be simple to setup, but I must have done something wrong. The display setup screen looked great with nice crisp images, but when I run DCS, the exported displays are blurred and unreadable. To show you the problem, attached are pictures: (1) of my configuration, (2) the simvc display setup screen, (3) the resulting DCS FA-18C with simvc , (4) closeup of blurry left DDI, (5) closeup of blurry right DDI, and (6) closeup of blurry AMPCD. It appears like the export is writing the image two or three times but shifting a pixel each time. I have repeated the setup several times without affecting the problem. Do you have any idea of whats wrong and how to fix it? Monitor 1 is a 55" 4k TV for main cockpit, Monitor 2 is a 27" 1920X1080 auxiliary display and Monitor 3 is another 27" 1920X1080 display for the instrument panel. I