Korundar

Problem solved!!!! In the aircraft.cfg of this (and others) model at the line [General] -> atc_model there was A330 and not A332 or A333 so AILGenerator didn't identify correctly the two models.

Hi Nico, first of all many thanks for your wonderful utility. I couldn't fly without. I'm not new to modifying AI aircrafts liveries so I wouldn't bother you asking for help if AILGenerator didn't show a weird behaviour. I use FLAI liveries as default, but I added the UTLive folder and some others to complete the livery roster but not all are used as expected. For example, the A332 Air Italy livery shows correctly if I manually add the entry to the xml file, but it's deleted if I run AILGenerator because there's an Invalid Airline Codes error. I checked many times the aircraft.cfg but honestly I can't understand why it happens. This is the AirItaly livery line : [fltsim.12] title=TFS A330-200 GE Air Italy sim=TFS_A332 model=GE/New Tail texture=AirItaly atc_id= atc_airline=Air Italy ui_manufacturer=The Fruit Stand ui_type=Airbus A330-200 GE ui_variation=Air Italy description=TFS A330-200 GE Ait Italy Airlines - by Jon Hanf atc_heavy=1 atc_parking_codes=ISS atc_parking_types=GATE

It depends on how you compile your flightplan. It should start from one of the waypoints on the SID charts and it should end on a waypoint of one of the STARs. Assuming that it's correctly compiled (and filed if online) it always ends on the first waypoint of the related STAR. An example should be better: Flight from LIML to LIRN. assuming that arrival is on Rwy 24. Route LOGDI Y663 EKDIR M872 LOMED Z910 AKAMO AKAMO will be your last waypoint and there's obviously a STAR starting from there, usually AKAM1A Obviously if online (or using some software) ATC can direct you to another waypoint due to traffic or weather, but in most cases you'll fly the last waypoint STAR.

According to this logic we will never see another aircraft by PMDG

Just one aircraft from my hangar so I can fly in v4. PMDG 737 NGX Aerosoft Bus Majestic Dash Q400

Same here. It seems to be something wrong server side.

I'll post even there but I can't understand why if I have installed only AS2016 and ASCA I can't see clouds. I don't know if it's a REX issue or not.

Hi all, yesterday I uninstalled REX+SC to try AS2016+ASCA only. After this I have no more clouds in every weather situation, just ASCA sky colors and visibility and precipitation injected by AS2016. I tried reinstalling REX+SC but still no clouds in the sky, even if I load a P3D weather preset. What can I do?

Good news! Hope that LM will solve this issue once for all. Florian, I don't think it's related with using other applications, it's an issue that happens when you move the focus out of the P3D window. I tried to make some flights without moving the focus and I've been able to complete them all the times. While flying the same routes in the same conditions and with the same aircraft but moving focus between applications has caused P3D to crash 3 times out of 4. It's definitely something wrong with the focus change, but it's very hard to understand as P3D closes without errors.

Same issue for me with 3.3.5 as I discussed here. I haven't found the problem yet and nothing in the CTD-guide seems to solve the issue, neither a full P3D reinstall (or even Windows). Normally P3D crashes without giving errors, while a few times I've had a kernelbase.dll error but it's not a specific error. I hope it's not some Windows 10 update. System: Intel Core i7-6700K never OC 16 GB RAM nVidia GeForce GTX 770 Win10 64Bit no overclockings

I have the same issue with 3.3.5. Suddenly P3D stops responding and simply closes without errors. I always have only Chrome running and I think it's something related with the nVidia drivers too, in my case 372.90 I'm able to complete 1 flight out of 4... don't know what to do.

Hi Jim, again thank you for your help. I always run P3D as an administrator. Now I'm doing another flight with even old scenery.cfg back in its folder and it seems to work smoothly. Last thing to do is to move back also p3d.cfg and see what happens. At this point I really think that you were right and settings were too high, maybe too autogen. Regards, Massimiliano

I've never used a previous p3d.cfg. I'm not moving P3D to another window, maybe I didn't explain myself well :wink: I use P3D in windowed mode so during a flight a can do other things at the same time. If I'm in the P3D window and don't leave it, I don't have any issue but as soon as I move the focus on Chrome or ASN or any other program, P3D freezes. Regards, Massimiliano

Hi Jim, thank you for your answer. P3D is installed in the default folder on a SSD and it's completely excluded by Windows Defender Scan (the only AV I have). As explained on the guide I moved the various files outside their folders and the first flight with the Baron 58 has gone well. Now I'll try to move one by one back and see what happens. Don't think my system is not capable of running those settings because they were exactly the same before the Windows reinstall Most likely is some addon, very hard to know which. Strange thing is that if I keep the focus on P3D I could fly for hours, while as soon as I move it on another window I get the crash. Regards, Massimiliano

Hello all, I hope that someone here could help me because I'm really going mad. P3D v.3.3 crashes everytime I move the focus on another windows, while if I keep the focus on P3D I could fly forever without issues. In years of flight simulation I never ever heard something like that. The error in the event viewer is normally related to kernelbase.dll, sometimes it's menus.dll while a few time it simply closes without any error. I read the guide on AVSIM and I tried anything I could try. Disabled all the addons, lowered the settings, changed videocard drivers and so on, but it still crashes even with default aircrafts and sceneries. My specs are i6700K not OC (never), 16GB RAM, GTX770 and Win 10. They were the same before a system reinstall due to a virus and all was smooth and working. Nothing has changed since then and all other applications included heavy games and 3d software work perfectly. I know that a full P3D reinstall could solve the issue but I'm not so sure and wouldn't try to avoid it, if possible. Any ideas? Thank you!

That's right, but I really can't find any possible use of this feature in P3D.

I'm playing Fernbus Simulator and even if it has some bugs and needs some fixes, it's a good alternative to flight simulation. But I love buses, so... :smile: DTG Train sim is a total DLC oriented simulator, used to play but there's too much to pay to play it good.

I like that DTG listens to our opinions, it's not so common. :wink: But honestly I don't want to tweak my simulator anymore. I'd love it more like all modern games, a simple menu with some graphic options and nothing else. Take a quick look at a random AAA game and you'll know what I'd want DTG FS to be like. I don't think it's up to us try to find the correct combination of tweaks to make it smooth and good looking. My two cents.

Same here with the expansion for P3D. Let's give'em some time to fully back to normal. Major improvements always cause issues. :wink:

Guys it's clearly a problem on out computers, as Kyle Rodgers stated in another thread. The very same problem in the same day of the outage has appeared on many computers just by a very very weird coincidence. We know that when big operations are made something wrong can happen, but don't keep telling us that's because we didn't install DirectX correctly or that's our pc's fault. C'mon PMDG, help us to solve this issue :smile:

I don't think it's DX related, why the activation should be? Anyway I bought the 737 NGX 600/700 expansion for P3D and I installed it on a system where there's obviously the base installed and running without any issue. Furthermore I've also the T7 on FSX and it works fine. I've all the simconnect and all it's perfectly working. I think that's more related with the FlexNet licensing system but honestly I still don't know how to sorting it out. If anyone has ideas it would be really appreciated. :wink:

I've got this error after two consecutive short flights. During the first one, Madeira to Laayoune, all went perfect. I didn't close FSX:SE but I simply set up the aircraft and took off towards Dakar, just like a normal pilot would have done. After about two hours and half I've got the terrain.dll error. My configuration is : Aerosoft A319, Orbx FTX Global and Vector, REX 4 Textures. No sceneries, no weather engine, all settings to max except for water. Even with many more addons installed I haven't ever got this error on FSX or P3D.

Hi all, I have this strange issue with AS2012 and P3D 1.4 (but I had it also with FSX). I'm based in Naples Capodichino Airport (LIRN) but everytime AS depicts the weather from a wrong station, in my case KQNN. If I try to disable the station AS loads the nearest one (KQLQ) as if I was in Naples US and not the one in Italy. It shouldn't be a great issue but, you know, in LIRN I have now 12 degrees and light rain while AS depicts heavy snow and -12°C. Besides the snow ceases suddenly to fall after 2-3 minutes and when I look at the weather it's neither the LIRN one nor the KQNN one. LIRN METAR 02003KT 350V060 9999 SCT040 14/10 Q1020 KQNN METAR 35002KT 0400 +SN FG BKN012 M11/M12 A3003 Depicted weather is 07806KT M11/M12 A3003 Thank you!