AMI refuel over Korea

Love the new external lights implementation!

Hello,
here are some video tutorial in italian, maybe still useful to someone here too

Take off from Gioia del Colle: Linci passing by Linci

Hello everyone,

VIAF - Virtual Italian Air Force hosts public open sorties.

Next open flight is planned on 04.02.22 on Balkans Theater - Briefing 21:00 CET.

The initiative is not restricted to the italian BMS community. Welcome are groups and lone wolfs as well.

More info on our discord
https://discord.gg/ge8H8sYA

@dema Beautiful model and (of course) beautiful livery!

<p>@Jackal <br />from the answer I got, it seems that developers will not be opening new beta testing positions for now.</p>

Version
4.36.0 (x64)

Build
26181

Detailed Description
When landing at a place different from the original planned airbase, landing steerpoint (the last one of your flight plan) jumps autonomously to this new location.
As you can see on the video below, flight plan starts and ends at Suwon. Anyway if I land at different airbases youcan see that steerpoint 5 jumps from its original position to the position where I land. It seems there is a specific point along the runway that triggers this change.
First I touch and go on Seoul (no ATC interaction): steerpoint goes at Seoul location and reverts back once i’m back in the air.
Then I full stop at Kimpo. Steerpoint goes from Suwon to Kimpo and remain on Kimpo.
Exiting TE, UI map shows original flight plan.

Pictures

Seoul landing at 06:30, Kimpo landing at 12:30.

Example files
none

Crash logs
n.a.

Reproducibility Procedure

1. Put down a simple TE. In my case click on the map, choose Suwon as airbase for a new F-16 squadron. DCA mission, single ship, start at takeoff.
2. Fly out of home base and land at any airbase not comprised on your flight plan.

Expected Behavior
Flight plan should stay as it is unless you manually edit steerpoint coordinates.

Of course arresting gear is the first thing I had to try!
Again, thank you BMS Team!

To be honest, at first I was sure there was autolasing because I was seing my TGP automatically lase with a simple TMS-Up (i.e. ground stabylize lead to flashing L).

But then I noticed that in fact I was doing it wrong: my HOTAS (T16k) has separate buttons for first and second trigger detent.
The phisycal trigger is mapped as second detent, the one you press for cannon. This button causes also a stuck first detent (you need to press it at least one time, every next ground stabylize “remembers” that is pressed).

Lasing with the button mapped to the first detent works as described in the manual.

All this came from muscular memory from my previous HOTAS X-52 that has a dual stage trigger.

To be honest, at first I was sure there was autolasing because I was seing my TGP automatically lase with a simple TMS-Up (i.e. ground stabylize lead to flashing L).

But then I noticed that in fact I was doing it wrong: my HOTAS (T16k) has separate buttons for first and second trigger detent.
The phisycal trigger is mapped as second detent, the one you press for cannon. This button causes also a stuck first detent (you need to press it at least one time, every next ground stabylize “remembers” that is pressed).

Lasing with the button mapped to the first detent works as described in the manual.

All this came from muscular memory from my previous HOTAS X-52 that has a dual stage trigger.

@LorikEolmin I would first rule out problems on my side but I was sharing my cursor position and instead started a IFF interrogation. On a second attempt 1-2 seconds later worked as expected.

Is there a way to show on screen what button are you pressing and what callback is being recalled?
I am unsure about something similar that happened to me during our flight.

Hello,
here are some video tutorial in italian, maybe still useful to someone here too

Take off from Gioia del Colle: Linci passing by Linci

AMI refuel over Korea

@spooky wait do you mean different skins or just different tails?

Version
4.36.0 (x64)

Build
26181

Detailed Description
When landing at a place different from the original planned airbase, landing steerpoint (the last one of your flight plan) jumps autonomously to this new location.
As you can see on the video below, flight plan starts and ends at Suwon. Anyway if I land at different airbases youcan see that steerpoint 5 jumps from its original position to the position where I land. It seems there is a specific point along the runway that triggers this change.
First I touch and go on Seoul (no ATC interaction): steerpoint goes at Seoul location and reverts back once i’m back in the air.
Then I full stop at Kimpo. Steerpoint goes from Suwon to Kimpo and remain on Kimpo.
Exiting TE, UI map shows original flight plan.

Pictures

Seoul landing at 06:30, Kimpo landing at 12:30.

Example files
none

Crash logs
n.a.

Reproducibility Procedure

1. Put down a simple TE. In my case click on the map, choose Suwon as airbase for a new F-16 squadron. DCA mission, single ship, start at takeoff.
2. Fly out of home base and land at any airbase not comprised on your flight plan.

Expected Behavior
Flight plan should stay as it is unless you manually edit steerpoint coordinates.

Happened to me too but without proper documentation and due to the fact that I was not on KTO I didn’t report it. In previous versions was the alternate landing airport steerpoint that changed wenn asking awacs for alternate.

This time was the last regular steerpoint exactly how described.

Document: TO BMS1-F16CM-34-1-1
Page: 78
Original sentence: “The symbol on the HMCS is initially moved on the ground point with head movement Once the symbol is ground stabilized, it may be slewed.”
Corrected sentence: typo, a period is missing between the two senteces
“The symbol on the HMCS is initially moved on the ground point with head movement. Once the symbol is ground stabilized, it may be slewed.”

Page: 80
Original sentence: “The backup sensor can be accessed also from any OFF MFD page”
Corrected sentence:“The backup sensor can be accessed also from any A-G FCR MFD page”