EliGrim

This is so weird! No idea what is wrong on my end and why it only relates to KLGA.

It happens with every schedule, custom and RT with this DLC.

Depending on the game engine used and optimization or missing optimization, this is what you typically try to do if you experience stuttering in the game or very unstable frame rates. Open Task Manager Click "Details" Tab Right-click "tower3d.exe" Click "Set affinity" Normally your PC handles the use of the cores very well, so that fiddling around at this place is not necessary and can be counterproductive in many cases. It limits the app to using the selected cores/threads even if they are already under load. I did it temporarily because I was curious if there was a change in the described behavior. Unless you're using an app that is poorly or non-optimized for multicore processors, I wouldn't recommend making changes here. Edit: Apart from gaming, there are some useful scenarios; VMs could be an example. In my opinion, the "typical" Windows user is better advised to set priorities, if necessary, instead of manually assigning cores.

Just tested it. This is the complete schedule, played in 1x speed: ATL, LGA, 320, DL, 1001, 10:01, 12:00, 1, DL ATL, LGA, 717, DL, 1003, 10:07, 12:00, 1, DL ATL, LGA, 735, DL, 1005, 10:13, 12:00, 1, DL LGA, ATL, 739, DL, 1002, 12:00, 10:04, 1, DL LGA, ATL, 73H, DL, 1004, 12:00, 10:10, 1, DL LGA, ATL, 320, DL, 1006, 12:00, 10:16, 1, DL After I pushed DAL1002 back and sent it to the runway (about 3 minutes in game), I got the blue screen with the Page File Warning and the PC shuts down. After the restart, the CPU was still at 73 °C / 163 °F. I played EDDM for 2.5 hours straight earlier this day without any problems. Edit: Even if the CPU gets hotter all the time (KLGA only) the load never exceeds 35%. Restricting the Tower!3D Task via the Task Manager to threads 0-3 has also not caused any change. This is a mystery to me and I also don't know what the flooding of the Page File causes.

I used the vanilla RT schedule at 1100h, 1500h and 2000h or 2200h.

Hi @hexzed, yes, JFK also stutters for me as soon as I use DBRITE or ADIRS on a second monitor. Hi @DeltaVII, thanks for your reply. I used UNetbootin to use SystemRescueCD on a USB Drive to check for hardware errors, without result. eventvwr.msc (Windows Event Viewer) shows the crashes (shutdown), but otherwise no abnormalities and a RAM test using mdsched.exe (Windows Memory Diagnostic) doesn't detected any problems. I use dust filters under the magnetic air inlet grids (I don't know if this is the right English translation) of the PC case. However, I have checked that my PC is clean. I also made sure that the thermal paste (ARCTIC MX-4 2019) is not dried out. I successfully ran CPU, GPU and Drive stress tests and benchmarks using CINEBENCH, 3DMark AE and 7-Zip. Tower!3D Pro and all AddOns were uninstalled, system and registry cleaned and then reinstalled before I replayed all DLCs (including KLGA). T!3D Pro typically uses ~1.5 GB of dedicated GPU memory at (of course) near maximum 3D utilization (96 - 98%), ~5.5 GB of system memory, the CPU temperature rarely exceeds 63 °C / 144 °F, and the CPU core power draws about 20 W with peaks of up to 63 W. Once I play KLGA these values explode within minutes. And it is EXCLUSIVELY the case with KLGA! I think it's fair to say I'm completely at a loss!

Hello everyone, I bought KLGA quite a while ago, but I only got to try it yesterday. At first I noticed that the movements are faster than at other airport DLCs. The aircraft models move so fast that it is comparable to twice or maybe even four times the speed at other airports. Personally, that's very welcome to me, but... At the same time T!3D Pro overheats my CPU while playing KLGA and overflows the Windows Page File. After a few minutes this results either in a safety shutdown of the system or in a crash with blue screen and Page File warning. Changes to the Page File, such as reducing or enlarging does not bring any change. A deactivation of the Page File results in a Windows system hold with blue screen due to insufficient RAM or an even faster emergency shutdown of the PC due to overheating. CPU, GPU and case are dynamically cooled. Typically the case fans are at 100% when 60 °C / 140 °F are reached. The CPU cooling is at over 71 °C / 160 °F at 100%. Running all fans manually at 100% (2200 rpm CPU - 140mm, 2900 rpm system fans - 5x 120mm - 2x front in, 3x top/back out) is merely loud, but does not prevent overheating when I try to play KLGA. Today I tried the base game airports and all DLCs in my possession. Only KLGA has these problems. Other DLCs or other CPU-intensive games like Planet Coster don't overheat my system. My Specs (as detailed as possible to avoid a back and forth): - Windows 10 Pro v1903 (latest build, latest updates) - MB MSI B350M PRO-VDH (latest Bios) - CPU AMD Ryzen 5 2600 (6 cores / 12 threads, 3,4 / 3,9 GHz, not OC) - GPU MSI GTX 1060 GAMING X (6GB GDDR5, 192-bit), (core clocks 1784 MHz / 1569 MHz, memory speed 8008 MHz, not OC) Latest GeForce Game Ready Driver v441.08 (10/29/2019) installed - RAM T-Force Nighthawk 32 GB DDR4-3200 (running in 2999 MHz profile with 1.32 V) - SSD (240 GB) for Windows, SSD (250 GB) for Temp, Data and Program Cache, SSHD (2 TB) for games - Latest Steam Version of T!3D Pro (SP3.3c), RC for KLGA (and others), RT sp6v17 Has anyone experienced anything like this or has any idea what I can do? Regards EliGrim

Haven't @runduur and @Michi10 reported something similar for EDDM, which is also a @nyergesdesign DLC?

Nope, not really. Just downloaded the latest version of the RC Master List, saw this thread and thought: Well, why not?

You need to understand the differences between ICAO codes (used for the technical aspects of airline operations), IATA codes (used to identify an airline for commercial purposes), callsigns (with that I mean the telephony designators) and airline (or operator) names. Using your first entry as an example: "tcx Textrol KESTREL" "TCX" is the ICAO code with the telephony designator "KESTREL". This entry is included below, with the IATA code "MT" and the airline name "Thomas Cook Airlines". The same applies to the other entries. If you took a look at a flight ticket, you might see that it is for example for flight UA 419. UA (IATA) then stands for the operator (United Airlines) and 419 is the flight number. An air traffic controller will most likely have UAL419 as callsign on his/her screen. UAL (ICAO) and 419 as flight identification number. (The flight identification may but does not have to match the flight number.) ATC will then call the flight with the telephony designator (gernally referred to as callsign) + identification number. Here: UNITED 419

So the 10 EDDM CARGO liveries are in the LFPG RC? I may be mistaken but I can't read that from the first post! What I get from the post is that EDDM RC will be updated along with 10 bonus CARGO liveries (without specifying a timeframe) and that RT will be updated with the release of LFPG (which was the case).

Let's take it this way: It makes the game a better challenge! 😁🙄

That should solve your problem. With every new airport DLC a new version of Real Traffic will be released. This version has to be downloaded and installed for Real Color to work for the new airport. Real Traffic does not need to be uninstalled; just reinstall the new version.

Yes and no. It's the other way around. (Sorry I didn't make myself clear.) The landing plane QFA132 on runway 09 hasn't completed its landing or passed the intersection before you gave clearance to QFA444 on runway 16. In that moment, for the game runway 16 was not clear. In the real world it may not be a problem, but the game doesn't differentiate whether to start from before or after the intersection. It only asks if the runway is clear or not. Only if a take-off or landing process on the crossing runway (here: 09/27) is completed or the intersection has been passed the other runway (here: 16/34, your starting runway) is clear for take-off or landing. I hope that makes it a little more understandable. Otherwise @hexzed or another user will surely step in, because English is not my first language.

I wouldn't necessarily call it Bug. It is simply not considered in the programming that with crossing runways, airplanes start their take off procedure behind the intersection. For the game it makes no difference whether you roll onto the take-off runway in front of or behind the crossing runway. Your runway is clear if: a) the take-off or landing process on the crossing runway is completed. (You get the -successful takeoff/landing- message plus your 10 points.) It doesn't matter if this happens before or after the intersection. b) (as @hexzed wrote) the starting or landing plane has passed the intersection. In the case of a), however, there is the possibility that minus points will still be awarded if there is no way to exit (for the arriving aircraft) in front of the intersection and the aircraft passes over the crossing runway while you have already given take-off clearance on your starting runway.

I don't know what is causing this issue, but it is generally possible to use STRIPS in a separate window. I hope someone can help.

@707FAN Here is something quite interesting for your chart: https://steamcommunity.com/app/588190/discussions/0/1639793203780808014/

Same for Win 8.1, 8 and 7.

Done! It would be great if you give a short feedback if it's working now.

Unfortunately I cannot test the schedule myself. I hope that another user has an idea and can help. Leider kann ich das Schedule selber nicht testen. Ich hoffe, dass ein anderer User noch eine Idee hat und weiterhelfen kann.

@danilars The log file refers to some non-existing airport codes, like E70, which is an aircraft type, and flights with unassigned terminals, which according to Braf's files shouldn't happen either, as I understand it. That's a bit odd! Did the airport load before you tried Braf's schedule? If so, please try this: - Delete the following files in the folder ..\Steam\steamapps\common\Tower 3D Pro\Extensions\Airfields\LFPG lfpg_airlines.txt lfpg_airplanes.txt lfpg_airports.txt lfpg_gaandlocaltraffic.txt lfpg_schedule.txt lfpg_terminal.txt - Reinstall Real Traffic (RT_Tower3D_PRO_sp6v15.exe). - Make a backup of the folder LFPG. - Copy the files from the ZIP attachment (LFPG_by_Braf123456.zip) into the LFPG folder. (Braf's schedule) Overwrite the existing files. - Test if the schedule can be loaded. If the airport still does not load, copy the files of the second ZIP attachment (LFPG_by_Braf123456_split.zip) into the LFPG folder and overwrite existing files. Decide which files from the download you want to copy, depending on whether you want to start the game with a time in the morning or in the afternoon. If it still doesn't work, please attach the new output_log.txt. Die Protokolldatei bezieht sich auf einige nicht existierende Flughafencodes, wie z.B. E70, bei dem es sich um einen Flugzeugtyp handelt, und Flüge mit nicht zugewiesenen Terminals, was nach den Dateien von Braf auch nicht passieren sollte, zumindest nach meinem Verständnis. Das ist schon recht seltsam! Wurde der Flughafen geladen, bevor du Brafs Zeitplan ausprobiert hast? Wenn ja, dann versuche es bitte damit: - Lösche die folgenden Dateien im Ordner ..\Steam\steamapps\common\Tower 3D Pro\Extensions\Airfields\LFPG lfpg_airlines.txt lfpg_airplanes.txt lfpg_airports.txt lfpg_gaandlocaltraffic.txt lfpg_schedule.txt lfpg_terminal.txt - Installiere Real Traffic erneut (RT_Tower3D_PRO_sp6v15.exe). - Erstelle ein Backup des Ordners LFPG. - Kopiere die Dateien aus dem ZIP-Anhang (LFPG_by_Braf123456.zip) in den Ordner LFPG. (Brafs Schedule) Überschreibe die vorhandenen Dateien. - Teste, ob der Zeitplan bzw. der Flughafen dann geladen werden kann. Wenn der Flughafen immer noch nicht lädt, kopiere die Dateien des zweiten ZIP-Anhangs (LFPG_by_Braf123456_split.zip) in den Ordner LFPG und überschreibe bestehende Dateien. Entscheide, welche Dateien aus dem Download du kopieren möchtest, je nachdem, ob du das Spiel mit einer Zeit am Morgen oder am Nachmittag starten möchtest. Wenn es immer noch nicht funktioniert, füge bitte die neue output_log.txt an.

To narrow down the problem it might be helpful you would attach your log file (output_log.txt - after the error has occurred and you have quit the game) from the ..\tower3d_Data\ folder in this thread. Um der Sache auf den Grund zu gehen, könnte es hilfreich sein, wenn du deine Logdatei (output_log.txt - nachdem der Fehler aufgetreten ist und du das Spiel beendet hast) aus dem Ordner ..\tower3d_Data\ in diesem Thread anhängst.

I can't check it right now, but I'm very sure that the ICAO code is used in the file structure for CDG. Therefore, the files would most likely have to be renamed to: lfpg_terminal.txt lfpg_airlines.txt lfpg_schedule.txt Ich kann es gerade nicht überprüfen, aber ich bin mir sehr sicher, dass der ICAO-Code in der Dateistruktur von CDG verwendet wird. Daher müssten die Dateien höchstwahrscheinlich umbenannt werden.

You need to assign the intersect with "at [taxiway]". At Pushback: [callsign], pushback approved, expect runway [xx], at [x] After Pushback: [callsign], runway [xx], at [x] or [callsign], runway [xx], at [x], via [xyz]