Just double-klick the entry and toggle via click on the “PRESS”-Button and it’ll change to “RELEASE”.
Final translation to your setup should be:
ICP Drift C/O Switch - ON --> DX8
ICP Drift C/O Switch - NORM --> DX8 RELEASE, DX16 RELEASE
ICP Drift C/O Switch - WARN RESET --> DX16
cheers
Magic
@Thombalabomba
Do you have only “weapon release” mapped to your stick?
You need to map “second trigger detent” if you want to shoot your gun!
cheers
Magic
Well, i have an idea actually, just verfified it.
Go launch Falcon via AL with the ACMI button depressed.
Open TaskManager, go to Processes tab, enable Command line column (right-click on any column to get context menu), check the options in the commandline for “-acmi”.
If you don’t see the “-acmi” parameter, there’s something porked with AL.
If you do have “-acmi” in the commandline, there’s something wrong with Falcon.
cheers
Magic
Hey,
actually positive Mode IV reply means most of the time friendly (according to ID-matrix).
For hostile ID, lack of any IFF (spades) is usually not enough.
As tiag mentioned, it all depends on the ID-matrix which is layed out in the theater specific ROE.
And btw, you can NOT get a positive reply on all IFF modes. See what the different IFF modes mean.
Modes I, II & 3 are mainly for airspace control agencies which have a list of all flights/aircraft and their respective iff modes (ATO). So they can check if the mode I, II, III are correct. A fighter pilot doesn’t have that list or the time to check it.
cheers
Magic
Hi,
try adding “set g_nFontSize XY” in your Falcon BMS User.cfg. XY being 10 for me.
I think that’s what it does.
cheers
Magic
Hi,
i suggest you try the following mapping via AL to see if that helps:
I use a Vipergear ICPv2 and this mapping works like a charm.
For your stup that would translate to:
ICP Drift C/O Switch - ON --> DX8
ICP Drift C/O Switch - NORM --> DX8 RELEASE, DX? RELEASE
ICP Drift C/O Switch - WARN RESET --> DX?
You didn’t mention what WARN REEST position translates to regarding DX-button.
Hope this helps
Magic
how far away must the awacs be to not receive communications?
as mentioned earlier, around 200nm
with the IFF and the link16 it is possible to understand who our enemies and allies are, but only for air to air, while the same thing is not possible for the A/G: is it possible that there is no possibility of distinguishing also for the troops on the ground?
no AWACS = no ID via comms, no L16. so no, in your situation there is no way.
We also noticed that the reading of the aircraft speed that is highlighted on the MFD is very different from the real one. In this specific case we were traveling at 370kn, while the speed indicated on the MFD was below 350, is this normal?
on which MFD? and to what speed did you compare it? if you give more details i’m sure we can shed light into this one. many possibilities have been mentioned already.
cheers
Magic
You should NOT loose your keymappings.
They are saved as XML-files in your FalconBMS/user/config folder.
That’s how i backup my mappings, save all XML-files in that folder.
cheers
Magic
Hey,
isn’t https://maps.falcon-bms.com already serving this purpose?
cheers
Magic
It’s in your FalconBMS Setup.
Go to Setup >> Sound >> deactivate “Player Voice”.
cheers
Magic
Hey,
it would help immensely to get more details.
I can create/edit and run custom TEs with no problem.
Best would be to get the TE-file so people can have a look at it.
cheers
Magic
Hey,
isn’t https://maps.falcon-bms.com already serving this purpose?
cheers
Magic
how far away must the awacs be to not receive communications?
as mentioned earlier, around 200nm
with the IFF and the link16 it is possible to understand who our enemies and allies are, but only for air to air, while the same thing is not possible for the A/G: is it possible that there is no possibility of distinguishing also for the troops on the ground?
no AWACS = no ID via comms, no L16. so no, in your situation there is no way.
We also noticed that the reading of the aircraft speed that is highlighted on the MFD is very different from the real one. In this specific case we were traveling at 370kn, while the speed indicated on the MFD was below 350, is this normal?
on which MFD? and to what speed did you compare it? if you give more details i’m sure we can shed light into this one. many possibilities have been mentioned already.
cheers
Magic
Hi,
i don’t know of any mismatch between actual terrain and the TFR.
To judge the behaviour one would need an ACMI and the TFR settings used like ride type, cleareance, mode.
cheers
Magic
Hi,
please let us know which theater you are refering to.
Since you said “In KTO or Balkans it is there.”, i assume the problem is confined to a specific theater other than KTO.
Did you apply any other modifications apart from installing the 3rd party theater?
cheers
Magic
Hey,
actually positive Mode IV reply means most of the time friendly (according to ID-matrix).
For hostile ID, lack of any IFF (spades) is usually not enough.
As tiag mentioned, it all depends on the ID-matrix which is layed out in the theater specific ROE.
And btw, you can NOT get a positive reply on all IFF modes. See what the different IFF modes mean.
Modes I, II & 3 are mainly for airspace control agencies which have a list of all flights/aircraft and their respective iff modes (ATO). So they can check if the mode I, II, III are correct. A fighter pilot doesn’t have that list or the time to check it.
cheers
Magic
Ok guys, thx for the info directing to brakes overheat.
But then the published chart for accumulative brakes energy is wrong.
I checked our grossweight, wind and airspeed when brakes were apllied, according to the mentioned chart we are in the green area.
So why brakes overheat when in green area?
https://www.falcon-bms.com/articles/flight-model/changing-the-brakes-model/
cheers
Magic
Hi,
something like described here happened two times in MP to me(us) over the last few days.
In both cases we made a hotpit refuel.
First occasion:
Second Occasion
In both cases we had good landings, Also checked “brakes-chart” to be sure no overheat problem.
Tried to repro in SP, no luck.
cheers
Magic
Hi,
it looks like a DeviceSorting problem.
I highly recommend using the Alterative Launcher to map your Cougar & MFDs. It will take care of the DeviceSorting and is really easy to use.
cheers
Magic