Adamski_NZ

I very much doubt the O.P. meant simultaneously. Even if you could sort out the controllers profiles mess, I suspect your system simply wouldn't have enough RAM (or CPU power for that matter).

I'll add my vote of confidence here as well. I have MSFS, DCS and XP11 (now XP12). All are totally separate - and don't appear to interfere with each other at all. However - they're all HD space hogs, so maybe a separate drive/partition for each <?>.

Still getting it, I'm afraid - even with GSX inactive (though it's still installed). In external view, I can see the gear bouncing up and down (when I rotate the view slightly) - as if they're being raised/lowered - with or without chocks in place.

Another little time saving gem I hadn't realised I could use!

I think the Linker documentation is quite good with respect to "moving" native MSFS stuff but, like you, I've always thought it'd be a dangerous thing to mess about with. EDIT: I did actual try it once (now I remember) - with just a simple aircraft. It worked - but then I thought I'd need to do the whole thing all over again next time there was an update. *Also* - some Asobo aircraft rely on components from other [default] aircraft (eg. the Icon, I think), so removing one of those could impact all sorts of stuff.

Yes - I did see that, thanks. I actually "browsed" to my Community folder just to be sure ... and it copied some files there before exiting early.

I got a quick response from support at GAS (many thanks!!) - recommending that I point the EXE to a temporary location (then copying over) rather than directly into my MSFS Community folder. That worked fine - and I could see all the folders and files ... yay!! What a beauty! For some reason, installing directly into my Community folder did not work - probably because of the usual protection/encryption that folder has ... yet other installs of other aircraft have had no problems. I see the installer EXE also writes an uninstaller exe into the Community folder - could that be the problem? I tried the installer again (to Community) with Defender disabled, but that didn't work either. I wonder what's peculiar about my system <??>. Anyway - many thanks for the excellent support from GAS (and, of course, for the wonderful aircraft)!

I've just fired off an email to GAS: ========================== I *think* it may be an incomplete archive, or the extractor is exiting too early. Looking at the folder in Community, there don't seem to be any textures, liveries etc. My guess is that maybe the archive is an *update* for an already installed aircraft. I downloaded from all the SimMarket mirror sites (just in case just the one was hosting the incomplete archive) but they all have the same file: GAS_Boeing_Stearman_MSFS_V1.2.exe [328 MB (344,121,368 bytes) 336,057 Kb]

Unfortunately, it appears that the SimMarket archive is incomplete (or the installer doesn't extract everything correctly). No textures or liveries. Grrrr ....

... and duly grabbed! 🙂

Many thanks!

I find that in some cases I have to bind the tiller to "Helicopter Steering" (but you may need to reverse that axis).

I've spent a couple of hours searching, trying to find out how to buy the [MSFS] Stearman ... and got nowhere. Any ideas, folks? The original Paypal link no longer works.

You've got me utterly confused by that statement! Which does what <?>.

Rudder trim does the trick! Many thanks.

Try searching with DHC-7 as well ...

UPDATE: I think you've identified the cause (yay - thanks!). I did two things: 1) Increased the tolerance for the throttle "notch". 2) After take off, I settled everything down (in level flight) - applying elevator and aileron trim ... engaged the A/P and started the climb. 2nd test flight without problems - so far so good!!!

You get the REAL airport thrown in! LOL!

Thanks! Usually - yes. I find I often have to put in some right aileron - which would indicate that the payload (or fuel) isn't balanced <?> ... though I can't see anything out of order there. I've tried it with fuel crossfeed enabled, but no difference. If I engage A/P and make note of the elevator trim and then add that value manually before re-engaging, I still get disconnects.

I think the trick is to always ensure that gate selection is the very last thing you do before clicking on "fly". IMHO, the MSFS GUI needs a total rewrite ... it's a mess.

I'm having problems with the A/P constantly disengaging (sepearate thread) - and am finding similar issues: I don't think the ATR initialises fully (and consistently) between flights/sessions.

I'm getting a sound loop when parking after a flight and shutting the engines down. Sounds like the landing gear. If I go into external view, I see the wheels bouncing up an down (even with chocks on). Anyone else?

I'm part way through logging all the weights etc. before/after Simbrief import (via MCDU or EFB). As soon as I'm done I'll post them here. One thing that's apparent already is that inputting all the values (from Simbrief) manually into the PERF/WEIGHT page gives me a trim of 1.1 UP - whereas the EFB always gives me 1.4 UP. Do people set the trim manually - or via the payload screen in the EFB? I'll also share my test Simbrief flight plan when I've finished logging.

Thanks for the tip. I already do something similar - as I use AAO. All my MSFS profiles are CLEAN/EMPTY and I then add AAO profiles on a per-aircraft basis. I used to do this with FSUIPC, but AAO is much easier. So far so good ... it does appear to be a Simbrief or payload loading bug - rather than spurious control inputs.

I *think* I've found the problem. It happens whenever I load fuel/payload from the imported Simbrief plan. Whether I load via the EFB or by the MCDU, I get the error. If I load the Simbrief plan (for the flight plan only) and don't do any payload edits, it all works fine. So it seems to me that trim (or C of G) aren't being correctly loaded and the ATR is unbalanced in some way - and the a/p struggles to make sense of it. Testing continues!