New! Freeware Dassault Falcon 20E

[rotorhub]

Well I thoroughly enjoyed version 1.0 while it lasted!

Sorry about the rookie mistakes There were no big issues for P3D users. The biggest issue was the black VC for FSX users, that needed new interior models/material.

The panel cfg had some broken references due to a "find and replace" accident There are also two new gauges (Cabin alt and Cabin pressure), and a fix to the Cabin Altitude Warning. Thanks mpni, it was a syntax error.
The other stuff you is already known to you.

Rotorhub

 

[simtech]

Fuzzy Paint

Rotorhub,, thank you for this neat airplane. Unfortunately, I'm having the issue of blurry texures. In the texture folder, the thumbnail looks great, but when I call the airplane up in the selection menu, it's blurry, can't read the tail numbers. This is how it appears in FSX-A. I checked in fsx.cfg and max tex is 1024, the gauges are all clear and sharp inside. It's only the outside view. I d/l your V1 + the update you had in the drop box and all textures were .dds. What am I doing wrong? Any ideas..?? I'd like to make this puppy happy... Again thank you for your gift... Terry

 

[mpni]

You right, no big issues for P3D users.
But now, everything is perfect with P3Dv4. No mistake.
Nice work

 

[fsafranek]

I'm confused. The thread title says Falcon 20 (as in Dassault Falcon 20 I'm assuming) but a paint request shows images of a Gulfstream
and an inflight image is of a Falcon 50? I guess I should follow the link to avsim and see exactly what the original poster was referring to.


Okay, sorted it. The Gulfstream is an admitted fictitious paint request. And the Falcon 50 is, well, a Falcon.

 

[MrZippy]

First point A to Point B flight with the new download was a success! I did notice the oil temp in the 2D cockpit was always in the red! Other than that, all was good

 

[expat]

And the Falcon 50 is, well, a Falcon.

Yeah, and it's a dandy one Frank - as someone who knows his way 'round Dassualt's . .

 

[rotorhub]

Oil temp 2D panel

First point A to Point B flight with the new download was a success! I did notice the oil temp in the 2D cockpit was always in the red! Other than that, all was good

I did not make any changes to the Learjet gauges and 2D panel. The learjet probably have a different temp setting. The VC gauge should be correct. Oil temp is set from the Falcon 20 manual that I have. Published values in Celsius are converted to Rankine and inserted into the airfile.
Rotorhub

 

[rotorhub]

Rotorhub,, thank you for this neat airplane. Unfortunately, I'm having the issue of blurry texures. In the texture folder, the thumbnail looks great, but when I call the airplane up in the selection menu, it's blurry, can't read the tail numbers. This is how it appears in FSX-A. I checked in fsx.cfg and max tex is 1024, the gauges are all clear and sharp inside. It's only the outside view. I d/l your V1 + the update you had in the drop box and all textures were .dds. What am I doing wrong? Any ideas..?? I'd like to make this puppy happy... Again thank you for your gift... Terry

I you know how to edit your FSX.cfg file, just change "Max Texture Load" setting from 1024 to 2048. The default Falcon 20 textures are 2048 px.
Hope it works for you! Update the Falcon 20 to version 1.1, to get all the bug fixes.

Rotorhub

 

[simtech]

Rotorhub,... Thank you for the heads up. It took a few moments to edit the cfg.. seems the sliders always overwrite the cfg upon loading. Anyway, found the magic spot and the textures show up very well now.. Thank you for a delightful airplane...

 

[falcon409]

Rotorhub,... Thank you for the heads up. It took a few moments to edit the cfg.. seems the sliders always overwrite the cfg upon loading. Anyway, found the magic spot and the textures show up very well now.. Thank you for a delightful airplane...

One thing to remember also is that if you make any changes that affect the FSX config file, that 2048 setting will revert back to 1024. As long as you don't do anything to change a setting that is written to the cfg file you're safe, but if you do you'll have to reset that TextureMaxLoad setting back to 2048.

You might want to check out a little utility called Texture_Max_Load_Editor, which sets the correct setting and then maintains that setting no matter what other changes are made to the FSX.cfg file. . .pretty handy.

 

[simtech]

Ed, thank you for the info. I had the TML at one time. I'll see if I can pull it out. If it went back to 1024, I'd be ok.. but it goes back to 128... That's pretty basic..
I'll try and dig out TML.. Thank you.. Ok, found it... It's now installed. The old noggin needed stirring.. I'd forgotten I had that...Thank you..

 

[falcon409]

Ed, thank you for the info. I had the TML at one time. I'll see if I can pull it out. If it went back to 1024, I'd be ok.. but it goes back to 128... That's pretty basic..
I'll try and dig out TML.. Thank you.. Ok, found it... It's now installed. The old noggin needed stirring.. I'd forgotten I had that...Thank you..

I'm surprised that yours defaults to such a low setting. . .it should default no lower than 256 (which by todays standards shouldn't even be allowed, lol), but at least the TML Editor will keep everything looking as sharp as possible.

 

[gaab]

Hi Rotorhub,

If you dont like the Falcon 20E, there is no need to tell me. Just remove it from your hard drive.
It was free!

and if I like it, can I tell you

One question please, P3D V4 is complaining about visual effect "L_Light" missing. Any suggestion to assign another effect in the aircraft.cfg for the landing lights ?

And yes, I like it very much.

Gérard

 

[MrZippy]

Good find on the landing light effect. I didn't see it in my effects folder for FSX. I just inserted a Shockwave effect and will test!

Plenty bright now!

 

[TiAr]

Exactly 40 years ago I caught the real D-CONU in Stuttgart EDDS during its approach to runway 25 with my first camera, a Zeiss Ikon. I was a boy 15 years old. Nice, that the model is now available in P3DV4.3.

Thomas

 

[Hamza Omar]

Is a paint-kit also available for this wonderful aircraft. There are a couple of Pakistani schemes I had in mind

 

[expat]

I just inserted a Shockwave effect and will test!

Have to do more testing but I am getting mixed results with shockwave lights in 64 bit. Landing lights are visible - for me - but just little teeny faint points of light when looking straight at them. Elevating the a/c above the runway does cast a good amount of flooding on the pavement however. But nowhere near the dramatic effect of the landing light looking at it directly. No splash on the fuselage either.

However, your screenie shows the landing lights the way they should be. I need to test maybe with dynamic lighting turned off?

Have been testing with both the Falcon 20 and 50. What is really surprising is I cannot get any effect at all from shockwave strobes - beacons and navs seem OK.

 

[expat]

Further testing completed. Learned that it helps to also migrate across shockwave effects/texture files​ - all working better now!

 

[mpni]

Hi Rotorhub
I confirm that L_Light.fx is missing.
Best regards

 

[expat]

What then are the "fx_landing" entries for?

[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0 =3, -35.197000, -26.519000, -2.368000, fx_navredm
light.1 =3, -35.197000, 26.519000, -2.368000, fx_navgrem
light.2 =3, -56.670000, 0.000000, 10.320000, fx_navwhi
light.3 =1, -24.000000, 0.000000, -4.253000, fx_beaconb
light.4 =2, -51.850000, 0.000000, 10.980000, fx_strobe
light.5 =1, -51.830000, 0.000000, 10.920000, fx_beaconh
//light.6 = 5, -18.7, -2.7, -3.71, fx_landing ,
//light.7 = 5, -18.7, 2.7, -3.71, fx_landing ,
light.8 =4, -9.2.000000, 0.000000, 1.000000, fx_vclight
//light.9 =4, -8.5.000000, -1.200000, 1.000000, fx_vclight
light.10 =5, -25.000000, -3.150000, -3.950000, L_Light
light.11 =5, -25.000000, 3.150000, -3.950000, L_Light