longhaul747

Against my better judgement and the desire for a Classic 737 I decided to give this plane a try last night. I did not have any trouble with the install or setting it up but the rest of the plane is making me really question this purchase? Despite looking at several pictures of this model on the internet and thinking it was visually okay once I had it installed on my system I actually find the exterior model a bit off. The angle of the tail slope for example just does not look right? Maybe it is just me or my curved monitor but it does seem off a bit. Also the 400 model looks a bit short in length but maybe it is just the tail curvature that is throwing it off? I see they are working on a V2 so hopefully that improves the exterior model! 2nd issue is despite multiple tries I have not even managed to get a proper flight going. For the most part systems seem to be working but for whatever reason my throttle levers refuse to move together. The left throttle lever works properly but the right one stays with the left one for the 1st quarter of the way but but slowly falls behind the left lever and refuses to go beyond about half. So you have a serious asymmetric thrust issue. On one flight I managed to keep it on a runway and takeoff but keeping in the air was a real challenge. I have the most basic setup with a CH Flightstick and use the keyboard for a lot of stuff. Like F1-F4 for throttle control using the default FS2020 key maps since that is what I am used to using but fly in FS2024. When I press F3 on the keyboard I see no reason why those throttle levers can't move evenly. When I hold the F3 key down I notice that the right side throttle lever shakes like it is trying to move but some other force is holding it back. I checked for key binding conflicts but don't see any. For now I just sort of shrugged it off and shelved it for now. Also gave myself a lecture that I need to trust my instincts next time. Some things about it impress me and I feel it is so close yet many stupid things make it so far away. I will likely revisit it after the next update(s) but for now it is still very broken.

Oh that is interesting... I did not really give it a thought that it was related specific to the iBlueYonder PDX release. Kind of glad it is the only airport I noticed it for now but it is annoying enough I hope gets corrected. The developer was fairly active out there a while back. Hopefully he knows about it!

A couple updates with some of the issues I was experiencing with SU6..... The first ones was blurry/ghosting gauges especially on gauges that move fast like altitude and airspeed indicators. Primarily digital display styles in glass cockpits. I had this problem when FS2024 first came out that was really bad. I found a fix that you edit the User.cfg file inside FS2024 and it fixed it and it stayed fixed until SU6 came out. The blurry/ghosting gauges were back. Not as bad as it was originally but still bad enough to be annoying. I first thought that the fix was unfixed during the update and I can simply go in there and fix it again but this time the old fix was still in place and no longer working. Googling it I tried running in TAA and the sim looked absolutely superb as in almost a born again religious experience type of look. Unfortunately, performance on my now dated system was so horrible it was unplayable. Flickered horribly and got like 1 FPS. I have to run in DLSS on my system. If I do performance is great! The fix actually ended up being pretty simple. Below the DLSS option in the graphics settings is an option called NVIDIA SUPER RESOLUTION. Changing this setting to anything other than AUTO seemed to solve the blurry/ghosting gauges. I first tried QUALITY and things looked really sharp but performance suffered. Not nearly as bad as it did on TAA but still not really good. I next tried PERFORMANCE and the blurry/ghosting gauges still looked really good. I would say within 95% the same as Quality but system performance was 100% solid again. A new computer is in the budget forecast for this Fall or Winter and I hope the new system will be able to run in TAA like how my system runs in DLSS but not sure such an animal exist just yet? Another odd issue was when I was taxiing around PDX airport at night in the PMDG 737NG. My interior cockpit lighting kept on flickering on and off that varied in intensity depending on how bright the airport apron lights were. Once airborne the flickering stopped. Interestingly when I landed at SEA the cockpit lighting was not flickering no matter the intensity of the apron lights just like it did before SU6. Ironically this issue has not repeated itself in FS2024 since. So I might have been some sort of odd anomaly perhaps from millions of users trying to check out SU6 at the same time. Now that my issues are solved I am very impressed with SU6. Well, PHX and surrounding area needs fixing but I am thinking it will be fixed soon..I hope!

SU6 looks pretty good and I feel my performance has improved a tad. I agree the clouds look better! However a few issues have I that I did not have pre update. When flying the PMDG 737 at night and taxiing around the airport my panel lighting would randomly turn on and off. Once airborne this was not an issue. I don't remember it doing that before. Will have to check the PMDG forums and see if it has been reported as an issue? 2nd issue is my gauges seem to be pretty blurry again. Not as bad as before but definitely more blurry than before. Also it sort of looks like its frozen in a blurry sort of way. Kind of hard to explain but it was solid before. I did have this issue way back but someone posted an edit that fixed it but it seems back again. 3rd the on going issue of Phoenix area and a few others not far away apparently not working. This is a travesty and an insult to the flight simmers in those areas. I thought by SU6 it would be magically fixed but it is not. This needs to be fixed in my opinion!

Out of curiosity I loaded up Phoenix Arizona. It had been a few months since I flew in out of PHX. Sadly Phoenix is still broken! For some reason and I believe it just happened randomly a while back the photogrammetry scenery for the Phoenix area just disappeared in FS2024. I believe it still works in FS2020 but in FS2024 it looks pretty awful now.

I just loaded up the new SU6 briefly after it installed. Noticed a few things right off that bat. Textures look much sharper very sharp and things look much cleaner. In the new 707 before it took a few seconds for the gauges to properly load but it now loads instantly. Can't yet comment on raw performance but from the brief look it looked unaffected. Tomorrow morning I plan to do a fast trip like SEA-PDX in the PMDG 737 testing it out!

I still want to pick this up but I am going to wait for it to be available on the iniBuilds website and depending on how well it tracks I might wait until the A220-100 comes out. I am always nervous when a developer basically promises a project and for whatever reason just decides not to do it or it is taking so long I will probably die of old age before it gets here. If I somehow had assurance that the A220-100 would be out in a few months I might bite now but I have not seen anything that is it coming that soon. Please correct me if I am wrong?

Still down in the US West Coast as of a minute ago. A friend located in Norway could not get on at first but just got in now! Seems some European locations are coming back hopefully!

The Irony in all this is I got a message on my cell phone that FS2024 is now ON SALE 🤣 Maybe that is why the servers are not working? I doubt it! I meant what I said about this folks who said it was not a big deal on this forum. It really does help you get thru this. I actually went out at 7am this morning and pulled out my motorcycle and put a coat of wax on it instead of sitting on my bottom playing FS. If those servers are not back on I might just give up on MSFS for good and ride off into the sunset. Probably come back and buy X-Plane. Need something to do during the winter!

Just tried again this morning...still down as of 9:20am Pacific Standard Time in Seattle Washington. Now a 13 hour issue! I really admire those folks who say it is not a big deal. I guess in the grand scheme of things it is not a big deal but this is total BS. A big company like M$ should have back ups.

Yes, servers have not worked since 8:45pm Pacific Standard Time in Seattle Washington USA. Hopefully it is just maintenance and will be back up tomorrow morning!

Picked up the Bijan's Season Enhanced utility this evening but unfortunately I can't test it out since M$ is currently experiencing server issues. It looks like the utility is completely automated I don't see a way to launch any sort of outside program. It just sits in my Community2024 folder!

I was not aware that only I can see the pictures hosted by imgur. I put them in PostImages so hopefully that works. Hopefully this works... Looks like this is a bug in FS2024 and FS2020 but FS2024 is apparently a lot worse. Within the perimeter of the airport everything is fine but trees galore outside of the airport and even on the mountain tops. After much research after posting this thread you have a few utilities that help this situation. The one mentioned above by Bijan and another one available on the Marketplace called Real Trees Size by 4Simmers. Both products seem to fix the problem well. As far as tree sizing they probably do the same exact job so work the same. Bijan gives you additional features that will be useful plus I have purchases his products in the past with favorable results. I think I get a discount from those other purchases so I will likely go that route. Some localized tree fixes on flightsim.to but nothing for the Cook Islands or Rarotonga specifically!

I picked up this airport for some South Pacific Island hopping and installed it in 2024. Airport itself looks fabulous but just beyond the perimeter fence of the airport is many excessively tall trees. In fact landing from the west one tree is so tall you end up hitting it as you are about to touch down. At first I probably would not be annoyed about it except when I see photos of this scenery package it hardly contains any trees and the few that do show are not tall at all. So I am thinking something must be messed up with my install but not sure what? The latest update from Kiwiflightsim supposedly fixed the tall tree problem but it is still present in my install. I don't have any aftermarket tree packages installed. It is all default unless another scenery package is causing the conflict but I don't have this issue anywhere else. In fact the entire island seems plagued with over abundance of trees and some of them are very tall. Some pictures of what I am seeing.... What they show in the product pictures and looks about right..

I got a response from Just Flight over the steering issue I am having. It has been deemed a bug and they will fix it in the next update or two. A hot fix update is coming very soon and it might make that one but if not update 1.3 is coming not long after that.

Last night I set it for 2024 keyboard but it did not make any difference unfortunately. I did check for conflicting bindings at that time and the only one I have related to the rudder is on the 2020 keyboard map and related to the numerical keypad 5 key. This 5 key centers the rudder. I remember a few models by Inibuild's the nose gear won't center using the 5 key but when I added that extra binding option it would center. The duplicate binding does not cause issues with other models so I left it. This duplicate binding is not active on default 2024 map and did not make a difference with the F70. Just for word not alloweds and giggles I loaded up the F28 and on that aircraft you have a switch above the tiller that turns off the nose wheel steering. With that switch set OFF the F28 acts just like the F70. The F70 does not have that switch in the same location. In fact I am not sure it even has that switch? I looked around the cockpit of the F70 and could not locate it but if it has it and set to OFF it might be the problem. Searching the internet it appears several people have had issues with the keyboard nose gear steering not working on several other Just Flight aircraft. It just does not work for some people but does work for others. I have had this issue with other Just Flight planes in the past that magically worked itself out in a future update. One of the Just Flight planes (but can't remember which?)has an external exe utility you launch that has some additional nose gear options and launching that utility and selecting those options allows the nose gear to work. The F70/F100 does not have that external executable utility! Personally it looks like and least on my install the Rudder Axis Steering button is not working. On the last update I completely uninstalled the F70 and reinstalled it just so everything is fresh but that did not help. Next thing will be loading it into FS2020 and see what I get there? Slight delay with my simming hobby since my boss is on vacation and I have to fill in for them. So very limited time tinkering with this issue this week but I do get an hour here and an hour there!

Rudder Controls Steering or as Just Flight calls it Rudder Axis Steering is turned ON. For familiarity reasons with FS2020 I already have it set for FS2020 Keyboard already. I remember I had to add some of my own key commands like F1-F4 function keys for throttle and F5-F8 for flaps control. I don't think I had to add any key bindings for the Numerical pad so I don't think I would have a conflict and don't have any issues with other planes. My next experiment will be setting the keyboard back to 2024 and using what keys 2024 uses for rudder turning. Another thing I might try is loading the Fokker into FS2020 and see if I get different results? I don't fly FS2020 much these days but it is still installed so I could do that. It is very bizarre and does not seem widely reported. No other plane I have including the F28 has an issue. I remember a 2 or 3 years ago I had issues with nose gear steering on the F28 but it seemed to fix itself in one of the later updates.

A little update on my nose wheel steering issue... If I take the tiller and physically manually move it off center using my mouse the nose gear of coarse turns. With the landing gear off center with the tiller wheel magically my numerical keypad keys 0 and ENTER start to work and I can steer the aircraft. However the nose wheel will not center but set itself on what position the tiller was set manually before making it still mostly unusable. If I take the tiller wheel and manually center it with the mouse I loose the ability to steer again using the numerical keyboard. I feel it is some sort of systems issue that locks the nose gear in place when the tiller wheel is centered regardless if you have the gust lock on or off or what you have the Rudder Axis Steering is set at. Tiller wheel does not move at all when you finely do get it to work off center. Tiller wheel never actually moves even when you get the nose gear to turn when set off center. A disconnect between the rudder and the tiller is taking place regardless of the Rudder Axis Steering option is set at. Really surprised this bug has not been reported by more people. I can only guess but I think if you have a tiller wheel option on your flight controls it works that way. No response so far from Just Flight on the issue! I am assuming if Just Flight's F28 works (along with all other FS Aircraft) 100% correctly out of the box as it should something is definitely haywire with the nose gear steering on the F70 and F100.

Tonight I filled out an official support ticket for the ground steering issue on the Just Flight web site. Hopefully it is either something simple I missed but I kind of doubt it since all my other planes are working fine as is Just Flight's own F28. I think they forgot something simple during development and once they know about it will be an easy fix hopefully!

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!