Hello everyone. I'm new to FSX, I flew FS9 for many years, had all kinds of great add-ons and was quite happy with the setup I had, was in a VA and all. Then life happened and FS got set aside for a long time. At some point, I started watching youtube videos of FSX and was inspired to try it (can't stop the persistent FS itch). Here are a list of problems I'm having so far trying to get started. Any advice you folks have would be hugely appreciated!1. I wouldn't exactly call this one a problem as more just a question of curiosity. I run windows 7 ultimate 64bit. When I start up FSX, windows changes it's color scheme to basic. Does this happen for everyone or is it a problem on my end?2. I have both the CH Pro Flight Yoke and CH Pro Pedals that I've used a long time with FS9. In FSX, I'm having a problem with the pedals that FS is reading the brakes as always being applied, either differential brakes or just straight brakes. I've calibrated the pedals over and over again, adjusted the neutral zone of the pedals, etc. and can't solve the problem. It's difficult to taxi/takeoff when you're overcoming brakes. The brakes aren't full-on, just enough to make it a large annoyance. Maybe it's a problem with the pedals compatibility with Windows 7? I haven't used FS9 on windows 7, I upgraded from XP a few months ago and haven't done any simming on 7 up until now.3. Probably the biggest problem at this point is with add-on aircraft. I detest default aircraft, can't sim with them. Since I had Wilco's 737PIC pack for FS9, the FSX version of it was waiting for me free of charge on wilco's website. I downloaded and installed it and followed all recommendations from Wilco, and I'm having the problem with gauges not being visible and buttons and switches not working. I made sure I was running FSX with SP1, I downloaded and installed the latest version of FSUIPC, I made sure the aircraft loaded in 2D cockpit instead of 3D. Can't fix the problem. Wilco recommends having Microsoft VS2005 installed for some reason. The latest version of Visual Studio is VS2010, but I'm not sure what I'm supposed to be installing. There are all these different trial downloads and different version, etc. I'm sure I don't have to buy VS, I'm just not sure if I need it and if I do, where to get the right one.I guess that's it, there are some other issues and questions, but I can get to those later. If I can't get the above solved, it wont matter anyways, I can't sim like this. Anyways, thanks for the help.[edit] Also, the no gauges and buttons not working problem isn't only on the Wilco 737PIC, same problem exists on PMDG's 747-400 V2.

1. Yes. FSX is a 32 bit program. Basic color scheme only.2. I fixed that by reducing the null zone on the pedals. You need to play about with the value to get it right.3. Your best bet is to make sure the add-on gauges and dlls are added to the TRUSTED section of the FSX.cfg. I would also suggest that UAC be OFF. Finally, I have installed FSX to its own directory C:\FSX rather than installing to the Program Files (x86) directory. You may want to try that.

I made sure I was running FSX with SP1

I'm not sure if it has any bearing on the problem you are having with the 737, but generally speaking you should be running FSX with either SP2 or the Acceleration expansion pack (which contains SP2). Most FSX addons require one of those.

Wilco recommends having Microsoft VS2005 installed for some reason. The latest version of Visual Studio is VS2010, but I'm not sure what I'm supposed to be installing.

You should not install MS Visual Studio, only the redistributable (runtime) components. It is available here, in case the Wilco installer does not take care of installing it: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en

I agree about using SP2.If you choose to use just RTM or SP1 be aware there are some limitations you’ll have to accept.Chiefly frame rates are lower , and ‘oversized’ textures won’t load.As I understand, for best performance add-ons should use fewer large textures - rather than many small textures.SP2 allows designers to combine textures into larger maps…like a 2048x2048.This will improve performance…but limits the add-on to SP2 users (or Acceleration).

Ok well I have applied service pack 2, that went just fine. Still have a problem with no button functionality or gauges though. Very disheartening. I guess I'll try to make sure the files and such are marked as trusted by the FSX.cfg but I'll need more time to figure out how. I'm about to head off to work for the day so it'll have to wait. I know that before I installed the 737PIC I made sure to adjust security settings in FSX.exe to allow all.

rgoff1 - Normal win 7 and Vista automatically 'disable' Aero when you start FSX as it is not compatible with Aero - as someone says its a 32-bit program2- To prevent brakes always on you need to check the 'Reverse' box in FSX and make sure that you do NOT have any duplicate axes assigned I've seen FSX assign brakes to the mouse! :( #. No answerRegardsPeterH

There was a tip posted somewhere a long while back for the CH toe brakes problem. I think it came from the CH support folks. Basically the idea is to put something like a video cassette (remember those ?)under the pedals when calibrating to restrict the degree of travel and fool the calibration logic.Can't vouch for this solution personally, but it sounds worth a try.

Hi DisckIt was actually a CD case - bit thinner! :( :( :( However if you set them up properly in FSX you don't need to do anything else!RegardsPeterH

Hi DisckIt was actually a CD case - bit thinner! :( :( :( However if you set them up properly in FSX you don't need to do anything else!RegardsPeterH

You're right Peter. Might explain why it didn't work for me ! I did try to fix it with FSX settings, but couldn't make that work either. Eventually I gave up and assigned the brakes to buttons on the yoke, which is actually more realistic for the a/c I fly.

Normally, reversing the axis on rudder pedals solves the problem with the brakes. I had to do that on my Saitek ones, dunno exactly why it works, but it does.Al