Downloads

Store

Everything posted by Litjan

Hi mizra,
we are aware of the oil-temp problem, the latest updated to X-Plane (11.40) finally makes this "accessible" to third-party designers, so I hope to adress that in a future update.
The N1 carots (orange triangle markers) are normally driven by the FMC. You can set them manually, but you have to pull out and then turn the little knobs on the instrument gauges themselves. This is just a backup method, though. The autothrottle will not adhere to the manually placed carots.
The IDG oil temperature indication is on our list to fix as well, your observation is correct.
Fuel temperature works as the other guys explained. It will drift towards the TAT (total air temperature) slowly, with the A hydraulic system only providing very limited heating.
Cheers, Jan

Hmm, not sure what happened - are you sure there is a STAR to runway 07 from PELEN? Also you want to select runway 07 first, then you should be given the choice of all STARS associated with it.
Cheers, Jan

Your observations are correct - there is an entry in our bug-fix-list to correct these.
For the operation of the aircraft these deficiencies have no effect, however, since with the engine shut down:
Operating the reverser will have no effect on thrust
The engine delivers no bleed air, so the position of the bleed valve has no effect (we don´t simulate the possible contamination of the air supply with smoke/fire retardant gas)
The engine driven generator will drop off-line very soon when N2 decays, so the Control Relay tripping would have no effect
Cheers, Jan

Hi Colin,
thanks for the nice words!
I am not sure exactly which part of the ground handling is giving you problems, is it the directional control or do you feel the airplane is not staying on the runway enough when you cross ridgelines?
We override the directional control of X-Plane with our own plugin - this was absolutely necessary when we first released this aircraft, because X-Plane´s default ground physics were deficient back then. There have been many advances to this in the meantime, and we will review the need for our overriding with the next update.
For now you may want to experiment with your control response curve of the rudder (you have hardware rudder pedals, right?) in the X-Plane settings, if you find the response too twitchy.
The "heaviness" of the aircraft is goverened by X-Plane´s physics but it feels pretty realistic to me - and I have flown the 737 irl for 10 years. Sometimes X-Plane´s runways are a bit "wild", especially with airports that have just recently been added and the terrain on them hasn´t been smoothed out during a scenery recut (next one will be for XP12).
Cheers, Jan

Hmm, this reminds me of the problem others had when using the (now defunct) option of "show vertices".
The "show vertices" option was a dubious addition playing with some OpenGL commands that where "not officially supported" at that time by Laminar Research. It worked, though, and looked kinda cool, so we added it.
Over the course of many years Laminar changed some inner workings, and now the "show vertices" option makes the 3D cockpit disappear from time to time - this option will be removed in a future update.
For now we ask to manually uncheck that option in the preferences menu of the IXEG 737.
Let me know if that helps, cheers, Jan

Hi,
it doesn´t sound like licensing would be your problem - thats a good thing!
I haven´t heard of anyone having a similiar problem - the values on the MCP should be changeable by grabbing (left-click) and then moving the mouse laterally.
Make sure you don´t have any third-party stuff interfering - especially notorious are "fly with lua" and python scripts running and influencing datarefs.
Also make sure that you don´t have hardware interfering (like programmable consoles or joysticks/throttles).
Last but not least make sure you have fuel - the fuel state is saved between sessions, and if you forget to refill the tanks, your engines will spool right down after respawning, even when picking the "ready to fly" state.
Let me know how it goes, Jan

Hi Seb,
we used a two-class cabin configuration - but that was a flexible arrangement! There was a curtain that would be moved back and forth, according to demand. Business class had the same chairs as economy class (after they finally did away with those pesky seatrows that could be changed from 3 abreast to 2 abreast), but in C configuration the middle seat had to stay empty.
Maximum seats available was 123 in all economy config.
A typical DOW (dry operating weight) for the 737-300 was 34.000 kgs (give or take a little dependent on catering group).
Cheers, Jan

Hi,
you have loaded your X-Plane with plugins to a point where something is bound to give and break.
The usual suspects are fly with lua, python interface and ground service plugins. I would start with removing those and see if that helps.
If it does not, you have to remove all your plugins and test again - then once you are stable, you can add them back in batches to identify the problematic one.
Often users are running an outdated plugin and can fix the problem by updating to the newest version.
Good luck, Jan

Hmm, why don´t you just operate it with the mouse? You only need to operate those fuel cutoff switches when starting or shutting down the engines, so its not really that important to have them on a HOTAS setup.
Second - for a realistic start sequence you would need to move them one by one anyway - you could turn them off simultaneously, though.
Maybe you can experiment with the command "Mixture lean a bit" and "Mixture rich a bit" - maybe they control all engines at once?
Cheers, Jan

You need to remove all other third-party plugins (addons, scenery, etc.) and then try again. When you see that the crashing stopped, you can add your third-party content again one by one and find out that way which one is conflicting.
Cheers, Jan

I am almost certain it has to do with some third-party plugin you are using (I see the little yellow "Boardin" in the corner)...try to disable all your plugins, then see if the behaviour persists.
Then start adding your plugins one by one to find out which one is causing the problem.
Cheers, Jan

Hmm, I am really not sure what is going on there. The gear and speedbrakes work with the default X-Plane controls. Make sure you don´t have any third-party code (fly with lua, etc.) messing with things...
Cheers, Jan

Hi Volvic,
sorry for the late reply.
The stall warning test not working on the ground was fixed in April 2018 - it may have been to late for 1.21, but possibly included in a small "ninja patch" that fixed the aircraft having wrong drag in XP10.
You may want to re-download the latest version (1.21) and see if that fixes that...
Cheers, Jan