@Faucon Sorry but this is not how bug reporting works.

Repro means constantly reproduceable steps to demonstrate the bug.

A video or tacview would assist in eliminating a range of factors for further investion to begin. If you are unwilling to help us, help you - then my hands are tied as I am busy doing a million other things.

I refer you to this post: https://forum.falcon-bms.com/topic/14576/how-to-make-a-bug-report

@hiuuz It’s worth that wait

@gankailer verify they are using the ICP BRT knob, not the CONT knob on the ICP to project the image.

@airtex2019

Thanks Mate!

Worked like a treat.

🙂

@SOBO-87 said in TFR and terrain mis-match?:

@Tiger-0 Different weather on the second attempt?

Same weather. It’s a TE with good weather.

@DanielTheFox for log files / crash dumps

check in your \Falcon BMS 4.37\User\Logs directory

@Atlas - I know that in a RL Trainer I adjust the seat quite a bit during a session as I fly…and in the WRONG direction 180 out as to how a RL pilot would do/does it, so I’ve come to be told…

…I once knew a pilot that would run his seat full down to refuel…never understood why, other than with probe and drogue there could be a chance of shattering the windscreen during a plug. So it’s cool that BMS at least models the ability.

@razo Thanks, I’ll try that!

@windnc60 lol yeah that Nvidia control panel is the worst

makes no use of modern UI frameworks and libraries designed to adapt to different screen sizes and dpi … but it’s probably the one UI that needs it most!

thanks

this one has been fixed already, check next release

@white_fang said in Flares on takeoff:

@Ironman53rd said in Flares on takeoff:

MAV-jp

It may be that the trigger for flare release is being painted by friendly Radar ?

Ironman

Even by the friendly radar, YES. AI is constantly doing that since … huuh, 4.35/36 ? … but , for some/long time.

When spiked they’ll do that, drop CM’s, but only if attacked they’ll do evasive actions.

Once, my wingman (idiot) , was spiked by SA-19 at 34000ft , dropped flare/chaff and dived for evasion to some 10-15000ft … and guess what , they nailed him. … QUIT

Good remark , we need to check altitude engagement range in the AI décision routine. Duely noted

@jayb said in Hook is not fully retracted:

@Mav-jp said in Hook is not fully retracted:

@Tiger-0 said in Hook is not fully retracted:

@Mav-jp said in Hook is not fully retracted:

not a bug, thats a feature

the hook is spring mounted, you can’t retract it from the cockpit alone

I could at some point code a ground crew to reload like the Jfs

That would be sweet. The use case would be if we had done a FARP landing to refuel and during landing used the hook. Then get the hook restored to its original state for the remaining part of the mission

That hook is not make for this. Hook is an emergency device.
After such a stop, the airframe and équipements needs maintenance.
The same way you don’t use the ejection seat to go out the plane rapidly to go to the toilet, arrestor is not made to allow normal ops on short runways.

@Icarus Hey bro, great to see you again. We have to catch up on the discord. Thanks again for your help.

@hoover said in Planes spawning in super late:

progressively harder opponents

Honestly, the difficulty is fluctuating rather than continuously getting harder, though I’m talking from the perspective of someone who memorised the pattern quite well.

Wave 2 (4x Su-25, 3x MiG-19, 3x MiG-21) is a huge difficulty spike, as you face an extremely large number of aircraft spawning very close. It’s near impossible to get all of them before the merge and I think even the Su-25s can kill you.

The other difficulty spike is wave 7 (2x MiG-25, 4x MiG-23). The -23s are quite close and in vertically stacked pairs and you have to react very quickly to get them before they shoot you. Even if you win, you might see an AA-7 or two fly just over your cockpit. The other problem is that the MiG-25s from the previous wave might be still around and potentially quite close. In the previous round (2x MiG-25, 5x MiG-23), the -23s are flying away from you and if you take you time to deal with them, the timer for the next wave might run out before you’re finished with the -25s. Oh, and the -25s are already tricky on their own, as your AMRAAMs perform very poorly at 50k ft, even if you’re really deep inside R_tr.

@airtex2019 said in Possible intra-flight comm issue:

Were they not greyed out, in your case? (You were actually able to issue comms to “flight”?) That may be a small bug. Hard to repro, obviously… but plausible.

I use VoiceAttack to issue intra-flight comms, so I didn’t notice. Now that you say that, I should have used the keyboard to check during the flight, but I didn’t think of it.

@MaxWaldorf That’s probably that, netbios doesn’t support blank, so the system must have truncate the name before the space, resulting in the same name.

I have a physical rotary switch for this wired onto a Bodnar BBI-64 so the callbacks are mapped to DirectX.

The switch is left at the NORM position but when starting in the air (AAR TE), the in-cockpit switch goes to the RAM position so I have to rotate the switch out of the NORM position and then back to get it in the correct setting. All my other DX-mapped controls “sync” with how the physical controls are set up on jet start. Is there any reason the Air Source is different?

@airtex2019

Ok, thanks. Matches my perception. Was just asking, whether an AVTR active status indication in the cockpit is still desirable.