Litjan

Thanks for getting back on that - it sounds like an overspeed protection kicking in (blinking 8 symbol) - but this should limit the speed to 195 if you are on flaps 15, not 222... Next time it happens, can you try to dial the speed down to max speed minus 15 (this gets the autothrottle out of reversion mode) and see if this helps? So in this case you´d have to change it down to at least 180. Thanks, Jan

It´s smart enough to first disengage VNAV

Hi lanman, thanks for the rundown on your status with 1.0.4 - it is easy to loose track how everyone is doing in between the updates, so it´s good for us to know what is still not working for you! Most of your points are on our list - however the "autopilot getting stuck at 222" is something that really grabs my attention and I would like to find out why. Could you tell me what flap setting this happened at? Thanks, Jan

Hi Ken, thanks for reporting back and following up! Point 8 (VOR bank angle) is noted - I think it will be easy to implement this and you saved me the trouble of hunting through the manual, thanks! And thanks again for the nice words - the no AC power case was a bit of an ugly stepchild - and implementing it was partially driven from the "equipment still available" list, my fuzzy simulator memory (while frantically finding a place to put her down) and assorted lists of electrical consumer & bus listings. Incidentially found out that there was also quite a bit of wiring difference between individual manufacturer numbers... Please absolutey keep the scrutiny up, your feedback is invaluable! Cheers, Jan

Thanks for reporting back. I will state again that you removing (temporarily) all your other plugins (except gizmo and plugin admin) and rebooting X-Plane will be the only way to narrow this down. Flying with different aircraft and saying that they don´t have a problem is helpful, but only in a very limited way. I realize that this is a hassle, but short of me buying your exact same computer and buying and installing all your software in the very exact same way we won´t be able to find the problem... Jan

I would put money on VNAV overspeeding (getting within 10kts of the upper speed limit) due to a steep segment. Jan

Hi lanman, you are correct, VNAV should stay engaged in the MOD phase - I will see what we can do about this. Thanks about the .84 report - we had a couple cases where this happened that we fixed, it looks like we missed this one! Jan

Hi Muskoka, while I fully understand your frustration, in this case I would like to point you towards Laminar Research (good luck!) - they are allowing to render a limited number of lights without HDR and the logo-lights are far down on our list. What you may see on other aircraft is a "night" texture that has the glow-cast baked into the texture... or they don´t have a large number of exterior lights, and can preserve one for the logo lights (IXEG: 2 Wheel wells, 1 Taxi, 2 Turnoff, 2 inboard landing, 2 outboard landing, 2 wing illumination, 2 logo lights = 13 total) Jan

Remedy: Remove other plugins, test and report which plugin causes crash. Jan

Hi, we are investigating some subtle differences between published bearings and bearings we have in the simulator. In the real world, a discrepancy of ca. 1-2 degrees would not cause much concern and is explained by old IRS magnetic variation database. In X-Plane things get a bit more difficult - especially when flying longer flights where the Mag Var changes substantially. I think we are calculating magnetic track when first loading the route (True Track + Mag Var). But for this calculation we are taking "present mag var" - there is simply no way to read the "destination mag var" easily in X-Plane, though I have some ideas (after all I am the one who supplied LR with an updated MagVar table a year ago, or so). So when you get towards the destination, you will see this discrepancy - however when flying LNAV, this should have 0 impact, because you are flying between waypoints that are fixed geometrically. Jan

If this happens again, please output the brake setting to your screen (go to SETTINGS, DATA INPUT & OUTPUT, pick row 14, 4th box from the left). Now you should be able to see how much (and if) your brakes are employed... Let me know if this crops up again - ideally take a short movie, showing N1, GS readout on EHSI and also report the airport, grossweight and temperature. Thanks, Jan

Clouds, Shadows, objects, car traffic, etc. are all calculated by the CPU in X-Plane - not GPU. Jan

Hi Nic, to troubleshoot which plugins conflict, you would need to remove all of them (temporarily, but don´t remove gizmo or plugin admin) and then reboot X-Plane. Also, do you know what your soundchip properties are? Thanks, Jan

Ok - can you find out what your soundchip properties are? We are trying to see if there is a pattern to the soundreports we get. Thanks, Jan

Yeah, there might be a slight discrepancy - will look into it. Jan

...and I won´t be going away - I appreciate your willingness to investigate and help us narrow down on this. The Simhaven issue might indeed be a clue - we had a report of a crash related to a faulty tile, see here: http://forums.x-pilot.com/forums/topic/9247-dialing-speed-on-mcp-caught-an-unhandled-c-exception-vector-too-long-hl_threadcpp262/#comment-99496 Let´s keep trying to figure out the cause of your problem! Jan

This could be - we "enlarged" the armed position range a bit because people complained that it was too hard to hit it - maybe this introduced the problem...

Which was to be expected, we can not ship "texture fixes" with the hotfix method. Jan

Ok, will have to see if I can reproduce that... Jan

Its a new bug in 1.0.4 that will be fixed very soon - it happens when you don´t have a departure runway selected and go to the TAKEOFF page, I think. Jan

Excellent - and please keep reporting all findings you may have, every bit is helpful in making this better! Jan

Hi Jojo, at least a step in the right direction... it´s a shot into the wild, but can you try to close as many other programs possibly using sounds (like browsers, youtube, SoundMaxx, etc) and try again? Also try this: Fly at 5000 feet, set the MCP ALT to 5000 feet. Now climb to 6000 feet (leave the MCP ALT at 5000!). Do you get the sound now? Thanks, Jan

Very weird - can you post your gizmo-log.txt file so we can figure out what went wrong? Thanks! Jan

Hi Theo, you are right, it does not sound like a heat problem. I am a bit at a loss - we ruled out heat and (I think) you confirmed that you have absolutely no anti-virus or other security programs running. This only leaves a possible conflicting other plugin - I see in your signature that you have quite the hangar - and are probably running just as many plugins. If I may - could you (temporarily!) remove all plugins (except for the default X-Plane ones and the gizmo plugin) from your plugin folder, reboot X-Plane and then try this again? We would be very interested in finding the conflicting plugin, so we could get in contact with them and resolve it! Thanks for your help, Jan

Thanks, Cris - something quirky going on there... Will investigate! Jan