February 8, 200422 yr I made flight from Tunis (DTTA) to Dakar (GOOY) yesterday and had a slight issue with the temperatures:Climbing out of DTTA I had a temp of +22
February 13, 200422 yr I've been getting the same thing. I thought it was just a one off, but now that I have started an around the world, every country, tour (currently working the South Pacific) it happens just about every flight.eg. right now I am enroute from Nauru to Marshall Islands (524nm) in my trusty old (new!) 737NG, and after 32 minutes of flight I am only at FL352 climbing for FL410 at a lazy 300fpm. Fuel / cargo weight is just fine for a FL410 cruise (currently 119.2Klbs GW). TAT is 8C and OAT is -23C. Back at FL260, TAT was a hot 24C (didn't check OAT then).My AS2004 flight log shows (for a FL410 cruise level):ANAUNINB 0.5 52 53 94 13 -50.7 450 440 1MARTI 280.1 20 21 94 13 -50.7 450 444 37PKMJ 244.2 20 22 82 26 -51.4 450 433 33 ----- ----- 524.8 71m 1.18HCurrent winds aloft are:FL030: 060/05 (29.0) FL060: 064/06 (23.0) FL090: 068/07 (17.0)FL120: 072/08 (11.0) FL180: 076/09 (5.0) FL240: 080/10 (-1.0)FL300: 084/11 (-7.0) FL340: 088/12 (-13.0) FL390: 092/13 (-19.0)BTW I am running the MR1 beta in offline mode (TAF processing off), but I was getting the same behaviour with the update 1 alpha. I also tried three other wx files with similar results.I guess it simply comes down to two questions: 1. Should the actual winds aloft temps be this high (ie. -19C at FL390)?2. Why do the flight log temps differ so much from the actual temps experienced in flight? eg. -50.7C planned at MARTI, but only -30C was realised (yes, I finally made it to FL410 by MARTI).Gary 9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit MSFS @ 4K Ultra DLSS Performance FG 80 FPS | VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11 Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11
February 20, 200422 yr Bump. Jim/Damien any comment, specifcally re Question 2? 9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit MSFS @ 4K Ultra DLSS Performance FG 80 FPS | VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11 Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11
February 20, 200422 yr OK: something has been introduced into the code causing this to happen. Damian is aware and will be back in a few! I know it's hard to climb to flight level with those kinds of temps and we'll get it straightened out ASAP. Hope this helps,JimActiveSky Support
February 20, 200422 yr Thanks Jim. Just wanted to make sure it was on the 'to do' list, along with the other MR1 beta issues. BTW, since my world tour has taken me into US airspace, MR1 beta has been taking mucho time (ie. up to a minute) to write data to FS, and being non-responsive as an application in the process. Didn't start happening until I arrived at Honolulu from Samoa.Gary 9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit MSFS @ 4K Ultra DLSS Performance FG 80 FPS | VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11 Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11
February 20, 200422 yr The write time is normal for right now. Not sure if that will change.Hope this helps,JimActiveSky Support
Create an account or sign in to comment