Capt. Windh

FYI Had to change settings on my video in order for PMDG support to view it. https://vimeo.com/74512274 password: pmdg

Hi Vaughan. Not really sure what you mean by this? Cool site anyway! Ok, so that's established. It's not a crucial deal, but for someone like me, who enjoy to make FS-videos it simply makes them less realistic. And it that case, it is rather annoying. Is that done via the PMDG homepage?

Interesting findings Kevin. Thanks. I've been looking at Real World NG crosswind landings (wingviews) on youtube and not seen any of them having the spoilerons move after touchdown, they stay at fully deployed. Watching some FS-videos of the NGX I find that some people have these issues and some don't, as predicted. The question remains though.. Is there a way to fix/tweak this? Or at least make the spoilerons' movements less sensitive?

Here's another video, with both the wings and the VC-yoke in frame, so you'll see the amount of input. This is "live" and with only keyboard assigned to control the ailerons. First with spoilers down and then with speedbrakes fully extended in ground mode. https://vimeo.com/74512274

Yep, I use the yoke to steer on the ground. But just after touchdown you would still use aerodynamic control together with the nose wheel to steer the acft until it settles filly, so this *should* affect people with pedals too. I can reproduce this in both fsrecorder and 'live'.

Ok, cheers. Perhaps there's a way to minimize it at least then.

True. But other people not having this problem (at least on the ground) means that there is something to do about it. The question is what.

Hi, I recently started a thread about this. (Also new to the NGX) http://forum.avsim.net/topic/419759-ngx-and-idle-thrust-on-touchdown/ After some research I found that this is normal in the 73NG's.

OK Kevin, But still some people report that they don't have the problem that can be seen in the video I provided.

OK, was able to test it again. I tested without any external controllers connected. It was not Autorudder. I then tried it with keyboard inputs for Ailerons. Also checked with lowering the sensitivity for Ailerons. Nope. The problem remains... Hmm....

Hmm... interesting.. Well, no, my controls aren't super sensitive.. And my yoke is not connected through FSUIPC.

Right... It cannot be due to the fact that I use "autorudder", right? (not able to test at the moment) If not, wouldn't more people have noticed this? Fixable?

Here's a video showing how the spoilerons "overreact" when spoilers are deployed: https://vimeo.com/74471597 (please bear with my sloppy landing, it's my first logged flight with the NGX)

For example, when making replay/videos the spoilerons fold down with every little move, and I don't think I've ever seen a RW video with the spoilerons moving this much just after touchdown. Perhaps with extreme crosswind and the PF makes serious input, but not by just nudging the yoke, as the case is at the moment. Let me upload a video to clarify.

I'm guessing, if anything, it is something about these values: spoiler_limit = 60.0 spoiler_extension_time = 2.0 spoilerons_available = 0 //Spoilerons Available? aileron_to_spoileron_gain = 3 //Aileron to spoileron gain min_ailerons_for_spoilerons = 10 //Degrees min_flaps_for_spoilerons = 0 //Minimum flap handleposition when spoilerons activate auto_spoiler_available = 1

Hi, The spoilerons on the NGX becomes much more sensitive once the spoilers deploy on touchdown. This results in the spoilerons going back down (or a bit up) by only small control inputs. It remains like thisnuntil the spoilers are stowed back down. I wonder if there's a way to change this so that they have the same sensitivity as when the spoilers are back down? Kind regards Johan

Ok, thanx Rob.

Interesting input, however I don't use my TrackIR on IFR flying. However, I have solved the problem by following Kyle's advice and by remapping in FSUIPC. It must have been corrupt of sorts. Many thanks guys!

UPDATE: I also noticied this. When I switch the starter to GRD and the sequence begins, the no 1 reverser flips into a position and the "Speedbrake Armed" light lights up: Also note the Oil Temp, Quantity and Engine Vibration indicators on No 1 which differs from No 2. At first I thought that it might have been "mouse as yoke" was the problem, since I've been testing engines without my Yoke (or throttles) connected. But deactivating that didn't help either..

Well, I tried something else... I started from cold dark. set it up to where I wanted it. Saved new panel state. Reloaded aircraft (and set NGX to start with my profile), all workes fine. I continue to start up. IT ALL WORKS! Yehooooo! UNTIL.... I try and shut down the engines. No 2 shuts down normally but No 1 stays on, even though FUEL is CUTOFF.... So, I reload the NGX to get to my profile. It loads up. The profile is the same, with one exeption now... ENGINE NO 1 IS RUNNING! AND CANNOT BE SHUT DOWN! (sorry for shouting, but this is Crazy) So NGX seems to be making up stuff on its own now, overriding my profiles and everything. Seems corrupt.. And I'm clueless.. Re-starting FSX is the only way to "clear" this thing in NGX and load the panel state I've commanded it to. And now, it seems the problem is back... No input on Engine no 1 after startup.. Looks like this:

Thanks Steve, I literally minutes ago found another way around it! by going into Nvidia settings and choosing "use Nvidia settings" in the color preferences, I now am able to get to windowed mode. Still cannot task switch from full screen, it Blacks out, but if I from Black screen press windowed mode, it works again, so I guess this one is solved!

I tried this by just killing it in task manager, but this only made FSX crash when alt+tabbing... In which way did you disable it? Now I actually only get CTD... It's either that or Black Screen. Extremely annoying.

I also tried to do the procedure with my CH-throttle quad disconnected, but the problem remains the same. Engine No 1 will start, but not more than that.

Hi, I tried starting up (from shut down, but power on). Did the sequence as I've done it hundreds times before, but when everyting is up and running, Engine No 1 instruments is not working. The throttle in the VC reacts when I push my CH throttle forward, I hear the engine spool up, but there is nothing happening in the upper EICAS... Does anyone have an idea of what's going on here? Regards Johan EDIT: Upon further inspection I realize that it is not instrumental, the engine itself does not react to the throttle after the startup. It runs normally when the flight loads up with engines running.

OK Kyle. Any second opinions? Can someone explain why it is this way? If I choose VC and then add the 2D-main panel on top, the light is bright and nice, but I get the VC behind the 2D main obviously.. So it should be possible...