skiselkov

The rain sound is the X-Plane default sound that we have no control over. We'll see if we can override environmental rain sounds in update 1.1, but currently this isn't a bug. That is not a bug. The Master caution sound is played into the headset as well as into the cockpit speaker. When setting the parking brake, you need to depress toe brakes first. That's how the real aircraft works. Without it, the parking brake has no pressure to lock into the braking system. Recommend you have a look at the "Operating the Throttle" interactive tutorial in the aircraft (tutorials can be accessed via Plugins > TBM900 > Tutorials).

Some plugins remove the TBM's crash handler, which prevents us from getting good crash logs and diagnostics to be able to debug problems. Please remove all plugins except for Gizmo and retest if you can get it to crash again. Since you said it happens during preflight, it should be a simple matter of a few minutes to get it to crash. If the crash doesn't occur anymore, try putting some plugins back and tracing down which one is causing it. Any info you can provide us on plugin incompatibility is valuable, as we can then try and address that incompatibility.

This is an artifact of how the refraction simulation works (it refracts in "screen space", i.e. it simply shifts local pixel lookup to another part of the rendered image). This is a performance saving measure, as realistic refraction would require ray tracing, which no production hardware (aside from the latest Nvidia stuff) can do in real time.

Yes, we simulate random ingestion of FOD if the INERT SEP isn't on. The chance is low, but increases based on surface type (lowest on pavement, higher on gravel, highest on grass).

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.