Thunderchief2000

You need a space after the DCS.exe” before the —force_Vr cheers

Yes, it does seem to be working ok now. Cheers.

First tests for me in Vr are positive, I’m m running a HTC Vive pro at 250% in steam vr, and most graphics options on max. The vive pro locks its frames at 90, 45 or 30fps. I have my settings set so that I get a solid 45fps in most missions. My rig is a 12900k with a 4090. perviously my cpu frame timings would be on the limit of 45 fps and in busy moments regularly drop into the 30’s. With multi threading I’m am getting frame times equivalent to 90fps and in busy scenes drops to a solid 45fps. No drops below that as of yet. there seems to be a small gain in gpu frame times as well, such that there is a bit more headroom if I want to turn on more graphic settings. so for me this is a great improvement, I’m very pleased. thanks ED.

Yes this is what I do as well. hope its fixed in the next patch.

There is the "SHKVAL Centre" control which will centre the targeting circle on the nose of the aircraft, so you can point the nose at the target and press centre for quick acquisition.

The sense of speed in Vr is generally very good as VR always uses the correct FOV. Certainly in Assetto Corsa the improvement of speed perception in Vr is quite remarkable. I find DCS pretty good in speed perception as long as my frame rates stay at 45fps or above. Fly in the weeds and it soon gets a bit intense.

There are two AH-64’s to choose from when you first load the mission. One is labeled “checkpoint”. That is one that starts mid mission, like a quick start if you like. You should choose the other one if you want to do the full mission.

Quoting myself here, but I’ve just completed mission two and it includes the full coordinates in the kneeboard, so perhaps it’s just an omission in the first mission?

I have just started the Campaign, completed the first mission. enjoyed it very much. The only thing that caused me an issue is the target coordinates in the kneeboard are missing the first 3 characters. So if you try to get ahead and input them on the carrier during start up (like i did) then you get the wrong first 3 digits. it should be 40J i think but it gives you 39L or something. so when you enter the co-ords the wp and tg's are not shown due to them being wrong (out of range of the tsd map), but the apache accepts them anyway. you can figure it out by looking at the other co-ords but it would be better to have the full co-ords in the kneeboard i think. minor issue really, but had me stumped for a bit, doesn't take much to be fair. looking forward to the other missions.

Just tried this and it works for the first mission of the mad campaign. I noticed that I was wrong in my first post, in the mad campaign, when starting the right engine, the percent does not go above 45, so the starter never turns off. well this work around will keep me going for now anyway. cheers. I think it might have to do with weather conditions of the mission, do you have the mad campaign? If so try the first mission.

Thanks I will give it a try

Hi, is anyone else having a problem with starting the right engine? since the mini patch (although it is a bit random so it might have been the patch before) both in my own missions and in the new Mad campaign. The right engine does not start. However some times it does. my method, battery on apu on check throttles to cut off (I use a warthog throttle for the left and right engines) Press the start on the left engine, engage idle at 20percent. Engine starts fine press the start on the right engine, engage idle at 20percent, engine rises to 50percent and the starter clicks off as normal, but then the engine just starts to die. Never getting above 55percent. however some times it works fine, at least in my own missions. let me know if I’m doing some thing wrong. cheers.

I was hoping that this line in the current beta patch notes would be a fix for the monocle being the wrong size/location in vr on HTC Vive Pro (and others). Fixed: IHADSS image scale incorrect But it does not seem to have effected the monocle overlay on the Vive pro but it still looks like the attached image.

Which Aircraft are you setting your controls for? make sure you are setting the correct profile for the aircraft, most have one called "Game Mode" and one called "sim" make sure you are setting the controls for the SIM mode. (This is assuming you are not trying to run DCS in "GAME Mode", which is more arcade based mode for the game, but it is not well supported so you should not use it in my opinion.)

This is exactly what I see when using my VIVE pro as well. Thanks for the screen shots i think they illustrate the problem perfectly.

Yes this is pretty much what I get as well, great vid.

I have been flying the Apache at night a lot lately and the stuttering with the PNVS is still there. just to reiterate what others have stated in this thread. It is not FPS related, if you do not move your head and instead turn the helicopter, there are no stutters. It is only when turning my head do I see the stuttering, and it is just like the tracking is jumping to position. The video from the PNVS still seems smooth although it is hard to tell and the rest of the simulation is at full speed. (45 fps in my case, HTC Vive Pro) The effect does not seem to change, it is the same from the start of the mission to the end. turning the PNVS on and off make no difference for me. Changing the displays setting to "every frame" made no difference for me.

Thanks yes I seem to remember it being mentioned in another thread but I couldn't find a specific thread for the Vive ihadss scaling/positioning issue.

HI, I'm not sure if this has been reported already but the scale of the eyepiece is wrong when viewed in vr on an HTC Vive pro, I don't know if it affects other HMDs Replicate, by starting any AH-64 and turning on the ihadss and the flir here are a couple of images to demonstrate: The first is how it looks currently in game, as you can see the image extends beyond the edges of the glass reflector, which would be impossible. The second is a quick Photoshop of about how it should be. I think the eyepiece is modelled too far away from the virtual eye, as a result it is not really usable in VR, it would be really nice to have this working please. Thanks Simon

Yeah it looks that way. It's not the end of the world, but it would be nice to be able to use the monocle overlay.

I have a Vive Pro and I am not seeing a problem with the size of the display, it seems perfect to my eye. I have it set to right eye only. I do find that the monocle surround is too zoomed out, the IHADSS display doses not fit in the confines of the glass reflector, so I have that turned off.

And another update, changing the apache in the mission editor to another helicopter and then back to the apache has fixed the issue. strange one. cheers.

Just a quick update on this, after posting I reailised in had not tested a hot start or a cold start in a fresh mission. When I do this it works fine with no left stick required. The mission that I am having a problem with is one generated by the RotorOps mission generator. It used to work fine before the patch. I will try adding a new Apache to see what happens. Cheers.

Since the last beta update i have had to put a lot of left stick to get the apache to fly straight. The amount does not seem to change significantly with speed and is constant from the beginning of a cold start flight. I have attached a pic showing the controls indicator with a the ah64 in level (ish) flight. Is this a known bug with the new beta?

I had this last night too, it turns out that the radar altimeter is turned off by default on a cold start now. you have to go to the flt page on the mpd and turn it on. I cant remember the exact button but it is in the bottom right of the flt page. hope that helps. Cheers.