Going a bit crazy with Eyefly.

A functioning Rate-of-Turn Indicator.

https://youtu.be/jJe9cfGu1ac?t=798

So, any flight you can walk away from is a good one?

Is it possible to have, in the UI, the steerpoints display the compass direction between them, negating the need for the Ruler to get headings?

Maybe I just need to reinstall 4.36 and U1 . . . . but I’m finding in Vipers other than the D, e.g. when I fly the CM-40, the light switches on the EXT LIGHTING panel do not rotate/cycle through all of the available settings like they do in the D.

Sweet!

Took me a couple weeks to get the hang of Boresighting.

@bohni said in Radio Message Colors: Hex Values Order?:

@Crassus
The manual reads:

A color code consists of four different values, in order: Alpha, Blue, Green and Red -> 0xAABBGGRR

So the order for RGBA is reversed in BMS.

But you’re right about the picture - Cyan should be 0XFFFFFF00

@b0bl00i, thanks for the reply.

I think I get what’s going on: I was reading this,

A color code consists of four different values, in order: Alpha, Blue, Green and Red -> 0xAABBGGRR

to mean the values as they exist outside of BMS, and I was taking

So the order for RGBA is reversed in BMS.

to mean the order we should be coding in.

Cheers!

@MaxWaldorf

I may have missed a couple (I went through all of the Vipers ) – here are the ones that don’t work:

F-16B-15
F-16C-32
F-16CM-40
F-16CM-42
F-16CM-50
F-16CM-52

Also, please take a look at these: F-16AM BAC / F-16AM RDAF / F-16AM RJAF / F-16AM RNDAF / F-16AM RNLAF:

The rotaries other POSITION switches work as they should, but the MASTER 3-position (COVERT-NORM-OFF) switch animates as follows:

• From OFF: Left-click goes to COVERT; right-click goes back to OFF.
• From COVERT: left-click 3x goes to NORM, then a right-click goes to back to COVERT instead of OFF, and 3 right-clicks from there go to OFF.
• From NORM: left-click has no effect; right-click goes to COVERT.

@freedomlike

I’m not going to admit how long it took me, but I will admit that the results in the screenshot aren’t always that consistent. I’m so focused on getting a successful kill with a Mav (focused too much on watching for a steady Weapon Pointing Cross on the WPN page, but not the range/ MLE) that I’m getting too close to AA.

I need to train more on actual employment.

@jc1

Have you tried using the default view keys: Left Shift + NumPad 8, 4, 6, and 2?

Hi, Frederf. Is this a bug, or normal functionality?

Is anyone else experiencing a cursor jump, for lack of a better title, of their TGP Cursor?

When trying to lock up a target in the TGP, I first have to deal with a “jump” of the cursor off of the SPI, and then I’m able to move the cursor to where I need it.

I’ve a couple of videos showing slewing the TGP Cursor in 4.36 and 4.35:

4.36
https://www.youtube.com/watch?v=xUP-7b4kkSU

4.35
https://www.youtube.com/watch?v=3YD3Ad_5pqA

My apologies to all who used their time to work on this.

@Mav-jp And I very much appreciate your help!

So after many uninstalls and re-installs to track down the causes of my *Formation Lights issue, I find it was due to my importing the CkptArt folders I’d backed-up from my 4.35 install (I have custom cockpit views set up in each of those variants I’d been having Lights issues with. )

On the off-chance I’m not the only one with the EXT Lighting issue, i.e. a bonehead, open up the 3dbuttons.dat file for the Block you’re flying. Scroll down to // Exterior Lighting.

Here’s what it looks like prior to 4.36:

// Exterior Lighting
SimAntiCollOn                    0.396671    1.181653   -2.339894    30    115    1
SimAntiCollOff                   0.396671    1.181653   -2.339894    30    115    2
SimLightsFlash                   0.303051    1.178091   -2.341300    30    115    1
SimLightsSteady                  0.303051    1.178091   -2.341300    30    115    2
SimWingLightBrt                  0.218657    1.163248   -2.352303    30    115    1
SimWingLightOff                  0.218657    1.163248   -2.352303    30    115    2
SimWingLightBrt                  0.114784    1.159700   -2.353764    30    115    1
SimWingLightOff                  0.114784    1.159700   -2.353764    30    115    2
//unused: Extl Form Inc          0.381256    1.065437   -2.357922    35    116    1    w
//unused: Extl Form Dec          0.381256    1.065437   -2.357922    35    116    2    w
SimExtlMasterNorm                0.264571    1.047735   -2.362698    30    115    1
SimExtlMasterOff                 0.264571    1.047735   -2.362698    30    115    2
//unused: Extl Aerial Inc        0.152837    1.063020   -2.377246    35    116    1    w
//unused: Extl Aerial Dec        0.152837    1.063020   -2.377246    35    116    2    w

Here’s the 4.36 upgrade:

// Exterior Lighting (New Panel)
SimStepAnticolModeDown           0.401000    1.176000   -2.321000    30    115    2    w
SimStepAnticolModeUp             0.401000    1.176000   -2.321000    30    115    1    w

SimLightsSteady                  0.303051    1.178091   -2.341300    30    115    2
SimLightsFlash                   0.303051    1.178091   -2.341300    30    115    1

SimWingLightDec                  0.218657    1.163248   -2.352303    30    115    2
SimWingLightInc                  0.218657    1.163248   -2.352303    30    115    1

SimFuselageLightDec              0.114784    1.159700   -2.353764    30    115    2
SimFuselageLightInc              0.114784    1.159700   -2.353764    30    115    1

SimStepFormationLightsUp         0.398000    1.049000   -2.345000    35    116    1    w
SimStepFormationLightsDown       0.398000    1.049000   -2.345000    35    116    2    w

SimExtlMasterDec                 0.264571    1.047735   -2.362698    30    115    2    w
SimExtlMasterInc                 0.264571    1.047735   -2.362698    30    115    1    w

SimStepAARLightsUp               0.137000    1.047000   -2.354000    35    116    1    w
SimStepAARLightsDown             0.137000    1.047000   -2.354000    35    116    2    w

@cougar56th

Weird.

I’ll try a fresh install of 4.36 and then U1, maybe that’ll fix it. Will report back later.

@UglyGrendel
I don’t have 4.36 in the vanilla Falcon 4.0 directory, though both are in a Games folder. That wouldn’t be an issue, would it?

@LorikEolmin

Is that Joe Satriani or Steve Vai shreddin’?

@Falcas

For 1 and 2, I’m loading a mission in the default KTO.

Are these the correctly-loaded parameters(?):

For # 3, I am making a feature request.

@Falcas

My apologies if you’ve addressed these already:

1. I just updated to Mission Commander 0.5.21 (and a fresh re-install of BMS 4.36 and U1) and got the following when first loading a mission.

2. I get this every time I Open a squadron:

3. Feature request:

a) Maybe I’m not seeing it’s already in MC, but is it possible to implement a bulk squadron move to a specific airbase, in addition to closest base?