skiselkov

I believe this will be fixed in 1.0.6. Found a regression in the license checker code that could accidentally act up. The build that fixes this should be out soon. Please let us know if it helped.

This one is a known issue on the Mac with certain graphics driver combos. We'll try to get this resolved in the coming days. The stencil operation in the shader is acting up and not properly masking away the floating window overlays.

This should be fixed in build 1.0.6. Please check that (should be out any moment now) and let us know if it helped. Game crashing should definitely not be occurring, so please send us a log file on that. However, the fuel imbalance isn't entirely unusual. The automatic fuel selector is simply a timer to switch tanks. If you happen to align your fuel use such that you have higher fuel flow when on one tank and lower while on the other (simple as a coincidence of power changes), then a fuel-imbalance situation can develop. That's why the manufacturer provides the SHIFT button on the fuel panel - this lets you manually change the tank being fed from and start a new timing cycle. I would recommend you give the fuel section of the POH a read (we link it from the Quick Start Guide in the "External Resources" section).

Can you please provide: A description of your system (operating system, CPU, GPU, RAM amounts) A screenshot of the windows task manager on the detailed performance tab (or equivalent on your OS of choice). A screenshot of GPU-Z or a similar GPU performance measuring tool. A screenshot of your X-Plane visual settings. Thank you. With this info in hand, I'm confident we'll be able to pinpoint the issue rather quickly.

Can you please attach a screenshot? Apologies if you've already done so in another thread and I didn't find it.

Can I send you an experimental build? I've been trying to chase this issue down today and I believe I have a workable fix.

We've investigating this. Several users have reported long-term framerate losses.

No, the engine can be started with the AUX BP off, this just increases wear on the engine-driven high-pressure fuel pump.

If you have a saitek switch panel, make sure you have your avionics switch on. Also check breakers.

Can you record a video of it? Not quite sure what you mean.

You've engaged DISPLAY BACKUP mode. Press the red button on the intercom panel to return back to normal mode:

That is often not enough to actually disable a plugin. The enable/disable checkbox is a soft request from X-Plane that the plugin can ignore (and many do).

Can you please take a screenshot of your panel?

Folks, please retest with 1.0.5 and let us know what sorts of improvements you are getting. Rest assured, we've got more we want to do. But even just this should help you get into the comfort zone in terms of performance.

Real autopilots aren't always 100% perfectly trimmed. They sometimes apply a little bit of pitch / roll force. Once the forces become too great, the AP trims. Otherwise the trim will would have to be constantly moving.

Thank you. Yes, this helped. Fix will be in next build.

Sadly the log just says that the crash reporter has been interfered with by some other plugin. Can you reproduce this issue? If so, can you please all plugins other than Gizmo and invoke the crash? That should point us in the direction of what needs to be fixed. Thank you for your help!

We have a build in the works for tonight. Testers reporting performance improvements of between 25 and 50%. Seems I accidentally left some debug code in the builds that was slowing them down. Stay tuned for the next update, it should help quite a bit.

@malenca Please send this information to Laminar using their bugreporter: http://dev.x-plane.com/support/bugreport.html This isn't any of our code, so we cannot fix it.

This is unfortunately a limitation of the underlying Laminar G1000 system. Please file a bug with them, because we cannot change this bit.

It is an understandably somewhat confusing detail of the manipulator design. If you hold the command down for too long after the throttle has moved 1 notch (more than ~1 second), it moves immediately to low idle. We have this control in there so you can go straight from low idle to flight idle in one fluid motion. I'll try to see if I redesign it so it's a little less confusing. But what you were probably experiencing is "as designed" at the moment.

@ANordheim Thank you for the kind words. We've just pushed out an update that should help with frame rates. Reductions in mesh complexity and the ability to selectively disable some reflection effects should help you guys out. We'll be working on more improvements, but we wanted you folks to have the benefits as soon as possible.

Can you please attach a log file from such a run? It sounds like the aircraft might be having trouble saving the state files.

We'll consider it for a future update.

Thank you for the log. I found an oversight on my part in the 1.0.3 update that didn't quite get everything in the original issue. We'll be publishing a fix soon that'll address this once and for all.