StringBean

Just because a gauge tells you some info does not assure that it is telling you the correct info. You seem to have two gauges confirming windspeed and direction... Taking off with a 7 knot tailwind is acceptable and common in the sim (and the real world) where calm wind runway assignment is usually the runway closest to pointing North. peace, the Bean

That is an old version of DXTBmp. Step one would be to get the newest version and try with that. http://www.mwgfx.co.uk/index.htm peace, the Bean

It is on the prop texture sheet. peace, the Bean

Did you intend to say "With a backcourse approach you never have a glideslope"? Because that is a true statement. You most certainly can have DME on backcourse approach. Also, there is no way in the sim to differentiate between a CAT1, CAT2, or CAT3 approach. peace, the Bean

Did you try turning off aircraft shadows? peace, the Bean

It might also help to know if you are using FSX boxed or Steam.

I guess what I should have said was... With a constant speed prop, engine revs are not as directly connected to prop revs as they are with a fixed pitch prop. The point I was trying to make was that with a CS prop we use separate gauges for prop speed and power setting. As opposed to a FP prop where a single gauge, like a tachometer, will suffice. peace, the Bean

The gas generator spins in the neighborhood of 10 times faster than the prop. Think of the NG gauge as the turboprop's version of the manifold pressure gauge of a piston engine. They are both used to monitor engine power output. With a constant speed prop, engine revs are not directly connected to prop revs, which is why we want gauges to monitor both. peace, the Bean

Nice guess except that gauge is not measuring force, it is measuring revs as a percentage. N literally equals number. peace, the Bean

From- https://en.wikipedia.org/wiki/Variable_(mathematics)

try moving your scrape points above your float points. peace, the Bean

Was not asking you, it's relevance is for me to decide. According to the FSX SDK... There is no reference to "water splash" in the SDK pertaining to contact points. Also, ever heard of Spellchecker?

Why the mismatch? peace the Beean

If Karol's numbers do not work, try these.... gauge02=A380_PA_Gauges_VC!digital_trim, 125,261,130,75 Let us know. peace, the Bean

You are creating a Window that is 281 pixels wide and 353 pixels tall. You are then adding gauges that have the top, left corner of the gauge 415, 441, and 655 pixels down from the top. Your gauges are being placed outside of the Window. FSX will not tolerate this, IIRC FS9 did. Try this... //-------------PRIMARY FLIGHT DISPLAY------------------------------- [Window02] Background_color=0,0,0 size_mm= 281, 353 position=0 visible=0 ident=500 //window_size= 0.600, 0.740 // CUSTOM BDP //window_pos= 0.260, 0.390 //CUSTOM BDP gauge00=A380_PA_Gauges_2D!background, 0,0,281,353 gauge01=A380_PA_Gauges_VC!pfd, 26,26,229,289 gauge02=A380_PA_Gauges_VC!digital_trim, 26,26,130,75

Of course I remember because I understand what all those numbers mean and do. The "border", or Window size is determined by... size_mm= 281, 353 ...which creates a Window 281 pixels wide by 353 pixels tall. This line... gauge00=A380_PA_Gauges_2D!background, 0,0,281,353 ...places that gauge in that Window and places it's top left corner 0 pixels in from the left and 0 pixels down from the top of that Window. It also scales that gauge to be 281 pixels wide by 353 pixels tall thereby filling the Window from edge to edge and top to bottom (which is what you want). These lines... window_size= 0.600, 0.740 window_pos= 0.260, 0.390 ...scale that Window (and all gauges in it) to cover 60% of the width of your monitor and 74% of the height. The top left corner of that Window will be placed 26% of the way across your monitor, from the left, and 39% down. So, comment out these two lines... //window_size= 0.600, 0.740 //window_pos= 0.260, 0.390 ...and test. The gauge should fill the Window with no extra "border". Then remove the comments... window_size= 0.600, 0.740 window_pos= 0.260, 0.390 ...and tweak those values to get desired results. peace, the Bean

OK, try this... size_mm=341, 353 ...and... gauge01=A32X!popup_pfd_mfd_screen_bezel, 0,0,341,353 gauge02=A32X!A_PFD, 26,26,289,289 peace, the Bean

That is not compiling, that is saving. There is a difference in ADE. peace, the Bean

Parking brake on a skid equipped helicopter???

Due respect, if you had FSX-SE you would have spent the last 2 days flying. Just saying. peace, the bean

VC?

That is a band aid that fixes the symptom, not the problem. What the OP is seeing is a result of missing textures. When FSX, in DX10 mode, cannot find a texture being called by the model it will substitute a file named bkg.bmp (which can be found in the root FSX folder) for the missing texture. The cause of the OP's problem is that he is missing either the bump or spec (or both) textures. An easy fix is to place a copy of the texture.cfg in the folder containing the new livery. Just copy it from one of the other texture folders for that plane. peace, the Bean Sorry, this is not for the OP, it is for WarIsa92

Did you try FSRecorder after you ran the installers? The working SimConnect.dll files are not what you see in the SDK folders. SimConnect is not like a gauge that simply needs to be placed in the correct folder to work. It is, in essence, a part of Windows. This is from 64 bit Win 7... Red arrow, top left, shows this is from a search for simconnect in C:\Windows\winsxs Red circles show the misleading version numbers that also can be found in the SDK folder. However, if you check the file properties for the .dll files you will find what is circled in green. Unless you are color blind. peace, the Bean

In each of those folders (RTM, SP1, XPACK) is an .msi file. This is the installer that you need to run to install the legacy SimConnects. Until you run the installer you will be dead in the water. Disregard the version numbers you are seeing, run the installers. Might as well run all 3. peace, the Bean

These are the 3 versions that come with Boxed w/Acceleration or SP2... As can plainly be seen, the version you are needing is the SP1 version. Regardless of whether you have it on your computer, I suggest it is not installed properly. Or FSRecorder is not Steam compatible, that I do not know. peace, the Bean