Tea-Pig

Further update: I've done some more launches with the Hornet (Damm, that nose wheel steering makes life easier!) on the George Washington. Mostly ok, but at least one launch has had the shaking, so the Washington/Hornet doesn't seem to be totally immune.

OK, so I figured out the Hornet enough to taxi and launch. Tried the A4 on the Washington again. Shaking present. Changed plane to Hornet. Did several launches all with no shaking. Changed carrier to Roosevelt. Shaking returned. So it would seem that whatever fixes things on the Washington for the Hornet doesn't work for the A4.

Yes, I've wondered about this too. I've mentioned it on their Discord in the hope it will help someone dubugging. I will have a go at trying the Hornet. Can't be that hard to figure out but I'm WW2 guy really. Multi function screens? WTF are those for...

Here you go. Mover grab and mission file. Maybe it's because I'm using the A4E. I could try it with the Hornet if I can work out how to drive it, (bought ages ago and never flown. Major buyers' remorse lol) A-4E-C Carrier Land Practice.miz

For me, CVN-73 is just the same as the rest of the supercarriers. They all have the same shaking. Maybe 1 in 10 hook ups will be ok.

Thanks to all responsible for the new version of this fantastic mod with the wing fold trick. Now I can enjoy being directed around the carrier after landing. So far I've been directed to park in the island, on top of a another plane and off the stern of the ship. These directors are not the brightest cookies in the jar.

I've got an Alpha grip on mine and everything works properly so you should be fine.

My opinion after a couple of weeks with the Moza unit is that while the hardware seems really, really nice, the software is pretty much useless and thoroughly spoils the show. In DCS, assuming you manage to get the software installed and it doesn't crash regularly, the experience is not too bad as the stick manages to reproduce DCS's own FFB effects quite well, although any additional "telemetry" generated stuff is very underwhelming. In MSFS, which doesn't make its own FFB effects, the Moza telemetry effects are crude, robotic and so weak they're usually often barely noticeable. And in IL2, which is not fully supported yet, the Moza can't even replicate IL2's own FFB effects properly. Youtube is full of glowing reviews for the Moza stick but I think most of these reviewers are raving about the concept of FFB rather than the Moza experience in particular. For me personally, I was having a better experience with my old modified Sidewinder than I am with the Moza, which might well have date with Ebay in it's future.

I just start up all the various programs I need to fly (I have a lot) including a DCS launcher, put the headset on and just peek under it for the final "Start game in VR" click. I guess it's a bit clunky but it's better than being pestered about controllers all the time when you're flying.

I used to have this controller problem until I discovered you can turn them off by holding the menu button on each controller for about 10 seconds. I've not felt the need to turn them back on for nearly a year now.

How do people here feel about the strength of some of the 'Telemetry' generated effects, particularly the stall buffet? The 'Direct' effects from DCS are great: a typical warbird stall will have my whole rig shaking with the stick, but when trying to replicate that for a plane with no FFB implementation using Telemetry, even with all the sliders maxxed out the best I can get is a barely noticeable twitching.

Info for anyone installing the Moza base: if you have V-joy installed there appears to be some compatibility issue with the Moza app. I found it necessary to open the V-Joy config and switch off all FFB settings (they seem to default to ON). Before doing this the Moza software would not reproduce any 'Direct' effects and only the 'Telemetry' generated effects would work.

Thanks for the confirmation that there is some sort of bug @NineLine. The best track I can give is the one I posted earlier and is repeated here. It's short and sweet: failure with all the usual symptoms at about 17 seconds in. I have others, but since the track recorder isn't very accurate it's a lottery whether it will get to the engine fail before being shot down by AI doing something completely different to when the track was recorded. I've had failures at full throttle with MW50 and at under 2500 rpm loitering throttle. I have not been able to see any definite pattern, although cruising at moderate throttle following a period of full power dogfighting seems to be a common failure point. It starts with a momentary power loss (which I can feel in my motion rig) which triggers the oil to overheat suddenly, and the engines dies shortly after. 1.trk

Yes, still bugged here too. Momentary drop in RPM/power and then the oil immediately overheats. Throttle setting and engine use seem not to be a factor. If I'm at high altitude then I can glide for a considerable time after the engine quits but the oil temperature never drops. The MW50 breaker thing I mentioned above is not relevant and seems to have gone back to normal. Maybe I had some spurious keybinding. I have a dual throttle and seem to get just about tolerable reliability by binding the cowl flaps to the second lever so that they open as the throttle is increased, but it might just be placebo effect. I doubt if we'll ever see a real fix for this. ED have had several apparently half-hearted attempts, and we all know where their real focus is. Perhaps the best we can do is consider it "historically accurate". Engines built with slave labour probably weren't very reliable. At least the A8 is vaguely usable again as long as it's in bright sunshine. Another half-hearted fix it seems.

Regarding the TACAN, I've not seen it mentioned here but it has been discussed on the A4E Discord page. Apparently a recent DCS update broke it. There is a replacement LUA file published on the Github page which fixed it for me. https://github.com/Community-A-4E/community-a4e-c/blob/develop/A-4E-C%2FCockpit%2FScripts%2FSystems%2Fmission.lua

Not feeling hopeful now. Another failure and track attached. The failure event starts just about 10 seconds into the track. The rear fuel tank light flashes and there is a momentary drop in engine RPM. The oil temperature immediately starts to climb and engine is toasted shortly after. 1.trk

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.