Not quite finished with the Eagle p*rn:

How good is the new flanker model!

Great flight with Tiago and Leech - flying the Viper for the first time in a while with no HMCS or link/IDM is good to keep your skills polished!

Yep I’m having the same issue and was about to log an internal bug report.
@Boxer would you have any idea about why the IVC offset function isn’t working?

Thanks for your report, this bug is known about internally and will hopefully be fixed for the next version.

Cheers

@Reinhard-Eichler

Strange that the closer friendlies aren’t responding mode 4. It’s unlikely that they aren’t equipped with IFF, almost everything in the BMS ecosystem is IIRC.

As far as avoiding blue on blue. You have to build your SA using all the tools at your disposal, this is one of the greatest (and most fun) challenges as an air superiority platform.

So in this scenario, you don’t have positive hostile ID yet when they are flanking you at 40nm (as depicted). In addition to no IFF response, If AWACS can’t give you a declare + no link-16 surveillance track on them, then you have to resort to other sensors to get an ID before you shoot.

1. What does your RWR tell you, hostile nails/spike indication? If no, then you are probably not at threat so hold your missile. If yes, and the spike is coming along the same bearing of those contacts, then you could probably safely assume they are hostile and shoot.
2. Try STT at a closer range (<30nm) and see if you get a buddy spike response then. It’s possible that at greater ranges the AI won’t necessarily respond to a buddyspike situation.
3. If all that fails and you still aren’t positive they are hostile, then you need VID! And that’s where you make your money as an Eagle pilot.

In future versions of BMS we hope to improve the AIFF simulation to be more accurate to the real deal. Currently the ‘disassociated’ circles are somewhat of a copy over of the Viper model and not accurate to the Eagles amazing IFF suite.

@Rainmaker Thanks for your feedback on this.

While we are discussing FM and FCS, another thing to note is that the speedbreak does not operate per the RL -1 manual.

Currently in BMS, the speedbreak will auto retract to a ‘slightly extended position’ as soon as the LG (or flaps - I forget now which) is selected DOWN, regardless of AoA.

@Civetta I can’t reproduce the issue, working perfectly well for me. Can you send a screenshot of your launcher with the bindings?

@Civetta

1. Bug has been fixed already for the next release
2. Sorry about the Shift+3 view. I think it is a legacy option that is not really maintained these days. I will investigate to see if it can be improved.
3. That is really impossible to debug unless you provide repro steps or some campaign files. It’s possible it’s an F-15D squadron you were flying but we only have a F-15C cockpit model which would explain the discrepancy.

@Tomcatter31 Those are the formation lights that are black and it is a confirmed bug. If you increase the formation light brightness via the knob in the cockpit, they will work on a higher brightness setting.

@zap737 Yep, that’s correct.

@zap737

Yeah the radio 2 volume knob was moved to be more correct. From the old version, it was on the lighting intensity knob but now it functions correctly on the R2 knob.

@zap737 The number to the right of the current G is the current max allowable G force. This number is dynamic and changes depending on a few factors including current mach.

Re the other issues, I’ll check and get back to you. The ramp start video is a bit out of date and I believe the JFS light is meant to stay steady/on when JFS is on regardless of whether it is being used to crank an engine. So the new behaviour is more correct.

The clickspot for the Aux radio is an interesting one. I’ll check whats going on there.