Good day,

 

Please see this same topic in MS FSX Forum from yesterday . It would seem that the problem I was experiencing with the dials and their parameters is somehow related to the shader10 patch.

 

Can anyone on this DX10 Forum perhaps point me in the right direction with this??

 

Thanks

ou toppie

Hi ou toppie,

 

I suspect this is the post you are refering to - http://forum.avsim.net/topic/394289-autopilot-dial-setting-adjustments/#entry2546867. I don't see how the DX10 Shader Fix could affect how your autopilot settings. As I recall there's an easy fix to your issue but all my searching can't find out how to fix it.

 

Best regards,

Jim

Hi Jim,

Thanks for the reply.

further to my post stating that the problem was solved, regret to say that it came back again.

 

All aircraft ( default,the PA airbuses and all other aircraft are performing the same, even the GA aircraft )

altimeter settings-----1000 where should be 100 and 10000 where should be 1000

CRS-----10 point movement when should be single units

HDG----same as above

SPD ----same as above

 

It seem to be ok when i first load up and make the initial settings then appears to change as I start to fly.

 

The only additions/changes i have made recently are the shader10 fix plus the associated changes to the FSX cfg file as per the DX10"How-To" Notes.

 

Any advice gratefully appreciated

 

Thanks

ou toppie

Good day,

I have just carried out a repair run with the FSX installation discs and also a repair with the Acceleration disc. The problem is still there.

I can shut down, change back to DX9, run fsx in DX9 where there is no problem, shut down FSX, change back to DX10, start up FSX and set the aircraft up with all autopilot info working correctly.

I then get the aircraft in the air, and at the first adjustment of heading to comply with ATC all the parameters change as noted above.

 

I cannot see there being any other reason than me maybe doing something wrong loading the shader10 fix.

 

I have also checked the before and after cfg files but cannot see anything obvious.

dont know where else to go with this other than a complete reinstall of the SH10 fix.

 

thanks

outoppie

I cannot see there being any other reason than me maybe doing something wrong loading the shader10 fix.

 

Paul has a link to the complete Shader10 he made with all of the updates already made. The link to it is up in the pinned How To document he prepared for this forum. All you have to do is download and drop it in your Shader10 folder and you won't have to run the Shader10 fix program.

 

Best regards,

Jim

Good day Jim,

Thanks for the suggestion.I have loaded the latest shader10 but the fault still existed.

However, after hours of starting and stopping FSX and changing from dx10 to dx9 and back again I finally narrowed it down to the fact that the fault occured after pushback, as soon as I started to open the throttles for taxi. At one point the fault shut down the engines and this was the final pointer.

I ran a check on the functioning of the Saitek throttle quadrant and found that the propellor lever was indicating at full fine and feather at the same time even though it was set in the zero position.

As I have not flown piston or turboprop for quite a while the fault had not shown up.

Have now stripped the TQ and found the yellow wire on the prop pot broken.

I have now put back the 3 levers and recoupled the wires on the CH yoke system and am back flying DX10 successfully.

I have the TQ stripped and find that the soldered connections on all the 3 pots are very fragile and, because they have been covered with a silicon sealer at assembly are extremely difficult to clean to enable a resolder job.

Thanks for the help

Merry xmas to all readers

outoppie

"Have now stripped the TQ and found the yellow wire on the prop pot broken."

 

Yikes! The yellow one!! That's an easy one to fix! Fortunately it wasn't the red one cut. :Just Kidding: :LMAO:

 

Best regards & Happy New Year,

 

Jim