JupiterJoe

Anybody else finding ICS & ARC-182 volumes are no longer adjustable under some circumstances? More alarmingly my ALR-67 volume is at zero and not adjustable. Other than that, the new engine sounds are great. Although a significant engine volume increase when we open the canopy would be nice. You can hear radio static constantly (on external views it's most noticeable when things are quiet), and squelch is not working. The ECS is heard on the carrier bridge/AirBoss view. I'm also getting almost constant contact callouts from my wingman, like he's on a loop (the distance to target remains constant). I even tried asking him to switch his radar off to shut him up. No dice. When he's locked-in he won't respond to other orders. Auto-pilot not working consistently with MS Sidewinder FFB2 stick. ACLS doesn't work with this stick either. Auto-throttle disengaged warning light not illuminating when it should. Saved Track.trk

I didn't know this. Once again, amazing work by HB.

Blimey! Good thing it has a titanium wing-box.

You've made the datalink to the wrong carrier? Easily done amongst a big taskforce.

Shouldn't my wingman have his formation lights on? null

@NaquaiiWith all due respect, there is no way for the community on this forum to know if a bug is already being tracked or not. There are hundreds (perhaps thousands) of disparate threads, many relating to the same bugs in some circumstances. On more than one occasion there have been cases where a long-standing bug has again been brought to a Developer's attention, only to have them say 'Oops, our bad, we forgot all about that.'. To say 'if it's not acknowledged here it's acknowledged on Discord'; and vice-versa, is a feedback loop from which there is no escape. As an example, I posted two bugs on July 4th and there's been no acknowledgement whether they're already tracked, or if it's the first time they're being brought to HB's attention: As I've stated before, our frustration is what has organically brought threads like this into being. I ask HB to reconsider their policy of not sharing a current list of tracked bugs with the community. After all, the bug list featured at the beginning of this thread is not very long. In the building trade it would be referred to as a Snag List.

Noticed this in the extreme distance the other day: Only one or two clouds are casting a shadow, the ones closest to the sun. Looks like cloud shadows do exist, they're just not being rendered properly. I think people are currently mistaking reflections of clouds on the water's surface for shadows.

Please compare the volume of the engines when you're in the cockpit to when the the canopy is open. IRL it would be deafening without your helmet on, would it not?

Okay and by-the-way, I have edited my previous statement to say that the volume of your own engines does not increase as much as I think it should when raising the canopy. See what you think. Cheers.

I recommend deselecting 'Hear like in helmet', in the audio menu. I believe that option doesn't do the nuance of HB's soundscape any favours. The new howl from the induction noise is amazing.

The fire suppression system works great. Thank you Heatblur Although, I've yet to create a fireball from a compressor stall . Anybody? EDIT: I've seen the fireball. Was looking at the wrong end of the engine

Both elevons recorded as being destroyed, but graphically show still attached (you can see the separation cracks). Again, I believe this is something HB may already be aware of.

Okay, but this has always been the case with the F-14, not just since yesterday's reworked engine soundscape. Open the canopy on a running F-14 and you'll notice the volume of your own engines barely increases. I believe this may have already been acknowledged by HB in the past, as being something they wanted to tackle (I'll be damned if I can find it though). Adjusting the cockpit sounds and/or exterior sounds sliders doesn't do the job either. Whether you have the 'Hear sound like wearing a helmet' option selected, or not.

With regard to sound. I would like to see it added to the Fix/Wishlist that engine sound volume increases more than it currently does, when the canopy is raised. Adjusting the cockpit sounds and/or exterior sounds sliders doesn't do the job either. Thank you.

What do you mean you failed to reproduce? You failed to reproduce the bug, or what happens in the video? It's supposed to illuminate under the circumstances depicted in the video, isn't it? Therefore the bug stands.

Good morning Scommander2. Thank you. In the F-14 Special Menu I do have the 'Use FFB Trim Implementation' box selected. I also have the Force Feedback box selected in the miscellaneous menu. I'll try de-selecting Trim implementation and see if that allows ACLS to work... EDIT: It does!! Thank you @scommander2 I'll update my bug report.

Wait, you have bug reports in two seperate locations?!

Yes, but this video seems to show it working as intended. In this example, as Cap traps and goes to full a/b he's manually over-riding the AT and the light comes on. You obviously wouldn't just need that warning light when you've landed, but on approach, to give the pilot a chance to react, especially at night, or in fog, when you'd need to know in a hurry if you've accidentally knocked the throttle out of AT. At the moment I can't get the warning to illuminate by any means. Hence I suspect a bug.

Anything for the F-14 included this time? It's been a minute.

Bug: Use of FFB stick affects auto-pilot and ACLS. Can I reproduce it 100%: Yes If not 100%, how often out of 10: 9 How to reproduce/ description: Engage ACLS and/or Auto-pilot. F-14 frequently not able to sustain level flight with ALT HOLD engaged. Track shows pitching up to 50+ degrees without any player control input. ACLS shuts off and aircraft pitches down once AP ref button pushed. I have sometimes found taxiing through another aircraft's wake can break FFB. Time compression has also caused problems. A restart is necessary to get FFB functioning as it should. Ground Track does not seem t work properly either. Version: 2.9.5.55918 M/T 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 FFB2 Throttle: Virpil Controls T-50 CM3 Head-tracker: Third-party Track IR Mission File: Instant Action: F-14A Carrier Quals - Marianas. Track: See attached. Please compare two tracks, with and without FFB sticks. It should also be noted that FFB ceases to work properly if you switch aircraft. A full restart is required. ACLS test with ffb.trk auto throttle test no ffb.trk Workaround: Deselecting 'Use FFB Trim Implementation' in the F-14's Special Menu enables ACLS to work as it should. A shame because realism is sacrificed. Perhaps HB and/or ED will find a fix in future. It should be noted that auto-pilot behaviour remains erratic with FFB. A big thank you to @scommander2 for pointing me in the right direction.

Bug: Auto-throttle disengaged warning light not illuminating. Can I reproduce it 100%: Yes If not 100%, how often out of 10: 9 How to reproduce/ description: Step1: Engage ACLS and activate auto-throttle. Step2: Manually over-ride auto-throttle. DCS Version: 2.9.5.55918 M/T 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: Thrustmaster T-Flight Stick X Throttle: Virpil Controls T-50 CM3 Headtracker: Third-party Track IR Mission File: Instant Action: F-14A Carrier Quals - Marianas. Track: Please ignore first pass. The second pass demonstrates taking manual control of the throttle and the auto-throttle disengaged light not illuminating. It should also be noted that FFB ceases to work properly if you switch aircraft. A full restart is required. auto throttle test no ffb.trk

Be great if there was such a thing at this stage. The F-14 is near completion, hence why the list is currently a manageable size. We, the community, have no idea what bugs are currently known/not known to the Devs. Hence why this thread organically came into being.

The F-14's FFB model was originally developed on the MS Sidewinder FFB2, by Fat Creason apparently. I doubt HB would have released it to market if the autopilot was un-useable with it. I suspect subsequent patches have screwed something up. Personally I am getting a spurious flight controls input (gradually pitching up/down to at least 50 degrees) when AP is engaged. It doesn't cause the AP ref light to illuminate in ALT HOLD, which makes me think it's more than just a slack/loose centralising force.

The F-4 alone must be one of the most complex flight sims ever offered to the public. As well as all the other modules each patch has to cater for. DCS continues to offer a calibre of product we wouldn't even dare dream about a few short years ago. So let's cut the guys some slack, eh? Otherwise we're in danger of sounding like a bunch of spoilt brats. This community strives to be better than that.

Thank you Lt_Jaeger. I understand in real life the ACLS was rarely used and manual carrier landings is the way to go, but it would be nice to get autopilot/ACLS to work as it should with FFB. I'm very new to the world of FFB and find my MS Sidewinder FFB2 stick breaks away from ATT/ALT hold too often to be useable. A huge shame, because it's so wonderful in manual flight. EDIT: No patch today Be nice to see what, if anything, was planned for the F-14 in the next patch.