Litjan

comment allez-vous Ca va, Daniel, it´s all relative - if you have two crazy kids roaming the house, then flying airliners is like vacation, you are right! The flying part is really fun - the tedious part is from brakes on to brakes off... Cheers, Jan

Super, thanks. I will send a link of this thread to Jennifer. I doubt that Laminar will invest much time into solving this - its a classical "draw order" problem of clouds (Ben Supnik loves those!) and when Vulcan comes along, everything is going to change, anyway... Cheers, Jan

Super, thanks for the info...I don´t have Ortho4XP but that should have nothing to do with it. Yeah, it would be PERFECT to see this on a default plane as well (I bet it will happen), as that would save us a lot of work . Thanks again, Jan

Hi Paul, thanks for the feedback and I am happy the suggestions work for you! Cheers, Jan

Thanks for everyones´s feedback. I think we discussed this a few months ago internally, and there was no easy solution... I will add this to the bug-tracker again to make sure the team takes another look. I can see how it is irritating. Cheers, Jan

Hi mga010, We provide these datarefs for the sake of completeness. In the real plane, the autothrottle disengage buttons (just like the AP disengage bar) are almost never used, so there is not a dire need to assign buttons to them. You can always use the mouse to operate these functions, too (if you find clicking the buttons on the thrust levers too cumbersome, just toggle the A/T switch on the MCP). However: The correct procedure to revert from autothrottle control to manual control of thrust is to disengage the corresponding mode (by pushing the SPD button on the MCP control panel, for example). This will revert the A/T mode from MCP SPD to ARM and you can control thrust manually. It has the added benefit of still having the A/T in ARM, so it can engage automatically when needed (during Go-Around, for example!) We can´t use the default XP datarefs for most of the AP stuff since the functions of the XP10 autopilot are very crude and our AP is fully custom-made. I do understand that buttons are limited and that it is unfortunate if different aircraft require different buttons to set up - I run into the same problem on my computer. Cheers, Jan

Hi naigovan, I have not seen this before - are you running with another plugin that may affect artcontrols in X-Plane? To troubleshoot, I would disable all plugins except those necessary to run the 737 and then add them back in until the problem recurs. Let me know how it goes, Jan

Well noted and still on the list! Thanks, Jan

Please try some flights with our option "draw vortices" unchecked. This is causing problems for some xEnviro users. We are still investigating the root cause... Cheers, Jan

I think this depends on the floodlights of the airport you are parked at. There is also something weird about your engine not showing the decals (warning stickers), so something odd is going on with your setup. Cheers, Jan

Hi, could you give me a bit more detail on how this happens? Which sound on the IXEG sound menu is affecting which X-Plane sound? Thanks! Jan

Ok, tried to experiment with this a bit more, but could not reproduce what you show on your pics above. Can you give me a bit of detail on how you got those clouds showing through the airplane? Also important may be the reflection setting you have... I did get some "draw order" problems that are abundant in X-Plane, but have those for both the IXEG and default aircraft... Jan

Hi CharlieZulu, by "green flicker", are you talking about the effect that happens when you turn the "Background" knob all the way to bright? Cheers, Jan

Cebulon, did you try to turn off the option "draw vortices"? Jan

Hmm, I tested this with the RIIVR arrival and the PGS transition at KLAX, and everything is loading fine on my end. I don´t have the IRNM1 on my navdata set yet (because I don´t subsribe to monthly updates) - is there another example you have that doesn´t load properly? I will buy a current cycle if these problems persist, please let me know! Cheers, Jan

I have created an entry to look at the sound volume. We had a discussion about this before, its not an easy fix. Cheers, Jan

Doublechecked, we "hardcode" the year to 1987, as there is no "year" function in X-Plane. I think we chose 1987 because that is the last year that I had full hair and a six-pack for a stomach! Cheers, Jan

Hi everyone, we are still investigating this problem, your help with all this is greatly appreciated. A cursory glance at our code relating to OpenGL and the "draw vortices" option did not reveal anything obvious. We are not claiming this bug to be "xEnviro´s problem", they have a great add-on that we want to have compatibility with eventually! Thanks for your patience and support, Jan

Bon jour, I think the light-levels are pretty "realistic". I often had some problem reading the CRT´s and LCD´s in bright daylight, and running the panel lighting at full bright even during the day helps. Maintenance will not readily change a CRT as they are crazy expensive, they "test" the brightness and then put it into another aircraft as "ok" (until the next pilot grounds the plane) . Here are two shots in bright daylight, one with lighting off, one with on:

Poweer is right. Aileron trim is RARELY used on the 737 - as it limits your available aileron travel (which you may need in strong crosswinds). So if the plane constantly banks, you need to find out why (and rectify that). Small banking tendencies can be countered with the rudder (even though that results in a bit of uncoordination). The correct trim procedure, however, is like this: Fly straight and level, make sure N1´s and wingtank fuel levels are the same. Maintain wings level with aileron, stop any turning tendency (yaw) with rudder-trim. Then use aileron trim if needed. For more than one unit (see top of yoke), make a maintenance entry. Jan

If you guys can give me a step-by-step guide (or even better a movie!) on how to recreate those problems I will do so and create an entry into our bug-log to get that fixed! Cheers, Jan

Ok, I have added an entry into our dev-log to take a look at it. No promises, but at least it won´t be forgotten this way. Cheers, Jan

Hi, we tried to keep the radar and terrain display accurate in colour and capability. The radar is masked by terrain, can be reflected by terrain, and can be subject to "overscanning" (icy tops) and underscanning. Update frequency is similiar to the real one, but we don´t model attenuation. The terrain return is a poll of X-Plane´s dsf elevation map, colour coded as shown above. Cheers, Jan

Not sure if this was done deliberately or with regard to some footage I provided. Could be a hommage to the "vintage" area that this great plane was built in . I don´t think it has any consequences, but I will add it to our bug-base just the same to take a look. Cheers, Jan

Hi Ian, thanks for the feedback! I will see what we can do about the clickspots. The yoke movement times have been subject to much debate - the real yoke can´t be moved nearly as fast as the joystick can, it simply takes time to move the flightcontrols, even for the hydraulics, and the yoke is always "in sync" with the flight control surfaces. This is great for the pilot, as it reduces "overcontrolling", unlike on the Airbus´ joystick (I deliberately avoid the word "flightstick", here), where you have no idea how far the ailerons really are when flying in gusty conditions. Really annoying and dangerous. I feel that the yoke response time in our model is pretty much accurate - I have done lots of "flight-control-checks" in the real one (every flight), where you move the yoke through the full travel, and it definitely takes a second or more to move it from one full stop to the other. It also needs to be said that X-Plane´s turbulence model is way too excessive and I NEVER fly with real weather on for this reason. The speed and frequency of wind speed and direction shift is just plain unreal and way overdone, and I have been working on a profound portfolio of videos and documentation of real-world cockpit footage to present my case to Austin. He likes "fun and exciting", so its always a battle to "tone something down". We will see. Cheers, Jan