Kai-Uwe Wei

Yes, I meant TLOD, sorry for that. I'll try your advice; I had to renew my settings lately so it is possible of course that I have had higher settings before. Thank you. Kai

Just watched that without expert option I get 90FPS only, with expert options choosed I get 400FPS. I can remember I got the higher values without choosen expert modus in former times too. Kai #1 https://www.directupload.eu/file/d/9286/z66zzp6h_jpg.htm #2 https://www.directupload.eu/file/d/9286/i5z6hudw_jpg.htm

I had a try with DLSS-enabler and my RTX4080; here I took ingame FG3X, so I had 90fps with native 30fps setted. After deleting the enabler-file (I couldn't use it for longer because my monitor went out of its specs) auto-fps remains in 90fps when the modus stayed in FG. Only 2X is bringing back my 60fps (30fps ingame and FG2X). I wonder where the 90fps are stored and from which source the tool is reading out the (wrong) measurements. https://www.directupload.eu/file/d/9260/2gjn6o4v_jpg.htm and https://www.directupload.eu/file/d/9260/gxbvmua9_jpg.htm

Sorry for my late replying. Reinstalling and repaIring solved the problem.

Since today autofps doesn't start anymore; I don't know why. I'm on beta 5 FS2024. What informations do you (or me) need for looking for errors? The log-file from today contains this; I tried installing an older version inbetween but it doesn't help.: 2026-03-20 15:05:47.295 [INF] ----------------------------------------------------------------------- 2026-03-20 15:05:47.326 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:05:47.353 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:05:47.356 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:05:47.586 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:05:47.586 [INF] [ MainWindow:MainWindow ] Initial window position set to (103,110) 2026-03-20 15:07:44.686 [INF] ----------------------------------------------------------------------- 2026-03-20 15:07:44.706 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:07:44.733 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:07:44.736 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:07:44.946 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:07:44.946 [INF] [ MainWindow:MainWindow ] Initial window position set to (103,110) 2026-03-20 15:08:02.965 [INF] ----------------------------------------------------------------------- 2026-03-20 15:08:02.983 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:08:03.008 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:08:03.011 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:08:03.216 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:08:03.217 [INF] [ MainWindow:MainWindow ] Initial window position set to (103,110) 2026-03-20 15:12:56.836 [INF] ----------------------------------------------------------------------- 2026-03-20 15:12:56.854 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:12:56.876 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:12:56.879 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:12:57.063 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:12:57.064 [INF] [ MainWindow:MainWindow ] Initial window position set to (103,110) 2026-03-20 15:14:06.136 [INF] ----------------------------------------------------------------------- 2026-03-20 15:14:06.161 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:14:06.183 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:14:06.186 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:14:06.380 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:14:06.380 [INF] [ MainWindow:MainWindow ] Initial window position set to (103,110) 2026-03-20 15:15:18.641 [INF] ----------------------------------------------------------------------- 2026-03-20 15:15:18.658 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:15:18.682 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:15:18.684 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:15:18.869 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:15:18.870 [INF] [ MainWindow:MainWindow ] Initial window position set to (103,110) 2026-03-20 15:15:25.349 [INF] ----------------------------------------------------------------------- 2026-03-20 15:15:25.366 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:15:25.389 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:15:25.392 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:15:25.579 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:15:25.579 [INF] [ MainWindow:MainWindow ] Initial window position set to (50,50) 2026-03-20 15:21:00.730 [INF] ----------------------------------------------------------------------- 2026-03-20 15:21:00.748 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.6 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:21:00.770 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:21:00.773 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:21:00.956 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:21:00.956 [INF] [ MainWindow:MainWindow ] Initial window position set to (50,50) 2026-03-20 15:21:00.963 [INF] [ MainWindow:cbTargetFPSType_Selec ] Default graphics mode is FG 2026-03-20 15:21:00.964 [INF] [ MainWindow:LoadSettings ] MSFS:24 Expert:False Mode:FG ATgtFPS:True FltType:IFR TgtFPS:60 TLODMethod:Sens Tol:5 LOS-C:False TMin:50 TBXtra:false TMax:200 TMtns:False TNightDiv2:True TLODBAlt:0 TLODTAlt:0 CustomOLOD:True OLODB:0 OLODT:0 OLODBAlt:2000 OLODTAlt:10000 RSet:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 2026-03-20 15:21:01.491 [INF] [ MainWindow:DownloadLatestRelease ] Downloaded fresh release data to check for updates. 2026-03-20 15:21:01.519 [INF] [ MainWindow:CheckForUpdates ] Latest test version available: 0.4.6.7-test3. Update option: Silent Updates + Test Versions 2026-03-20 15:21:01.642 [INF] [ MainWindow:AutoUpdate ] New app version available for auto update. 2026-03-20 15:21:01.643 [INF] [ MainWindow:AutoUpdate ] User silently agreed to auto update app to 0.4.6.7-test3. 2026-03-20 15:21:01.674 [INF] [ MainWindow:AutoUpdate ] Auto update in progress. 2026-03-20 15:21:01.685 [INF] [ ServiceModel:RestorePriority ] Priority restore skipped — no priority change was applied. 2026-03-20 15:21:01.685 [INF] [ ServiceModel:RestoreAffinity ] Affinity restore skipped — no affinity change was applied. 2026-03-20 15:21:01.685 [INF] [ ServiceModel:RestoreOriginalPowe ] No power plan change to restore. 2026-03-20 15:21:01.685 [INF] [ App:OnExit ] MSFS_AutoFPS exiting ... 2026-03-20 15:21:06.092 [INF] ----------------------------------------------------------------------- 2026-03-20 15:21:06.111 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:21:06.141 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:21:06.143 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:21:06.342 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:21:06.342 [INF] [ MainWindow:MainWindow ] Initial window position set to (50,50) 2026-03-20 15:21:21.564 [INF] ----------------------------------------------------------------------- 2026-03-20 15:21:21.581 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:21:21.603 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:21:21.605 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:21:21.790 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:21:21.790 [INF] [ MainWindow:MainWindow ] Initial window position set to (50,50) 2026-03-20 15:21:41.462 [INF] ----------------------------------------------------------------------- 2026-03-20 15:21:41.480 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:21:41.503 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:21:41.506 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:21:41.695 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:21:41.695 [INF] [ MainWindow:MainWindow ] Initial window position set to (50,50) 2026-03-20 15:43:58.306 [INF] ----------------------------------------------------------------------- 2026-03-20 15:43:58.328 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:43:58.372 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:43:58.375 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:43:58.654 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:43:58.654 [INF] [ MainWindow:MainWindow ] Initial window position set to (50,50) 2026-03-20 15:51:58.855 [INF] ----------------------------------------------------------------------- 2026-03-20 15:51:58.877 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 15:51:58.906 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 15:51:58.910 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 15:51:59.149 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 15:51:59.149 [INF] [ MainWindow:MainWindow ] Initial window position set to (50,50) 2026-03-20 16:08:54.645 [INF] ----------------------------------------------------------------------- 2026-03-20 16:08:54.669 [INF] [ App:InitLog ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 2026-03-20 16:08:54.701 [INF] [ App:OnStartup ] Test Mode active 2026-03-20 16:08:54.705 [INF] [ ServiceController:Run ] Service starting ... 2026-03-20 16:08:54.962 [INF] [ MainWindow:MainWindow ] Virtual screen coordinates: (0,0) (3840,1600) 2026-03-20 16:08:54.962 [INF] [ MainWindow:MainWindow ] Initial window position set to (50,50) mfg Kai

Thank you☺️ Kai

The ORBX-citypack of Frankfurt - is it still necessary after WU18? Just asking regarding performance and compatibility reasons. Kai

hello, after installing Tegel X I recognized that I have zero AI-traffic there. I've seen that in all three Berlin-ports (EDDB, EDDI and EDDT) there is no AI-traffic at all. Only cars on the roads. In other airports traffic is well to be seen. I 've installed ORBX base, openLC, vector, Megaairport Berlin-Brandenburg, Tegel X, Simmershome airports surrounding Berlin. But even without all of these (stock using) there is no traffic here. There must be a responsible file for AI-traffic Berlin which seems to be excluded. I dond't like to install the whole sim again because I don't even know the reason why and so will be possible to put the error into the new installation again. I use P3Dv3.2. thanks Kai

hello, When I switch from VC to the exterior view I feel that one view doesn't exist. I mean the first view I have in other planes when I switch to outside. If I am outside there (in other planes) I can press "a" three times to have the bird perspective. In the dash only twice, so the first view is missing. Thats a pity; this view allows a very smooth panning around the aircraft. The second view is very abrupt in stopping panning. So is there a way to get back this special first view? Kai

SLI-mode- -does it work now like in 2.5 before or even better? Kai

ah I see, thank you very much! Kai

hi Barry, yes, I see what you mean and I'll try this. Thanks! with greetings Kai

hi Jim, you don't have understand me. I try to explain the situation again: If I start the FSX and the main window is open I saw as aircraft the 737NGX, AirBerlin, ready to be at the gate in Tegel. This is my saved startsituation. If I start the FSX I'm at the gate in the plane, can make, for example, groundconnection (battery is on of course) and after that I can switch on the logo light and the landing lights too and the logo is lightened and the landing light come from within the wings. If I load in this situation another 737NGX (AA for example) the new aircraft will be loaded again cold and dark. Thats okay. So now I make the same procedere as above and I have my lights.Now: I close the FSX. I start it again, the same main window BUT: now I choose the AA-Livery first, in this window. Not the AirBerlin first. After that, at the gate in Tegel I do the same workflow again as above described. But now there's no logos illuminated nor the landing lights in the wings. Do you see? Everytime I have to load first the AirBerlin-Livery if I'd like to fly at night. No matter which airport or country. with greetings Kai

hello, something with the 737NGX make me wonder and I'll try to explain what I mean:in my FSX everytime I start with the 737NGX AirBerlin with a cold and dark cockpit. This is saved as the default flight and the c&d cockpit is saved in the FMC too. If I load this plane in the evening everything works alright. But if I use another livery the logo and landinglights are not illuminated. Only if I load first the airBerlin-livery and after that the other livery the lights work. What is the reason and how can I solve this problem? thanks Kai

hello, I have some trouble with logo and landing lights: the 737NGX stands in Hobart, Australia late at night, 3.30 a.m. With Qantaslivery. Now I wake up the plane, Apu, after that engines. After successfully starting I switch on the Logo and Landing lights. But the logo remains dark and the landing lights make only a white cone in front of the plane but there were no lamps, illuminated in the wings. For comparison: if I try this in Germany, Tegel with an AirBerlin everything works fine and if I put a Qantas to Tegel it works fine too! I try the Qantas as second machine, so I have to load everything again before I can put the lights on but it works then. Are there problems with australia? thanks Kai

my systemrestoring is not corrupted; I only had installed too much between the Jetstream and recognizing that its'nt working. I use Vista 64 and the oldest point was just this one after installing the BAe (Murphy greets). So my question is: deinstallation yes, that's possible of course. Is it nessessary and possible to delete some entries in the registry or does PMDG offer a cleaner?with regards Kai

hello,I have a strange problem (behaviour) of the Jetstream: I bought it about a month ago. There I used Win7. The aircraft was installed and activated and worked fine. Now, for some reasons I went back again to Vista64. I installed the aircraft too and if I try to load it everytime the FSX crashed to desktop (heavy error...). The first time it took place already when I activated the software and I don't know if the problem starts here. I can't set back the systemsettings to a point before the Jetstream-installation. I install FSUIPC 4.53 registered. It crashes immediately when the picture of the plane comes; the mousepointer turns into a circle and then FSX goes down. How can I get it out of the registry completely for a new installation or how could I resolve this problem?thanksKai