Lynnux

That's wrong ! Throttle - HOTAS Warthog.diff.lua: ["a3015cd8"] = { ["added"] = { [1] = { ["key"] = "JOY_RZ", }, }, ["name"] = "Radiator Flaps", }, . . . ["dnilp3014unilcd8vdnilvp-0.1vunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_D", }, }, ["name"] = "Radiator Flaps Close", }, ["dnilp3014unilcd8vdnilvp0.1vunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_U", }, }, ["name"] = "Radiator Flaps Open", }, JOY_RZ is the throttle lever for the second engine on the Warthog which was mechanically connected to the normal throttle, JOY_Z. Meaning, they had always the same position. This explains why the radiator flaps once were fully closed after landing but still there was one occasion when I reduced the throttle before diving and increased it afterwards and the flaps were fully closed. Still shouldn't happen. So it seems there is some interference between analogue and digital inputs for the radiator flaps. Question to the devs: Is there an "overflow" from fully opened to fully closed possible ? E.g. reducing the throttle, then opening the radiator flaps fully with digital inputs, then throttle up again... or reducing the throttle, closing the radiator flaps with digital inputs (which fully closed them) and then throttle up again (which didn't operate them for some reason). Concerning track files: I flew multiplayer (as usually I do) => track files too large. And they are highly unreliable: in most cases the replay is different and planes are often already crashing at take-off in the replay.

Joystick: default.lua: --GunSight EZ42 {combos = {{key = 'M'}}, down = device_commands.Button_14, cockpit_device_id = devices.EZ42_GUNSIGHT, value_down = 1.0, name = _('EZ42 Gunsight Gyro Power Switch'), category = _('EZ42 Gunsight')}, {combos = {{key = 'M', reformers = {'LCtrl','LWin'}}}, down = device_commands.Button_1, cockpit_device_id = devices.EZ42_GUNSIGHT, value_down = 1.0, name = _('EZ42 Gunsight Gyro Power Switch - On'), category = _('EZ42 Gunsight')}, {combos = {{key = 'M', reformers = {'LShift','LWin'}}}, down = device_commands.Button_1, cockpit_device_id = devices.EZ42_GUNSIGHT, value_down = 0.0, name = _('EZ42 Gunsight Gyro Power Switch - Off'), category = _('EZ42 Gunsight')}, {combos = {{key = 'N'}}, down = device_commands.Button_15, cockpit_device_id = devices.EZ42_GUNSIGHT, value_down = 1.0, name = _('EZ42 Gunsight Night Lens Filter'), category = _('EZ42 Gunsight')}, {combos = {{key = 'N', reformers = {'LCtrl','LWin'}}}, down = device_commands.Button_11, cockpit_device_id = devices.EZ42_GUNSIGHT, value_down = 1.0, name = _('EZ42 Gunsight Night Lens Filter - On'), category = _('EZ42 Gunsight')}, {combos = {{key = 'N', reformers = {'LShift','LWin'}}}, down = device_commands.Button_11, cockpit_device_id = devices.EZ42_GUNSIGHT, value_down = 0.0, name = _('EZ42 Gunsight Night Lens Filter - Off'), category = _('EZ42 Gunsight')}, {combos = {{key = 'O', reformers = {'RCtrl'}}}, pressed = device_commands.Button_6, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = -1.0, name = _('EZ42 Gunsight Brightness Control - CCW/Increase'), category = _('EZ42 Gunsight')}, {combos = {{key = 'O', reformers = {'RAlt'}}}, pressed = device_commands.Button_6, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = 1.0, name = _('EZ42 Gunsight Brightness Control - CW/Decrease'), category = _('EZ42 Gunsight')}, {combos = {{key = ','}}, pressed = device_commands.Button_10, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = 0.5, name = _('EZ42 Gunsight Target Wingspan Knob - CW/Increase'), category = _('EZ42 Gunsight')}, {combos = {{key = '/'}}, pressed = device_commands.Button_10, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = -0.5, name = _('EZ42 Gunsight Target Wingspan Knob - CCW/Decrease'), category = _('EZ42 Gunsight')}, {combos = {{key = ';'}}, pressed = device_commands.Button_16, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = 0.14, name = _('EZ42 Gunsight Target Distance Control (Throttle Twist Grip) - CW/Increase'), category = _('EZ42 Gunsight')}, {combos = {{key = '.'}}, pressed = device_commands.Button_16, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = -0.14, name = _('EZ42 Gunsight Target Distance Control (Throttle Twist Grip) - CCW/Decrease'), category = _('EZ42 Gunsight')}, {pressed = device_commands.Button_18, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = 0.2, name = _('EZ42 Gunsight Altitude Aiming Correction Adjusting Knob I - CW/Increase'), category = _('EZ42 Gunsight')}, {pressed = device_commands.Button_18, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = -0.2, name = _('EZ42 Gunsight Altitude Aiming Correction Adjusting Knob I - CCW/Decrease'), category = _('EZ42 Gunsight')}, Joystick - HOTAS Warthog.diff.lua: Added gunsight controls to joystick buttons. ["dnilp3010unilcd21vdnilvp-0.5vunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN13", }, }, ["name"] = "EZ42 Gunsight Target Wingspan Knob - CCW/Decrease", }, ["dnilp3010unilcd21vdnilvp0.5vunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN11", }, }, ["name"] = "EZ42 Gunsight Target Wingspan Knob - CW/Increase", }, ["dnilp3016unilcd21vdnilvp-0.14vunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN14", }, }, ["name"] = "EZ42 Gunsight Target Distance Control (Throttle Twist Grip) - CCW/Decrease", }, ["dnilp3016unilcd21vdnilvp0.14vunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN12", }, }, ["name"] = "EZ42 Gunsight Target Distance Control (Throttle Twist Grip) - CW/Increase", }, No gunsight-related settings on the throttle. I tried those joystick buttons but no success. Will take a closer look to this in the next trial What I noticed when looking into default.lua are the clock settings are obviously taken from the 109, but this may be ok (scroll right to see the names): --Clock {combos = {{key = 'W', reformers = {'RShift'}}}, down = device_commands.Button_8, up = device_commands.Button_8, cockpit_device_id = devices.CLOCK, value_down = 1.0, value_up = 0.0, name = _('Input.Bf109K4.clock_stopwatch'), category = _('Clock')}, {combos = {{key = 'W', reformers = {'RAlt'}}}, down = device_commands.Button_6, cockpit_device_id = devices.CLOCK, value_down = 1.0, name = _('Input.Bf109K4.clock_stop_1'), category = _('Clock')}, {combos = {{key = 'W', reformers = {'RCtrl'}}}, down = device_commands.Button_6, cockpit_device_id = devices.CLOCK, value_down = 0.0, name = _('Input.Bf109K4.clock_stop_0'), category = _('Clock')}, { down = device_commands.Button_7, cockpit_device_id = devices.CLOCK, value_down = 1.0, name = _('Input.Bf109K4.clock_stop'), category = _('Clock')}, {combos = {{key = 'W', reformers = {'RAlt','RCtrl'}}}, pressed = device_commands.Button_2, cockpit_device_id = devices.CLOCK, value_pressed = 1.0, name = _('Input.Bf109K4.clock_scale_plus'), category = _('Clock')}, {combos = {{key = 'W', reformers = {'RAlt','RShift'}}}, pressed = device_commands.Button_2, cockpit_device_id = devices.CLOCK, value_pressed = -1.0, name = _('Input.Bf109K4.clock_scale_minus'), category = _('Clock')}, { pressed = device_commands.Button_5, cockpit_device_id = devices.CLOCK, value_pressed = -1.0, name = _('Input.Bf109K4.clock_pinion_minus'), category = _('Clock')}, { pressed = device_commands.Button_5, cockpit_device_id = devices.CLOCK, value_pressed = 1.0, name = _('Input.Bf109K4.clock_pinion_plus'), category = _('Clock')}, }, }

(August 2022 trial) On three occasions the radiator flaps fully closed without operating them, despite they were fully opened. I didn't bind any analogue control to the radiator flaps (there was an old bug report related to the analogue input), just digital throttle inputs. This one is a bit annoying since the engine is now overheating quite fast with fully closed flaps (and subsequently dying if you don't notice that immediately).

(August 2022 trial period) I never saw the circle of the gunsight. Didn't bind any analogue input. Only bound the range setting keys but it didn't help (gyro on/off also no influence) Maybe this is a known setting issue or some wrong settings in a .lua file but I didn't find this issue in a bug report.

Do you mean with APP mode that you land on autopilot or just manually with the HUD being in APP ? If you didn't try it yet: Do a landing on autopilot and the throttle should be fine. At least it is for me. After switching off the AP the nose will drop and you have to compensate. "Overreacting" here causes speed loss which you have to also compensate => landing more instable... With all the recent changes of the flight model, FCS, engine, reaction on turbolences near the ground etc. the Mirage controls feel more sensitive than 1.5 years ago, when the Mirage was "rock stable". But we will get used to it

Obviously the tanker is acting like a flare in this case but should the missile launch at all when a deviation to the radar target is detected ? Or at least the symbology and target on the HUD should change ?

Locked an enemy plane via boresight mode and assigned the IR missile to the radar target. The triangle appeared (= IR missile locked, flew a Mirage 2000). The plane was flying level from right to left. and turned into me. I launched the missile at 1.75 nm distance. The enemy plane didn't drop a flare. The missile immediately went after a friendly KC-135 which was passing from left to right behind the enemy plane (exactly the opposite direction, a little bit higher on the HUD). The distance of the KC-135 was 8 nm at this moment. The cockpit view shows the situation at the moment of the missile launch. The satellite view shows the missile flight path. Happened also with a PL-5EII in a pretty similar situation, the PL-5EII was also assigned and locked to an enemy radar target but switched to a friendly passing behind. Also here the enemy plane didn't drop a flare. How can a missile which is assigned and locked to a target via radar simply switch to another target at launch (friendlies in both cases) ?

We remember the times when there was a perpetuum mobile installed in front of the MiG-29, building up energy on every rebound until the nose of the MiG finally went up vertically. Just had the same effect with the tailwheel of the 190A. Likewise, the plane finally assumed a vertical position: Was the first time I've experienced this. The plane was damaged, maybe this contributed to the behaviour. Happened on multiplayer server.

Not really. ... I guess what he meant is that the Bo-105 is the only helicopter that is approved for aerobatics. So basically there is only the Bo-105 for civilians like Red Bull to do this.

You can be pretty successful, though, if the circumstances work in your favor. One of my very rare multiplayer missions on the Storm of War server, there was an allied bomber formation incoming. 8 bombers, altitude 8km. Got 5 of them and one P-47 in between. Wasn't alone, of course. Initially there was a friendly 109, later there were two more. One of them tangled with a Spit, keeping it away from us. If you're going against air targets, take the mineshell (anti-bomber) ammunition and remove the bomb mount. Don't attack the bombers from the rear. Only the last one you can attack from the rear because you'll be damaged for sure.

Haha, nice ! We are experiencing a community of faith here trying to find and produce evidence that the F-16 is better in a dogfight than the "F-16 on steroids". Can the F-16 beat the "F-16 on steroids" in a dogfight ? Yes Is this the rule or the exception ? Exception Remark: "F-16 on steroids" is a term for the Typhoon used by a british fighter pilot who flew both types (F-16 as exchange pilot).

What does "faulty server connection (bad Wi-Fi)" mean ? Is it a problem on the MP server side ? Or was it on your (client) side ? Ping is no big issue, I've played on Australian servers with 250 ms ping and the game was running surprisingly smooth (and stable).

Riddle solved: I never considered that the LS-6 also has an alignment time. By rushing to the targets to keep the track-file as short as possible the alignment was not finished, resulting in the deviation. The target area is close to the airfield, so this obviously happened also before. Did a short test to confirm: rushed to the targets, dropped to LS-6s while still aligning. Both missed. Waited for the alignment of the remaining two bombs before dropping them => both were accurate. What remains is the not considered drift of the GB-6 submunition due to the wind but that's the same issue as for the Viggen BK90.

The LS-6 deviations are a strange one: The MP server I'm playing on cycles between 3 missions. 3 days ago pre-planned LS-6 were not hitting targets. In the same mission 1 day later all pre-planned LS-6s were accurate. When the LS-6s are not hitting, the deviation is random, i.e. not drift due to the wind. When watching them I sometimes saw the the last second before impact they suddenly bank and turn away from the target but that's not always the case when they are missing. Investigation to be continued but will be paused for 3 weeks... Oh, and something else you likely already got reported because it's a very old behaviour: When the first bomb is released in pre-planned mode the target in all previously set up programs A/S1..6 are reset to PP1 (channel 36). Don't know if this is "normal" but for a real pilot in combat this would be pretty inconvenient.

When a player is joining the server there is lag for 1..2 seconds. Never had such an obvious impact from players joining the server. But I can't tell exactly which patch introduced the behaviour but it was 2.7.12.23362 (28. April) or later.

To be more specific: Effective range when launched at 30000 feet: ca. 20 nm Missiles launched at 30000 feet at a distance of 25.4 nm (47 km) didn't reach the target. When launched from this range they act more like TIALDS just soaking the missiles out of SAMs since they are also very slow then. But the ones not reaching the target were not shot down, just to avoid misunderstandings. Btw. launched from 30000 feet the range of the GB-6 is higher than that of the LD-10... One reason for the lower range is that the missiles don't loft anymore. I think before the change they behaved like an AGM-88.

The GB-6 deviation on multiplayer looks like it's caused by the wind.

No there are no drift settings like for the Mirage. Tried AGM-154s in pre-planned mode and they are accurate, just for comparison.

No drift but I have to check that and flight to target was short. The behaviour looks similar to that of the BK90 of the Viggen. Have the glide bombs been changed in recent patches ? Is drift switched on/off in the options ?

No, MP track is 27 MB, even if I keep the mission short. Maybe on a different server where the plane is spawned hot but even then it may be too much.

Yes, I have to "take the helmet off", too. Had to lower the cockpit sound volume to have approx. the same volume as with the helmet but I hear my plane being hit now.

In multiplayer the LS-6 and also GB-6 are inaccurate in pre-planned mode (PP1...4 on F10 map) rendering the LS-6 useless in this mode. In single player the weapons are accurate in pre-planned mode. In TOO mode (target via TGP) the weapons are accurate in both single and multiplayer. HNS: INS+GPS INS calibration: GC (long, high accuracy) The issue was introduced in one of the recent patches.

I remember it working well in March/April. Used pre-planned mode with azimuth setting and it was ok. Some recent patch broke it, currently the LS-6 doesn't hit targets in pre-planned mode. Didn't find anything in the update notes...

Will try that since the bug is back again. @Flappie Is the autoexec.cfg still valid for the current version ? (2.7.14.24228)

Something like that ? Just found it on YT...