Regarding the panel night lighting, would it be possible for you to add a lightmap texture (using MultiplyBlendUserControlled emissive mode) to the radio panels so that we can paint the night lighting ourselves according to our gauge setups and have customisable lighting that doesn't need to be either all bright including bezels or all dark including screens. (so long as you don't mind working with DDS images, but if not it can just be left grey for a somewhat lit all over appearance.)

Regarding the panel night lighting, would it be possible for you to add a lightmap texture (using MultiplyBlendUserControlled emissive mode) to the radio panels so that we can paint the night lighting ourselves according to our gauge setups and have customisable lighting that doesn't need to be either all bright including bezels or all dark including screens. (so long as you don't mind working with DDS images, but if not it can just be left grey for a somewhat lit all over appearance.)

 

Will do, why not ... never tried MultiplyBlendUC ... but which value of grey would be best for this? Please advise.

 

OldAsDirt: When in doubt whether the AP is active use and check the button on the Yoke.

Will do, why not ... never tried MultiplyBlendUC ... but which value of grey would be best for this? Please advise.

For a simple all over glow maybe 40, if splitting bezels and screens I would use maybe 30/100. More advanced lightmaps be created by editing screenshots of the gauges, for example:

Right, used 40% of 256/white = 102. Model is called bt67_interior_DIY_allblank_MB (for MultiplyBlend). Same link as above.

 

Note, this is for testing the idea only. If it proves viable, we will have to assign the blank space to a separate VC section so that the other gauges of VC01 aren't affected.

 

The blank space can be used for placing all sorts of gauges, so it's difficult to anticipate what users would put there. So the "overall glow" would seem best.

 

The bezels are currently lit by the cabin light effect acting on VC_gauges.dds. I do not use a _night variant texture there.

What I meant was that the model would use an additional texture file for self illumination. There's a short article about it here: http://www.freeflightdesign.org/tutorials/FSX_Emissive_Textures_and_VCLighting.zip

Leaving this added texture grey would allow users to have the option of either having an overall glow, or to create their own lightmap texture appropriate to their setup.

OK Guys,

 

I am back and have been playing around with the BT .cfg files. I know... I know nothing about these things.

 

Anyway, I adjusted the GS numbers a little and have found that it will "lock on" with little regard for speed:

 

[autopilot]

 

autopilot_available= 1

 

flight_director_available= 1

 

default_vertical_speed= 500.0

 

autothrottle_available= 0

 

pitch_takeoff_ga=8.0

 

max_pitch=10.0

 

max_pitch_acceleration=1.0

 

max_pitch_velocity_lo_alt=2.0

 

max_pitch_velocity_hi_alt=1.5

 

max_pitch_velocity_lo_alt_breakpoint=5000.0

 

max_pitch_velocity_hi_alt_breakpoint=10000.0

 

max_bank=22.5 //25.0 adjusted to 2 min turn @130 KIAS

 

max_bank_acceleration=1.8

 

max_bank_velocity=3.00

 

max_throttle_rate=0.00

 

nav_proportional_control=15 //9.00

 

nav_integrator_control=0.10 //0.25

 

nav_derivative_control=0.00

 

nav_integrator_boundary=2.50

 

nav_derivative_boundary=0.00

 

gs_proportional_control=20 //15 //9.52

 

gs_integrator_control=0.50 //0.10 //0.26

 

gs_derivative_control=0.00

 

gs_integrator_boundary=2.50 //1.0 //0.5//0.7

 

gs_derivative_boundary=0.00

 

yaw_damper_gain = 1.0

 

autothrottle_arming_required=0

 

autothrottle_takeoff_ga=0

 

autothrottle_max_rpm=100.0

 

Looks like this:

 

 

 

By the way - I know the speed is way too high, but just wanted to illustrate that it doesn't seem to matter......

Update:

 

I dropped this one line back a notch as the engines tended to over-rev upon landing although AP was off. Don't know why, but it happened.

 

gs_integrator_boundary=2.50 //1.0 //0.5//0.7 to gs_integrator_boundary=1.0 //0.5 //0.7

 

Seems to correct it and everything else stayed the same.

 

John

John,

 

It looks like from your screenshots that you are still making your approach too fast. You are doing 130 KIAS. The manual that comes with the Basler says to fly your approach at 100 KIAS with 1/4 flaps. Your final approach speed should be about 80 KIAS aft setting 1/2 flaps. Once the runway set full flaps but maintain 80 KIAS until touchdown. Give this a try and see if it helps.

 

Bill

 

Agreed. It is sensitive to keeping the correct speeds during approach. Too much speed and you will find yourself above the GS which then causes the autopilot to increase the descent rate, which then will cause an even greater airspeed. You do have to stick with 1/4 flaps and 100 KIAS. Have to be careful not to get too slow or the opposite will happen, you will find yourself below the glideslope which will result result in a decreased descent rate, and even further decrease in airspeed. I don't think its a problem with the autopilot, some are more sensitive than others, its just a matter of following correct procedures.

What I meant was that the model would use an additional texture file for self illumination. There's a short article about it here: http://www.freefligh..._VCLighting.zip

Leaving this added texture grey would allow users to have the option of either having an overall glow, or to create their own lightmap texture appropriate to their setup.

 

I have got that tutorial, but miss your point. You want a different solution for the gauge polys or for the 3D VC objects, or both? I need more explicit instructions I am afraid.

 

Regarding the MultiplyBlend model in reply to your other post, does it work?

desbean,

 

Thanks. Yes, I agree. I was deliberately overspeed just to test and see if different settings would hold the slope and it appears that they do. Earlier, even when right on speed and trying hard to balance all, it seemed to drift. Now, I can generally come down right on target.

 

John

Just a quick question for the designers: do you have any particular restrictions or requests regarding the uploading of repaints done using the paintkit? Apart from the usual acknowledgments, of course. My RAF repaint is just about ready, I propose uploading it at Flightsim and maybe here at Avsim, if that's OK.

Just a quick question for the designers: do you have any particular restrictions or requests regarding the uploading of repaints done using the paintkit? Apart from the usual acknowledgments, of course. My RAF repaint is just about ready, I propose uploading it at Flightsim and maybe here at Avsim, if that's OK.

 

Go right ahead, no special permission needed. We are looking forward to your paint.

desbean,

 

Thanks. Yes, I agree. I was deliberately overspeed just to test and see if different settings would hold the slope and it appears that they do. Earlier, even when right on speed and trying hard to balance all, it seemed to drift. Now, I can generally come down right on target.

 

John

 

It does chase the GS up/down even at 80-100kias, especially with a full load. The frequent adjustments on my joystick throttle are a pain, because tiny movements result in rather large changes. I will try your adjustment.

My fictional RAF paint for the Basler is now finished. It is available here at Avsim and should be up soon at Flightsim also.

 

 

Your RAF looks really nice. Is the registration under the wing upside-down or is that the way a UK reistration appears?