ron6468

Recently my Saitek Multi Panel Heading control has been acting up. All other rotary commands such as Course, Altitude, etc are working perfect. When turning the tuning knob in Heading Mode, the needle in the simulator (MSFS) jumps erratically many digits at a time. This also shows on the Saitek screen. It's worse in MSFS but I've noticed even in X-Plane 11 it is not smooth although it doesn't jump multiple digits. I reloaded the Saitek driver but that didn't make any difference. It's the same issue on any aircraft in MSFS and often the Heading I'm seeing on the Saitek screen itself does not match the image on the simulator cockpit HSI or heading indicator. It's odd though that the Course, Altitude, VSI, etc all work perfectly. Trying now to determine if it's an MSFS, Saitek hardware or software issue, so wondering if anyone else has had any similar issues.

I tried assigning commands to the yoke even though it didn't appear to be recognized. Surprisingly the commands worked including the axis. The only thing I can't find anywhere is the recognition of a hat switch for views. It seems to only work in various directions but not panning or snapping back to center. Strange too that after I was able to program the yoke it still shows up in FS as a big question mark.

Installation went smoothly except for one thing. When I clicked on CONTROLS, it showed all my USB connected hardware (throttle, rudder pedals, etc). Each one with a graphic underneath and fully functioning. The Yoke control shows the connected model in the top list bar but instead of a graphic it has a default greyed out controller with a big ? question mark on it. Regardless of what I connect - Yoko, Saitek, Logitech, etc. They all show as listed but no graphic and no ability to program and therefore don't function either. Any ideas would be welcome. Hate the thought of reinstalling considering this is the only thing not working right now.

Thanks for the help. I had tried this - or thought I did. Nothing was happening so I rebooted both P3D and the computer and what do you know/ - It came up perfect - covering all 3 screens. I've been doing this FS thing a long time - you'd think I'd remember to reboot when all else fails. Thanks again.

I've been running FSX in Widescreen (NVIDIA) at 5760X1080x32 over 3 - 28" monitors. I installed P3D V3 today, however, even though the resolution is set in both the config file and the P3D setup start screen - it won't stretch over the 3 monitors. Pretty sure I'm just missing something so hoping someone will know what. Thanks,

Your keyboard works outside of FSX as in Notes, etc? You don't accidentily have the Joystick Controller Disable checked? You can program anything in FSUIPC using either keyboard or joystick?

I fixed the blue aircraft texture on my DX10 setup last year. Trying to help a friend with his but cant remember what the fix was. Must be getting old or maybe just the long cold winter. Anyhow, any help solving the BLUE texture issue would be appreciated.

In a lot of ways the numbers you are posting there tell me that FS9 will not run very well. So much of the 3rd party airports and aircraft back then were very hard on CPU power and your numbers dont look very promising. If you run FS9 stock with no add-ons and keep the sliders to mid low, sure you can run it. Your question cannot be answered specifically since you havent told us enough about your expectations. Also, as others have said, pc specs would be far more useful.

Looks like you're having fun! Are you sure you want your wife getting close to that? My cockpit setup is so complex, no one comes near it except me which is just how I like it

I would sggest the H100i cooler - far more effective at cooling that i5 which you will want to take to 4.2 at least. The 680 is overkill unless you have lots of $$ to toss around. The money difference would be better spent on a SSD 120 for Win7 and a minimum 200GB+ SSD for FSX. The standard HD used strictly for storage of files, etc. A 660 OC or TI will save you lots of $ and you will see very little performance difference from a more expensive 680. The smooth and fast performane of the properly cooled CPU and the SSD drives will be huge though compared to your current hardware decision.

While Im not a big AMD fan, if you can OC to 4.4 and keep it stable then you should enjoy good performance. The H100i cooler is a great product so it should be ok. Looks like a nice rig!

Yes. Very good depending on what the rest of your pc is and what your expectations are.

I've had weather drop outs in FSX several times in the past 2 years for a full day at a time but since I use mainly Active Sky, etc I haven't been concerned. I think you may have dropped into the temporary FSX twighlight zone which you can esily prove if you try a different live weather program - just to confirm its was not your internet connection.

Save your FSX.cfg while in DX9 and simply uncheck the DX10 preview and your back to where you were before. You will need to revert back to previous Nivia Inspector settings but that too is as easy as saving your previous NI config. Suggest you switch over to the DX10 forum to continue the converstaion - all answers are there.

Totally agree. I followed the Avsim Tuning guide and will never go back to DX9. Still some airport lighting issues with certain developers and some white AI traffic issues but they are getting resolved gradually. The flight smoothness and graphics improvements far outweigh the few other issues. In many ways it's like flying a newer upgrade to FSX. Definite, although not huge frame rate increase too which is always welcome.

The argument for performance is 50/50. A more practical reason has to do with reinstalling or repairing either Windows or FSX where one doesn't effect the other. Either way, always install FSX in its own folder and not the default Microsoft method. SSD for FSX is always nice. Everyone that has done it, has seen an improvement in smoothness due to file reading, loading, etc. The problem is a budget to afford the size required. Given that SSD's should not be used beyond 80% capacity, you should really be using an SSD with 300+ GB which gets expensive. It all depends on whether you use lots of scenery, textures and aircraft. My SSD is a 480 is 1/2 full after one year.

Disconnect your joystick and rudder. Start FSx and use your keyboard to Pushback and move around with. Use a default aircraft to do this with. If no problems then like you figure, its in your joystick or your joystick config. When you plug the joystick back in, go through the calibration and resetup the axis. Try a default aircraft and determine for certain if it's the United program, etc or the Joystick. Process of elimination.

Send me a private message and Ill give you a contact in Denver who would be very helpful .... if he's available.

Quick questions: What kind of joystick? Have you tried programming them in FSUIPC assuming you have it installed?

Bruce, no one ever wants to discourage anyone myself included, but the truth is you will not get much performance with your current setup. I highly recommend heading over to the Hardware Forum here and read the document on Hardware and FSX. You will get a lot of guidance from this. You need to have 3.8GHz at least to enjoy the complexity of PMDG along with nice airports, scenery and any kind of interesting weather. I am fairly certain also that if you remove one of those GeForce cards your frame rates will improve. Additionally, you will get better performance all around with Win7-64Bit and at least 6GB of Ram. There are many more improvents you can make and I know that budgets have everything to with how much and how soon. Meantime read that document as it will head you in the right direction.

Based on your problem description I would say that cable is exactly your problem and as Martin said - take the shortest route regardless.

Check this out too. Its an old style Century 3 A/P system. This pdf tells you exactly how it works in real life - not sure if the Seneca is modeled to suit 100%. http://www.centuryflight.com/manuals/CENTIII.PDF

That might be related to North American rules of FL100 where landing lights are turned on and speed under 250knt observed?

Just to clarify - you plugged the PSU into the wall with nothing attached to it? All pc connctions were disconnected from it? It wouldn't start, no fan, etc - its a digital start circuit or did you short that with a paper clip to get it going - not sure I understand that part.

When sitting with my wife in an airplane ready to take off or land and Im telling her everything that's really going on and she's pretending to listen.