Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About NZWW

  • Rank
  1. NZWW

    Number of bugs and some feedback

    I tried to be more gentle with rudder upon rollout, so far it works, yet haven't tested under heavy cross-wind/slippery runway. Having seen your last edit, unfortunately mine autobrake disarms with full rudder deflection. I use regular joystick with Z axis, nothing complicated, no pedals for now. Another few things. 1. With the latest versions of xEnviro (1.08, 1.09) wipers don't clean off the glass. I understand it is more to do with xEnviro / XP, but still. Almost blind with heavy precipitation. 2. No morse code identification or barely audible. Since there is no auto-translation of morse into letters on ND as on 737NG, it is potentially unsafe. 3. Those scratch marks on cockpit windows are nice, but under certain lighting conditions you can distinctly see underlying boxed areas with each scratch mark that are not fully transparent as the glass itself. Thank you.
  2. NZWW

    Number of bugs and some feedback

    I did some tests with auto brake and this is what I found. eXnviro (latest 1.08) and use of reverse thrust does not affect auto brake operation. About half of full rudder deflection and more (either direction) causes auto brake to disarm. It perhaps more than possible to control aircraft on centerline in good conditions, but under cross-wind, gusts, contaminated runway, etc. more aggressive deflection may well be required, and this will cause auto brake to disarm. Is this intended or a bug? Is there any way to override this logic? PS. I did play with various joystick sensitivity settings.
  3. NZWW

    Number of bugs and some feedback

    Litjan, thank you for a quick reply and your great product. In regards to autobrake, I'm pretty sure it doesn't work for me at all. I do arm spoilers on approach and I do set engines to idle thrust upon touchdown, as per fcom-fctm. I tried both with application of reverse thrust and without. Is there any way to troubleshoot this or to check some specific settings? I'm on XP11 latest beta as of this date and xEnviro 1.07 (all landings performed in dry conditions so far). Thank you
  4. Hi I purchased XP11 & ixeg several days ago and really happy with it (after being devoted fan of PMDG B737NG on FSX). It is a very fluid, immersive and realistic simulation of B737CL, on par with PMDG, if not beyond. However, there is a number of bugs which I discovered having completed about 10 flights so far: 1. While on ground, unable to enter CRZ speed in FMC (e.g. "0.7", "0.72", etc.), "not allowed (or so)" message prompts, this is however possible when airborne; 2. Unable to enter DES speed and speed restriction in FMC, although EXEC prompts, fields remain blank; 3. ANP value not given (0.0); 4. Climb de-rate (apparently) not removed gradually to full CLB while climbing to cruise flight level; 5. By switching seatbelts off at night time cockpit becomes lit with light (dome light apparently); 6. On takeoff, after rotation, "glideslope" aural message plays (I always set NAV1 prior departure to ILS for emerg return, as per SOP); 7. Autobrake either does not perform at all or performs insufficiently for the selected position (I DO arm spoilers on approach with the appropriate light illuminated, and there is no "disarmed" light upon rollout); Please, consider allowing entry of raw coordinates and/or radial-distance waypoint in FMC. This is a pretty crucial thing, I couldn't believe at first it was still not implemented, as it is such a basic thing to have. In general, FMC needs significant further development and refinement. VNAV issues, HOLD page, inhibition of DME-VOR-GPS, custom waypoints, fuel predictions, supplementary pages & functions, etc. It would be also nice if you could specify what exact FMC software version you replicated (U5.0, etc.). Own failure model would be nice too (I'm aware about that small LUA script). Other systems, designs, dynamics, performance (especially fuel burn) are spot on! Thank you!