@Korbi said in F-16 stick angled/offset?:
Be aware that the stick has a forward angle mounted on the stickbase indeed - BUT the base itself has a angle backwards, so the stick is pretty upright more or less.
Also the seat in the real cockpit is tilted backwards, the stickbase is tilted backwards (as you pointed out) and the stick is tilted forward. The reference for the stick angle should not be the ground but the seat.
@sungad
The issue with the cursor stuck at the bugged target is there since 4.35.
https://forum.falcon-bms.com/topic/21207/radar-cursor-in-crm-sam-mode
And since then I never came across a solution.
The advices are known (cursor speed = 100% and make sure that the cursor axis can provide full deflection) but they don’t help.
For me it takes a while to get the cursor off from the bugged target and select the 2nd target in SAM mode. If I can’t make it in time then I only engage a single target. TWS is no option any more.
We’re slowly getting familiar with the new missile behavior. However sometimes we see things in the ACMI that doesn’t seem to be right to our eyes.
Here are two things that happened just recently. Maybe you can have a look give us some feedback.
AIM-120C5 going after wrong targets:
We had a range presentation of 2x2 Mig-29. Jaguar51 picked up both contacts of the trail group in SAM mode (even if that was not the smartest decision :D). But the missiles actually went after the target that was locked by Jaguar53 at this point.
https://imgur.com/HLPbnKz
AIM-120C5 successfully avoids target:
Well… I don’t really know what to say about this. Maybe you have some words?
https://imgur.com/67Z9BQU
Full tape:
https://www.dropbox.com/s/sjt15i8ksl0ids5/2022-05-16_FE-ITO.zip.acmi?dl=0
Disclaimer:
This was recorded in ITO and we know that you probably don’t care for any issues here. But maybe it’s worth to have a look at it.
Asking the ITO dev’s if something is wrong with their AIM-120C5 doesn’t seem to make sense as they would probably refer back to you.
TO BMS 1F-16CM-34-1-1.pdf
Page 190/191:
“Note well: Flight models were comprehensively updated in 4.33 for many missiles, including the AIM-120B and AIM-120C, which now have very different characteristics. Experienced pilots will notice many missiles behave more realistically now. As a result the DLZ can be relied upon as a much more accurate trigger for offensive and defensive maneuvers; previously you often needed the target deep in the No Escape (Rtr) region in order to kill it. In simple terms, if you shot at Rpi the missile loss of energy at end game allowed targets to be head-on when the missile went active (Pitbull), turn away, accelerate while going low, out drag the missile for a good 30s and come out of it alive.
This also meant that Minimum Abort Ranges (see below) were not really critical and you could usually overshoot MAR without sweating too much. Hopefully, with the new missiles, this won’t happen and Minimum Abort Range will be critical again.”
This note can be removed.
We’re at 4.36 now and most of what is mentioned in the note is not valid any more.
The missile loss of energy at end game is incredible. The target just has to turn away, go low and light up the AB to evade a missle.
Instead add a reference to the training manual, where additional stuff (chapter 18.3.1 WEZ & co.) is explained.
@sobo-87
I heard some rumors that this will come in one of the next releases. 
@Mav-jp said in 4.36 FLCS improvements:
Absolutely no change a all i this area
Only things that changed are digital FLCS limited to 9.0G instead of 9.3g
No idea why noeone noticed this bug in 15 years lol
Because it was a feature to pull more than 9G. 
@kujo
They both look fine to me. But I don’t think that they both show the PW intake.
https://glomilstrat.blogspot.com/2017/07/the-two-types-of-intakes-on-f-16.html
@MaxWaldorf said in AIM 120:
@Bloodhound161 did you read the changelog?
It’s clearly mentioned
Is this what you call “clearly mentioned”?
From the change log:
“AA Missiles logic and homing radar logic completely reworked for better realism (Fox3)”
@airtex2019 said in Trim Reset:
But the real answer to your question is, install and use Alternative Launcher for modifying key bindings.
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases
I really would like to use AL again. But it doesn’t work with the Winwing throttle. So AL might be a good choice for you but definitely not for everyone.
@Frederf
Sorry but there is no cursor jump. The screen record is at 20 fps. The cursor moves without any jumps.
The issue is that the GM radar doesn’t update after selecting the FCR Mark page.
The work around for this issue is to go to the FCR Mark page first and the select the GM mode.
@Frederf
Here’s a screen recording of the feature/bug:
https://www.dropbox.com/s/mpi3d78ucmh4b2g/Video_2022-08-02_133916.mp4?dl=0
Edit:
All done in NAV mode. I didn’t try in AG or AA mode. But I expect the same there.
This behavior was introduced with 4.36.0.
@FireWind said in WinWing Orion 2 - Paddle Switch:
@Razor161 D8 (pressed) is supposed to temporarily disengage the autopilot and D7 (release) to engage it again…
The paddle switch is supposed to act as a paddle switch and the devs coded the behavior of the paddle switch. You simply map it to “STICK: PADDLE SWITCH”.
If you press the paddle switch then the auto pilot is temp. disenganged. If you release the paddle switch then the auto pilot is engaged again. There’s no need to fiddle with D7/8.
At least for me it works for years now. But maybe you’re right and I’m doing it wrong for years without noticing…
And as kouzi said… stop using AL until AL is able to handle the Winwing stuff. Instead I would suggest to read the technical manual if there’s something you can not map in the BMS settings.
@FireWind
Why do you need the key up event for the paddle switch? DX7 is fired as long as you hold the paddle. DX7 stops if you release it.
What action is intended when releasing the paddle?
@FireWind
That seems to be an issue with the alternative launcher. I have the same issue with my Winwing Orion throttle. AL is not able to somehow see all the switch positions.
On the Winwing device every switch positions is a key down event. It seems that the time between two key events is too short for AL.
In your case: the time between releasing DX7 and pressing DX8 is too short. AL does not see the next key event (DX8).
Since I don’t need to configure key up events I don’t really need the alternative launcher. I did my setup in the BMS settings.
@Mav-jp
If you mean this by analog…
https://www.thrustmaster.com/en-us/products/tpr-thrustmaster-pendular-rudder/
then you’re right.
@Mav-jp said in Nose wheel failure:
can you guys check in the setup advanced that your analog brakes are at zero when no input ?
They are at zero when I do not touch them. But they were not at zero when I was rolling into parking position and gently touched them to stop the aircraft.
I had the same thing in 4.36.1 at Gunsan when rolling into parking position. Weather was set to fair without fmap.
@sheref
Your 8010.dds and 8031.dds also need a rework. The rivets at the HMCS sensor look strange.