Hi AllI have purchased the PSS 777 and have read things on these forums about a merge with the POSKY model. I understand the point of this is to use the PSS panel/systems but the POSKY model, as it is better than the PSS model, is this correct?I have downloaded the following file from the libraryposky_pss_777_merge.zipand the instructions call for you to download "any POSKY 777-200 model". When I go to the POSKY/FreeSkyProject website, and go to Downloads>Boeing>777>777-200>Model there are about 30 different files...and I'm slightly confused at exactly what I need to be downloading!Is anybody who has done this able to clarify exactly what POSKY files I need to download? The instructions for the merge seem fairly straightforward from there on in, which I think I should be able to follow!ThanksMartin

The POSKY download page is indeed horrible confusing, but there is logic. There are first of all two categories of files:- FSX files- FS9 filesThe difference is simple: FSX files have a FSX prefix in the filename. Secondly comes whether you want a VC or not. The VC files can be recognized because of the "VC" in the filename. Then, thrirdly, there are different engine models. These can be recognized because of the engine type mentioned in the filename. And finally, there are various cargo and pax models and such. So, if you would want the three 777-200 models with the different engines and VC, here's the files to pick:- GE90 engine with VC in pax configuration: VC>SP2A_GE90 Model (OS772V2_GE90_VC)- Trent800 engine with VC in pax configuration: VC>SP2A_Trent800 (OS772V2_Trent800_VC)- PW4000 engine with VC in pax configuration: VC>SP2A_PW4000 (OS772V2_PW4000_VC)I hope this clears it up somewhat. Do not forget to download liveries also. These can be found by simply clicking on the 777-200 link (not any of the tiny sub-links)

The POSKY download page is indeed horrible confusing, but there is logic. There are first of all two categories of files:- FSX files- FS9 filesThe difference is simple: FSX files have a FSX prefix in the filename. Secondly comes whether you want a VC or not. The VC files can be recognized because of the "VC" in the filename. Then, thrirdly, there are different engine models. These can be recognized because of the engine type mentioned in the filename. And finally, there are various cargo and pax models and such. So, if you would want the three 777-200 models with the different engines and VC, here's the files to pick:- GE90 engine with engine in pax configuration: VC>SP2A_GE90 Model (OS772V2_GE90_VC)- Trent800 engine with engine in pax configuration: VC>SP2A_Trent800 (OS772V2_Trent800_VC)- PW4000 engine with engine in pax configuration: VC>SP2A_PW4000 (OS772V2_PW4000_VC)I hope this clears it up somewhat. Do not forget to download liveries also. These can be found by simply clicking on the 777-200 link (not any of the tiny sub-links)

Thanks for the very detail guide :biggrin:Another choice is to download the mega merge 777,it is quite well too :(

Thanks for the very detail guide :biggrin:Another choice is to download the mega merge 777,it is quite well too :(

Thanks Benjamin, that's really useful! Will get downloading this weekend!

The POSKY download page is indeed horrible confusing, but there is logic. There are first of all two categories of files:- FSX files- FS9 filesThe difference is simple: FSX files have a FSX prefix in the filename. Secondly comes whether you want a VC or not. The VC files can be recognized because of the "VC" in the filename. Then, thrirdly, there are different engine models. These can be recognized because of the engine type mentioned in the filename. And finally, there are various cargo and pax models and such. So, if you would want the three 777-200 models with the different engines and VC, here's the files to pick:- GE90 engine with VC in pax configuration: VC>SP2A_GE90 Model (OS772V2_GE90_VC)- Trent800 engine with VC in pax configuration: VC>SP2A_Trent800 (OS772V2_Trent800_VC)- PW4000 engine with VC in pax configuration: VC>SP2A_PW4000 (OS772V2_PW4000_VC)I hope this clears it up somewhat. Do not forget to download liveries also. These can be found by simply clicking on the 777-200 link (not any of the tiny sub-links)

BenjaminTried to do this, but am having issues at the very first step!The readme says to make backups of the Posky panel and aircraft.cfg, but in those model files I downloaded as you pointed out above...there are no aircraft.cfg files, it's just model and texture folders.Any tips?ThanksMartin

BenjaminTried to do this, but am having issues at the very first step!The readme says to make backups of the Posky panel and aircraft.cfg, but in those model files I downloaded as you pointed out above...there are no aircraft.cfg files, it's just model and texture folders.Any tips?ThanksMartin

Go into the Freeskyproject boeing 777 packages and find the 777 base file. The ones pointed above I think are only the virtual cockpit update model.

Here is a Boeing 777-200ER package i made for my virtual airline. Based on real world specifications using real world data for the 200ER.http://singaporevirtualairlines.org/index.php?option=com_content&view=article&id=51&Itemid=12 (File: POSKY-PSS Boeing 777-200ER Merge )Enjoy :(

Here is a Boeing 777-200ER package i made for my virtual airline. Based on real world specifications using real world data for the 200ER.http://singaporevirt...id=51&Itemid=12 (File: POSKY-PSS Boeing 777-200ER Merge )Enjoy :(

Thanks for that! So can I apply other POSKY liveries on top of this? Sorry I'm a bit hopeless when it comes to these things unless they install themselves from .exe files!!Also would this be easy enough to set up for the other engine variants?Many thanks

Thanks for that! So can I apply other POSKY liveries on top of this? Sorry I'm a bit hopeless when it comes to these things unless they install themselves from .exe files!!Also would this be easy enough to set up for the other engine variants?Many thanks

Hmm...ok this will require a bit of copy and pasting etc.1) First make 3 copies of the folder (the merge folder you got from the website). Name it to whatever you want to name it -key is that you should be able to differentiate between each variant.2) Copy and paste: model + texture from another 777 (I.e. a united 777 or whatever) into the newly created folder3) Add texture into aircraft.cfg4) Change the "sim=" to portray the exact name as the air file. E.g. if the air file is named "Boeing 777-200ER RR" then: "sim=Boeing 777-200ER RR". 5) In aircraft.cfg go to "turbine_engine_data". Change the "static_thrust" to the thrust of the engine variant. E.g. if it is a GE90-94, then: "static_thrust=93400". Currently it is 92000 since Singapore Airlines 200ERs have Rolls Royce Trent 892 engines which provide 92000lbs thrust.6) Add a sound pack7) Copy the folder into aircraft folder and fly!I hope it's not too confusing :(. Have fun!

Hi Boeingsta,Can you please confirm if your merge is compatible with the latest POSKY FDE? I believe the version is G.

BenjaminTried to do this, but am having issues at the very first step!The readme says to make backups of the Posky panel and aircraft.cfg, but in those model files I downloaded as you pointed out above...there are no aircraft.cfg files, it's just model and texture folders.Any tips?ThanksMartin

Well yes, these are model files only and include nothing for the rest. They do not include the full aircraft. The easiest way to get a full aircraft, is to download a livery from Avsim, FreeSkyProject or flightsim.com. Then edit the aircraft.cfg that's within that package to suit the model files and such.

Hi Boeingsta,Can you please confirm if your merge is compatible with the latest POSKY FDE? I believe the version is G.

All you need to do with the merge is update the models and textures and sounds. YOU SHOULD NOT CHANGE THE AIRCRAFT.CFG AND AIR FILE WITH THE POSKY ONES. The autothrottle may not work etc and other problems may arise.The aircraft.cfg and air file have been made to correspond with the 200ER and changing these to the POSKY ones might cause some problems.I don't advise of it.:( Just upgrade the models, textures and sounds if you wish. But keep the FDE components of this merge (the aircraft.cfg and .air file) the same.Hope this helps :(

Hi, I have just tried this merge and there seems to be a big problem...Landing with about 28,857lbs of fuel remaining, causes all the ECAM warnings and audbile alerts to go off and the electrical, hydraulics and engines to turn off and the aircraft becomes a glider!I thought 25-30,000lbs of fuel on landing is more than enough for a 777?

Problem solved, the issue only occurs when any one of the five fuel tanks are completely empty.