Haven't said anything about this since it's not a BIG deal but the set speed seems to run away when setting anything below 250kts. e.g. You can tell it to go from 300kts to 240kts and all is fine. If you try to go slower by saying "set speed 210" after slowing below 250kts it will start to count down to 210, slow around 5 knots before the target speed and then blow thru it without stopping. The "set VREF plus XXX" does the same. The "cancel last command" works to stop it from continuing it's runaway altho another command to slow causes the same problem. Anyone else experiencing this?

 

-Rick

 

Oh yeah. A little cosmetic request whenever you have a spare few (like there are such things as "a spare few"). After the FO activates a switch or dial the cursor remains as a hand rather than going back to the pointer. Hence the cursor stays visible. A slight move by the mouse on my end fixes it. Purely cosmetic like I said.

Hi Rick,

 

Speed runaway below 210 knots: Sorry, I can't reproduce it and I've tried a 1000 times.

 

That happens to you every time?

 

 

Mouse Cursor: Out of my control. That's a function of the PMDG SDK.

Rick

 

Do you use Radar Contact ?

 

I was getting the Set Speed runaway problem until I moved RC to a client computer, now its fine.

 

Glen

I also get this runaway now with 1.4. Only use it on final though so for me a disco the AT and handfly if that happens.

You can speak "Cancel last Command" if you get a runaway.

 

Are you using Radar Contact?

Yup. Using RC. But was using RC before. I also have Proflight Emulator. I'll try it out with that and see if it still does it. Not sure how RC would cause the problem tho since it's interacts with FSX thru FSUIPC and FS2Crew interact with PMDG thru it's SDK. That's weird.

 

-Rick

Hi Rick,

 

Nothing in that area of code changed from 1.3 to 1.4.

 

FSUIPC can now apparently interact with the NGX via offsets (bypassing the SDK), so maybe there's something funky going on there.

 

Cheers,