dock999

Someone had already pointed it out. Now I realize the dropping tank is more about Mach Number rather than Speed Number.

Thanks for the excellent input.

I noticed that the 800 L tank could be jettisoned at about 500 km/h but the 1100 L tank could be done only at about 430 km/h, which was a bit annoying in the PVP match.

Right, so this is a known limitation.

I have been experiencing the difficulty of jettisoning JF-17's external fuel tanks for quite a while. There seems to be a speed limit for dropping tanks. You can not jettison the external fuel tanks until the speed is below around 450 km/h and I wonder if anyone has had a similar issue? , The limitation can cause a great deal of difficulty in performing a defensive maneuver after firing a missile.

I do not have Oculus. I was using Pico 4 via VD. For some reason Pico 4 runs Oculus running time

Have you EVER TESTed by urself?? U So-called "ED Beta tester" I can prove to you : ( BTW PICO4 is one of my headset) 1) DCS MT can be run by OpenVR with no command line rather than OPenXR .2) The Launch Must be completed through WD panel 3) it can bypass SteamVR I just did a test for you "" beta tester??" and the followings are just some lines from the log file . I also have attached the entire log file to the message A: 023-10-08 12:26:21.630 INFO APP (2768): Command line: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" 2023-10-08 12:26:21.630 INFO APP (2768): DCS/2.8.8.43704 (x86_64; MT; Windows NT 10.0.19045) 2023-10-08 12:26:21.630 INFO APP (2768): Application revision: 223704 2023-10-08 12:26:21.630 INFO APP (2768): Renderer revision: 24140 B: 023-10-08 12:27:29.345 ERROR VISUALIZER (2768): OpenXR exception: XrResult failure [XR_ERROR_FORM_FACTOR_UNAVAILABLE] Origin: xr Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:447 2023-10-08 12:27:29.534 INFO VISUALIZER (2768): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S 2023-10-08 12:27:29.535 INFO VISUALIZER (2768): render thread initialization... C; Look at the screenshot: this is the hallmark of MT: CPU limited warning sentence . However The DCS MT was running under OpenVR dcs.log

Yes u can!. You can launch MT via VD panel . When MT is launched by this way, MT runs OpenVR rather than OpenXR and U can even bypass SteamVR.

The issue has been well-known over the past several days and the basic reason is the server of the Opencomposite is down. You can go to the discord channel of Opencomposite where there are tons of discussions and proper instructions to solve the problem.

When I disabled the XR necksafer layer +- the toolkit, I did notice the DCS MT crashing decreased. However, the DCS MT which was run under OpenXR was unplayable since there were just too many stutters in my case. For your 2nd question, I can confirm to you that DCS MT or ST will be run under open VR rather than Open XR if you launch them through the VD panel, that is because the DCS log files indicate this clearly. By this method, You can bypass Steam VR and launch DCS in VR directly Several days ago I had a bit chat with J2-Nobiwan in the message and asked him whether he could write a program similar to the XR necksafer in an OpenVR version. He said that VRNS was the OpenVR version . I tested it and found it was pretty much workable but the VRNS has to be run with SteamVR. My conclusion is that Pico4 does not go well with Open XR in DCS and Pico4 is better to go with OpenVR Pico4 + VRNS is quite workable under OpenVR in DCS.

In My case even if I disable the XR-necksafer DCS MT still crashes. I did some tests and noticed the only way to run DCS MT+PICO4 in my case was the DCS MT had to be run in a NON-openXR environment. The method was to add the command line and launch DCS MT through the VD streamer panel. then you would find the DCS MT actually ran under Open VR rather than Open XR although the command line indicated "-- force open XR". But certainly, you will benefit from the toolkit and the necksafer. Another interesting finding is that by this method, you actually can bypass STEAM VR , so your PICO4 headset enters a VR environment without SteamVR and it runs under open VR.

No, not in my case. Pico 4 + VD can launch DCS MT in VR indeed . But when you try to load missions , DCS crashes. I still can not figure out what the reason is. No issue with DCS ST. However, ST in Steam will not let you use the toolkit and necksafer.

The main problem is DCS crash. The crash only happened during the Open beta MT went through SteamVR with or without necksafer. This is the reason that I always prefer to go through the Non-SteamVR pathway. However, the Pico 4 would not allow to use OpenXR.

I have 3 headsets which are HP G2, Pico 4, and Crystal and I used them to run DCS VR and MSFS VR . I would like to use OpenXR Toolkit and Necksafer when I run DCS VR and MSFS VR. I am aware that OpenComposite is not required to run DCS VR and MDFS VR. However, the switcher let me choose to go Non Steam pathway to launch VR, and the OPXRTK and Necksafer have no issue in this pathway . So I have no problem of using these 2 programs in G2 and Crystal when the switcher is set to OpenComposite. While the switcher is set to SteamVR , OpXRTK and Necksafer become nonfunctional in all 3 headsets . This is the reason why I would like to avoid going through SteamVR. However, Pico 4 is such a unique headset and very pleasant to wear but Pico 4 is a SteamVR(?only)- headset . When I saw someone who could run OPXRTK +- necksafer in the SteamVR environment, I became really curious.

I notice DCS OpenBeta MT really does not go well with SteamVR which is through OpenXR/steamVR. However, DCS OpenBeta ST and DCS stable version can run SteamVR reasonably well. But if you look at the DCS log, both of them actually through OpenVR which are Oculus Quest 2 and OculusRift respectively (in my Pico 4 case ) . This is why the toolkit +- necksafer are non-functional. This is the reason that I wonder why some of you guys can use the toolkit in SteamVR.

Have just tried the suggestions but the results are not ideal. Current Beta MT: can see the toolkit works but DCS crashes. Current Beta ST: toolkit nonfunctional. DCS runs normally Current stable ST: toolkit nonfunctional. Dcs runs normally. The default Running-time is set to Steam VR/openxr by the OpenComposite switcher . It looks like Picco 4 serves people differently.

Great in detail, many thanks . It sounds the VR process will need OpenXR running time to get it to work.

Have been following up on this interesting topic for a while and just try to clarify 2 questions. 1) How do you run the OXRTK ( +-necksafer ) in DCS VR with Pico 4? I have failed both Steam VR and VD tray ( Option of Launch game ) methods, I noticed that was because the running times of both methods were not OpenXR. I have OpenComposite as well. 2) what is QVFR? Many thanks in advance.

PL 12 is not a mod and PL -12 has been constantly assessed and updated over the past several patches of DCS . No sure why some severe still think PL 12 break the integrity.

Great . but once you did this, you will not pass the check of " pure client" . For example, you can not login into Growlling Sidewinder's severe if you did this even if you have installed the newest patch.

Anyone knows how to get PL 12 for JF17, can not see the option of PL12 but SD 10.

I bought the Normandy 2 indeed. My module management indicates the installed version is Normandy 2 rather than Normandy . I am on Open Beta as well and I runs DCS on standalone version . If no one else has had similar issue .that will be my system problem.

I have found Paris is a bit blurred in VR, namely, the structures are there but the images are blurred for some reason . Am I the only one who experienced this? The parts of the new map overlapping the original Normandy map seem to be sharper in comparison with the parts of the map in Paris. Have not tried London yet.