ARM505

I have the same. I do not run tacview and I have ensured all cores are unparked. It has defeated me, I have tried everything I can find here, but it still occasionally happens exactly as described above (including the dcs.log showing the 'ANTIFREEZE' message). The worst is when it happens on spawn in (although this may be a slightly different problem) - after platform selection, the sim can 'hang' with one CPU core sitting at 100%, the rest (everything, including RAM, drive activity, GPU) just absolutely chilling out and having a wonderful day. Then, when I do actually spawn in, somebody else has already taken the parking spot, and the natural result of two objects occupying the same space happens (explosion).

Well, that's a few hours of my life I won't get back Through some kind of coincidence, I discovered you can get Virtual Desktop to connect to the Quest 3 via USB cable using the Microsoft Mixed Reality app from the MS Store. It just worked, no problem. No need for routers of any kind, just the cable. Except....it's still actually worse than the Link software using the cable. Maybe I haven't set one of the myriad settings right though, who knows. Just to illustrate the house of cards that DCS is though, after all the experimenting and tweaking was over, I ran it using the usual Link software, as I have been for hundreds of hours....except now DCS refuses to play sound through the Quest, no matter what I do It doesn't help that there are so many 'layers' of control software over the hardware nowdays. Between Windows, Meta, Virtual Desktop.....so many layers and layers of settings and checkboxes, who knows what isn't right where. I'll just leave it for the day. Better things to do than fix stuff that shouldn't be so delicate.

Meta seems to be confused when people want to do what we do with their headset, yes. They are their own worst enemy. Literally every problem I have with the Quest 3 (which is physically a decent headset) is entirely Metas horrific attempts at software. You'd think that 'What part of "plug headset into a PC and transmit images" was hard?' but then you meet their link software which requires a lot of tweaking, and has a separate, legacy UI to the actual headset UI.

I have a USB to ethernet adapter, and tried using a surplus router dedicated to my Quest 3 - using the standard Meta airlink the image update rate was absolute garbage using the standard 5GHz setting that router was able to provide, I'm told you need a really good router. Is that what you mean by your last sentence? RT-RP looks to be above my IQ level, but I'll have a go.

I'd also like to know if this is possible. I'm not buying a fast router just for VR, when the link cable should be able to do the job (despite Meta's best efforts to make it the worst possible solution).

I can see it out of both eyes, in the correct place, in my Quest 3. It wasn't specifically asked for, but it was quite well received for the MiG29, once they removed the internal reflections.

It's the helmet visor cutout for your nose, as the visor is now rendered as a physical object in front of your face, as opposed to just darkening the image. It was added for the F16 and F18 in this update, to follow in the lines of the MiG29.

The same logic should apply to the Apache IHADSS (you're not wrong, but it seems they've not gone that route).

Off topic (but light related), the sunlight reflection glint from the helmet mounted sight (when stowed) in the rear view mirror is very well done IMHO.

I've also used a lot of tinted visors on motorcycles, and yes the effect is overdone. That being said, you do, in certain conditions get *some* reflections on the inside of your visor. In real life, due to focusing ability at different distances (which cannot be done in VR), it is also not as distracting. I do like the 'real object in real lighting conditions' idea, but it'll have to be toned down (as another poster said, it's as if light is coming in from above and behind, which would not be the case), as well as some kind of simulation of focal effect to make it less 'in your face'.

Noticed the same on 4YA. Weird. I still need to test some things which I might have used to get it to work....

The internet is an ego damaging place (what I mean is that there will ALWAYS be somebody who criticises, so don't take it personally). Thanks for trying to put information out there. If it were me I'd use an AI voice, or subtitles (purely to spare myself the irritation of getting needless criticism, as well as anonymity) Regarding the OPT setting on the range prediction (which currently just shows the same range as TACT or whatever the 'current' setting is called) - any idea what ideal parameters it should use? I'm assuming there's a 'best range' table or something along the best cruise range table you mentioned? And when the manual I have mentions 'fuel reserve', do you know what value that is? I haven't tested enough to see if it just flames out when it reaches zero. I should have looked, because I did flame out due to fuel starvation while playing online. Managed a glide approach onto a field, no issues - which also brought the question, how are the hydraulics powered with the engines shut down? Anyway, it flies really nicely, so that was a help.

The Alan Wise 'Flight Manual' just states: "The available flight range computer is used for computing and indicating the available flight range by reference to the information on the fuel reserve and consumption and true airspeed" So...not much help on the specifics of what those variables might be, where they're obtained from, or how it's calculated. I couldn't find any other reference, but then again, it's not like it's easily searched (I only have the actual book, not an electronic copy).

VPForce Rhino worked first time, no issues. Strange. I just let the stick wander around doing it's thing and it all worked.

*cries quietly in trying to get stable, reliable, simming with DCS and the horrific afterthought that is Meta's idea of PCVR with it's Link software* Note to those who want to get VR - get something where the designers actually have at least 1% of a clue what PCVR is about and how people actually use their headsets.