riojax

@uboatsabout the @Riojanoissue, must it be reported to deka or ED?

Still present on OB 2.8.4.39313

Latest OB 2.8.4.39313 is still ignoring the callsign in reply (only says "one")

Still present on OB 2.8.4.39313

Still present on OB 2.8.4.38947 null f1.trk

Still present on OB 2.8.4.38947

In OB 2.8.4.38947 the reply is muted

The EWR callsign is "Eyeball" in the F10 radio menu all is ok, but later it calls as "Darkstar" ewr2.trk

They wouldn't overlap and also not call out the same contact, at now is impossible to do detection meshes. ewr.trk

Ok, it seems reasonable then. Thank you a lot!

Yes, I think the same, but in the track the throttle is very low... anyway I replayed it and tested (using the ESC menu -> Take control) to put the engine in idle and then it recovered, but took around 40 seconds in idle, good speed, low AoA, etc. I don't know too much the 9K-50 internals but I think that is too much time to recover the compression and combustion chamber pressure levels in this situation, also I think that is good to check the minimum throttle/fuel flow to recover the combustion chamber pressure in this engine. What do you think in your knowledge and experience?

After a spin recovery, with clean air, good speed and AoA the cockpit still vibrate. flat1.trk

The radar target reticle must to be confined to the HUD area, if a contact is out of this zone, the target reticle must to stay in the border. For example, in this image, the red marked plane is locked, and the missing target reticle should to be near the blue circle, that is the HUD limit.

+1 It will add a very interesting value to this module

Ok, but... where is this command? nullnull

I have a Pimax 5k+ and with the last patch happened the same until I opened the opencomposite tool and selected SteamVR as compositor, run DCS, and later change it to OpenXR again, but I did lose 15fps and the reprojection. Now with this patch I recovered the reprojection but I did lose another 15fps, /s great job... Yeah, I'm in the same boat. I miss too much the DCS 1.5.x times, from 2.0 all was to worse.

Ok, fixed following this guide: https://forum.dcs.world/topic/318004-dcs-now-supports-openxr-natively/

In F1CE and F1EE the mouse seems to point to the horizon and it is almost impossible to click any object (other modules work ok) P.S. I've a Pimax 5k+ With tooltips enabled is possible to click (but not see the cursor) EDIT: I found a workaround, if you set the IPD Distance to 40 is possible to see the cursor, but the cockpit is a lot bigger than the real one. Also with 50 on IPD Distance, the cursor is rendered at halfs, (left half on left eye and right half on rigth eye). Maybe it's a reprojection issue, but I tested with and without it active and the result was the same.

Thank you for the feedback. The core engine improvements are really needed. Anyway is better to have more options regarding distance rendering, for example, maybe I prefer to sacrifice objects or buildings render distance and terrain LOD but render static lights a lot distance to have nice performance and a useful night flying.

@BIGNEWY @NineLine Any news? I fly in VR and to have a decent perfermance the visual range must to be on Low, and with this, the lights are almost no rendering.

bump

Any update on this, we are suffering this problem in our servers too.

Please, make it optional. This effect is horrible in VR!

I also get a FPS drop when lock

bump +1