Joch1955

bin-mt dcs.exe There is actually no longer any need to use target lines, edit parameters or use any outside files, just link your shortcut to the bin-mt dcs.exe and the game will automatically start in Open XR and VR if your G2 is connected. No need to do anything else.

Are you using ICLS? essential to make sure you are lined up right. If you follow the ICLS cross and are on AOA, you are 90% there.

Not sure why you keep claiming that after I provided you with the pertinent link to the website, but maybe we can get @mbucchia to comment on whether there is any benefit to try to use QuadView if you have a headset that does not support eye tracking like the plainjane Reverb G2.

well no, there seems to be a lot of confusion on that part. QuadView only works with HMDs that have eye tracking. If you force it on a HMD like the regular G2, you just get the same FFR already available in the OpenXR tool kit: Home · mbucchia/Quad-Views-Foveated Wiki · GitHub

yes, I have a G2, Quadview does not work on the regular G2 because it does not have eye tracking, but you can try turning on Fixed Foveated Rendering through Open XR toolkit, it may give you some extra FPS without noticeably affecting image quality. 60 vs 90 HZ does not really affect the image, the G2 is designed for 90 HZ and that is what you should leave it at. If you do not have the horsepower to consistently run at 90 fps, you can try Motion Reprojection. In DCS, it's side effects are pretty much unnoticeable. I run with MR on, FPS is locked at 45 fps which allows me to bump up a lot of the in game graphic settings. The only real way to increase image clarity to increase Pixel Density and/or the the native resolution, although obviously you need the HP. I have 3070ti so leave it at PD = 1.0 and the native resolution. I can read all the cockpit instruments clearly which is what I care about. You can also try turning off all FSAA, which will make the cockpit instruments clearer. You will get jaggies outside the cockpit, although that is only really noticeable close to the ground. DLAA is also good, smooths out the jaggies with only a small hit on FPS.

I did some launches this A.M. from the Supercarrier with no issues. I have the AB detent OFF in options since I have a physical detent on my joystick. MIL power + salute = take off in MIL AB + salute = take off in AB I presume the trick is that the salute has to be the last step before launch after you set MIL or AB, but that is the way I have always done it. I setup COMMS beforehand so it only requires pressing the F6 key. Set power, salute and I'm off.

yes, looks neat! your pilot will salute, grab the bar and launch!

well I guess it is the nature of forums that players only post when they have an issue so you get a warped view of the quality of these products. I have had a Orion 2 for close to a year with zero issues and am very happy with my purchase. I got it 1 week after ordering. Price was reasonable, less than a TM Warthog even after shipping, foreign exchange and duties. It was easy to put together and setup in DCS. Build quality, feel of the handles and switches is top notch. It works perfectly with no issues in DCS. I have no problem recommending it.

well, if you need six missiles to shoot down one aircraft, then maybe you are the one who is doing something wrong.

good for you! Well I "harder disagree" then. 1. There is more to a module than just what long range missile it carries or how well it does in MP. What is important is the entire flying experience from takeoff to landing. On that front, the Mirage 2000c is a very sweet airplane. Easy to fly, easy to navigate, easy to maneuver, easy to multitask with its wonderful autopilot, easy to carry out air-to-air or air-to-ground missions, easy to land, just a wonderful plane all around. 2. The Mirage 2000c is more than capable to carry out its intended missions in game during its historical time frame in realistic missions and against opponents it would have realistically gone up against in RL. In SP missions and campaigns, it is more than capable to handle any potential RED air or ground SAM opponent. 3. Yes, the Mirage will be at a disadvantage going up in a Quake dogfight server against AIM-120 equipped F15/16/18s, but those are totally artificial matchups which have very little to do with RL modern air warfare. And honestly, if the only thing a player cares about is how many virtual ACs they can knock down in one session, they will always be better off choosing a F15/16/18 and clubbing baby seals all day with their AMRAAMS... so no, my personal opinion still stands, a Mirage 2000-5 would be nice to have, but would not bring much in terms of actual gameplay.

Open XR w. G2, works great here. I always had issues w. SteamVR or OpenVR, so have no plan to go back to them.

M2000c is great, also my favourite module. Once you learn it, it is very easy to fly and fight in. While newer versions would be great, they would not bring much in terms of actual gameplay.

Hi, nothing special about my settings, you just have to adjust graphic settings and resolution to produce the FPS you want. The end goal is to find the sweet spot between visual quality and performance that you are comfortable with. I used this article as a base and set the in game graphic and VR settings as recommended: vr optimization guide You can then tweak settings and see what the results are on your FPS, I pretty much left it as in the article except I bumped up in cockpit resolution to max since I want the instruments to be as clear as possible. OpenXR Toolkit: only used to set eye resolution and motion reprojection, all other settings are at default. The Eye Res is the big FPS hog since there are only so many pixels your CPU/GPU can push through. My setting (2750x2750 per eye) is roughly equal to 85% res in SteamVR. I know other players also use a lower res which they bump up with upscaling, but I was not happy with the result, either visually or in terms of FPS, I would rather just set exactly the Res I want. I can also bump up the FPS to an average 80-90 in the Air if I lower the eye resolution to 2150x2150 (roughly 68% res in SteamVR), but of course visual quality suffers a bit. WMR G2/openXR for WMR settings: all at default. I have tried to tweak these settings, but did not like the results, best to use the recommended settings and/or let Windows decide.

Well I guess I am the outlier here, my system (HP G2, 5800x3d, ASUS CrosshairVIII Hero mother board, 3070ti GPU, Win 11) and my settings (RES: around 2800x2800 per eye, medium/hi graphics, no MSAA, reprojection ON) work perfectly in DCS native OpenXR. I set Resolution and reprojection via the OpenXR Toolkit. No upscaling or other changes through the OpenXR toolkit. My FPS is locked at 45 all the time in MT whether in the Air or on a crowded airbase or the Supercarrier. More importantly for me, the image is smooth with no stuttering at all, not even when I move my head quickly from side to side.

HT on or off is game specific as to whether it has an impact. In my case (5800x3d, ASUS Crosshair VIII mother board, 5700ti GPU, Win 11), HT on or off has zero impact on performance in DCS MT, so I leave it on. Switching HT on or off only takes a few seconds in BIOS so anyone can quickly check on their own.

I have the same "issue". Firmware update for the F16 stick/base has been showing "retrieving" for about 2 weeks, but when I check on the site, I have the latest version of software/firmware. A bit annoying, but the stick/throttle work fine in the App and DCS, so I don't bother with it. As I learned a long time ago with computer hardware/software, "If it ain't broke, don't fix it".

it says that, but when I try MR in game with OpenXR Tools for WMR alone, it does not work. MR for me only works with OpenXR Tool Kit which makes the MR setting in the other App redundant.

I have a Reverb G2. I use DCS OpenXR plus forcing motion reproduction in OpenXR ToolKit and it works fine here in both MT and ST. No need to use OpenComposite anymore, DCS native OpenXr works as well (or better IMHO). Note that Motion Reproduction via the OpenXR Tools for WMR App does not work, DCS ignores the setting.

yes that was it, HOME FUEL shows up on the left DDI. Thanks.

that was reported in the M2000c forum. Check here, the Devs released an interim hot fix for now: Personally only using the ST version with the M2000c for now. The MT version also screws up the HUD colors.

Looked into it again and I think I figured it out, most likely candidate seems to be a low fuel warning triggered by the FPAS. As I understand it, the FPAS will trigger the Master Caution light when it calculates you will only have 2000 lbs of fuel until you reach your Home location as designated in FPAS. In the scenario I am playing, "Airfield VFR landing" on the Nevada map, you start with around 2200 lbs and land on the runway with almost exactly 2000 lbs remaining. In other scenarios where you start with more fuel, I don't have that issue. Thanks for the help.

Picked up the module recently and having been slowly learning it. I have been practicing airfield landings to better understand how the "Trim" works. When on final approach to land (gear down, flaps down, speed around 130 kts, on 8 degree AOA, trim to be more or less hands off), the master caution lights keeps going on, but with no associated warning. I checked the manuals, but can't figure out what it is. I am thinking it may be related to the Trim or slow speed?

Seeing an improvement here in OpenXR/VR with my system (HP G2, 5800x3d, 3070ti, Win 11) and my settings (RES: 2800x2800 per eye, medium/hi graphics, no MSAA, reprojection ON). My FPS is locked at 45 in the Air using the in game FPS counter because of reprojection, but was usually around 30 on the ground in a crowded airfield or on the carrier deck. The low end has now bumped up to 45 all the time. FPS counter says I am always "CPU bound (main thread)" which is an indication that I should retweak my settings since I seem to have some headroom. Obviously no reason why a 5800x3D should be a bottleneck. Very pleased with the new DCS HT so far, seeing an immediate improvement and since this is the first draft, there is obviously room for improvement in the future.

so, tried the plane last night to see the new changes, saw that TACAN was not working, popped in here to see if the issue had been reported and was happy to see there is already an interim hot fix! That is service. other issues: saw that the last beta finally brought in clickable radio menus for the M2000? (unless I was doing something wrong), but the hot fix promptly killed them. Hope they can be brought back. Also see that no one mentioned that the HUD now displays two shades of green which looks rather cool. Is that an intended change? I did not see anything about this in the change log.

From what I understand, the 530 will also continue to fly on its assigned path until it self-destructs even after the launching AC loses lock. If the missile happens to fly close to a target, it will trigger the proximity fuze. Looking at the track, this may also be what happened. I have been doing a lot of AA combat with the M2000 lately and have still not seen one instance of the 530 hitting a target after I lose lock, so it would seem to be a pretty rare occurence.