Beech D-18 Question

C

Crewchief408

Guest
I tried finding the answer via the search tool but had no luck, sorry if this has been posted elsewhere..

My question is regarding Milton Shupe's D-18. Doesn't the rear navigation light move up/down with the elevator? I thought it did anyway, but mine isn't moving anymore. I recently applied some lighting changes to take advantage of Shockwave's 3-D Lights.

Here's the changes I've made, could any of this possibly messed things up??

[LIGHTS]
// types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
// 6=Taxi, 7=Recognition, 8=Wing, 9=Logo, 10=Cabin
light.0 = 3, -0.6, -23.400, 1.796, fx_shockwave_navred ,
light.1 = 3, -0.5, 23.400, 1.696, fx_shockwave_navgre ,
light.2 = 3, -24.3, 0, 3.700, fx_shockwave_navwhi ,
light.3 = 4, 5.00, 0.00, 2.250, fx_vclight ,
light.4 = 10, 2.70, 0.00, 2.050, fx_vclight ,
light.5 = 10, -3.70, 0.00, 3.250, fx_vclight ,
light.6 = 1, -17.68, 0.00, 4.150, fx_shockwave_beacon_lowl , //top
light.7 = 1, -0.1, 0.00, -1.400, fx_shockwave_beacon_lowl , //bottom
light.8 = 5, 0.3, -10.250, -0.9, fx_Shockwave_landing_light , //wing lite reflections
light.9 = 5, 0.3, 10.250, -0.9, fx_Shockwave_landing_light , //wing
light.10 = 8, 7.5, -6.5, 0.036, fx_coco_d18FlameL ,
light.11 = 9, 7.5, -6.5, 0.036, fx_coco_d18FlameL ,
light.12= 6, 7.5, 6.5, 0.036, fx_coco_d18FlameR ,
light.13= 7, 7.5, 6.5, 0.036, fx_coco_d18FlameR ,

Thank you for such a wonderful plane Mr. Shupe, and thank all for any assistance!

Regards,
Chris
 
If 'light.2' is assigned to the tail light then it will not move up and down as the A2A lights can only be used in fixed positions. The lights need to be part of the model in order to move and not assigned as 'lights' in the [Lights] section of the .cfg file. The same thing happens with aircraft that feature 'wing flexing', the A2A lights will remain in a fixed position when the wing flexes.
 
That's probably why light.2 and light.3 are originally disabled in the cfg. I disabled them both again and loaded up the plane but I still don't have a rear nav light, so I guess I'll still have to experiment.

Thanks for the help.
 
Larry is correct. The lights are modeled to the elevator and effects lighting will not work.

Since you have added lights to the lights section, it may be that you need to increase the number of lights that FS allows. Max is 18 I believe. Look in your FS Display settings, hardward section I think.

I hope this helps, and happy to see that you are still enjoying the D18S. :jump:
 
Well, after spending most of my afternoon and evening trying to sort out the problem, I finally found the culprit.

I had recently installed a livery package that added some 70+ liveries and a few user tweaks all packed into an easy to install executable. It seems that one of the addon tweaks, a flame/smoke effect and gauge named "Coco-gauges!CocoFXControlTwinjet.xml" that is added to the panel.cfg some how turns off the rear nav lights.. once I deleted the gauge and light entries in the aircraft.cfg the nav lights started working again. Additionally, the originally modelled startup flame/smoke still works perfectly so I'm very happy with that.

I appreciate the help and advice.. and again, thanks for a excellent addon!

Cheers,
Chris

P.S. If anyone out there uses the Shockwave 3-D Light addon, here is my final configuration for the D-18, works in all versions.. Enjoy! :)
[LIGHTS]
light.0 = 3, -0.6, -23.400, 1.796, fx_shockwave_navred ,
light.1 = 3, -0.5, 23.400, 1.696, fx_shockwave_navgre ,
//light.2 = 3, -24.3, 0, 3.700, fx_navwhi ,
//light.3 = 4, 5.00, 0.00, 2.250, fx_vclight ,
light.4 = 10, 2.70, 0.00, 2.050, fx_vclight ,
light.5 = 10, -3.70, 0.00, 3.250, fx_vclight ,
light.6 = 1, -17.68, 0.00, 4.150, fx_shockwave_beacon , //top beacon
light.7 = 1, -0.1, 0.00, -1.400, fx_shockwave_beacon , //bottom beacon
light.8 = 5, 0.3, -10.250, -0.9, fx_Shockwave_landing_light , //Shockwave landing light
light.9 = 5, 0.3, 10.250, -0.9, fx_Shockwave_landing_light , //Shockwave landing light
 
You must log in or register to reply here.
Back
Top