creating smoother guages

[aobt14 0]

Hey everybody,

 

The main qualm I have with FS9 aircraft is that the gauges in the cockpit move in a jerky motion. In addition, they only move whenever I push my yoke a certain distance. In fsX, say the RealAir turbine duke, every movement I make on my yoke is immediately shown on the AI, Airspeed etc. I hate "guessing" how much I moved the aircraft and would much rather it show on the gauges themselves. Is there a way to fix this and/or a good turboprop aircraft that has smooth gauges? I love the PMDG Beech 1900 but again, it suffers from the lack of smooth gauges.

 

Thanks

[mebull 27]

 

Is there a way to fix this and/or a good turboprop aircraft that has smooth gauges?

 

The short answer is, . . . there is no short answer. All gauges basically reflect or affect what variables within the simulator read at any given moment. gauges that are already programed would be difficult or impossible and even illegal to change. That said, a gauge can be written so that it checks or changes the condition / value of a variable more or less often. The more often this 'polling' takes place the more computing resources are used. Very many of the ultra smooth gauges can affect performance. So, most are written in a way that tries for the happy median between clunky and very smooth. It is possible to modify a XML based gauge if you know how to program in XML and have the Cabdir SDK. As a final note, the smoothness or lack of it in a FS9 panel may also be related to other factors besides just the gauges.

 

Aeroworx KingAir 200; For FS9, a excellent and highly regarded turbo prop although probably not quite up the the Duke standards.

 

I hope this answers your question(s).

 

Regards,

Mel

[ematheson 19]

I usually don't fly turboprops in FS - not my style - but here is one you might look at. Although it is a bit tough on FPS, the gauges are smooth: The Carenado Cessna 208 for FS9.

 

There are MANY other aircraft in FS9 with smooth gauges (achieved through various methods, including coded directly into the model) and I could compile a good list of them for you, but there aren't many turboprops I could tell you about. Hope someone else can help better.

[Bert Pieke 7,584]

RealAir was one of the first companies to go to 3d gauges... the FS9 SF260 is an example.

 

Also the add-on gauges from Reality XP are smooth. 

 

You can put their JL2 gauges into the B1900 (!).

 

 

[aobt14 0]

Also the add-on gauges from Reality XP are smooth.

 

 

 

You can put their JL2 gauges into the B1900 (!).

 

I just purchased these gauges. After reading the manuals, I am totally lost on how to import them into my 1900C. In addition, when it automatically installed them into my Kingair, it put the JL2 into some of my AI aircraft. Obviously, this will decrease performance and because I don't know much about programming, I sent a tech request asking them to walk me through the install/uninstall process.

 

Thanks for the advice

[Bert Pieke 7,584]

I just purchased these gauges. After reading the manuals, I am totally lost on how to import them into my 1900C. In addition, when it automatically installed them into my Kingair, it put the JL2 into some of my AI aircraft. Obviously, this will decrease performance and because I don't know much about programming, I sent a tech request asking them to walk me through the install/uninstall process.

 

Thanks for the advice

 

Not sure the AI aircraft have a panel.. but if they do, you can edit their panel.cfg file and remove the JL2 gauges.

 

Here is the panel.cfg file from my B1900D

 

[Window00]

...

...

gauge22=RealityXP_JetLine2!EADI,  494,453,181,174

gauge23=RealityXP_JetLine2!EHSI,  494,630,181,176

...

gauge61=RealityXP_JetLine2!IC_RTU1,  774,372,19,18

 

//--------------------------------------------------------

[VCockpit01]

size_mm=512,512

pixel_size=512,512

texture=$DISPLAY1

background_color=1,1,1

visible=1

 

gauge00=KingAir!Pitot_Switch,  268,124,35,48

gauge01=KingAir!Vsi,  330,194,178

gauge02=KingAir!Altimeter,  322,3,183

gauge03=RealityXP_JetLine2!EADI,  3,4,249

gauge04=RealityXP_JetLine2!EHSI,  3,243,275

gauge05=KingAir!Turn_Coordinator,  403,388,104,105

gauge06=KingAir!Prop_Sync,  338,375,57,53

gauge07=KingAir!Master_Caution,  264,70,47,47

gauge08=KingAir!Master_Warning,  265,12,48,48

gauge09=KingAir!Prop_Sync_Spinner,  339,  452 ,55

 

...

 

[VCockpit07]

size_mm=512,512

pixel_size=512,512

texture=$DISPLAY7

background_color=0,0,0

 

 

gauge00=RealityXP_JetLine2!RTU,  0,0,496,440

 

 

If you need more help, send me a PM with details

 

 

[Bert Pieke 7,584]

OOPS, you said 1900C (not D)..

 

Here goes:

 

[Window00]

...

gauge37=PMDG_B1900C!B1900C_NavSwitcher,  726,918,77,42
gauge38=PMDG_B1900C!B1900C_PanelSwitcher,  717,443,106,54
//gauge39=PMDG_B1900C!B1900C_HSI,  536,689,165,166
gauge39=RealityXP_JetLine2!EHSI,  536,689,165,166
gauge40=KingAir!AutoFeather_Light,  817,933,28,25
gauge41=KingAir!Landing_Gear_Indicator,  1201,912,36,37
//gauge42=PMDG_B1900C!B1900C_ADI,  535,514,165
gauge42=RealityXP_JetLine2!EADI,  535,514,165
gauge43=PMDG_B1900C!B1900C_APInd,  532,454,169,54

 

[Window07]
Background_color=0,0,0
size_mm=645,122
window_size_ratio=0.732  
position=7
visible=1
ident=MINIPANEL
window_size= 1.000, 0.250
window_pos= 0.000, 0.753

gauge00=PMDG_B1900C!B1900C_Airspeed,  2,1,120
//gauge01=PMDG_B1900C!B1900C_ADI,  128,0,129,121
//gauge02=PMDG_B1900C!B1900C_HSI,  266,0,129,122
gauge01=RealityXP_JetLine2!EADI,  128,0,129,121
gauge02=RealityXP_JetLine2!EHSI,  266,0,129,121
gauge03=PMDG_B1900C!B1900C_Altimeter,  399,1,121
gauge04=PMDG_B1900C!B1900C_VSI,  525,1,118

 

//--------------------------------------------------------
[Window09]
file=..\panel\B1900C_Panel_Zoom.bmp
file_1024=B1900C_Panel_Zoom.bmp
size_mm=848,544
window_size_ratio=1.000  
position=6
visible=0
ident=10001
render_3d_window=0
window_size= 0.662, 0.571
window_pos= 0.000, 0.430

gauge00=PMDG_B1900C!B1900C_Airspeed,  276,193,169,170
//gauge01=PMDG_B1900C!B1900C_HSI,  457,338,204,204
gauge01=RealityXP_JetLine2!EHSI,  457,338,204,204
gauge02=PMDG_B1900C!B1900C_Altimeter,  673,100,169,169
gauge03=PMDG_B1900C!B1900C_VSI,  671,272,164,164
gauge04=PMDG_B1900C!B1900C_PanelSwitcher,  717,30,106,54
gauge05=Kingair!Rmi,  280,364,163,164,1
gauge06=Kingair!Dme,  673,442,167,81
gauge07=PMDG_B1900C!B1900C_FuelLuminosity,  0,329,253,218
//gauge08=PMDG_B1900C!B1900C_ADI,  457,127,198
gauge08=RealityXP_JetLine2!EADI,  457,127,198
gauge09=PMDG_B1900C!B1900C_APInd,  457,56,201,,2

 

//--------------------------------------------------------
[Window10]
Background_color=0,0,0
size_mm=200,125
window_size_ratio=1.000  
position=2
visible=0
ident=15233
window_size= 0.312, 0.260
window_pos= 0.694, 0.000

gauge00=RealityXP_JetLine2!RTU,  0,0,200,125


//--------------------------------------------------------
[Window11]
file=JetLine2Back.bmp
size_mm=234,237
window_size_ratio=1.000  
position=7
visible=0
ident=15231
window_size= 0.366, 0.494
window_pos= 0.134, 0.492

gauge00=RealityXP_JetLine2!EADI,  0,0,234,237

//--------------------------------------------------------
[Window12]
file=JetLine2Back.bmp
size_mm=234,237
window_size_ratio=1.000  
position=7
visible=0
ident=15232
window_size= 0.366, 0.494
window_pos= 0.500, 0.492

gauge00=RealityXP_JetLine2!EHSI,  0,0,234,237

 

//--------------------------------------------------------
[Vcockpit01]
...
gauge02=PMDG_B1900C!B1900C_VSI,  569,2,299,299
//gauge03=PMDG_B1900C!B1900C_HSI,  871,2,341,342
gauge03=RealityXP_JetLine2!EHSI,  871,2,341,342

...

//gauge39=PMDG_B1900C!B1900C_ADI,  1214,5,340,341
gauge39=RealityXP_JetLine2!EADI,  1214,5,340,341

 

Also, put the JetLine2Back.bmp file in the panel folder.

Last but not least, contents of the RXPJetline2.ini file, also in the panel folder:

 

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// Reality XP JetLine 2 Configuration File for PMDG Express B1900C
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

[settings]
VMO=247
RadAlt=-4.5
FDMode=CROSS
APTFILT_Type=H
APTFILT_Len=3000
CDI=ON
RTU1Pages=1,3,4
RTU1Com=1
RTUMaster=OFF
GEARWind=ON
SoundVolume=80
YokeAPDisco=ON
Screws=ON
EADIPopup=15231
EHSIPopup=15232
EHSIPopupalt=15233
RTU1Popup=15233
RTU2Popup=15233
PopupMaster=YES
ClearMain=NO
FDAvail=YES
RunwayGuide=ON
//SkyColor=0,101,150
//GndColor=175,81,41
NoFrame=OFF

[mebull 27]

As for the AI - just delete the panel folder for the AI aircraft involved. AI don't need or use one.

 

Mel

[aobt14 0]

As for the AI - just delete the panel folder for the AI aircraft involved. AI don't need or use one.

 

So I can delete all the panels in all my AI traffic?

 

For some reason, all of the AI airplanes are in the menu along will all the other aircraft and I can fly them. I am using My Traffic 2006. On a different note, how do I get the AI traffic out of the menu?

 

OOPS, you said 1900C (not D)..

 

Thank you for taking the time to post this. I got the gauges installed and can I just say WOW! Tremendous improvement. It's practically a new aircraft! I think I may purchase the regular gauges as well for airspeed, altimeter, vsi and turn coordinator. Would the reality XP 6-pack work for this? 

[Bert Pieke 7,584]

Thank you for taking the time to post this. I got the gauges installed and can I just say WOW! Tremendous improvement. It's practically a new aircraft! I think I may purchase the regular gauges as well for airspeed, altimeter, vsi and turn coordinator. Would the reality XP 6-pack work for this? 

 

You probably could replace the other gauges, but they are actually rather nice and typical for the aircraft..

 

I'd be inclined to leave them in place.. they add to the "Atmospherics"...

[mebull 27]

 

So I can delete all the panels in all my AI traffic?

For some reason, all of the AI airplanes are in the menu along will all the other aircraft and I can fly them. I am using My Traffic 2006. On a different note, how do I get the AI traffic out of the menu?

 

Yes you can delete the panel folders, also the in the corresponding AIs aircraft configuration file where each paint - [Fltsim.nnn] - may have a line such as panel=, make sure that entry is blank. And, . . . . to prevent the AI from being loaded into the aircraft selection menu which slows FS9 load up time, goto;

 

http://library.avsim.net/search.php?SearchTerm=AirEd&CatID=root&Go=Search

 

and download : aired152_update806.zip

 

Use that utility to open each aircrafts airfile. find the entry 'Aircraft Type= x' ,........if the aircraft is showing in the selection menu, that value will be 0, change it so the the line reads 'Aircraft Type=2, save and close, that aircraft will no longer show in the selection menu unless it is changed back to 0.

 

Regards,

Mel