Jump to content

Recommended Posts

Posted

Hi Guys,

I´ve been struggling when merging the LVLD 767 panel with SkySpirit, there´s tons of tutorials which I´ve followed step by step, and everything is ok, except for the lights, seems that the LVLD 767 lights are, somehow, attached to its panel so whenever I place the panel on the SkySpirit folder it uses the LVLD 767 lights, instead of using the SkySpirit default lights,

now, is there anyway that I can keep the SkySpirit lights using the LVLD767 Panel?

 

 

Thanks,

Best Regards

SIM: P3DV5.3 CPU: Intel Core i7-4790k @ 4.0GHz GPU: GTX1060 6GB  OS: Windows 10 64Bits RAM: XPG DDR3 1600 16GB (2x 8GB) Display: Samsung LC27JG50QQLXZX 27´

Posted

 

 


I´ve been struggling when merging the LVLD 767 panel with SkySpirit, there´s tons of tutorials which I´ve followed step by step, and everything is ok, except for the lights, seems that the LVLD 767 lights are, somehow, attached to its panel so whenever I place the panel on the SkySpirit folder it uses the LVLD 767 lights, instead of using the SkySpirit default lights,

now, is there anyway that I can keep the SkySpirit lights using the LVLD767 Panel?

 

Hi, rafikihd,

 

I haven't messed with this for awhile, but it looks like I put the SkySpirit [lights] section entries in the aircraft.cfg and commented out the Level-D [lights] section.  I honestly don't remember if the lights worked properly or not, but you might want to give it a try.

 

Mike

 

                    bUmq4nJ.jpg?2

 

Posted

Hi, rafikihd,

 

I haven't messed with this for awhile, but it looks like I put the SkySpirit [lights] section entries in the aircraft.cfg and commented out the Level-D [lights] section.  I honestly don't remember if the lights worked properly or not, but you might want to give it a try.

 

Mike

Hi Mike,

Thanks for your answer, thats what I´ve been doing by following the tutorials, I put the SkySpirit lights into the LVLD lights section but it still uses the default LVLD lights. Thats why im struggling.

 

Thanks

SIM: P3DV5.3 CPU: Intel Core i7-4790k @ 4.0GHz GPU: GTX1060 6GB  OS: Windows 10 64Bits RAM: XPG DDR3 1600 16GB (2x 8GB) Display: Samsung LC27JG50QQLXZX 27´

Posted

 

 


Thanks for your answer, thats what I´ve been doing by following the tutorials, I put the SkySpirit lights into the LVLD lights section but it still uses the default LVLD lights. Thats why im struggling.

 

Hi, RafikiHD,

 

I don't fully understand your issue.  The level-D light switches appear to work the SkySpirit lights OK, except for the runway turnoff lights and some other minor things.  However I am using FSX - my FS9 doesn't want to start at the moment.  But what, exactly, are you seeing when you operate the following Level-D switches: landing light, Position, Nose Gear, Red anti-collision, White anti-collision, Wing?

 

Mike

 

                    bUmq4nJ.jpg?2

 

Posted

Hi, RafikiHD,

 

I don't fully understand your issue.  The level-D light switches appear to work the SkySpirit lights OK, except for the runway turnoff lights and some other minor things.  However I am using FSX - my FS9 doesn't want to start at the moment.  But what, exactly, are you seeing when you operate the following Level-D switches: landing light, Position, Nose Gear, Red anti-collision, White anti-collision, Wing?

 

Mike

Hello Mike,

Here´s the deal, the taxi/ runway turnoff/ landing light and wing light switches are working just fine, now the beacon and strobes aren´t working with the exception that when I turn on the position lights the nav lights, strobes and beacon start working all at once instead of working independently by their own respective switch and its using those thick LVLD default lights instead of using the SkySpirit reflected on ground lights.

 

Thanks for your answer

SIM: P3DV5.3 CPU: Intel Core i7-4790k @ 4.0GHz GPU: GTX1060 6GB  OS: Windows 10 64Bits RAM: XPG DDR3 1600 16GB (2x 8GB) Display: Samsung LC27JG50QQLXZX 27´

Posted

SIM: P3DV5.3 CPU: Intel Core i7-4790k @ 4.0GHz GPU: GTX1060 6GB  OS: Windows 10 64Bits RAM: XPG DDR3 1600 16GB (2x 8GB) Display: Samsung LC27JG50QQLXZX 27´

Posted

If you do get a succesful merge please post it on the avsim library or just tell how you managed to get it working. 

 

Cheers,

Swapnil.

Swapnil Sirdeshpande

Posted

Hello Swapnil,

Just follow the instructions step by step on the video that Ahmet posted on one of the replies that'll make the panel work,

 

Cheers

SIM: P3DV5.3 CPU: Intel Core i7-4790k @ 4.0GHz GPU: GTX1060 6GB  OS: Windows 10 64Bits RAM: XPG DDR3 1600 16GB (2x 8GB) Display: Samsung LC27JG50QQLXZX 27´

Posted

Here´s the deal, the taxi/ runway turnoff/ landing light and wing light switches are working just fine, now the beacon and strobes aren´t working with the exception that when I turn on the position lights the nav lights, strobes and beacon start working all at once instead of working independently by their own respective switch and its using those thick LVLD default lights instead of using the SkySpirit reflected on ground lights.

 

My red beacon and white strobe are working OK  and I don't have to turn on the position lights to get them to turn on or off.  They do reflect on the ground.

 

It is possible the aircraft you downloaded did not have the correct [lights] entries.  Here are mine (the commented out lines are that way from Skyspirit):

 

------------

//SKYSPIRIT2010 LIGHTS

 

[LIGHTS]    

//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing 6=taxi, 7=recognition, 8=wing, 9=logo

//light.1 = 1,  48.500,   0.000,   9.800, Opensky_beacon,          // top beacon

//light.2 = 1,  12.500,   0.000,  -8.700, Opensky_beacon,          // bottom beacon

//light.3 = 4,  84.000,   0.000,   3.000, Opensky_Boeing_vclight , // Boeing Orange

light.4 = 3,  55.000,   0.000,  -4.000, Opensky_nacelle_refl ,   // front cargo

light.5 = 3, -32.000,   0.000,  -4.000, Opensky_nacelle_refl ,   // rear cargo

light.6 = 3,  73.000,   0.000,   4.000, Opensky_nacelle_refl ,   // pax door

//light.7 = 5,  19.700,  19.000,  -4.000, Opensky_nacelle_refl,    // nacelle rays from inspection lights

//light.8 = 5,  19.700, -19.000,  -4.000, Opensky_nacelle_refl,    // nacelle rays from inspection lights

//light.9 = 5   18.000,  27.000,  -4.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.10= 5,  18.000, -27.000,  -4.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.11= 5,  15.500, -45.000,  12.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.12= 5,  15.500,  45.000,  12.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.13= 5,  42.350,   8.350,  -0.250, Opensky_nav_yellow ,     // flap inspection light

//light.14= 5,  42.350,  -8.350,  -0.250, Opensky_nav_yellow ,     // flap inspection light

//light.15= 5,  28.000, -25.000,   0.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.16= 5,  28.000,  25.000,   0.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.17= 6,  80.000,   0.000,  -8.350, Opensky_wing_light,      // gear bay taxi light rays from taxi lights

 

------------

Your downloaded Skyspirit aircraft might have had an older model.  Also, if it came with the FSX model (the name will start w/ "OSX") you might want to try the FS9 model with the same name.

 

I am using  OSX763ERV5_PW4000--AWL.mdl (winglet model) and OSX763ERV5_PW4000--AL.mdl (non-winglet).

This is all FSX, but the models w/out the X in them should be pretty much identical in FS9.

The model file will be in the model folder of the merged aircraft.

 

You might want to make sure you have the correct, and latest model by downloading from this web site:

http://ssp.cyber-ninja.jp/SSP2010Update.html

 

Mike

 

                    bUmq4nJ.jpg?2

 

Posted

My red beacon and white strobe are working OK  and I don't have to turn on the position lights to get them to turn on or off.  They do reflect on the ground.

 

It is possible the aircraft you downloaded did not have the correct [lights] entries.  Here are mine (the commented out lines are that way from Skyspirit):

 

------------

//SKYSPIRIT2010 LIGHTS

 

[LIGHTS]    

//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing 6=taxi, 7=recognition, 8=wing, 9=logo

//light.1 = 1,  48.500,   0.000,   9.800, Opensky_beacon,          // top beacon

//light.2 = 1,  12.500,   0.000,  -8.700, Opensky_beacon,          // bottom beacon

//light.3 = 4,  84.000,   0.000,   3.000, Opensky_Boeing_vclight , // Boeing Orange

light.4 = 3,  55.000,   0.000,  -4.000, Opensky_nacelle_refl ,   // front cargo

light.5 = 3, -32.000,   0.000,  -4.000, Opensky_nacelle_refl ,   // rear cargo

light.6 = 3,  73.000,   0.000,   4.000, Opensky_nacelle_refl ,   // pax door

//light.7 = 5,  19.700,  19.000,  -4.000, Opensky_nacelle_refl,    // nacelle rays from inspection lights

//light.8 = 5,  19.700, -19.000,  -4.000, Opensky_nacelle_refl,    // nacelle rays from inspection lights

//light.9 = 5   18.000,  27.000,  -4.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.10= 5,  18.000, -27.000,  -4.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.11= 5,  15.500, -45.000,  12.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.12= 5,  15.500,  45.000,  12.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.13= 5,  42.350,   8.350,  -0.250, Opensky_nav_yellow ,     // flap inspection light

//light.14= 5,  42.350,  -8.350,  -0.250, Opensky_nav_yellow ,     // flap inspection light

//light.15= 5,  28.000, -25.000,   0.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.16= 5,  28.000,  25.000,   0.000, Opensky_wing_light,      // wing/LE slat rays from inspection lights

//light.17= 6,  80.000,   0.000,  -8.350, Opensky_wing_light,      // gear bay taxi light rays from taxi lights

 

------------

Your downloaded Skyspirit aircraft might have had an older model.  Also, if it came with the FSX model (the name will start w/ "OSX") you might want to try the FS9 model with the same name.

 

I am using  OSX763ERV5_PW4000--AWL.mdl (winglet model) and OSX763ERV5_PW4000--AL.mdl (non-winglet).

This is all FSX, but the models w/out the X in them should be pretty much identical in FS9.

The model file will be in the model folder of the merged aircraft.

 

You might want to make sure you have the correct, and latest model by downloading from this web site:

http://ssp.cyber-ninja.jp/SSP2010Update.html

 

Mike

Hello Mike,

I´ve tried by pasting the lights section to the aircraft.cfg but still no success, now I´ve realized that everytime I delete the LVLD panel.cfg (just doing some trials) from the SkySpirit folder the usual SkySpirit lights come back again and when I paste it back again it goes back to the LVLD 767 lights, so that´s why I was saying that the lights are somehow attached to the panel.cfg.

Now I´m using FS9 so the model I´m using is the OS763ERV5_CF6-80C--AWL.mdl and I did the updates before having this trouble. But still struggling.

 

Thanks

SIM: P3DV5.3 CPU: Intel Core i7-4790k @ 4.0GHz GPU: GTX1060 6GB  OS: Windows 10 64Bits RAM: XPG DDR3 1600 16GB (2x 8GB) Display: Samsung LC27JG50QQLXZX 27´

Posted

 

 


I´ve tried by pasting the lights section to the aircraft.cfg but still no success, now I´ve realized that everytime I delete the LVLD panel.cfg (just doing some trials) from the SkySpirit folder the usual SkySpirit lights come back again and when I paste it back again it goes back to the LVLD 767 lights, so that´s why I was saying that the lights are somehow attached to the panel.cfg.

Now I´m using FS9 so the model I´m using is the OS763ERV5_CF6-80C--AWL.mdl and I did the updates before having this trouble. But still struggling.

 

Hi, rafikihd,

 

i have FS9 working again.

 

There are two things to check:

 

I) Do you have the following entry in your panel.cfg file?  There are two gauge entries that are especially important.  I've marked them.  Also make sure the [VCockpitXX] entry is correct.  Without this entry the lights don't work. If there are no other [VCockpit...] entries, it should go after the last [Windowxx] entry.

 

------------------------

[VCockpit01] //<< IF THERE ARE OTHER ENTRIES [VCockpitXX] this should be at the end and have the next consecutive number
size_mm=512,512
pixel_size=512,512
texture=$Posky_ACU
background_color=0,0,0
gauge00=Posky763!Pky_AdvInit, 140,80,140,80
gauge01=Posky763!PkyCALC, 140,80,140,80
gauge02=Posky763!Pkygearcalc, 140,80,140,80
gauge03=Posky763!Pky6WINGFLEX, 140,80,140,80
gauge04=Posky763!PkyNosegearsteerling, 140,80,140,80
gauge05=Posky763!PkyAileronL, 140,80,140,80
gauge06=Posky763!PkyAileronR, 140,80,140,80
gauge07=Posky763!PkyLSAileron, 140,80,140,80
gauge08=Posky763!PkySpoiler, 140,80,140,80
gauge09=Posky763!PkyAPUDoor, 140,80,140,80
gauge10=Posky763!PkyEngRev, 140,80,140,80
gauge11=Posky763!Pky_PB_Towhead, 140,80,140,80
gauge12=Posky763!PkySEA, 140,80,140,80
gauge13=Posky763!PkyFlasher, 140,80,140,80  //*** THIS ENTRY CONTROLS THE BEACON & FLASHER
gauge14=Posky763!Pkycondassign, 140,80,140,80 // *** THIS ENTRY APPEARS TO CONTROL SOME WING LIGHTS
-----------------------

 

II) Do you have a folder inside your panel folder called "Posky763"?  When you look inside it do you see a bunch of gauges ending in "xml"?  Especially important are one called "PkyFlasher.xml" and "Pkycondassign.xml" -- these are the two gauges to which the above last two gauge entries are pointing.

 

Mike

 

                    bUmq4nJ.jpg?2

 

Posted

Hi, rafikihd,

 

i have FS9 working again.

 

There are two things to check:

 

I) Do you have the following entry in your panel.cfg file?  There are two gauge entries that are especially important.  I've marked them.  Also make sure the [VCockpitXX] entry is correct.  Without this entry the lights don't work. If there are no other [VCockpit...] entries, it should go after the last [Windowxx] entry.

 

------------------------

[VCockpit01] //<< IF THERE ARE OTHER ENTRIES [VCockpitXX] this should be at the end and have the next consecutive number

size_mm=512,512

pixel_size=512,512

texture=$Posky_ACU

background_color=0,0,0

gauge00=Posky763!Pky_AdvInit, 140,80,140,80

gauge01=Posky763!PkyCALC, 140,80,140,80

gauge02=Posky763!Pkygearcalc, 140,80,140,80

gauge03=Posky763!Pky6WINGFLEX, 140,80,140,80

gauge04=Posky763!PkyNosegearsteerling, 140,80,140,80

gauge05=Posky763!PkyAileronL, 140,80,140,80

gauge06=Posky763!PkyAileronR, 140,80,140,80

gauge07=Posky763!PkyLSAileron, 140,80,140,80

gauge08=Posky763!PkySpoiler, 140,80,140,80

gauge09=Posky763!PkyAPUDoor, 140,80,140,80

gauge10=Posky763!PkyEngRev, 140,80,140,80

gauge11=Posky763!Pky_PB_Towhead, 140,80,140,80

gauge12=Posky763!PkySEA, 140,80,140,80

gauge13=Posky763!PkyFlasher, 140,80,140,80  //*** THIS ENTRY CONTROLS THE BEACON & FLASHER

gauge14=Posky763!Pkycondassign, 140,80,140,80 // *** THIS ENTRY APPEARS TO CONTROL SOME WING LIGHTS

-----------------------

 

II) Do you have a folder inside your panel folder called "Posky763"?  When you look inside it do you see a bunch of gauges ending in "xml"?  Especially important are one called "PkyFlasher.xml" and "Pkycondassign.xml" -- these are the two gauges to which the above last two gauge entries are pointing.

 

Mike

Hi Mike,

You are a genius, that was apparently the problem, now I got it working just fine with the LVLD cockpit and the SkySpirit Lights.

Thank you so much,

Cheers,

Rafa

SIM: P3DV5.3 CPU: Intel Core i7-4790k @ 4.0GHz GPU: GTX1060 6GB  OS: Windows 10 64Bits RAM: XPG DDR3 1600 16GB (2x 8GB) Display: Samsung LC27JG50QQLXZX 27´

Posted

that was apparently the problem, now I got it working just fine with the LVLD cockpit and the SkySpirit Lights.

 

Thank you so much,

 

Hi, Rafa,

 

Glad it's working! 

 

Just out of curiosity, did the video you used cover this?  It's pretty important.  So is installing some additional [WindowXX] entries in the panel.cfg file.

 

Mike

 

                    bUmq4nJ.jpg?2

 

Posted

Hi, Rafa,

 

Glad it's working! 

 

Just out of curiosity, did the video you used cover this?  It's pretty important.  So is installing some additional [WindowXX] entries in the panel.cfg file.

 

Mike

Hi Mike,

It actually does, the matter was that since I didnt want to merge the VC (Because I dont use it that much) I wasnt installing that VC section that you told me, but the video actually covers it, it basically covers it all.

 

Cheers,

Rafa

SIM: P3DV5.3 CPU: Intel Core i7-4790k @ 4.0GHz GPU: GTX1060 6GB  OS: Windows 10 64Bits RAM: XPG DDR3 1600 16GB (2x 8GB) Display: Samsung LC27JG50QQLXZX 27´

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...