Leaderboard

Hello all 737 lovers i just tested the 737 with the new xplane update, everything seems to be working fine but there are two issues i found: 1) External textures and shadows are blurry 2) There some moments where the instruments glass have some sparkles. But in general is working great.

Thanks for testing @Asgarmagol. I just fixed the rain issues here and will look into your other reports now. When SkyMaxx Pro 4.9.1 comes out, it should be even faster - I also found an optimization problem that's been fixed.

Good afternoon, I have just updated to the latest version of TBM900 ver 1.1.12 Many thanks for the great work undertaken by every one. Am I correct in assuming that the issue with the synthetic pathway in the G1000 has not been resolved in this release ?

Oddly enough, I haven't visited these forums in quite a while, but while I was in the process of getting ready to post some 11.50 Beta results, I saw this post. All I can say, with a modicum of respect to all parties, is that I JUST experienced a similar encounter with the same moderator. Not to throw too much shade at that site, but I will say that having to get the head admin involved was both good and bad. Initially he sided with the decision made in my case, but after virtually pleading that the issue wasn't my fault, I then received two PMs from both the head admin and the above referenced mod, saying that they reversed their decision. Needless, to say THESE forums are probably the most I will stay involved with for any sim-related forums. The staff here are professional, friendly and helpful and that goes a long way in my book.

Fixed the overcast issues @Asgarmagol for 4.9.1; thanks for catching that.

The new version is working very good so far with 11.50 Vulkan. The performance is quite good and I can even have the range slider to the max without frame loss (was not possible in the past with OpenGL). Some things I noticed: - the procedural Cloud Types for Overcast are not displayed right if viewed from above the clouds. - if I set the weather to "stormy" the frame rate drops to low single digit numbers (while having 60-80fps on all other weather variants) and the clouds are not rendered right. If viewed from above it is just a flat white area. Also It seems the rain particles are broken. All tests have been done with RWC set to "never" to use only the parameters from the sim. For the first XP11 Beta with Vulkan all in all the result is very promising :-)

Make sure you are not in autothrottle mode - the throttles won´t "work" (can´t be moved by your hardware) while that autothrottle is controlling them. You must be in "manual throttle control" (autothrottle disengaged or even off) for the throttle to work. When you transfer control from the autothrottle to manual throttle (by disengaging it) you will see some "ghost throttle" symbology. Move your hardware throttle until it "matches" the ghost throttle - at that point the throttles will "snap" and you have control again. Cheers, Jan

Support is very limited on X-Plane beta's, but this looks like an OpenGL issue. The best I can do right now is forward this to Saso and he'll look into it for when X-Plane gets out of beta. For now, I would recommend to staying with 11.41 with the TBM.

Hi Bill, This error is caused by large text pushing other info off of the installer screen. To fix this, please set your Windows operating system text size back down to 100% during install.

Hello Pierre, often the TOD does not change when you enter or change constraints on the descent path - because it is not affected by a new constraint, or lifting an old one doesn´t affect it. Imagine a "idle descent" path that passes well under a restriction of "be at FL250 or below". Now clearing this restriction won´t affect the calculated path, because it never affected it in the first place! The calculation of the VNAV PTH descent in the real 737 worked fine - but it was complex and had some potential pitfalls. Especially when winds were unknown (as they mostly are) or when ATC changed your lateral flightpath (as they almost always do) the calculation of the optimum path can get you in trouble. This is due to the fact that the FMS will plan the descent in an optimal way - without any conservative reserves. So if there is less headwind or the routing gets shortened you will immediately be "too high" to start your approach. This does not work well with the conservative and safety-oriented attitude that airline pilots have. Also the complexity and missing transparency of VNAV calculation make real pilots shy away from using it - don´t use what you can´t understand and doublecheck. So speaking for my airline, the typical use of VNAV was seen in climb and cruise. In those portions of the flight VNAV works exactly like FL CHG, with the difference being that the target speed is calculated by the FMS. Usage in descent was close to 0. We used the TOD and vertical deviation bar to "sanity check" our own descent calculation, but the VNAV PTH descent mode was barely ever used. Cheers, Jan

Of course!

To make you buy the plane so you can watch my great videos!