Sign in to follow this  
rafikihd

Merging LVLD 767 w/ SkySpirit2010

Recommended Posts

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

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

 

 


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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 

 


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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 

 


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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 

 


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.

 

Ok, thanks for clarifying.  As far as I know, there is no way to merge the Level-D VC w/ the SkySpirit model or any other merged aircraft in FS9 -- it can only be done in FSX (and quite easily).  If the Skyspirit 767 model had its own VC (which it doesn't), it might be possible to paste in the Level-D gauges, but it's hard to do.  I did it w/ the  Open Sky 777 VC models & PSS 777s, but I still needed to have several popups.

 

Happy flying!

 

Mike

Share this post


Link to post
Share on other sites

Ok, thanks for clarifying.  As far as I know, there is no way to merge the Level-D VC w/ the SkySpirit model or any other merged aircraft in FS9 -- it can only be done in FSX (and quite easily).  If the Skyspirit 767 model had its own VC (which it doesn't), it might be possible to paste in the Level-D gauges, but it's hard to do.  I did it w/ the  Open Sky 777 VC models & PSS 777s, but I still needed to have several popups.

 

Happy flying!

 

Mike

 

Yeah, I bet its not as easy as it looks, I don`t usually use the VC because it decreases my frame rates like crazy, btw I think there´s a pretty nice merge for the Posky777 with the PSS including virtual cockpit somewhere on the internet, just google "mega merge 777".

 

Thanks again for your help Mike,

Cheers,

Rafa

Share this post


Link to post
Share on other sites

First thing to learn is 
At SSP 's 767 , model animations and lights are controled by Animation and Light Control Guages defined in vcockpit section of panel.cfg
Why vcockpit section is simply thats the only place keeps moving at any mode.
(Except slew and Multiplayer side)
So that place is good to place a controler.

Panel side guage orders -> MDL side receives the order -> Animate/Lights

This is how it's working.
Then what will happen if removed those guages?
When I did that at the first time , I didn't code those and guys just yelled bug or so .
So now there is a backup code builted in to the MDL side too.
But those actions are limited and not as should be.
It's just to make the guys yelling less.
So if want to use as it should be , must define the animation/light  control guages.

I hope this clears up.
Same system is used  at Posky747V4A , POSKY777V2 , SSP767V5,TDS737V2,TDS787,TDS727

Merit of this is user can customize or even add functions.
I saw a person added a Aileron droop when engine shutted down.

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

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


Gear height management
gauge02=Posky763!Pkygearcalc, 140,80,140,80


Wing flex code
gauge03=Posky763!Pky6WINGFLEX, 140,80,140,80


Nose gear steering angle management
gauge04=Posky763!PkyNosegearsteerling, 140,80,140,80

Left aileron action
gauge05=Posky763!PkyAileronL, 140,80,140,80


Right aileron action
gauge06=Posky763!PkyAileronR, 140,80,140,80

Low speed  aileron action
gauge07=Posky763!PkyLSAileron, 140,80,140,80

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


APU door action
gauge09=Posky763!PkyAPUDoor, 140,80,140,80


Thrust reverser action
gauge10=Posky763!PkyEngRev, 140,80,140,80


Towing tractor  angle when push back
gauge11=Posky763!Pky_PB_Towhead, 140,80,140,80


Calculates day and night
gauge12=Posky763!PkySEA, 140,80,140,80


Flasher 
gauge13=Posky763!PkyFlasher, 140,80,140,80 


Wing inspection light bulb
gauge14=Posky763!Pkycondassign, 140,80,140,80

================================================================

Share this post


Link to post
Share on other sites

Panel side gauge orders -> MDL side receives the order -> Animate/Lights

Same system is used  at Posky747V4A

Sorry for hijacking the thread, Hiroshi, but I'd like to merge the iFly 747v2 with the Posky 744. I've noticed that, if I merge simply as it should be (including all Posky animation gauges in the VC section in panel.cfg and without editing any gauges):

 

- Logo Light is turned on using the left Runway Turnoff switch.

- Nav lights are turned on with the beacon switch.

- Beacon light is turned on with the right Runway Turnoff switch.

 

In summary, looks as if someone crossed all wires in the aircraft. So, with your previous post, would you mean that (at least technically), I could see what am I actually ordering when clicking on the switch and change it in XML so that I could fix this?

Share this post


Link to post
Share on other sites

Hi, Hiroshi,

 

Thank you for contributing to this thread. 

 

I also want to thank you and your friends at Opensky, SkySpirit and Tenkuu Developers Studio for excellent models, excellent animations and excellent FDEs!  i have been using them for years, in both FS9 and FSX, especially 767s & 777s.  They have given me a tremendous amount of enjoyment of realistic simulation.  I haven't kept track but I'm sure I have hundreds of hours flying them in various merged configurations.

 

Mike

Share this post


Link to post
Share on other sites

About those switches about lights.
Basics are like this.

Get MS defined data  and set on/off
At most of the case is like that , specially at 747V4A series , it's more like hard coded to the model.

What kind of Ms defined parameter is prepared  info is under.
https://msdn.microsoft.com/en-us/library/cc526981.aspx

The things I can guess is.
- Logo Light is turned on using the left Runway Turnoff switch.

ifly model designer modeled like that so panel side fitted to those use.
Also at 747V4 there is no 
Runway Turnoff switch defined since not on MS parameter.

- Nav lights are turned on with the beacon switch.
Same as above.

- Beacon light is turned on with the right Runway Turnoff switch.

Same as above.

So using ifly's panel is the matter.
If it's written at XML guages , see inside .
May be there is a way.
 


Mr Mike

Thank you for those words.
Animation/light guage system is quite unique way so many people just can't recognize.

I want to explain why using this systems here.

The largest merit for this is user customize.
One example , if want a wing flex more , user can just open the XML animation guage and modify.
For the lights .. same  , the flasher is made a bit slower softer then real not to make people ill but if you want to make it strong and sharp , can do those.
If someone wants to move a APU door by other systems , can just by editing XML codes.

At a old system , only model builder can do those and has to live with it.
This is a huge difference.

Also at this system , can make a animation at very complexed factors.

Why can't at a old way ?
Simply there was a limit of MDL file size at FS2004.
And XML+ Polygon+animation has to be  fit all in that same area.
But at this way , complexed calculation is done at panel side.
So can use a lot of parameters.

One example , At wingflex , airspeed . Aircraft weight , wind , ground effect, pitch angle , using all those and makes up how much flex is needed.
At a old way , most of case , air speed or G.

I've seen other person added a wing bounce when taxing.
It was a edit of the wing flex code.

This system was fully started using from Posky 777V2 .
At 747V4 .. it's at 747V4A so only 747-400 and 747-8I/8F
So far the newest model 727-200 is using this system too.

A complexed system but this is a useful way.
Merit for modeling side is speeds up the modeling since XML guage debug is just a text editor debug.
But If a Model compile , if using a special tool to get over 60000 polygons at FS2004.
Takes 15min for 1 compile.
Usually at test .. won't do that but still needs a compile.

Share this post


Link to post
Share on other sites

About those switches about lights.

Basics are like this.

 

Get MS defined data  and set on/off

At most of the case is like that , specially at 747V4A series , it's more like hard coded to the model.

 

What kind of Ms defined parameter is prepared  info is under.

https://msdn.microsoft.com/en-us/library/cc526981.aspx

 

The things I can guess is.

- Logo Light is turned on using the left Runway Turnoff switch.

ifly model designer modeled like that so panel side fitted to those use.

Also at 747V4 there is no Runway Turnoff switch defined since not on MS parameter.

 

- Nav lights are turned on with the beacon switch.

Same as above.

 

- Beacon light is turned on with the right Runway Turnoff switch.

Same as above.

 

So using ifly's panel is the matter.

If it's written at XML guages , see inside .

May be there is a way.

 

Mr Mike

 

Thank you for those words.

Animation/light guage system is quite unique way so many people just can't recognize.

 

I want to explain why using this systems here.

 

The largest merit for this is user customize.

One example , if want a wing flex more , user can just open the XML animation guage and modify.

For the lights .. same  , the flasher is made a bit slower softer then real not to make people ill but if you want to make it strong and sharp , can do those.

If someone wants to move a APU door by other systems , can just by editing XML codes.

 

At a old system , only model builder can do those and has to live with it.

This is a huge difference.

 

Also at this system , can make a animation at very complexed factors.

Why can't at a old way ?

Simply there was a limit of MDL file size at FS2004.

And XML+ Polygon+animation has to be  fit all in that same area.

But at this way , complexed calculation is done at panel side.

So can use a lot of parameters.

 

One example , At wingflex , airspeed . Aircraft weight , wind , ground effect, pitch angle , using all those and makes up how much flex is needed.

At a old way , most of case , air speed or G.

 

I've seen other person added a wing bounce when taxing.

It was a edit of the wing flex code.

 

This system was fully started using from Posky 777V2 .

At 747V4 .. it's at 747V4A so only 747-400 and 747-8I/8F

So far the newest model 727-200 is using this system too.

 

A complexed system but this is a useful way.

Merit for modeling side is speeds up the modeling since XML guage debug is just a text editor debug.

But If a Model compile , if using a special tool to get over 60000 polygons at FS2004.

Takes 15min for 1 compile.

Usually at test .. won't do that but still needs a compile.

 

Hi, Hiroshi,

 

Thanks for the explanation.  Although I've done a couple of merges using your models (and often your FDEs, as in the 767-200 merged w/ Level-D panel, and 777-200s and 200ERs using PSS panel), I never really understood why you did the animations that way.  Makes excellent sense!

 

Mike

Share this post


Link to post
Share on other sites

One more I just thought.

If I remember correct
Level-D can control  APU ON/Off.
(At MS default codes , can't)
At this model.
PkyAPUDoor.xml controls APU door.

If you can know the Level-D's variable name for APU door , can just change the variable written in that guage .
Then APU door will work with the Level-D side's switch.
 

Share this post


Link to post
Share on other sites

One more I just thought.

 

If I remember correct Level-D can control  APU ON/Off.

(At MS default codes , can't)

At this model.

PkyAPUDoor.xml controls APU door.

If you can know the Level-D's variable name for APU door , can just change the variable written in that guage .

Then APU door will work with the Level-D side's switch.

 

 

(L:LVLDAPUDoor, bool)

Share this post


Link to post
Share on other sites
Thank you Ed 
So  first open PkyAPUDoor.xml
Then you can see the codes under.
------------------------------------------------------------------
   (L:PkyOilPressure,percent) 100 < if{
       (L:PkyOilPressure,percent) 
   }
   els{
       (A:GEAR POSITION:0,percent)
   }   
   (>L:PkyAPUDoor,percent) 
------------------------------------------------------------------
This code meand if the Oil pressure is lower then 100% will be closed following the oil pressure.
If not , will use the amount of nose gear retract .

So changing place is 
       (A:GEAR POSITION:0,percent)

Ed saysi under is the code for Level-D's APU open/close
(L:LVLDAPUDoor, bool)
They are using bool so probably 0= close 1= Open


Then change       (A:GEAR POSITION:0,percent) to  
(L:LVLDAPUDoor, bool)  100 *

Then APU door should move with Level-D's panel side.
XML Animation Guage systems can make things like this.

 
  • Upvote 1

Share this post


Link to post
Share on other sites

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
Sign in to follow this