Sign in to follow this  
pontiac51

POSKY 742v4 + RFPv2 Merge (200+200F JT9D)

Recommended Posts

Since i couldnt find any specific guide, ill come up with my own on how to merge the Project Opensky B747-200 with the Ready for Pushback B747-200.What we want to achieve is to keep as much stuff from the RFP Boeing, while changing all the outward things to Project Openskys wonderfull model. I'll tried this on 2 Boeings from the RFP pack, one was the EL AL PAX model, the other the JAL Cargo model. Both these models have JT9D engines. They both work now even with the Project Opensky aux panel.First you'll need a fresh install of a Project Opensky B747-200 with all the current updates. So install the plane for EL AL and JAL (os742_v4_ely_4xaxh.zip and os742_v4_jal_ja8161.zip from AVSIM) and then apply the SP3A (OS742_V4A_JT9D_MDL_SP3A for PAX and OS742SF_V4A_JT9D_MDL_SP3A for CARGO). Then apply the FDE update V9.7D from Project Opensky (we need that ainly for the effects, we'll use the AIR file from the RFP).Ok, so you got your Project Opensky ready. Let's get the parts from RFP. First copy the *.mdl file (pax.mdl or freighter.mdl) from the VMAX aircraft directory (like VMAX-EL AL) to the POSKY directory. DON'T copy the *.cfg, only the *.mdl. Do the same for the 'panel' and 'sound' folder.Now, rename the aircraft.cfg in the POSKY folder. Then copy the files from the root folder of the VMAX aircraft folder (*.txt, *.cfg and *.air) to the POSKY folder. Be carefull NOT to overwrite the aircraft.cfg.Now open the RFP aircraft.cfg and insert the following parts from the POSKY aircraft.cfg (you have renamed it, haven't you?) overwriting the entries.lightssmokesystemeffectscontact_pointsflapsgeneralenginedataYou sould also copy the right parts from the 'exits' chapter according to your aircraft or otherwise the doors won't work.Also copy the 'texture=' entry from the POSK *.cfg to the RFP *.cfg.And now for the tricky stuff. This is the most important thing, otherwise you will end up with an aircraft that's not flying. Since the RFP model has an reference point of 0,0,0 and the POSKY has one of -97,0,0, all 3D Coordinates are now wrong at exactly that value. Therefor you have to ADD 97 to all longitude values of the model. This has to be done for the following. lightsgeneralenginedatacontact_pointssmokesystemEXAMPLE: In the RFP plane contact point for the nose gear looks like this (minus the >>> <<<, thats just to mark it):point.0=1, >>> 66.8 <<<, 0.0, -17.4, 1574.8, 0.000000, 5.826899, 70.0 ,0.800000, 2.500000, 0.900000, 14.000000, 14.000000, 0.000000, 0.000000, 0.000000In the POSKY plane its like that:point.0 = 1.000, >>> -20.333 <<<, 0.000, -13.833, 5181.102, 0.000, 2.042, 70.000, 0.300, 0.500, 0.880, 11.000, 11.000, 0.000, 240.000, 280.000 // Nose GearNow the models form RFP and POSKY arent the same considering size, but also the CG and reference point are different. We don't change that from the RFP, cause we still want to be able to use the cargo and fuel loaders. So we have to change the appearance for the plane to work.In fact, you have to edit every value for every contact point, light, engine data etc. This will only affect appearance, not performance.EXAMPLE:After we have copied the POSKY contact points, it looks like that:point.0 = 1.000, >>> -20.333 <<<, 0.000, -13.833, 5181.102, 0.000, 2.042, 70.000, 0.300, 0.500, 0.880, 11.000, 11.000, 0.000, 240.000, 280.000 // Nose GearFor the model to work, we have to change it to that (we add 97):point.0 = 1.000, >>> 77.333 <<<, 0.000, -13.833, 5181.102, 0.000, 2.042, 70.000, 0.300, 0.500, 0.880, 11.000, 11.000, 0.000, 240.000, 280.000 // Nose GearEXAMPLE:For a light it looks like this in POSKY:light.4 = 3, >>> -219.700 <<<, -0.250, 12.300, Opensky_nav_yellow ,We change that:light.4 = 3, >>> -122.700 <<<, -0.250, 12.300, Opensky_nav_yellow ,I'll attach my 2 aircraft.cfgs for the EL AL PAX and the JAL Cargo model.POSKY Utility Panel:If you want to use that, you have to copy all the files from the VMAX panel folder to your POSKY panel folder. Then edit the panel.cfg and replace the standard GPS with the POSKY utility panel (Window03). Youre flying with CIVA INS, so who needs GPS? Now you can open the POSKY panel with a click on the GPS button in the main panel or use SHIFT+4 on the outside.

Share this post


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

I repacked the two aircraft configs for the CARGO and PAX version. There were some slight inaccuracies with the contact points, now everything is just like in the original POSKY model.

Share this post


Link to post
Share on other sites

>I repacked the two aircraft configs for the CARGO and PAX>version. There were some slight inaccuracies with the contact>points, now everything is just like in the original POSKY>model. Robert,could you post your zip file again ??!!see youPhil

Share this post


Link to post
Share on other sites
Since i couldnt find any specific guide, ill come up with my own on how to merge the Project Opensky B747-200 with the Ready for Pushback B747-200.What we want to achieve is to keep as much stuff from the RFP Boeing, while changing all the outward things to Project Openskys wonderfull model. I'll tried this on 2 Boeings from the RFP pack, one was the EL AL PAX model, the other the JAL Cargo model. Both these models have JT9D engines. They both work now even with the Project Opensky aux panel.First you'll need a fresh install of a Project Opensky B747-200 with all the current updates. So install the plane for EL AL and JAL (os742_v4_ely_4xaxh.zip and os742_v4_jal_ja8161.zip from AVSIM) and then apply the SP3A (OS742_V4A_JT9D_MDL_SP3A for PAX and OS742SF_V4A_JT9D_MDL_SP3A for CARGO). Then apply the FDE update V9.7D from Project Opensky (we need that ainly for the effects, we'll use the AIR file from the RFP).Ok, so you got your Project Opensky ready. Let's get the parts from RFP. First copy the *.mdl file (pax.mdl or freighter.mdl) from the VMAX aircraft directory (like VMAX-EL AL) to the POSKY directory. DON'T copy the *.cfg, only the *.mdl. Do the same for the 'panel' and 'sound' folder.Now, rename the aircraft.cfg in the POSKY folder. Then copy the files from the root folder of the VMAX aircraft folder (*.txt, *.cfg and *.air) to the POSKY folder. Be carefull NOT to overwrite the aircraft.cfg.Now open the RFP aircraft.cfg and insert the following parts from the POSKY aircraft.cfg (you have renamed it, haven't you?) overwriting the entries.lightssmokesystemeffectscontact_pointsflapsgeneralenginedataYou sould also copy the right parts from the 'exits' chapter according to your aircraft or otherwise the doors won't work.Also copy the 'texture=' entry from the POSK *.cfg to the RFP *.cfg.And now for the tricky stuff. This is the most important thing, otherwise you will end up with an aircraft that's not flying. Since the RFP model has an reference point of 0,0,0 and the POSKY has one of -97,0,0, all 3D Coordinates are now wrong at exactly that value. Therefor you have to ADD 97 to all longitude values of the model. This has to be done for the following. lightsgeneralenginedatacontact_pointssmokesystemEXAMPLE: In the RFP plane contact point for the nose gear looks like this (minus the >>> <<<, thats just to mark it):point.0=1, >>> 66.8 <<<, 0.0, -17.4, 1574.8, 0.000000, 5.826899, 70.0 ,0.800000, 2.500000, 0.900000, 14.000000, 14.000000, 0.000000, 0.000000, 0.000000In the POSKY plane its like that:point.0 = 1.000, >>> -20.333 <<<, 0.000, -13.833, 5181.102, 0.000, 2.042, 70.000, 0.300, 0.500, 0.880, 11.000, 11.000, 0.000, 240.000, 280.000 // Nose GearNow the models form RFP and POSKY arent the same considering size, but also the CG and reference point are different. We don't change that from the RFP, cause we still want to be able to use the cargo and fuel loaders. So we have to change the appearance for the plane to work.In fact, you have to edit every value for every contact point, light, engine data etc. This will only affect appearance, not performance.EXAMPLE:After we have copied the POSKY contact points, it looks like that:point.0 = 1.000, >>> -20.333 <<<, 0.000, -13.833, 5181.102, 0.000, 2.042, 70.000, 0.300, 0.500, 0.880, 11.000, 11.000, 0.000, 240.000, 280.000 // Nose GearFor the model to work, we have to change it to that (we add 97):point.0 = 1.000, >>> 77.333 <<<, 0.000, -13.833, 5181.102, 0.000, 2.042, 70.000, 0.300, 0.500, 0.880, 11.000, 11.000, 0.000, 240.000, 280.000 // Nose GearEXAMPLE:For a light it looks like this in POSKY:light.4 = 3, >>> -219.700 <<<, -0.250, 12.300, Opensky_nav_yellow ,We change that:light.4 = 3, >>> -122.700 <<<, -0.250, 12.300, Opensky_nav_yellow ,I'll attach my 2 aircraft.cfgs for the EL AL PAX and the JAL Cargo model.POSKY Utility Panel:If you want to use that, you have to copy all the files from the VMAX panel folder to your POSKY panel folder. Then edit the panel.cfg and replace the standard GPS with the POSKY utility panel (Window03). Youre flying with CIVA INS, so who needs GPS? Now you can open the POSKY panel with a click on the GPS button in the main panel or use SHIFT+4 on the outside.
And now the RFP panel works properly or the engines at start up have a failure?

Share this post


Link to post
Share on other sites
hey G.Franco, thanks for trying to help, you wrote there you were going to attach the .cfg

Share this post


Link to post
Share on other sites

@G.Franco: Of course everything works, its still the RFP plane, just with the Opensky graphics.@YMA002: The system for conversion i presented may work on this too. If the planes are very similar in dimensions.@All: Ill try to find the files and upload them again.

Share this post


Link to post
Share on other sites

Hi,I am trying to merge the RFPv2 with the newly released POSKY Air China 747SP, but I get an engine failure when trying to start the engines. (I've got a merge working with the CLS742 panel, but I' really like to get it to work with the RFPv2 panel, as that's much more accurate and in-depth...the RFPv2 is amazing!) Has anyone else attempted this merge, or know how to do it? Any help would be appreciated!Thanks,Jim

Share this post


Link to post
Share on other sites

Hey everyone, Although this thread has been started some time ago, I would like to thank pontiac51 for his gorgeous guide on how merging the RFP 747-200 with the POSKY 747-200 model. Without your instructions I would never have been able to get these two outstanding aircraft together and would still fly using the 'oldie but goldie' RFP exterior model which is nice but nothing compared to the POSKY model. Maybe one of the forum mods could make this a sticky to save other people's nerves trying to merge them. Thank you very much, pontiac51!

Share this post


Link to post
Share on other sites

HiI had a go at this merge yesterday following a read of this thread.i used the ELAL pax model downloaded from the Posky site and added the updates as per the first thread.All seemed to work fine except in tower or spot view there is a cloud of water vapour or smoke surrounding the middle of the plane when on the ground, and in the air it is like there are puffs of smoke coming out the back of plane as if it is smoking a cigar !Anyone got any thoughts ?

Share this post


Link to post
Share on other sites

It says there are 11 replies, but I can only see one post... Any chance someone can PM the links?Thanks in advance,Sam

Share this post


Link to post
Share on other sites

Many thanks to the folks on this forum and particularly to Pontiac51 for this thread. I have not only got the RFP/Posky P+W variations set up, but have also got a BA 742 with RR engines installed. All works very well.ThanksPeter

Share this post


Link to post
Share on other sites
Many thanks to the folks on this forum and particularly to Pontiac51 for this thread. I have not only got the RFP/Posky P+W variations set up, but have also got a BA 742 with RR engines installed. All works very well.ThanksPeter
Peter,Can you post the config for your BA-RR installation?David.

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