zafgev

Thanks Adrian

Running 2.9, DLSS Balanced, Reverb G2, RTX4090 - when you fly close to any aircraft, player or AI, the aircraft judders, like it's vibrating in place. This also happens in any camera view. Any ideas what could be causing this.

After a flight when I do a complete shutdown the avionics/lights etc are still powered. Is this a bug?

I was so hoping Syria Map would not fall for the stupid rough runways. Please dial down the unrealistic rough runways. Especially for fighters getting thrown around like that especially at speed is not realistic in sim and in real life. Please stop this madness.

Please, please, please can ED please smooth out the uneven runways, especially in VR. When taking off runways often become so uneven, bouncing the aircraft around which is totally unrealistic - unless these runways are riddled with potholes - which would have then closed in real life. Or at least if anyone has a fix to dial down the unrealistic excessive bouncing please advise how to do so.... I beg you !! :cry::cry::cry:

When I select for example A/G and SMS on the left MFCD and then click on say the LOAD option, I am unable to navigate back to the primary A?G SMS page. How do I navigate back from sub-menus to the primary SMS page please?

Please can ED put some money aside to have the runways resurfaced? All jokes aside. ED can you provide a slider or a system setting where users can choose to have the runways surfaces smooth or rough. At present the new runway surface are way to rough and unrealistic except for, off course, if it's a dirt strip, and even then I've landed om some real smooth dirt strips in my day. But for most surfaces, cement, bitumen or like its like the runways are pothole covered and more annoying than fun.

1) Calibrate your room using WMR. Depending on the direction your headset is set to when you start-up the SteamVR plugin, that is what will set the "forward" or direction view for SteamVR - on my setup, this is usually never right in front of me or pointing exactly at my monitor. In cockpit set up a button to recenter your VR view (in DCS there is an option under "general controls". Pressing this should recenter the cockpit in the direction of whichever way you are looking with your headset on. If its slightly to far back, forward etc you can fine-tune that using Right ALT + numeric keypad keys and +*- to move the head position as you need it. To lock that position press Right ALT + numeric keypad 0. 2) Cant help you with framerate - many posts online for tuning that. 3) The Reverb screendoor is 100 times better than older headsets so most comments of seeing "nothing" come from people who used to see chicken wire on older units. Yeah it still there but hardly noticeable compared to the Vive or DK1/2. 4) You will most likely get motion sickness at first - fly a lot and you will get used to it - happens to the best of us 5) Yeah Reverb has a very very small sweet spot where things are clear and get blurry quickly outside of that sweet spot

I get this when I have any MSAA enabled - turning it off clears it for me.

I turn off Chimney Smoke completely. It kills framerates for me when its on.

+1

+1

After the update I get a "KA-Blackshark not authorized to be used with this account". Please provide a valid serial number. After entering the serial number DCS starts but the Black Shark is disabled. I get this every time I start DCS now. This has been working for years now until the most recent update. Any ideas?

I've not been able to record a video. However, I have managed to isolate what is causing the problem. Previously during startup I would turn on power, then select the "combat" button on the AAP (note here that HMD, RDR, SLNK, OESP, RWR, COM1, COM2, NAV, IFF, INS, WMMC1, WWMC2and SAIU is enabled). I would not touch the AAP options again. I would then enter the lat/long coordinates in FAST mode, then align. I would continue after alignment by loading the data cartridge. After data loading I would configure the aircraft for AA/AG based on weight and balance. This configuration would cause the navigation to waypoints to fail. What seems to work is to power up the aircraft. Then select COM1. COM2, WMMC1, WMMC2. Capture the lat/long coordinates in the UFCP - then FAST Align. Once aligned select INS NAV. I then select NAV on the AAP. Load the data cartridge and configure AA/AG. While the INS is aligning I'm configuring radios, etc. This startup appears to configure the navigation system correctly for flight. So the primary difference in the startup appears to be the sequence selection of NAV on the AAP. So not sure if its a bug or a feature of the plane.

Will capture a video tonight.

+1

Any update on this. It's getting to a point now on our MP servers that we are considering removing the YAK52 due to the fact that it is now severely impacting framerates for participants. With the rest of DCS and other modules becoming more complex and taxing systems the YAK with no LOD model is not helping any optimizations. Please update asap so we can take the best action in the interest of keeping the YAK else its days are numbered.

Creating waypoints on F10 map or entering individual LAT/LONG coordinates on MP map (Caucasus) and then flying towards those waypoints does not steer you to the physical ground (or elevated) locations. Once airborne the HUD I believe should indicate the course direction to the waypoint and a "small square" mapped to the area where the waypoint is placed. As you progress towards the waypoint the "small square" starts to move away from the intended waypoint and upon reaching the waypoint it is nowhere near where it was mapped on the F10 map or the intended lat/ling location. It is completely impossible at the moment to fly a sortie using waypoints and ending up where intended. Steering towards anyone of the predefined airports with the current build and selecting either FAF of ILS freezes the MFD in map mode with neither the DME or direction-changing irrespective of attitude, speed or direction. I've tested this on numerous occasions on the Aerobatics Online server in Caucasus map, using different startup configurations, INS alignment and data cartridge load sequences but every time the results are the same. The navigation system is not tracking lat/long coordinates correctly.

I can confirm that in MP on the Caucasus map the same happens. FAF if offset and RWY direction is offset by about 30 degrees. INS alignment is set to the kneepad but when flying around the airport the lat/long bug in the HUD moves around and is not stationary on the lat/long coordinate entered. I created a SP mission and it was working OK but not in MP.

Thanks. Will check it out.

Is there a way to stop the WMR interface to stop defaulting to the "press WIN+Y" when putting on the headset. What happens is that once WMR switches to this mode I lose keyboard focus in DCS. SO the only fix is I have to swivel my headset up, alt_tab to the WMR UI, press WIN+Y to close that option and then tab back to DCS. Very Annoying. Any advice?

For a while now, any of the planes and helicopters I fly, landing light reflections will not show up on the ground or runways. It is basically like they are not turned on at all. They do shine though looking at the aircraft from outside however they do not reflect on the surface. I've changed settings, rebuilt DCS etc. Nothing so far has fixed the issue. Any ideas please?

There is an option to select your preferred choice in Audio setting page in DCS. Set to PTT

Make sure "motion smoothing" is turned off in SteamVR - I think that is what you are experiencing.

Hi Jamie - no I've never tried one. I wish I had so I could compare it with the Vive and the Rift S.