gdx65

Hi. Thanks for the quick reply. I have now disabled HotPlug in Settings and I haven't had any issues so far. Tomorrow i will fly a bit more and let you know. By the way I do not use Trackir only TrackHat that is not an issue. I recommend TrackHat for those actively using a head tracking system. Again many thanks for the help. Hope this has solved the issue.

HI, II fly VR (Oculus 3), do not use TrackIR right now, I have also uninstalled the SW. But sometimes I use TrackHat which I have also unplugged it for troubleshooting purposes. While flying now and then (but rather often) I get "TrackIR disconnected" message, then "TrackIR connected". This will always deploy the landing gear of any airplane module. From the dcs.log i can see this event, below (and Attached the dcs.log file). Interesting if anyone has experienced this..... 2025-08-17 21:09:25.816 INFO APP (Main): Device plugged: [HID] HID-compliant device 2025-08-17 21:09:26.886 INFO INPUT (Main): created [TrackIR] 2025-08-17 21:09:27.773 INFO APP (Main): Device unplugged: [HID] HID-compliant device 2025-08-17 21:09:28.794 INFO APP (Main): Device plugged: [HID] HID-compliant device 2025-08-17 21:09:29.928 INFO INPUT (Main): created [TrackIR] 2025-08-17 21:09:32.874 INFO Dispatcher (Main): Stop 2025-08-17 21:09:33.903 INFO TERRAIN (Main): lSystem::CleanScenes() 2025-08-17 21:09:33.903 INFO WORLDGENERAL (Main): TerrainUtility:: updated in parallel: 29385, updated in the main thread: 0 2025-08-17 21:09:33.922 INFO VISUALIZER (4220): Stopped collection of statistic. 2025-08-17 21:01:40.000 ERROR_ONCE (): dcs.log

I have heard good thing about VD with Quest 3, need to try since I have learned it during my period with the Pico. I assume you use Quest 3 via WIFI?

I have not tried VD with the Quest 3 as I use a powered USB cable. Do not see the need so far...

Final update on the Pico Ultra... After one month testing it has been already sold to the next owner... To recap, the setup was easy, the Cons is that one needs to buy the Virtual Desktop from Pico store, cheap but still.... Nice quality, I was running all ta max resolution, the only Cons is the Pico lenses distort the image around their outer perimeter thus making the usable Field Of Vision much smaller. Unusable in warbirds where you need to clearly see controls to the left and right lower end of the cockpit (when you need to twist you body to the extreme to reach things). Still unable to read these tight areas of the cockpit. Otherwise nice visuals overall. I have not tested in jets where one has less body twist to reach and see things. Still A/B comparison with my Quest3, the Quest3 has larger FOV and it is lighter. The face interface it is much softer and comfortable, while the Pico Ultra is kind of hard face interface and hard on the top of the nose. To conclude, to date, the Quest 3 is still be best VR headset quality/price, but one need to master the Meta app and most of all the Oculus Diagnostic tool and best to register as Developer to open up other settings. Looking forward the next gen of Quest. I may give it a try to the Pimax even if the price it is hard to digest.

No still not fixed but solved in here. I posted the same question. You have to edit the LUA file Every time DCS update you have to re-edit the LUA file....

Auto-start/Stop Problem solved her

Very good module, now I have got control of the Corsair and systems. Landing on carrier ok. I which the aircraft carrier to have more activity as it is now it seems a ghost ship. Also the other war ships are of modern type vessels. It would be nice to have these ships matching the period.

For information only, a bit of an update after getting familiar with the Pico 4 Ultra and VD. These are my current setting in both DCS and VD where I am getting very good quality and 90fps steady. In VD under Streaming tab had to disable SSW. With SSW Always enabled or in Automatic I get smearing images on aircrafts a bit far away not clear. Best to keep it Disabled

See my reply to mrsylvestre above. Now all is ok…

Yes I am familiar the VR in DCS I already use a Quest 3 working very good. Anyway I got help from VD support on Discord "Set your Preferred OpenXR runtime to VDXR in the Streamer window" attaching a picture for reference for others if needed. Also the Audio Streaming needs to be on VR headset only and in DCS in Audio one needs to select Virtual Desktop no Pico headset otherwise there is no sound. Nice VR this PIco 4 Ultra. As VD works only with wifi I need to test a powered USB-CAT6 adapter directly connected to the router. Both Pico and VD they say they do not support this solution but it works according to several that use it. Same with Quest 3.

Hi, Just got a Pico 4 Ultra and cannot find the way to start DCS in VR. I have installed Virtual Desktop Streamer in both the Pico and the PC. All is working, when I connect the PIco to the PC via the virtual Desktop Streamer I get into the virtual room and see my PC monitor. DCS starts but in the PC monitor not in the headset?!? I can start Steam VR and play in IL2 as normal. I have a Quest 3 and no issues with that VR, I am quite experienced on with the Quest. Thanks

Ok I have now added you new script under --/N/ Engine *********************************************************************************** and it works, thanks (for info, see screenshot LUA screen 03) However I see at the bottom of the LUA file these scripts were there but under -- Autostart ****************************************** (See screenshot LUA screen02)) BTW I managed to download the pdf by using MS Edge, Chromes does not allow me (need check).

Hi, Ok I finally found the time to check this in the LUA file. (By the way the pdf guide in the link you shared cannot download ?!?) I have added the two scirt in teh F4U1D LUA file but cannot see any changes in the Controls section, Autostart and Autosop still disabled. Attached a screenshot of the LUA file now with the script. Maybe they should be placed not at the beginning? Thanks.

Hi, fantastic, thanks for the script, I will give a try.

Hi and thanks. I am familiar with editing the .lua file. Just did not think about that as I am not an expert into this type of details but can edit with confidence if guided.

Posted a question in here about not able to key bind the auto start and auto stop, then found this dedicated F4I-1D section…

In the Controls section for the F4U Corsair - it looks like it is not possible to assign Key / Button for Autostart/Autostop Procedure. For example by double clicking in the Throttle - HOTAS Warthog respective line.

Norwegian location as well here... I see the Pimax Crystal Suer 50PPD (early bird rewards included) is available but also a 57PPD version as well. I understood the 50PPD has better lenses solution?

I read similar solutions in other forms, if one uses WiFi best to have a dedicated WiFi access point. I only use the wired solution via USB, the cable does not bother me. Got a new USB powered cable and works great now. In the meantime I have upgraded my GPU to an RTX4090 found second hand and works great.

Hi, recently got the Spitfire module, any tip how to release bombs in the Spitfire? Testing the quick ready made missions, Hotas keybinding bomb release configured correct also using the keyboard the bombs are not releasing … maybe I am missing something interlock?

Same happened to me end of March. Meta Quest 3. Talking to meta support was useless as they always send you the same check list to do. Then last week doing trial and errors I solved the problem. In the Meta Debug tool I had the bitrate set to 500. When I set it to zero then everything is working fine. Has something changed in with some later upgrades? Now I run the ASUS drivers with default settings and meta Debug tool. Nothing else. I have the OpenXr disabled, I used it with my previous GPU RTX 4070 Dual OC For reference my PC has a Ryzen 7 7800X3D, 64GD RAM DDR6000 2 X 2TB SSD Crucial and Nvidia RTX4090FE

Old topic but still there. in VR Default seating position too high.

Same here, I am trying to find out why the default view is very high, as you describe one need to duck to see the full reflector. Meta Quest 3 here, all working fine with other aircrafts.

Little update. I now do not use Openxr toolkit at all, only DCS and Meta quest 3 all working smooth. I use the USB cable