Litjan

Hi Janis, Try the new Gizmo Beta and see if that works better for you? For general X-Plane stuttering you can also try the 11.50 beta versions of X-Plane (Vulkan) - this will also help with stuttering. Cheers, Jan

Hmm, that is really weird - the one thing I would maybe try is use the latest Beta version for Gizmo and see if that helps? Cheers, Jan

Hi Martin, something definitely wrong with your setup. With the CG at default - around 20% MAC (doublecheck on the "GROUND SERVICES" menu) - a trim of around 4 should not give you any problems. At the recommended trim, the speed is stable at around V2+20 kts. Initial rotation should require a definite nose-up input (up to 2/3 of full elevator), once the nose starts going up you can relax that to just a slightly nose-up input to rotate with ca. 3 deg/second. The full rotation to ca. 18 deg nose up should take you 6 seconds, roughly. Make sure you run with the "experimental flight model ON" - the plane is "tuned" for this new setting, it will soon become the default X-Plane flight model. Cheers, Jan

Hi Panman, I am kinda curious why you don´t run the latest version of SkyMaxxPro? This is normally the first thing to do if you have a problem - check if there was an update? Maybe try that one and see if it fixes things? Cheers, Jan https://forums.x-pilot.com/forums/forum/165-skymaxx-pro/

Hi Cavok, most often this is caused by the customer running a plugin or addon that changes the light levels in the simulator. If you don´t know which one this may be causing it, please attach the log.txt (found in your main X-Plane folder) and I will have a look. Cheers, Jan

You make it sound worse than it actually is - the list is only on the first page. The other 11 pages are just our customers complaining about it . Cheers, Jan

Hi martinlest, let me draw your attention to a few "stickied" posts that we have to let you know whats working and what is not ;-) https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v133/ https://forums.x-pilot.com/forums/topic/18101-faq-for-new-users/ https://forums.x-pilot.com/forums/topic/17981-version-133-known-bugs-and-workarounds/ The other stickied posts are also worth reading (and watching), but these are the most important. Cheers, Jan

Yeah, sometimes the code is weird like that - it could very well be that it somehow choked up in that particular situation when you were flying. If that ever happens again, please let us know - with as many details as possible (i.e. route entered, wether route was closed or had DISCO´s etc...) Thanks, Jan

Sure - I just tried it - selected MUSCLE3 and only the runway 30R, it looks like this: When I click on DEP ARR and then next to KMSP ARR I get: Picking ILS30L works as expected for me at that point...

Ok, I just tried with my navigraph dataset and it works as expected. Here on the first pic I selected the MUSCLE3 with ILS30R and the TRTL approach transition: Then (assuming I got instructions to change to ILS30L) I clicked on DEP/ARR then on ARR (next to KMSP) and got this page: Now all I had to do was click next to ILS30L and it worked fine... Maybe you can "drytest" this again on your side and tell me the sequence of events (or even better make a short video) so I can see if its a genuine bug, an error with the dataset (those happen quite a bit) or something unexpected you did? Cheers, Jan

Well, a real pilot has another guy with him in the cockpit - so there are 4 hands and 4 eyes.. To fly the 737 by yourself requires practice and a lot of planning ahead so you avoid situations where it gets "too much". Judicious use of the autopilot is recommended, especially when you have "stuff to do" besides just flying the airplane (like setting up radios etc.). The speedbrakes should not be used with more than 15 deg of flaps deployed - I guess you found out, why ;-) It will become easier with practice - try to remember the values for pitch and power for certain phases of flight (like downwind, on final,...) that makes precise flying easier instead of "hunting" for the correct pitch and power. Cheers, Jan

Hi - can you tell me which dataset (Navigraph or Aerosoft) you are using so I can check this on my end? Normally when you click on the ARR line-select key it will offer you ALL available runways, so I am not sure what went wrong :-( Cheers, Jan

Hehe, yes - once you complete them all, you should have a good idea of how the aircraft works. I also made some more movies to give you some ideas here: https://www.youtube.com/playlist?list=PLGRsg_6rB1D6f7lKjdw5r9P99swJtryhQ Cheers, Jan

Hi Beachdog, I assume you are talking about "track up" - there is no option to have "north up" - except for the PLAN mode (we have that as well). this has been requested a few times - appearantly a few airlines are operating with this option. I have an issue in our gitHub with this request, but it is a fairly invasive coding effort, so I am not sure when we will get to it. From a philosophical standpoint I can only say that flying with "track up" seems to be wrong to me - its like having an attitude indicator where the little aircraft banks, instead of staying steady in relation to the horizon and the attitude indicator banking and pitchting (staying fixed) with the aircraft. In my opinion, the top of the map should always be pointing where the aircraft is pointing. That way you see objects on the map at the same relative bearing as they are in real life. Imagine flying at a 20 degree crab angle, due to strong crosswind. Now you want to see the airport - on your (track up) map it is straight ahead, but if you look straight out of the window, it can´t be seen (because its 20 degrees off to the side). Cheers, Jan

Yes - this chart will give you the TASS for a flaps 15 takeoff - but only taking into account the runway length, not the obstacle situation. You read it like this (there is an example-dashed line in the diagram): 1.) Enter on left with airport OAT - go up until you hit the airport pressure altitude (elevation + QNH correction of 30`per hPa). Then go horizontal to right, until you hit the REF LINE. 2.) Now start on right with field length available, go up to first REF LINE, then follow it PARALLEL to the "slanted lines" for runway slope, then go up again to next REF LINE then follow it PARALLEL to the slanted lines for "head/tailwind", then go straight up (make a long line). Now follow from the final point of "1" PARALLEL to the "slanted lines" until you hit the vertical long line from 2. From that intersection go horizontal to the right to read off the maximum brake release weight. If you want to find out the TASS, you need to start the process in reserse. Start with 2.) to get the vertical line. Then go from the right (current weight) to the vertical line, followe PARALLE to slanted lines to the REF LINE (vertical), then go left until you hit the airport pressure altitude then go straight down to read the "theoretical" OAT (=TASS) that would still allow a takeoff with your current weight. Cheers, Jan

Yes, I have an issue in our gitHub for enhancing this... we may be able to do this on the avitab, for example. Cheers, Jan

Thanks, Ken! I personally believe that VR will be the future for flight simulation. Yes, current headsets and manipulation methods are still not there 100% - but its already incredible! We will keep our aircraft abreast that development - I have just recently tweaked the sensitivity of the kHz twist knobs since we implemented 8.3kHz spacing and we increased the "grab area" for both throttles - and am always listening for feedback. Cheers, Jan

We are working on fixing it!

Hi Fred, glad to hear all of that! I love the 737 - and I hope I was able to let some of that feeling permutate into the simulation of it we made. Regarding the things you mentioned missing - we have a stickied post up that explains what we consider still incomplete and what we will add - or not. https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v133/ Its well worth browsing through the stickied posts here in the general forum, but also in the "bug report" forums . I hope you will continue to enjoy the plane we made, and we don´t consider it finished yet! Cheers, Jan

Hi, I have seen this some times as well - it seems to be happening whenever there is a "turn direction" specified in the relevant SID or STAR. So the coding of the SID would be: After DOTOL turn RIGHT to .... So when you past something after DOTOL, the FMC will still adhere to the instructions of turning right, even if turning left will be shorter. To fix this you can wait until you are almost at DOTOL and then enter HANUL on the first line (as a direct-to). Cheers, Jan

There has been no change to the code for panning, in fact we have no code for panning, so I don´t know what could be the reason. All of that functionality is purely X-Plane. Cheers, Jan

Hi canadaclipper, the VNAV descent functionality is one of the areas where our logic is very "basic" - the vnav path works well if there are no restrictions on the descent, but currently restrictions can still throw our calculation off. We are planning a total rewrite of the VNAV logic. For now it is required to keep a close eye on your descent calculation. It is ok to use VNAV, but if the calculation seems suspect or acts up, revert to FL CHG mode or even V/S. I have made a video that shows how to calculate descents manually (it is one of the core competencies of real pilots - VNAV descents are not playing a huge role in real airline flying because often the path to be flown is not known beforehand). When I used to fly the 737 Classic (for 10 years) I was the only one who ever used VNAV on descents (out of curiosity). I have never seen a Captain use it (in my 6 years as a copilot) nor have I seen a FO use it (in my 4 years as a Captain). https://www.youtube.com/watch?v=hSemWBgRNnE Cheers, Jan

Well, that looks much better! Good framerate, too!

Excellent, thank you - maybe we can nail this one down! Happy flights, Jan

I don´t know - my airline stopped using them about 20 years ago, if I remember correctly... I don´t know where I would look for those...