JupiterJoe

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.

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?!