longhaul747

I don't think I got that far... I was going to do it but real life priorities escaped me and slipped into the forgot about category. Because of my PC being used by multiple family members it is not practical having rudder pedals so I have to use the keyboard for some stuff. 0 and Enter on the numerical keyboard have no affect on the nose wheel tiller. 5 on the numerical keyboard should center the rudder and nose gear. They are linked in the options under the EFB but it does not seem to have any affect. This process works fine on the F28 so whatever it is it's something in the F70 that is bugged up!

Keyboard nose gear steering still broken! Must be something I am missing?

Hopefully the next update fixes the keyboard ground steering issue.

I think the problem is limited to FS2024. For now FS2020 might be fine! One of the sim updates killed the Phoenix area and it's likely an easy fix but for whatever reason Asobo can't be bothered. It takes a bit of digging but it's a commonly logged issue!

Yeah it's most noticeable when you take off from PHX heading West and you see a mostly generic city on climb out. However I am pretty sure the whole Phoenix area is messed up to some degree. Apparently it might come down to a simple missing file on Asobo's side and likely an easy fix. Something about a missing TIN file or something along those lines. For some reason Asobo can't be bothered to fix it and the latest SU6 beta has the same issue.

Sorry for the somewhat late reply. I got a surprise 11 hour shift today but now looking into this further. Below is a picture of the problem... Most of the buildings are generic but a few a are looking okay. These might actually be the Samscene scenery coming through after all but major landmarks like the Chase Stadium and some others are just generic. I posted a picture below.... At work during a few minutes of downtime I searched Google and it definitely looks like a bug. Unfortunately Asobo is taking it's sweet time fixing it which is unfortunate. I am pretty sure it was working fine a couple of months ago if not soon than that. I don't think Samscene can fix it unless they decide to do the whole city. Hopefully it gets fixed soon!

I have been flying in and out of PHX lately and I have noticed that my downtown Phoenix is all messed up. It seemed to be working fine the last time I flew there a few months ago and I have not changed anything. The downtown core and possibly some other buildings are all messed up and show as generic buildings. I have the Samscene Modern Cities Vol 4 which contains Phoenix and the Glideslope Pro PHX installed. Uninstalling and reinstalling these products and a combination of removing one but not the other has failed to yield any desirable results. Its almost as if one of the Sim Updates killed the Phoenix area and as of right now you can't fix it or one of the scenery packages needs updating. Everywhere else I fly into looks fine so far but PHX area seems broken.

I am putting my vote in for the 1-250 longer variants as well. I believe at one point they hinted at possibly doing it but it was far from being firm.

Tonight I downloaded and installed the F28 from the Just Flight website. It had been a while and it has seen a few updates and FS2024 compatibility since last time I played with it. My main purpose was seeing if the nose gear steering was working on that model? They are pretty similar and probably the same developer. The nose gear steering works properly on that model. The EFB is fairly similar to the new F70 and when I go into Aircraft and Settings I see the same option called Rudder Access Steering. on the F28 this button is working properly but not on the F70. I think its pretty safe to assume this feature is currently broken on the F70. I will report it to Just Flight very shortly! I also purchased it as package so I have the F100 as well. I have not tried that model yet but it would be interesting if this feature works on the F100 model. It's also possible but not likely it was a corrupt install. So I might just try and uninstalling and reinstalling it just to double check. Edit: Just another little update. Installed the F100 and it is doing the same thing as the F70. It is likely an issue with this particular build. Probably an easy fix if they know about it. So I am reporting it!

I am about to do a flight from PSP back to PHX in the F70. Checked the key maps and looked for conflicts but it all looks good. For whatever reason Just Flight messed up and does not allow to use the keyboard for nose wheel steering. It should be a pretty simple option at least in the EFB. The option is there but does not actually work! Checked the hydraulics and the control lock again just in case and it is all good! I can steer it taking my mouse and hovering it over he nose gear tiller but I can't see out the window at the same time making this worthless. Needs another hot fix addressing this. Will shelve it until this is fixed!

Control lock is off. I did check that. Changing the setting in the EFB makes no difference on my install (FS2024). I don't think it is the CH Flight Stick Pro. I just don't think The Just Flight Fokker allows keyboard steering. Obviously if you have rudder pedals setup correctly or a tiller on your joystick it will likely work but not if you try and use the keyboard. The option to turn it on in the EFB should allow it to work but for some reason does not! At some point today when I have time I plan to check my key bindings making sure everything is okay there. Never really touched them and 90% set to default. All the other planes seem to work just fine. I remember a somewhat similar issue with the F28 that magically fixed itself after an update I think. I memory serves the nose gear steering worked but would not center itself when you centered the rudder.

Picked this up last night and just completed my first flight in the F70. Taking off from PHX despite the heat was rather sporty of coarse I only had enough fuel to reach PSP. Once above about 7000 feet it was noticeably less powerful and it took a while to reach 26000 ft. Sort of reminds of the British VC10 in design. It was not so much the engines doing all the work but an advanced wing design that created such great field performance. Speaking of VC10 we definitely need those in the sim. Only issue I had was I did not have any nose wheel steering. I have a simple old but trusty CH Flight Stick Pro and use the key board for some things. 0 and ENTER on the numerical pad control the nose wheel but for some reason on the F70 it is not working. I see an option for Rudder Axis Steering in the Aircraft section and Settings in the EFB but turning this ON or OFF does not make any difference. It must something simple I am missing? This nose wheel steering issue is limiting my enjoyment of the product so hopefully it is something simple or it is fixed soon!

Just completed my SEA-ANC flight and no CTD. It was pretty smooth sailing until on final I got one of the famous FS2024 memory error pop ups and it started to get little pauses when I changed views but luckily it never CTD on me. I think it might need more testing to know for sure but I think its extremely positive it did not CTD on this flight and after the update. Actually the 1st successful flight with SP1.

I am taking this up for a SEA-ANC flight checking to see if the CTD issue I have been having is fixed? I have noticed so far the plane feels a little less resource heavy on my machine. This certainly helps one way or another I would think! Please Stand By......

Yes, Unfortunately very true!

Unfortunately I got another CTD about 6 hours into the flight. I was over Greenland so not much more to go. This time it was sort of self induced but was going to happen any as soon as I started doing stuff anyway. All was well so I went to an exterior view of the aircraft. The sim stuttered and paused for a second and I got a pop in the audio. At that point I know I was doomed. Went back into cockpit view and it was pausing and stuttering pretty bad but still working. As soon as I dialed in a higher flight level on the AP it froze and about 5 seconds later shut down. This is a classic memory leakage issue. Probably related to the bug already reported. Different systems will react different with the bug but it will probably be fixed when the fix the official bug that has already been reported for FS2024. I plan to do some more debugging and joining the discord so I can report it and read about others with the issue. I don't think I am alone though.

So far so good...4 hours 10 minutes in. I have not gone this long without a CTD so far on SP1. Currently over Hudson Bay Canada.

With promotional videos like this coming out it can't be very long now!

Right now I am doing flight #4 as an acid test. Hopefully clearing the WASM folder helps! All the flights so far have been somewhat similar but the crash at the CTD was at the 2 to 2.5 hour mark each time. First was SEA-ANC and the second flight was SEA-KEF. Third flight was KEF-SEA and same results each time. Most of the time I am a pretty lazy flight simmer. Because of time constraints I usually just program DIR routing and not so much with way points. I don't think its a lot of way points causing the issue. I am going with strictly a memory leakage issue of some sort! Right now as I type this I am attempting to do SEA-KEF again. Currently about 57 minutes into the flight. I hope its now stable after clearing the WASM folder but I won't know for about another 2 hours. If not I will attempt to debug with the information above and I need to join the iFly discord anyway. I would not be entirely shocked if my system is now reaching a point that with the higher detailed scenery and airplanes coming into the market it will have a harder and harder time. Its a 2021 upper mid level build. CPU is surprisingly still current but my graphics card is showing its age being a 2070 Super. A new system is in my budget forecast for next Fall but it will only happen if the stars align. Lately they have not been aligning well this year. Amazingly despite my systems age it runs FS2024 really well. In fact I see better performance than what some people get with faster systems. So it is hard to say but I would like to be able to crank my display settings a bit. Some of it is on high but other settings mid level.

I did after a bit of searching find the WASM folder for the SP1 version of the iFly MAX 8. Microsoft.Limitless_8wekyb3d8bbwe\WASM\MSFS2020\ifly-aircraft-737max8 It's in the MSFS2020 folder even though it is installed in FS2024. I cleared it and rebooted the simulator and reloaded the iFly MAX 8. Everything was working fine but the real acid test will be tomorrow when I try a long haul flight again. I am also getting an Asobo Crash Log and its definitely something with the iFly MAX 8. It's mostly gibberish but I see a bunch of WASM related error dumps in the log. So hopefully clearing the WASM files and having the system rebuild them under the SP1 hopefully makes a difference. It has with some models in the past!

I did delete the old liveries and install the updated ones. So its likely not that I would think. Now the WASM folder is interesting and I have not deleted it but wanted to do that. This does feel similar to some types of WASM crashes I have seen. Now the irony is where is the iFly WASM folder? I found instructions for locating it but interestingly the iFly MAX was not listed in there. I believe it was in the past but I wonder if they somehow moved it?

I did read this bit of info that iFly put out. Its currently set for auto and I don't launch it manually. It loads automatically when I load the aircraft as recommended. It seems at least on my system the memory issue is still present even when following iFly's recommendations.

Unfortunately I had my 3rd CTD at the 2 to 2.5 hour mark with the iFly MAX 8 in FS2024 today. Last night I completely uninstalled and reinstalled it in the hopes it would not happen again. This not something that usually happens on my system with other aircraft and the iFly MAX 8 before SP1. It is my opinion something is still a bit haywire with the FS2024 install at least for some users. This has been reported by some others out there. I do know its an experimental build but not sure if this specific issue is related to that? Its possible this new build in SP1 is just very resource heavy and many mid level systems just give it up after a period of time. Hopefully someone else out there has found a fix for it? For now I am not going to fly with it much until an update comes out that hopefully addresses the issue.

I uninstalled and reinstalled the MAX 8 today in an effort to cure the 2 hour CTD in FS2024 that has now happened twice. I noticed I forgot to delete the previous ifly-aircraft-data folder during the first uninstall of the older version for the new install of SP1. I kind of doubt it has anything to do with it but just maybe it does? I will find out tomorrow when I try yet another long haul flight. Yesterday it CTD 2 hours into an SEA-ANC flight and today it did it again right at the 2 hour mark on a SEA-KEF flight. Usually when I am doing something else like hitting a switch or or changing views. The whole FS2024 program just disappears instantly.

It's probably going to be another year at least for the MAX 9 at this rate. The MAX 7 and 10 can wait since they are not certified and in service yet but the MAX 9 is the work horse and more popular than the MAX 8 in US skies at least. I hoping to see iFly introduce it a bit sooner but it is what is what it is. Maybe with a bit of luck it will come sooner? The native version for FS2024 just might make it out in the next few months. After that work begins on the MAX 9. Not sure if it is still this way but back in the old days once you have the systems finalized the rest is just modeling. Of coarse the models are a lot more detailed but I imagine perhaps a 3 or 4 months after the FS2024 MAX 8 is released? Just maybe the MAX 9 will make it time to for Christmas? We will just have to see!