ARM505

I've helped with counting 'early bursts' from prox fused 76mm rounds, also fired from OTO Melara's, and let me tell you, it was probably about 20% that burst immediately upon reaching the minimum arming distance. It's probably not limited to the Danish Navy

This is all well and good, but do some people realise that DEMOCRACY IS IN DANGER?!?! (For those unable to read between the lines - people need to chill and realise there are other games to play AND KILL BUGS IN)

Given that we can probably rule out time travel, and today's the 4th, I'd say yes, it got delayed.

No, no such option in DCS unfortunately. I'm not sure if an alt- modifier can be linked to an axis....a possible workaround if that's possible, but I don't think it is.

Game breaking bugs of this nature are EXTREMELY rare - a data point of one, but this is the first time I haven't been able to play when (or rather, how) I wanted to since I started with Lock On all those years ago. And, as mentioned, it can of course still be run in normal 2D mode (hence the 'how'). So while you technically have a point, let's not overstate it. Ironically, had this happened several weeks ago prior to the stable/openbeta path merger, we'd probably have had a hotfix already. So it's a rare 'window of vulnerability' that caught them. As you say, it SHOULDN'T happen, but it does, in very, very rare cases. It's acknowledged and fixed internally already. That'll have to do.

Quite ironic that as the open beta and stable paths are merged, and patch cycle times increase, a game breaking bug (for those on Meta VR devices at least) emerges And I mean that quite sincerely, what are the chances, lol. Ah, sims, always a game of patience. Anyway, 2D flying it is for the moment. Pity my Track IR decided to break in a super weird way at the same time (1 HZ position updates, no idea why)

You don't need to delete anything - just find 'options.lua' under your C:\Users\*your name*\Saved Games\DCS.openbeta *or whatever your install folder is called*\Config - under the ["VR"] subsection, look for ["enable"] = and set it to false And for ED, as I've said before, it would be better if there was an easier way to toggle VR on and off before starting DCS. Also for ED (forum mods) - the 'Game Crash' and 'VR Bugs' forum subsections have what seems like 10+ threads on this same topic/problem now. The official answer to this problem for the moment (again, buried somewhere in one of the threads) is that it's fixed internally, but given the lengthy waits between patches the newer system entails, we are stuck for the moment with no idea when the fix will be released, at least several weeks away it seems.

How convenient. One day they'll (edit to add: I mean Meta) employ people who don't randomly break stuff, but today is not that day I guess. Anyway, day x+1 of wishing DCS had a way of selecting VR on or off before launching the software. Yes, yes, DCS launcher (not installed on my new PC, not going to) so it's back to digging around in the .cfg files to turn VR off. It's all good. (edit to add: to those who don't know where this is, it's in 'options.lua' under your C:\Users\*your name*\Saved Games\DCS.openbeta *or whatever yours is called*\Config - under the ["VR"] subsection, look for ["enable"] = and set it to false )

I have the same issue. The above options don't work in the the headset's menu itself (there is not such PTC option in the 'Experimental' menu). In the Oculus software that runs on the desktop, there is a PTC switch, mine is OFF. DCS logs in, authenticates, then simply doesn't run. (MT)

The *wake* is missing the distinctive 4 screw pattern, not the actual carrier model. Yes, it's a bit of a nitpick, but it's a good catch

No, it isn't a normal 'zoom' command. The commands for VR 'zoom' are under the 'UI Layer' control category - there's a VR sub category, and the commands you're looking for are 'Toggle VR Spyglass Zoom' and 'Toggle VR Zoom' (one is just a higher zoom level than the other).

Sorry to add nothing of value, but I'm just laughing at this which is (to me) the quote of the week. Thanks.

The Spitfire cockpit got a re-bake.....I've also been hoping the Huey can get a spring clean, it's a great machine. I also don't mind paying for a V2, I understand that these things take resources. And ED has to forge a long term maintenance plan for these things, we have iconic aircraft that are going to need to evolve with the product, so....pretty much along the lines of the KA50 and A10, yeah.

Just out of interest, if you have a specific term in the 'search' bar at the top (for example, 'gear') then the command will not be highlighted if you press it, EVEN IF that command does appear in the searched for items below. e.g. 'gear' is searched for, all commands with 'gear' appear below, but if you press (for example) your command for 'landing gear down', that command will not highlight. You need to delete the search term above, then it all operates as normal. I'm not sure if this changed recently, but for some reason it stood out to me when changing commands very recently.

Is there any specific aircraft/manual you're referring to? But it's actually a very good question. My (probably wrong) answer is that in (for example) a 737, antiskid uses IRU data, compares it to wheelspeed sensor values, and maintain/releases brake pressure to maintain wheel speed at a certain reference speed in relation to ground speed (best guess, as the 737 FCOM isn't wonderfully explanatory in this regard if I remember correctly). The 777 manual is even less illustrative, saying only "When a wheel speed sensor detects a skid, the associated antiskid valve reduces brake pressure until skidding stops.", and that "Locked wheel protection is provided using a comparison with other wheel speeds". Apparently, pilots are on a 'need to know' basis in this regard, and they just don't need to know *shrugs* So: locked wheel protection on the other hand, compares one individual wheel speed to another specific wheel - then releasing brake pressure when the reference wheel is (for example) 50% slower than the other (basically three inputs: reference wheel speed, threshold, like the 50% in my example, and 'low' value, ie speed below which the protection will be inhibited)