June 7, 201411 yr Hello flight simmers! A bit of a pre-story, Recently I deleted my fsx.cfg and then started up fsx to receive a fresh default fsx.cfg. After that, I tweaked the fsx.cfg and replaced it with the fresh one. So now, I have a perfectly working fsx.cfg with, no problems. Ok, so then I look into my aircraft directory (in fsx) and see that all aircraft are there, however with no liveries. I deleted and reinstalled the liveries of the PMDG 777 in the operations center. However this did not work either. Now I don't know what to do! As I don not want to fly with the standard PMDG 777 paint which is the only one existing at the moment. Any answer would be appreciated, Thanks!
June 7, 201411 yr Hey, this is a simple fix. Open up your 777 cfg file and under the last line of [flightsim.0] which generally is visual_damage=0 copy and paste this. [fltsim.xx] title=PMDG 777-232LR Delta Air Lines sim=B777-200LR model= panel= sound= texture=DL atc_airline=DELTA atc_id=N702DN atc_flight_number=245 atc_heavy=1 atc_model=777-200LR atc_parking_types=GATE,RAMP atc_type=BOEING ui_createdby=PMDG ui_manufacturer=Boeing ui_type=777-200LRX ui_typerole=777-200LRX ui_variation=Delta Air Lines airline_name=Delta Air Lines description=Boeing 777-200LR powered by GE90 engines v 1.0\nPMDG Simulations\nwww.precisionmanuals.com \n\nProduced under license from Boeing Management Company.\n\nBoeing 777, 777-200LR, 777-200LR & Boeing are among the trademarks owned by Boeing. visual_damage=0 Replace [flightsim.xx] with the next number in the series for e.g. after [flightsim.1] it should be [flightsim.2] and etc. Replace the title with the name of the airline whose texture is being used. Under the field texture use the the title of the livery folder in the same folder where the cfg is located for e.g. Texture.pmdg, Texture.BA and etc. Omit the word texture and just use what follows it i.e. BA, pmdg and etc. You can change other details like the ones that follow atc_ but they are not necessary to make the livery work.
June 7, 201411 yr fix would be to tick the show all variants in the select aircraft section I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
June 7, 201411 yr fix would be to tick the show all variants in the select aircraft section Im going with the assumption that he has that checked. I believe his problem is that the op centre cannot write to the newly edited cfg file. Iceidic you can also try running running the pmdg op centre as admin or check whether the cfg is set to read only.
June 7, 201411 yr Author Hello Guys, Thanks for the quick response! Thats why I love this forum The problem is solved, I had all of the variants checked, but there were partially incomplete commands in the .cfg. I replaced the incomplete ones with the template above, and solved the problem Thanks a lot Brownman and pete_auau. Greetings
June 9, 201411 yr This is an automatic message. This topic has been moved from "Hangar Chat" to "PMDG 777". This move has been done for a number of possible reasons. The most likely reason is that the post was off topic. The topic could also have contained images or a video that were not appropriate to the original forum it was posted in. The images might not have been "illustrative" or "explanatory" in nature. The topic could have been moved because we deemed it to be more appropriately placed elsewhere. Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here. Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated. ADMIN BOT... Do not PM or send Email.
Create an account or sign in to comment