November 27, 20196 yr Hello, There seems to be a problem with the installation of the QW787 on my system. Most of the liveries I installed are missing from the aircraft selection screen. Only the most recently installed liveries are showing up. For example. I installed a KLM 789 and a Singapore 78X livery a few days ago. Now they were only the ones showing up. Just to test, I installed another livery, an Ethiopian 788 yesterday. When I opened up the sim, only the Ethiopian livery was showing up. The 787 doesn't add liveries using the old method of adding an entry in the cfg file of the aircraft, so I cannot diagnose what's causing this issue. Any ideas ? Cheers 9W
November 27, 20196 yr Hello, if it does not use "the old method of adding an entry in the cfg file of the aircraft", how does the simulator see the repaint? I would be intrigued to find out what the "new" method might be.
November 27, 20196 yr Author Each livery now comes with it's own cfg file, which is how it should be done properly according to the SDK. Even the FSLabs aircraft also use the same method iirc.
November 27, 20196 yr Of course, no repaint has ever worked without a cfg entry. I was asking about the "new" method, implied by the statement "the old method of adding an entry in the cfg file of the aircraft" FS Labs use the aircraft.cfg file. Quote // Livery Paint section // //////////////////////////////////////////////////////////////////////////////// [fltsim.0] title=FSLabs A320X CFM - Lufthansa D-AIPZ sim=A320 model= panel=D-AIPZ sound= texture=D-AIPZ etc Which part of the SDK states that if this is not done, the simulator will be able to see the aircraft? Edited November 27, 20196 yr by Reader
November 27, 20196 yr To address the original question, if only the latest repaint is being seen, perhaps the installer is creating a new aircraft.cfg file with only that repaint or there is an error in the text?
November 27, 20196 yr Author Well, the QW787 doesn't use the old method like I said. Here are the first 20 lines of the aircraft.cfg Quote [General] atc_type=BOEING atc_model=B788 Category=airplane [vacuum_system] max_pressure=5.150000 vacuum_type=2 electric_backup_pressure=0.000000 engine_map=0,0,0,0 [pneumatic_system] max_pressure=18.000000 bleed_air_scalar=1.000000 Instead, each livery has it's own file called texture.ini which has the stuff that used to be added to the cfg file. For example, here is one from the Ethiopian livery I have installed Quote [QW787_Repaint.General] texture=ETH ET-AOU atc_id=ET-AOU atc_airline=ETHIOPIAN destination=QualityWings 787-8 atc_parking_types = GATE, RAMP atc_parking_codes = ETH [QW787_fltsim.0] title=QualityWings 787-8 GE Ethiopian Airlines ET-AOU sim=Boeing 787-8 GE model=ge sound=ge ui_variation=Ethiopian Airlines ET-AOU description=QualityWings Boeing 787-8 As you can see, there is nothing in the aircraft.cfg now, but if I boot up the sim, I can still see the Ethiopian 787 in the aircraft selection screen.
November 27, 20196 yr Intriguing, are you sure that there is no aircraft.cfg entry as well? There is no obligation to put the aircraft.cfg entries at the top, I wonder if they might be at the end, as indeed they are in the FsLabs cfg file. I am struggling to understand how the simulator could see the aircraft repaint, given that it only understands [fltsim.0], [fltsim.1] and so on? It cannot see these if even one bracket is missing, so it seems unlikely that it will understand a great deal of extra text. Edited November 27, 20196 yr by Reader
November 27, 20196 yr I have now spoken with a friend who does own the aircraft model and he confirms that the repaint cfg entries are indeed at the end of the aircraft.cfg file and in the conventional format. It remains to check them for errors, most likely to be found in the [fltsim.X] headings.
November 28, 20196 yr Author I stand corrected. I also realised the same when I re-installed the aircraft yesterday. Thanks for your help.
November 28, 20196 yr 18 hours ago, ninerwhiskey9W said: Well, the QW787 doesn't use the old method like I said. Here are the first 20 lines of the aircraft.cfg Instead, each livery has it's own file called texture.ini which has the stuff that used to be added to the cfg file. For example, here is one from the Ethiopian livery I have installed As you can see, there is nothing in the aircraft.cfg now, but if I boot up the sim, I can still see the Ethiopian 787 in the aircraft selection screen. Dont' know how your cfg was installed but each aircraft texture is referenced by [fltsim.xxx] staring at [fltsim.0] - my working example shown below, however yours is referenced with [QW787_fltsim.0] it should just be [fltsim.0] [fltsim.0] title=QualityWings 787-9 RR QW House sim=Boeing 787-9 RR model = RR panel =hires sound = rr texture = qw kb_checklists = Boeing737-800_check kb_reference = Boeing737-800_ref atc_id = N787QW atc_airline = Boeing atc_flight_number = 787 ui_manufacturer=Boeing-QWSim ui_type = 787-9 ui_variation = QW House RR ui_typerole = 787-9 ui_createdby = QualityWings Simulations description = QualityWings Simulations Boeing 787-9 [fltsim.1] title=QualityWings 787-9 GE QW House sim=Boeing 787-9 GE model = GE panel =hires sound = ge texture = qw kb_checklists = Boeing737-800_check kb_reference = Boeing737-800_ref atc_id = N787QW atc_airline = Boeing atc_flight_number = ui_manufacturer=Boeing-QWSim ui_type = 787-9 ui_variation = QW House GE ui_typerole = 787-9 ui_createdby = QualityWings Simulations description = QualityWings Simulations Boeing 787-9 Steve YBCG
Archived
This topic is now archived and is closed to further replies.