Litjan

Thanks for the excellent report, will add to list! Jan

Thanks, I will put this to the hardware guys... This sound thing is really elusive, and it seems that one fix is working for some people, but making it worse for others... We will just need to keep working on it. The problem is usually that too many background programs are running that also use the soundcard - blocking it´s resources. Jan

prattpt6 is right - this is what you need to do for now, sorry - fix coming up for this! Jan

Can you try without the "enable custom animations in replay" option and report back? Also, please make sure you run without any other plugins (for testing!), remove them, reboot X-Plane and report back. We have had some plugins causing similiar problems. Jan

Hi, you are seeing the "baked shadows" which are a way of making the panel look more realistic. They are not rendered and calculated "in real time" - this would slow the simulator down too much. You will just have to memorize where the APP button is, if you find the writing too hard to read, I am afraid. Cheers, Jan

Yeah, you still need to "reboot gizmo" during turnarounds when doing a second flight, I am afraid. We have not had time to put in the correct resets to the FMC after landing... Jan

Hello Zain, to troubleshoot your problem, can you tell us what kind of soundchip your computer is using? Thanks, Jan

Yeah, we need to see the whole panel so we can see what modes your AP is in, wind displayed on the instruments, etc. Are you on 1.0.4? Thanks, we will get to the root of this, Jan

Hi apilot, very weird - I have no idea what could be causing this - do you have a weather plugin installed? One that enhances looks by changing the artwork settings (like real-terra-haze)? If you could, please make a short video of this happening, and also try again without any other plugins running (remove them completely, then reboot X-Plane) - just to troubleshoot the problem... Also post you log.txt file after shutting down X-Plane after the incident. Thanks, Jan

Not much to add to JRBarrett´s reply. Fuel temperature in wing-tanks will usually assume the roughly the TAT temperature, but it might take a long time.... I will take another look again, though, just to make sure we are in the ballpark. Thanks, Jan

Without HDR it is not possible to render many lights - therefore you will have a very limited experience with regard to lighting. To see all lights, you need to have HDR enabled. Jan

Hmm, ok - thanks for the report - we will continue to investigate... Jan

Ok, if you don´t have winglets enabled then I stand corrected about my assumption. As Tom asked, do you have HDR enabled? Jan

Ah, crap - this was a quick fix because someone complained that the autobrakes aren´t disarming when using the B or V key... Of course they should only "disarm" when they are actually "working"... Sorry, will add to list and fix in next hofix... Jan

Hi Ken, what a welcome and detailed report! Your remarks are well received, and very welcome in helping us push the boundary . CDU: 1.) Checked my pics and you are right - three characters for distance, only (I guess the rounding is arithmetical?) 2.) it should work the way you describe it - will verify and add to list (never added any temps when flying, so had to look up myself how this works ) 3.) this would make sense - not adding anything is a "+", anyway. Will add to list Electrical: 4.) You are probably right - but this goes way beyond what we are trying to achieve. I have flown the 737 for 10 years, and I couldn´t tell you a thing about what each TR should approximately indicate... 5.) see 4 6.) see 4+5 (I will, however, keep all this in mind and maybe Tom has a professional itch to change these - I guess it depends on where the voltage is taken - over the TR itself or just at the exit point vs. mass. I have never checked in the real aircraft, it would mean putting the transfer bus switch to off, then unpowering a gen bus) 7.) All noted - some systems (EGPWS) are still "default X-Plane" - those are pain to simulate electrically (you need to "fail" them if unpowered). Some could be fixed, I add those to the list! 8.) Right! Will add this to the list! AFDS: 8.) In VOR/LOC and in LNAV mode (at least in LOC) the limit selector is disregarded. The bank limit is 30 deg. After LOC on course guidance is established, bank limit is reduced to 8 degrees (iirc). I am not sure about the VOR capture mode, but I would think that the limiter is also disregarded or most captures might end in a disaster ;-) 9.) Yeah, I have seen some VOR quirkiness myself, sometimes. We have put this on a backburner during development, because the VOR mode is rarely used (or so I thought). Can you let us know which VOR you tried at (114.9 Mhz)? Also: Don´t fly with your centertank still filled and the wing-tanks not full - it is illegal . Again, I am really happy to see that someone is exploring some of the detail we have added - especially the electrical system took a lot of work. I think it´s nice to be able to simulate some bus (or even total AC power) failure - and you are limited by battery capacity and can even "save power" by turning off some heavy users or electing not to try an APU start... However, this in not Level-D fully certified simulator and you will eventually reach some boundaries. That being said - the stuff you turn up will probably slip by 95% of all real 737 pilots. Except for maybe that one Check-Captain that everyone hated going into the sim with . Jan

Yeah - you are probably right - or we change the label to transition alt . Have to check my pics... Jan

Excellent news, thanks for letting us know! Jan

Also check your fuel level is set up ok - no fuel, no APU Jan

Yeah, those are really hard to find. Who in their right mind would put them in a folder called "documentation"? Happy you found them, happy flying! Jan

try to up your gamma settings?

Winglets = no logo lights as discussed a million times and same in real life Edit: I think someone said that you are not running "winglets" - so my above comment was a shot in the wild, sorry.

Hi Simon, are you sure your autothrottle can work without getting interference from your hardware throttle? We see a lot of people that try to move their hardware throttle "along" with the ghost throttle - this can cause an inadvertant disconnect of the autothrottle when they trigger the rejected takeoff mode or you can accidentially "grab" the throttles when they enter THR HOLD at 84kts. To rule this out, just move your hardware throttles ALL THE WAY FORWARD right after you trigger TOGA. Does this help? Jan

Vielen Dank, Daniel! Viele Grüße, Jan

Yeah, I would think so - disable all of X-Plane´s failures (remove flaps in overspeed, etc...). Some failures will work (like engine fire, failure, etc.) - others might cause unwanted effects. I think you still did good to work around the problem and safely land, though! Thats why we have humans in the cockpit - they can think outsided the box and do stuff that a computer can´t plan for... Jan

Yeah... it is on the list - one of those things that have been there for a while and we just never got around to fixing. This feeds of a default X-Plane dataref, need to code around that. Jan