JupiterJoe

Have you recently tried the missions I've mentioned above? I've just blanked it off the sensor with black electrical tape.

Does anybody here fly Reflected's Speed & Angels campaign? I am noticing the FFB can break when you follow the lead (Paco) to the runway in the early missions. The wash from his engines makes the stick 'jolt' and then FFB no longer works as it should. I have reported this in the recent patch feedback thread, but am worried it may just be me. Thanks.

It did function before the last patch. Cycling it is part of the proper start-up procedures. It used to raise the launch bar, but not stay locked in position the way it should. Now the switch doesn't move. It's only a small thing I know. Perhaps this change indicates HB/ED are working on those things in conjunction with Supercarrier functionality.

The Laser Code is not selectable via Jester. It's cycling by itself.

@IronMike, @fat creason, @Naquaii Launch bar abort switch is no longer functioning. When using my MS FFB2 stick, Heading Hold won't level the plane, but Ground Track will. ACLS does not work with MS FFB2 stick The LANTIRN laser code is not selectable via Jester. The 2nd code number endlessly cycles itself. I think HB may have increased the external volume of the engines when you're in the cockpit with the canopy open. Can anyone else confirm this? If true it's fantastic news. Thanks HB.

There is a slight step in the graph as the Y-axis moves through the centrepoint. There's no step with the X-axis. Not seeing any dramatic 'spikes' in the data though, a nice flat line when stationary. It all looks pretty good to a layman like me. Perhaps it's something in DCS after all. What is DXView?

Yeah, here is a little video of these spikes/fluctuations/spurious signals, with no input from me. I'm now fairly certain this is what's causing my issues. I took the stick apart and my main focus was the potentiometer for the fore/aft axis and sure enough I found a slightly pinched blue wire. Might bust-out my multi-meter later and see if I can test it. The rest of the stick was in immaculate condition. Looked brand new. Be a shame if it can't be fixed. Going to try the Virpil Joystick tester. thanks for the heads-up. I have a Virpil Throttle, so have that software... fluctuations.mp4

...Okay, tried that, same result. When in a 20+ degree bank you can see in exterior view (F4), some spurious inputs on the elevons (they jolt up/down for a fraction of a second). This causes the aircraft to fluctuate whilst in ALT HOLD etc. The A/P is being fought by these spurious inputs, but not enough to illuminate the A/P reference light. In my opinion this speaks to a hardware issue (makes sense, it's a 20+ year-old, second-hand stick after all). I wonder why it happens in a turn and when wing-sweep is beyond 40 degrees, above 30k feet. At lower altitudes and in level flight it's pretty steady Trying to isolate the issue is driving me mad Might have to get a screwdriver, take apart this stick and see if anything can be cleaned/tightened etc.

So yesterday's patch would have done a full file check and repair, would it not? You're saying I just need to create a back up of my whole saved game folder (2.5 Gig), delete the original and the game will revert to default settings for controls? Thanks, I'll give it a try...

I think this pitching fore/aft is what is causing my A/P HOLD to breakaway. My controls are showing a significant amount of forward input when I have A/P engaged and am in level flight (see attached). Is yours the same? Apparently in real life a cold & dark F-14's stick is trimmed forward to aid pilot's ease of access to the cockpit. So this is probably modelled correctly. ACLS is broken for the FFB2 (maybe all ffb) stick(s). Give it a try. It's basically a suicide/self-destruct button. Just make sure you're not using your favourite pilot profile, or he's set to invulnerable. For this reason I am not sure other aspects of my set-up are functioning as they should. As I've said, my ALT/ATT hold will not work consistently. THe problem is so bad I am considering going back to a non-ffb stick, which is nowhere near as immersive. You mentioned not doing a full re-install. Is there another option I could try? It sounds like your set-up is working as it should, so perhaps it's not my stick but a corrupted config file, or whatever. Alas, there is currently no way to fine tune the autopilot 'breakout'. I understand there is with the F-4, so perhaps the F-14 will get something similar soon. null

I'd appreciate that. I don't know if I need to re-install DCS, or the stick is faulty.

'Before'? When's the last time you flew the F-14? Swap Axis selected 100% Shake force 100% Trim force FFB Trim implementation selected in the F-14 Special Menu No curves or dead zones

Weapons. AIM-54C does not reacquire lock to target if lost while active - fixed.

Is the stick supposed to rock fore/aft when autopilot is engaged on the F-14? Does anybody else experience these issues:

Did you sell your FFB2 on ebay? I recently bought a second-hand one and I suspect it isn't working as it should.

Does everybody's MS Sidewinder FFB2 rock fore/aft when autopilot is engaged? My ALT HOLD fails quite often. Is this normal? ACLS with this stick currently nosedives the plane into the ocean.

Bug: ACLS broken with FFB stick If not 100%, how often out of 10: 10 How to reproduce/ description: Step1: Activate ACLS Step2: Press A/P ref when indicated to do so. Step3: Take a swim. DCS Version: 2.9.17.11733 System Specs: Processor Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz 3.70 GHz Installed RAM 64.0 GB Device ID 36C95E96-CEE8-4C82-AF93-9730F33AFFDB Product ID 00330-80000-00000-AA169 System type 64-bit operating system, x64-based processor Windows 11 Pro NVDIA GEFORCE RTX 3070 Peripherals: Joystick: Microsoft Sidewinder FFB 2 Throttle: Virpil Controls T-50 CM3 Headtracker: Third-party Track IR Mission File: Any involving Carrier recovery and use of the ACLS. Track: Saved TrackACLS.trk

Thanks guys. I guess I'll try and play around with the mission that @draconus doctored in July: ReforgerII_m3_the raid.miz

I too have experienced some strange behaviour recently using the M/S FFB2 Sidewinder stick. By the way, does your auto-pilot hold level flight when banking over 15 degrees, or above 25k feet (I suspect wing-sweep angle is a factor)? Mine does not. I've heard the A/P in the F-14 could be sketchy. Perhaps this aspect is modelled correctly. FFB stops working if you swap aircraft, even from A to B. Are you aware? In fact it stops working frustratingly often, at least with this particular stick. I hope this is something that ED/HB manage to fix soon. I won't upgrade to a more expensive FFB stick, unless I know it works more consistently.

I think a trigger has broken in this mission since the last patch. Guided bomb not hitting the Northern bunker. Never had trouble in the past. The RIO declares an impact whilst the bomb is falling (perhaps triggered by the wingman's hit the Southern bunker), and your own bomb falls long, as though the RIO doesn't fire his laser. After three failures I tried changing the laser code before leaving base, still no dice. I even bombed the bunker manually with the remaining bombs, still no trigger. This is mission has a particularly laborious ingress to the target zone, so when it doesn't work it's frustrating.

Sometimes my AP won't hold altitude. Heading Hold also doesn't work on occasion. You can see the elevons making large un-commanded pitch changes, as if receiving spurious signals. Does anybody else have a problem with AP whilst using a FFB stick? AP with my non-FFB stick is steady as a rock. So I'm thinking either the FFB model is broken, or my MS Sidewinder FFB2 is.

Physics, it's not for everyone.

When applying brakes independently the starboard main gear wheel won't lock-up. It makes the sound of tyres-screeching, but continues to rotate. The port side wheel behaves as it should. This is with/without anti-skid. Stick only in full forward position (to aid ingress IRL), after repair. Normal cold start has the stick slightly forward of centre, but not fully forward.

Yes and it's even louder is AirBoss view than it is in your own cockpit. The F-14 is the only carrier capable module I have, so can't check if it's the same for other modules. I suspect there's a conflict somewhere because I have heard the AirBoss view ambient audio playing in my F-14 cockpit.