Litjan

Hi Hakan, your PC is certainly powerful enough, and getting over 30fps is good. I see your heartbeat spikes, and they are pretty much what everyone else expects. I think there is nothing else you can do to make it better. So please bear with us as we try to improve this - but I can not promise anything. We could move the code to "every" frame, but then the plane would run slow the whole time, instead of only every few seconds. I am not sure what is more desirable. You have NOT checked the correct box - you must check the "automatically update my license at sim start" as well. You can uncheck the lowest box ("notify me...") if you don´t care to get notified when it happens. Oh, and be careful not to turn on "airshow smoke" by accident (I think key "X" is default) - it looks like you have that running. Cheers, Jan

There is some "heartbeat like" variation in the framerate - it is due to certain systems doing calculations only every few seconds instead of every frame (to help with general performance). There is also some background work done by gizmo, and Ben has greatly reduced that effect with one of the last gizmo updates. Here is what I see on my system when sitting on the ramp at a big airport. My base framerate is ca. 24 fps and it dips down to ca. 20 fps every 3 seconds (a 18% drop). Here is a picture of the graph: While the whole team continues to strive for better (and smoother!) performance, this is something I barely notice, but of course your personal sensitivity to these variations may be very different. If you run at a higher framerate, the relative effect is stronger - sitting at Bermuda Islands Intl I get 60fps, and it dips down to 40 fps. So the drop is 33%, but of course the "lower" framerate is much better (40) than in the first example. What kind of drop do you see? Thanks, Jan

I just did some tests, and I came to the conclusion that everything works fine (both coordination in turns, and yaw damper). Look at this first picture. It was taken when initiating the turn. The yaw-onset is to the left (in the direction of the turn) and you can see the yaw-damper COUNTER it (as designed) by applying opposite (to the right input): Next picture shows the sustained turn at 220 kts - no rudder input. You can see that the ball is "almost" perfectly centered, the slip is about 0.4 degrees (its a bit hard to read): And just to complete the test, here is another sustained turn at final approach configuration, slip is 0.6 degres: These values are absolutely within what I would expect to see in the real plane. Cheers, Jan

Hi Mike, in the real plane the roll spoilers help to overcome the adverse yaw you get when initiating the turn, and the general aerodynamic shape of the airplane and wing keep the turns coordinated (don´t ask me how, but I think the big size of the vertical stabilizer needed for engine-failures helps)... there is no rudder input needed when making turns in airliners. The yaw damper is actually working against making a coordinated turn - it is a rate gyro that fights sudden "yaw onset". So when you initiate the turn, it will actually deflect the rudder opposite to stop the yaw. Once the turn is established (constant rate) the yaw damper input is washed out to zero. We are already looking at turn coordination in our current model and XP11 - there are bound to be some more flight-model changes (as Austin hinted at) - and we are wary of tuning, retuning and then again tuning the model until he seems satisfied. For now the plane flies ok and according to real performance and unless that changes we are inclined to let Austin do his thing and then revisit when the dust settles... Cheers, Jan

Hi Paul, (1) fly with V/S set to -1000 until you intercept your desired flight path, then use FL CHG descent. You need to do the calculations to meet your restrictions yourself (until we fix VNAV patch computations), but the green arc will help you (it shows where you reach the dialed-in altitude given your current V/S and GS). (2) not yet (3) no - I find it working pretty smoothly, and when following it precisely I stay on LOC and GS very accurately. Not sure what is going on on your side, there. Cheers, Jan

Hi Hakan, The "stutters" that people experience are very dependent on your hardware setup. I get subjectively very smooth gameplay. Most people seem content, but a few experience what they consider unacceptable pauses. I am not sure what the cause is, so my advice is just in general to make sure you have enough computing power (CPU, GPU) for the rendering settings you set up, and also to stop as much as possible any other programs running in the background on your system. To activate your license you just need to enter your customer email and the password you set up. Then it should do it. There is also different ways to set up the Gatekeeper DRM (look in the pop-out panel on the right side of your screen) to automatically do this, so it won´t ask you every two weeks. I hope this helps, Jan

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: