Litjan

Your installation went wrong, gizmo plugin is not running. Try to reinstall and follow the instructions exactly. Good luck, Jan

Hi Niall, there are several possible reasons for this. You can attach your log.txt (you will find it after the incident in the main X-Plane folder) and attach it here, so we can take a look at that. There is the possibility that a plugin you are using is causing this, that is why Ben asked you to try on a clean (or the demo) copy of X-Plane, you can also remove your plugins (just disabling them when in the game is not enough) by temporarily moving them into an extra folder to possibly isolate the problem. Another possibility is that your preferences accidentially set a button or key to "reset aircraft" function - you could check if that happened (scan your key and joystick bindings with the search for "reset"). Cheers, Jan

That you would have to ask my mother .

it´s Friday...again

Yes, I have heard of similiar problems from other users using Spadnext. I never even heard of Spadnext, so I can´t comment on what the incompatibility seems to be. Cheers, Jan

The light values for the landing and taxi lights are accessible in Planemaker, and you can increase and tweak them to your hearts content, I think. The engine values are a custom calculation that we do - the planemaker values have little to do with the thrust output. Jan

In other words - the proper mode for a smooth descent in your situation would be the V/S descent mode. You *could* use FL CHG, but you would need to advance your thrust levers again (after the RETARD-ARM cycle finishes) to add some thrust - that way the plane would descend less steep. Jan

Double check if windows defender is causing the problem, then, please. It re-activates itself sometimes during updates, and that has caused confusion before. Not making edits on the FMC during flight is really the worst solution and would severely hamper the enjoyment of our product... Cheers, Jan

http://forums.x-pilot.com/forums/topic/12240-solution-to-freeze-and-stutter-when-modifying-the-route-in-the-fmc/

Thanks for letting us know and I am happy that it is working for you now! Merry Christmas, Jan

Is it crashing or just gettting very slow?

Lol, and your Captain did not hit you on the head with the weight-control folder???

There are many thousands of users flying version 1.2 in XP11. You and Jolmos are the only ones having problems with the VOR and ILS radios . Jolmos is not an advanced member, he is a member who has had many problems and complaints with the IXEG 737 . I am not saying that our aircraft is without faults, but there are users that have only the problems that everyone has, and there are users that have "all sorts of problems" with our aircraft. http://forums.x-pilot.com/profile/28924-jolmos/content/ If you look at the youtube streams coming in (still), you may observe that no one seems to have problems with getting ILS or VORs to work. Here is an example, posted less than a day ago. https://www.youtube.com/watch?v=hn_yWzQHIa0 I would be the first one to move heaven and hell if our plane had problems receiving ILS and VORs, but in this case the evidence is strongly pointing at you (and maybe Jolmos) having something screwed up on your computers for it not to work. And we can´t patch around that. Jan

Thanks, Craig. I know that this point is hard to believe for the general public - just like the fact that "heavies" are not lumbering monsters that can bank at a maximum of 1 deg/minute, either . Especially since "other" aircraft circumvent this discussion by simply giving the customers what they expect. Cheers, Jan

Trust me, if you fly real passengers around you sometimes start wishing for a plane that has no doors! Cheers, Jan

The problem you are facing is that you don´t read or don´t understand what we wrote to you in this thread. It may be because you don´t understand english very well, or because you don´t have the necessary background in aviation or computer literacy or simply because you have a hard time reading and/or listening to people. Excuse me for being blunt, but my time is also not limitless and it is frustrating to talk (type) to people who don´t seem to read a single word I write. At any rate - the explanation and the solution to your problem was mentioned in the thread and we can´t provide support to those facing the above mentioned barriers. Happy landings, Jan

I don´t know who you sent a ticket to, but if it is to X-Aviation, you will not get a solutionr to your problem from them - they are responsible for technical support in relation to your purchase, the download or the installation not working. Anything not working on the plane itself (aircraft bugs/deficiencies) is handled by us (IXEG) through these forums. If you are experiencing a X-Plane bug, you need to tell Laminar Research through their bug report form. Cheers, Jan

Hmm, never heard of that. The only alarm bell in the aircraft is the fire-bell... and that should have nothing to do with the parking brake. There is the remote possibility that you have assigned the same key (V) to the parking brake and possibly also the fire-test button...I have seen strange things happen like that (people assigned B to brakes and beacon, for example)... If checking your assignments doesnt help, maybe post a short video of it happening? Cheers, Jan

Spoilers SHOULD be available in replay if you pick the preference of "show custom animations in replay" - at least on my system. Yes, the ground spoilers "pop up" too quick, sometimes, but visisble they are. Jan

The real cockpit is a deafening place. There is a reason we are forced (by rule) to wear noise-compensating headsets or hearing protection. It is common practice to lower the volume in the Level 4 simulators to 50%, just so the students and instructor can talk with each other (not over the intercomm). I don´t expect our users to play at realistic sound levels (what would the families and neighbours say?), but I think the sound is a good portion of the experience of what it is to fly in a 737 cockpit, a loud, rattling, shaking, dusty, warn and too cold or too hot place, stained with sweat and coffee . Cheers, Jan

Yes, I have been able to reproduce it, too. To tell you the truth, X-Plane´s replay system is not working well with custom-coded aircraft. It is just tracking and recording basic default parameters, and anything coded by third party developers won´t be recoded. So during replay everything custom made will not be working. The gear lever with his three positions (up, off, down) is one example of this. The logic is running during the replay, interfering with the recorded gear position. I am not sure how this could be fixed, so for now we have to live with those shortcomings, I am afraid. Cheers, Jan

Yeah, we never got around to changing that - if I recall the internal discussion it wasn´t as easy to change as I thought it would be. I am actually very happy with the windshield wiper sound - look at this video: https://www.youtube.com/watch?v=36DxYzNTFI4 It is a very loud and crude device. Our (well, especially mine) goal is to make the 737 as realistic as possible - including the not so convenient aspects. I was already overruled and we added a volume slider for the aircondition, don´t expect my help to nerf the windshield wiper sound . Cheers, Jan

Correct - on "AUTO" the cabin lighting will go off/dim/bright dependent on flight phase (crude implementation) - but due to an X-Plane bug the light will spill into the cockpit, even though the door is closed. The workaround is to keep the seatbelts set to ON all the time. Cheers, Jan

Or you can just do it like me - copy the new (Navigraph) data not only into the /Custom Data folder, but also into the /Custom Scenery/Global Airports/Earth Nav Data folder - then you will also use the new and updated data for all ILS approaches. Downsides: The LOC may not be exactly on the runway centerlines (on slightly misaligned airports) and you will be prompted to overwrite the data on every X-Plane update... However: The thing that is really interesting about this is that the OP said that he got the frequency for the ILS (109.75) from the X-Plane map, but X-Plane seems to use 109.70. So there are some possible reasons: 1.) A bug in X-Plane, possibly taking the data for the map from another source than the data for the actual indication 2.) A language barrier problem, maybe the OP took the ILS frequency from another (third party) "map", not the one in X-Plane Jan

The frequency that X-Plane uses is 109.70 in X-Plane and that works fine. The frequency MAY be 109.75 in the real world (it is according to my charts) - but X-Plane uses 109.70. If you see 109.75 on the map, file a bug with Laminar Research, because there may be the old "curated nav data" dilemma at work here. X-Plane will NOT use any updated data source like Navigraph or Aerosoft for the ILS approach information. The only way to change those is to file a bug report on the Scenery Gateway site, so Robin Peel can change the data manually. The reason is that they don´t want ILS approaches that don´t line up perfectly (because maybe the airport isn´t in the right spot). Further reading: https://developer.x-plane.com/?article=navdata-in-x-plane-11 Jan