Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
http://www.sim-outhouse.com/sohforums/showthread.php/109299-GPWS-gauge-V5-zip
Can be installed as a visible or non-visible gauge with the same callout functionality.
Works in FSX SE or P3D.
The gauge numbers have to run in sequence.
The "**" in his readme simply means you add the gauges at the end of "Vcockpit01" entry in the panel CFG and number them in order.... Does that make sense..??
If the gauges aren't in numerical sequence it wont work
ah I see, did I do it correctly?
[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$737_1
background_color=23,17,52
gauge01=RCB_GPWS5!GPWS_Default,0,0,0,0
gauge02=RCB_GPWS5/XMLSound32!Sound, 0,0,0,0, ./Gauges/RCB_GPWS5/XMLSound_Default.ini
gauge01=B737_800!overhead_popup, 4,4,581,529
gauge02=B737_800!pfd, 6,536,260,260
gauge03=B737_800!trim_popup, 6,801,194,154
gauge04=B737_800!annunciator_speed_brake_armed, 6,961,51,28
gauge05=B737_800!annunciator_below_glideslope, 6,994,52,27
gauge06=B737_800!annunciator_panel_1, 64,961,132,40
gauge07=B737_800!mfd, 347,536,260,260
gauge08=B737_800!autopilot, 205,801,463,90
gauge09=B737_800!annunciator_panel_gear, 205,895,66,71
gauge10=B737_800!annunciator_le_flaps, 204,974,100,28
gauge11=B737_800!annunciator_auto_brake_disarm, 275,895,47,27
gauge12=B737_800!annunciator_anti_skid_inop, 275,925,37,27
gauge13=B737_800!flap_indicator, 308,960,59,59
gauge14=B737_800!compass, 325,895,91,62
gauge15=B737_800!compass, 370,960,50,50
gauge16=B737_800!clock, 424,896,105,105
gauge17=737-400!Transponder, 589,4,190,78
gauge18=737-400!Nav 2, 589,87,190,78
gauge19=737-400!Nav 1, 589,169,190,77
gauge20=737-400!Comm 2, 589,249,190,78
gauge21=737-400!Comm 1, 589,330,190,78
gauge22=737-400!Audio, 589,411,190,40
gauge23=737-400!ADF, 589,454,190,80
gauge24=B737_800!eicas, 704,541,260,260
gauge25=B737_800!adf_vor_backup, 757,908,104,105
gauge26=B737_800!attitude_backup, 533,896,104,105
gauge27=B737_800!alti_and_asi_backup, 641,909,103,103
gauge28=B737_800!efis_control_panel, 672,815,143,76
No, you didn't.....
First step.... Get rid of the entries you made to [Vcockpit01], they are not numbered correctly, and you can't have multiple gauges with the same number.
Step Two... add this to the END of the [VCockpit01] file.....
gauge29=RCB_GPWS5!GPWS_Default,0,0,0,0
gauge30=RCB_GPWS5/XMLSound32!Sound, 0,0,0,0, ./Gauges/RCB_GPWS5/XMLSound_Default.ini
Step Three... after pasting this AT THE END of Vcockpit01, go back and make sure ALL the gauges are numbered in descending numerical sequence.
Your saved panel cfg file should have 30 gauges total, starting with 01 and ending with 30, and ending with the entries I noted above.
Hope this makes sense, I know it's easy to make mistakes with this stuff, i've done it many times myself.. lol
FWIW, if you've done everything correctly, you should start hearing the callouts at about 1500 feet AGL, if you don't something is not right...
Turn the speaker volume down... lol
Honestly, I don't know what to tell you, i'm not sure if there's a way to turn the volume down in the XML sound file, but there might be....
I'll take a look at it tomorrow, and if there's anything that can be done i'll let you know.
I don't see any way to edit the XML file so the only option is turn the volume down on your speakers.
I've been using these call outs for a while on large aircraft, and I never found the sound to be excessively loud, perhaps a little louder than the ambient cockpit noises, but turning the volume down a bit made it perfectly acceptable. It's only in use for the final minute or so of flight anyway, so turning the volume down a bit is a minor inconvenience at worst.
Thanks for this post. Without it I would never have known there was an update from rcgbp-33 which was causing a CTD when going fullscreen!