All Activity

Same.. no fix on CDU is a bummer.

The last update from HB is at: https://discord.com/channels/1071433028045377637/1071574236403081287/1395028665775161364 According to the update, they are preparing a "big" release, therefore, they are going to miss in few releases.

As concrete examples: - Meta XR simulator reports a FOV of 50 degrees upwards of center (well, 0.87266463 radians....) , and 49 degrees down, which is close enough to symmetrical for this to be subtle - My Quest Pro reports a much more substantial difference of 42 degrees up, 53 degrees down, so a crosshair that is put in the center of the render target without paying attention to the FOV angleUp/angleDown will be quite substantially off. These numbers are the angles provided to DCS by the runtime in the `xrLocateViews()` call - they are not a subjective measurement of my perceived field of view.

Is it correctly working along the TWS auto mode? So good bye to having to go AUTo>MAN>AUTO again to L&S target outside current AUTO rdr coverage? I'm away on vacation and we'll be unable to test for at least 1 week :( Enviado desde mi RMX5011 mediante Tapatalk

update looks good, whilst checking the details / updates i ran in to these. Gap in ground -camera 78.668887 1.905579 270.809218 -cameradir -0.336686 -0.429071 0.83817 Weird wall's -camera 75.204481 1.818567 272.915735 -cameradir -0.158311 -0.208943 -0.96502 Tree through building -camera 79.496264 1.846249 262.799602 -cameradir -0.183669 -0.266759 -0.94610 Akward elevation -camera 77.644519 1.888519 273.102521 -cameradir 0.912503 -0.303970 -0.27375 Akward waterway's -camera 79.458678 1.808526 276.163650 -cameradir 0.967789 -0.201339 0.15115 Bridge -camera -259.386621 1.032934 -46.885197 -cameradir -0.826349 -0.361326 0.43196 Weird? -camera 122.771216 1.517924 274.471822 -cameradir 0.547517 -0.215264 0.80863

Thanks for the track! But I still don't understand the issue. For 2 minutes everything looks perfectly normal, and at the end I can't tell from the track what kind of inputs you're providing. The switching of SOI and SPI all throughout the track also makes it hard for me to understand what you're trying to show. At this stage I'll go ahead and say that everything looks to be working as intended as far as I can tell.

I find a lot of problems with the harm missile and DCS world First off dismissal travels at Mach 2.9 The fastest I have ever seen in travel in DCS world is 680 mph Yesterday I noticed there is only point about 20 miles of ranges about 80 miles And mostly This is true Because the size of the missile it has a tiny tiny tiny radar cross-section Because the speed and the size is not likely to be picked up by radar

I believe so, yes. That is also my understanding of the overall system. But we will see in a future video where exactly ED is going with this...

thank you for the ping, I will run it by the team in my morning. Its late here and about to head to bed.

Someone in this video created a pink block in Blender, injected it to the cessna cockpit, then added it to MSFS. Then he managed to get a nice MR blend. I understand that in DCS, one needs to use the blender EDM Exporter. Would anyone know how to something similar for DCS, taking care of the texture or mesh files in the right mod folder? This will make a nice MR result. But I am clueless about Blender and DCS texture mod. I can achieve MR using VD and OpenKneeboard. But the latter requires constant realigning with DCS virtual cockpit. Fixing a pink block merged with the cockpit in DCS then let VD do the passthrough will give us a good result like the MSFS video above.

Open up the comms menu, open Ground Crew ... , select Rearm & Refuel. Then in the lower left lower corner of the GUI you see the Cargo field/buttons, considering you are in the vicinity of cargos (Static objects -> Cargos).

Official changelog is here:

From On Develop

Where do I find changelog info on their modules? and don't say Discord!

how could anyone answer that if you don't care enough to post a track?

This probably varies depending on whether the headset has a symmetrical field of view: my guess is that DCS draws the crosshairs in the vertical middle of the panel, which isn’t the center of the FOV on some recent headsets, but often is in simulators. this also ties into the “mirror window is too high” reports , but in that case it’s not a bug - it’s a mirror and it’s showing what’s on the panels, the panels are mounted off-center intentionally

Just did the latest update. No change. Still two seats.

Give more details, post a video, post a log, post a track. Wee don't know what you did wrong just because temps are good.

Oasis Driver now in Steam, will be release at the end of the month. https://store.steampowered.com/app/3824490/Oasis_Driver_for_Windows_Mixed_Reality/

Great find! Thank you!!!

Same experience. Only time the seeker even change tone is when pointing down to the ground. Not even a change when looking directly at a frogfoot flaring like crazy. Seeker uncaged.

Закон тривиальности Паркинсона в теме этой вижу я.

No track file showing the issue?

SAME PROBLEM