The A2A Simulations Community

I've seen this mentioned several time and people in the know can change the gauge to work correctly in day time. Well I'm a dummy with xml stuff so is there anyway you can make avable a correction to this gauge. Like a replaceable shockwave_Lights.cab file?

I noticed the same thing on the Beechcraft Baron 58 ...the lights come on for a second, but then quickly go out

I just made this util that should allow you to swap this configuration. Just double click the link below and click RUN (ignoring warnings), or save it to your hard drive and run it from there.

http://www.shockwaveproductions.com/sho ... s_util.exe

Scott.

Wow! You are awesome. Thanks a million...... It worked right on.

David

Scott, I just sent Lewis the updated Shockwave_Lights.cab file that will allow landing lights anytime of the day by email if you are interested.

Always glad to help and thanks for all your great work.

Tom

i see they have now released a fix so the lights will work during the day
the have just taken the time of day out form the .xml file i had already changed this from 1 to 0 and the gear form off to on this got the lights to work during the day and stay on when the gear retracted as i was still having problems on the beech baron when the gear was retracting even with the gear line removed in the gauge file. i modified the aircraft config
file to link the nose gear to the taxi light switch in the cockpit so when the gear retracts you just turn off the taxi light switch whic the leaves the lights in the engine cowls still on , to turn them off just turn off the landing light switch when you want to.
i've attached a copy of the light section in the config file that i've modified

[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi
light.0 = 3, -6.81, -19.30, 1.17, fx_shockwave_navred ,
light.1 = 3, -6.82, 19.29, 1.17, fx_shockwave_navgre ,
light.2 = 3, -25.33, 0.01, 1.08, fx_shockwave_navwhi_nl ,
light.3 = 2, -6.48, -19.04, 1.17, fx_shockwave_strobe ,
light.4 = 2, -6.48, 19.04, 1.17, fx_shockwave_strobe_2 ,
light.5 = 1, -24.20, 0.00, 6.54, fx_shockwave_beaconh_lowl ,
light.6 = 2, -7.52, 0.01, -1.28, fx_shockwave_strobe_3_nl ,
light.7 = 4, -8.30, 0.00, 3.00, fx_shockwave_vclight,
light.8 = 6, .84, 0.0, -1.5, fx_Shockwave_landing_light_small // Shockwave light
light.9 = 5, -1.4, 7.0, .1, fx_Shockwave_landing_light_small // Shockwave light
light.10 = 5, -1.4, -6.8, .1, fx_Shockwave_landing_light_small // Shockwave light

Scott - Shockwave wrote:I just made this util that should allow you to swap this configuration. Just double click the link below and click RUN (ignoring warnings), or save it to your hard drive and run it from there.

http://www.shockwaveproductions.com/sho ... s_util.exe

Scott.

Thank you very much

Baron issue solved

Scott,

this cures the same problem in FS9? I saw its only for FSX

cheerio

Jan

I purchased the Steam version that had Shockwave lights pre-installed. Is there a way to apply this fix there? I had also purchased the full version for an old stand alone non steam version of fsx.

Thanks,
LouP

Hi
I can`t make my landing lights work in the daytime on FSX SE.
How du I fix this problem ?

Scott - A2A wrote: ↑16 Dec 2007, 09:11 I just made this util that should allow you to swap this configuration. Just double click the link below and click RUN (ignoring warnings), or save it to your hard drive and run it from there.

http://www.shockwaveproductions.com/sho ... s_util.exe

Scott.

Hallo,
i am a new Member and I have a problem with the landing lights in daytime too!
Is it possible to send me a new Link for the Utility, because the Link above dont work.
Thanks

Scott - A2A wrote: ↑16 Dec 2007, 09:11 I just made this util that should allow you to swap this configuration. Just double click the link below and click RUN (ignoring warnings), or save it to your hard drive and run it from there.

http://www.shockwaveproductions.com/sho ... s_util.exe

Scott.

Hi Scott,
is it possible to send me a new Link. (the Link above doesnt work)
regards
Roland

Have you tried the latest update, whilst the product is now an older one the updates will still be able to fix this for you I believe.

thanks
Lewis - A2A