Tea-Pig

I think I perhaps see my issue. In a hot start or air start mission, when I first spawn into the cockpit the MW50 circuit breaker is on, but when I click the 'Fly' button to begin the mission the breaker immediately pops out. So I fly believing MW50 is engaged but it's actually disabled, hence the engine failures. I'm surprised I didn't notice immediately, but I think the engine sound has been tweaked a bit so this might have masked it. Since noticing this and pushing the circuit breaker back in at mission start I haven't had any unexplained failures. Feeling hopeful.

I just updated from 2.9.6 to 2.9.9 and was hopeful for a fix for the apparently long standing Dora engine random failure issue. The changelog for 2.9.8 claims: Fixed: Random engine failures (adjustments to oil system) and in a recent thread here @NineLine said: "This should be fixed now, thanks. " Out of three flights, two ended in spurious engine failure in the usual fashion: oil suddenly overheats and engine dies. So alas, no apparent change for me. How is everyone else doing?

Thanks @BIGNEWY. The gearboxes of my rig salute you and hope for an end to their torture.

I have added an overall amplitude control to my rig so I can turn down the movement as I nudge towards the shuttle and then turn it back up again after the shooter starts signalling for power up. It's a workaround but finding and fiddling with the knob still spoils the experience to some degree. I'm going to look at remoting this control to the HOTAS which would help but it might need another Arduino. I think it will be worth the effort as the chances of ED fixing the bug seem rather remote. I'd love to try a carrier launch on a Yaw. It must be quite something with that huge pitch range.

Can I add my voice to those to those already asking for this apparently long-standing bug to be fixed? I have the violent oscillations on all the carrier planes I have, F18, T45 and A4E. It's ok if I spawn in on the catapult but almost always shakes my tooth fillings out if go through the hook up procedure. The video posted by @Bojanglez looks pretty mild compared to what I get. It's a real shame because DCS carrier ops are otherwise superb with a motion rig.

Ooh, what's new? Is it worth the risk of a load of new ED bugs in the patch?

Is anyone from ED actually reading this thread or are we customers just whining amongst ourselves? While I absolutely appreciate the upgraded cockpit and think it's great that old modules aren't left to fade away, once again we see a plane rendered close to unusable by a well-intentioned update. It's Mosquito undercarriage syndrome again. Someone at ED needs to type the phrase "quality control" into Google and find out what it means. This situation is made worse by the apparent total lack of any official response. Does ED agree there's a problem? Are they fixing it? Are they even aware of it? The silence is as deafening as the guns in my Anton which are very, very silent because I can't see anything to shoot at. An official response please? Pretty please? @BIGNEWY

DCS does indeed allow the binding of multiple controls to a single axis but it doesn't do any form of addition of the inputs. The two inputs just fight with each other and the last one read wins resulting in a flickering mess, so it's not a terribly useful feature. I think it might be possible to achieve toe brake controls using the 'merge axis' function in Joystick Gremlin. We could add the toe brakes together to create an overall brake axis, and also subtract one toe from the other to create a steering axis. I had a quick look at this and it basically works but I can't see an easy way to combine this steering axis with the rudder. There is also a clipping issue to overcome.

My Oculus driver downloaded an update last night that appears to fix the OpenXR Toolkit crash issue.

These new spotting dots are working great for me. They look good at long distance and the aircraft just grow from them as they get closer with no jumpy transition. Good job ED. (VR, QuestPro, Oculus Link, RTX4090) Canopy reflections are a problem on the re-vamped FW190 Anton. Too strong and don't respond to slider in setup menu. Also they flicker with head movement.

I have the flickery canopy thing too. Also the canopy reflections are too strong and don't respond to the setup menu slider. Nice to see the A8 getting some updates though.

I agree that the new cockpit textures are a nice surprise. There's also so nice scratched perspex look on the canopy glazing that I've never noticed before. However I'm getting a problem with the canopy reflections which are too strong and don't respond to the slider in the menu. The reflections also flicker when I move my head (VR). Anyone else seeing this or just me? Other aircraft seem ok. Spotting dots seem to have had some attention too.

Just had my first few flights on this map and OMG I love, love, love it! I fly helicopters and WW2 so it's going to take me a long time to explore it all. And the performance is the best of any map I have tried. I just flew VR for about two hours over Falklands and around Puerto Natales and not a single stutter or dropped frame. I never knew DCS could be so smooth.

Given the positive comments, I succumbed to temptation. Downloading 77GB now...

I think the line "Fixed: tail wheel too sensitive" is something of an understatement. It seems that the whole ground behaviour has been re-done. It's now very easy (maybe too easy?) to land and take off. Much less bouncy and nothing seems to break. Tail up landing seems to be much more like the videos of real Mosquitos. The sharp, bumpy, racing car ride now feels like a luxury saloon car. The nose-over effect from the brakes is completely gone and the brakes are joy to use on my motion rig. Unfortunately the new update seems to have wiped out my FPS on the Normandy map. The frame time graph looks like a startled porcupine and the map is pretty much unusable. All my other maps seem ok, at least as far as anything in DCS is ok when it comes to stutters.

This.......

I've been tempted by this map in the past but was put off by the lack of free trial. Now it's revamped and half price in the sale and I'm tempted again, but put off now by the current Razbam situation. I see some mentions here and on Discord of this being a different team that's not affected by the current dispute. Is this an officially stated position by Razbam or ED, or just optimistic forum chatter? (No disrespect intended to anyone who has stated this.)

I just download the I-16. Same problem and same fix. Thanks for the thread.

Finally got round to doing the Mosquito engine box. It's a chunky beast.

If Early Access is an essential part of the DCS business model then I would suggest some steps are taken to fix it because it seems to me to be one of the major causes of angst among customers. To me the problem is that everything is far too vague. A module is released and all sorts of future upgrades are talked about, hinted at and even promised, but there's never any timescale given. Years go by with little or no progress and Early Access customers feel let down and that their trust has been betrayed. I think ED should introduce (and adhere to) some standards for Early Access, with definite lists of coming features and TIMESCALES, so that everyone knows exactly where they stand. Or do away with Early Access and have other systems, like what was done with the Normandy map and its V2, or the Afghanistan map. Looking at current releases it seems that the likes of the Kola map and the Chinook are being released barely half finished. It's a huge leap of faith to buy into that; faith that has not always been well rewarded for Early Access customers.

Welcome to the world of DCS, a place of eternal youth where nothing gets old because just being created takes forever. I would imagine the economics are that it's more profitable for a publisher to use its resources to bring new stuff to market than it is to fix and finish the existing stuff. Result: nothing gets finished and people who have bought early access modules (for a miserly discount) are left out in the cold. The solution would be for us customers to just stop buying unfinished stuff, but we want the latest toys so... Looking through the current catalogue there are a few things that I fancy getting, but I'm done with early access. If it ain't finished it ain't getting my money.

Yes, plenty of Pico/ethernet stuff but I didn't really see any Quest/ethernet worth pursuing. No matter for me, I'll be back at the other house next week where the big PC lives and will play about then. Thanks for all the replies.

LOL! Mine was actually "lightly used to work on an Unreal Engine project". Other than the seal broken on the box it would have passed as new. I've seen them on Amazon for £5-600 with Amazon return policy. Yes, but I declined to open a developer account after it demanded too much personal information.

I actually got mine for £430. It seems legit. Already did the rear pad mod. At the moment I'm just messing around with it on my old computer. VR in DCS is so fragile and I like to work out at least some idea of what I'm doing before mucking about with, and possibly screwing up my main PC which has XR Necksafer and XR Motion Compensation on it so there's a lot to screw up. I have bought Virtual Desktop but don't have a WIFI setup on the old PC to make it work properly. I didn't realize VD doesn't work with a cable until I'd bought it, lol. So at the moment I'm just messing with the Meta link. Perhaps once it's all setup there won't be much need to see the PC desktop so the dashboard thingy won't be an issue. My main PC is hard wired to a WIFI6 router so presumably VD will work when I move onto it. I did download Quad Views and saw it working, but only as fixed at the moment. As I understand things the eye tracking data is only available if I open a developer account and I baulked at that when Mr Zuckerman demanded my credit card details and phone number. This alone might be the decider for VD.

There seem to be a lot of apparently new and sealed QPros for sale in the UK at the moment for around £500ish (half what Meta UK are charging), so I picked one up to replace my G2 and have been setting it up with lots of help from this thread. So far I'm loving the quality of the visuals, not hugely loving the comfort, and not loving at all the bloated, intrusive META crap that comes with it. Part of that crap is the infuriating controller pop-ups. So far my research has only come up with keep the controllers on the charging dock or turn them off by holding the menu button for at least ten seconds. This seems to get rid of the pop-ups in game but there's still an even bigger one plastered over the PC link dashboard saying the controllers can't be found. I've even un-paired the controllers and this pop-up persists. Also there seems to be no way to interact with the link dashboard without the controllers. I can use hand tracking to start the link off but only the controllers seem to be able to click that one stupid button needed to show the PC desktop. I was wondering if a Bluetooth mouse might be able to click that button but presumably the stupid pop-up would remain. How are people here dealing with these pesky controllers?