-
Posts
5,604 -
Joined
-
Last visited
-
Days Won
404
Content Type
Profiles
Forums
Latest X-Plane & Community News
Events
Downloads
Store
Everything posted by Litjan
-
Hmm - Tom has seen something similiar on his machine, but I was unable to confirm it on my end (Geforce 1080). It warrants further troubleshooting, maybe a combination of drivers, Vulkan, graphics settings?
-
Backlighting of steam gauges (other then clock/fuel)
Litjan replied to Dozo's topic in General Discussion
Hi, the temperature you enter on that page is called the TASS - the "temperature assumed". This is done to "trick" the engine into thinking that it is really warm outside - so it will reduce the available take-off thrust to stay withing temperature limit for takeoff. Since it REALLY isn´t that hot, the engine runs at a reduced thrust, saving wear and tear. The engine is flat-rated to +30C, so a TASS lower than +30 will not work. Thats why you can´t enter negative numbers - normally you will not enter a TASS that is lower than +30C. http://www.b737.org.uk/assumedtemp.htm Jan -
Backlighting of steam gauges (other then clock/fuel)
Litjan replied to Dozo's topic in General Discussion
Hi Sebastian, thanks for the headsup - I will take a look, but this might be normal. Normally you will only enter the TASS on this page - which is by definition at least +30C. Cheers, Jan -
Backlighting of steam gauges (other then clock/fuel)
Litjan replied to Dozo's topic in General Discussion
Thats funny - yeah! Good excuse, isn´t it? I guess you can map keyboard keys to "left brake" and "right brake"...and possibly left and right (and center) rudder, too. Cheers, Jan -
Backlighting of steam gauges (other then clock/fuel)
Litjan replied to Dozo's topic in General Discussion
Good question! The aircraft (like the real 737) can autoLAND but not autoROLLOUT. The autopilots have no control over rudder or nosewheel. Thats why the aircraft is limited to the CAT IIIa minimum of 50-200. The pilot needs to SEE the runway lights at 50 feet (and have at least 200m runway visual range) to be able to keep it on the centerline after touchdown. So the proper procedure is to disengage the autopilot shortly after touchdown...it will try to maintain the LOC (centerline) with the ailerons...which don´t really do anything while you are on the ground . Cheers, Jan -
Backlighting of steam gauges (other then clock/fuel)
Litjan replied to Dozo's topic in General Discussion
No worries - and I am much more happy with this solution than you not having backlit gauges and not knowing why! Cheers, Jan -
Backlighting of steam gauges (other then clock/fuel)
Litjan replied to Dozo's topic in General Discussion
Ok, let me know what you find out - I just doublechecked on my side and all lighting in the steam gauge version seems to work as it should. Cheers, Jan -
Backlighting of steam gauges (other then clock/fuel)
Litjan replied to Dozo's topic in General Discussion
Hmm, are you running any scripts or other plugins that change the way that X-Plane looks? Things like "better nightlighting" or Reshade or such? These have been known to change lighting intensities so that is the first thing I would suspect and remove (temporarily) to rule this out. Cheers, Jan -
Hi Karsten, unfortunately I am no guru regarding online flying and comms. I have checked the website of VATSIM, there seem to be various ways to connect - xPilot, xSquawkbox,...possibly different versions. Did you investigate an alternative or check with the devs and other users there? https://www.vatsim.net/pilots/download-required-software I don´t know what we are doing different - as far as I know the datarefs that we use for our radios are standard... Cheers, Jan
-
Oh, there is one more thing coming to my mind - if one side of the aircraft "drops offline" as you lift off, this might hint at you forgetting to switch the electrical source from the APU to the engine generators. The APU can power both buses while on the ground, but as soon as you lift off, one bus will drop offline...
-
Hi, not to my knowledge - there is no random failure simulation on the IXEG 737 (yet), you can trigger some failures (like the hydraulic ones) through the IXEG menus, and some of the default X-Plane ones will also work (like engine or APU failures/fire). So I really don´t know what happened there for you - if it happens again, maybe go to the (default) failure menu and click the "fix all systems" button and see if that clears things up. If it does it would be a strong indication that you are getting random (default) failures somehow. Cheers, Jan
-
IXEG 737- Do I need to repurchase latest version?
Litjan replied to lehbird's topic in General Discussion
Hi Dave, your previous purchase should still be valid and you should be able to simply download and install the latest version. Cheers, Jan -
Hmm, I really have no idea what could be causing it, sorry. It seems to work for pretty much everyone else :-(
-
Ok, does it follow the FD eventually? You wrote "asap" - there is sometimes a bit of delay between the plane reacting to the commands of the FD...
-
Eventually we want to move to FMOD... however if your sounds are playing too quietly now, there may be something else wrong. I know that sometimes sound level settings from other aircraft carry over - so maybe doublecheck that you load up the 737 first (no other aircraft) and that all sound levels in X-Plane are really at maximum? Cheers, Jan PS: You can use the "test" button of the EGPWS to test the sounds.
-
Hi, I remember hearing about this problem before... but I don´t remember the solution :-/ For me the sounds are fine. Maybe you can browse to the sound folder of your IXEG installation and try to play the corresponding .wav file in Windows? Is the volume ok that way? Cheers, Jan
-
Hi Torbinator, yes, I can see those oscillations... The pitch oscillations are new to me - I have not seen those before...and really have no idea where they are coming from, especially if you say that they disappear in other autopilot modes. The VNAV pitch mode targets the the vertical deviation bar - and that one is not moving (at least I can´t see it in your video), so I don´t know where that input is coming from. It would be interesting to see where the stabilizer position (trim) is. It could be that it is at the limit of autopilot trim, so the autopilot keeps pushing against it? The LNAV oscillations in turn are looking similiar. We used to have a bit of those since turns are really just a segment of straight lines, we tried to dampen that out, though. I don´t recall seeing it this obvious on my end, I have to check again (sometimes one gets blind to these things!). Thanks for your report, Jan
-
I was never rated on the 737NG but I know there are some substantial differences between the NG and the Classic as far as the autopilot/flight-director system is concerned. Especially with regard to VNAV and but also some things like "arming" LNAV before takeoff and others... Cheers, Jan
-
Hmm, this sounds odd. Note that you should not use VNAV if you experience any problems with it - it does not work right in some circumstances (and never in a missed approach). Make sure that your framerate is sufficiently high (> 25fps) to avoid autopilot oscillations. Other than that you can also watch my tutorial videos on how to operate the autopilot system correctly - since you are the only one reporting these problems I am inclined to think that it must be something out of the ordinary you are doing ;-) Cheers, Jan
-
Ok - I don´t know why your power is "pushing back and forward" because your autothrottle is completely off. I see the flightdirector bars being completely centered - this is odd, because it looks like the plane is following its commands (the flight-director bars are actually always getting centered by the autopilot, because it flies exactly like the bars indicate). Did you "push" the ALT HOLD button? You have to be aware that the ALT HOLD command will maintain exactly the altitude at which it was pressed - not the altitude that is selected in the window. If you push it in a rapid descent (or climb) it will "go back" to that exact altitude, but it will take a second because otherwise the acceleration loads are too uncomfortable for the passengers. Cheers, Jan
-
I would need to see the whole panel - well, at least the EADI (with the green writing on top) to begin at guessing what you did wrong ;-) Cheers, Jan
-
Update Coming, Request your datarefs and commands here
Litjan replied to tkyler's topic in Hardware/Cockpit Dev
Yes, I wish I could have told you otherwise... When Tom put up this thread in April we were trying to "take stock" of which datarefs people were still looking for. We did not know if earlier requests were still valid or maybe if people moved on to other projects. We did get almost no replies to this query, so exposing more datarefs slipped down the priority scale. I did add quite a few commands, but naturally this isn´t the same as datarefs which cockpit builders need. Cheers, Jan -
Update Coming, Request your datarefs and commands here
Litjan replied to tkyler's topic in Hardware/Cockpit Dev
The AP P/RST caution (red) light is: ixeg/733/caution/caution_ap_rst_ind But that is the only dataref I could find - I think the other ones haven´t been added yet . Sorry, Jan -
Update Coming, Request your datarefs and commands here
Litjan replied to tkyler's topic in Hardware/Cockpit Dev
I think so. Look for the IXEG/733/caution/caution_ap_... datarefs (light, pushbutton) and the /caution_at_ and the /caution_fmc_.... datarefs. There are also several commands for those buttons (look for ixeg/.../instrument_panel/... Cheers, Jan