Frank.O

Scott, I seem to recall that I had something like that happening a long time ago and it was due to the AA settings. It is recommended everywhere to set AA to off in the sim and specify it in the graphic driver settings instead. This did not work for me but it produced the effect you describe above. And not only that. The same happened in the FSUIPC dialogues when scrolling the drop down lists of FS controls on the buttons or keys pages. Setting AA to "application dependant" in the graphics driver and to on in FS's settings cured the problem. My graphic card is a Geforce FX 5900 ultra btw. Regards, Frank

No, I don't think so. The jitter was surely caused by the pot (mainly) and the wires. May be the cold spot on the controller board had some influence. It was on one of the pins of the connector where the wires from the switches and pots come in so it's possible but I can't say for sure. A clear indicator that this was hardware related was the fact that sometimes a decent tap on the side of the console could "fix" it (the flashing of the avionics and/or the jitter). Regards, Frank

There were several things. When I first sent it in they said that it was a broken wire on the aileron pot. The second time they couldn't find anything and replaced the controller board. When I got it back it was still faulty so I opened it and found a bad protection diode in the power line for the avionics, a bad avionics master switch (both together made the avionics flash on and off wildley and display silly things), a bad soldering spot on the controller board and I think I resoldered some of the wires too. Regards, Frank

Hi, I've had something similar with my Cirrus II. Only the dot did not go fully left but only a small portion. If I used a certain amount of deflection I could actually make the plane bank left by turning the yoke to the right. This happened for elevator and rudder also (but the rudders are very old and I know they have a faulty pot). But I have never done anything special with assignments. I only ever fly the Baron and am using the twin prop quadrant exclusively. My Cirrus II did have some serious faults and after I had it sent for repairs the strange behaviour was gone. At some point it returned and I repaired the console myself and it was gone again. I haven't been flying for quite a long time now so I can't tell exactly how it developed but I allways suspected the hardware to be responsible. I seem to recall that now and then I had to deal with it by making the dead zones in a little wider. Regards, Frank

I stand corrected then :) .And for the rest - to each his own I think :wink: As I'm flying the Baron only (not that high) my preference is the smooth horizon. Thanks for making it possible via FSUIPC. The lowest limit in FS is much more than 30 miles (above the vis layer that is). Regards, Frank

Hi Joaquin, Pete, I found 30 miles to be the sweet spot. Set it to 31 and that sharp horizon line is back. But is it really that odd to want a more or less smooth transition from terrain to sky at the horizon? I don't have much experience in that regard but I remember flying to Tenerife once and there was no sharp horizon. Also I think the sharp line you can see in many screenshots is unrealistic somehow because I think it can't be there as long as you're inside the earth's atmosphere. That's why I love the visibility options in FSUIPC so much. Regards, Frank

Paolo, there's a sticky topic "READ THIS IF YOU LOSE YOUR FSUIPC or WIDEFS keys" near the top of this forum. Wasn't that of any help for you? Regards, Frank

Hi Chris, if I were you I wouldn't make it that complicated. Why not use a pair of buttons and assign the throttle increase/decrease controls available in FS to them. You don't even need to use FSUIPC for this. Just make the assignments in FS and activate the repeat function. If you want a slow change just tap on the respective button repeatedly, if you want a fast change keep holding it down. That's how I did it with prop and mixture until I got better hardware. And even easier - you could use the assignments that are already there in FS on F1-F4 (idle/dec/incr/full). I mean you have the keyboard in reach when you fly on a laptop, haven't you. Regards, Frank

Hi Warren, most of the times when the registration details are not accepted a simple typo or similar is the cause. The email adress in FSUIPC has no other function than identifying you, the user. So of course you must enter the adress you had when you registered. All details (name, email, reg-key) must be exactly the same as in the notification mail you got on purchase. Best is to copy and paste the data from that mail or from the FSUIPC.key file which you hopefully have a backup copy of or from your account on simmarket. The change of a graphic card should not make your FSUIPC unregistered unless you have also reinstalled windows. And you won't have to purchase a new registration since yours is valid for all 3.XX versions of FSUIPC. Regards, Frank

Hi, suggestions regarding FS should be sent tp tell_fs@microsoft.com. Regards, Frank

Hi, I seem to remember that an additional FSUIPC.dll in the main FS folder is (sometimes?) also read at startup and so could cause this error. Have you copied the file to the main FS folder as well by accident? Regards, Frank

Merry Christmas and a happy new year, Pete! I wish all the best to you and yours. I hope your eye sight is better meanwhile and developing towards normal. Thank you very much for the wonderful job you are doing here. Now give it a break and enjoy the holidays and your vacation in January. (Chasing steam railways again?) Kind regards, Frank

Hi, I use a Geforce FX 5900 ultra and a Samsung 191T flat screen at 1280x1024. Same resolution in Windows and FS. The picture quality is fine for me but I must admit I'm not so much into stunning screenshots but more into flying :wink: . From a grafical point of view - yes the AA could be improved. Regards, Frank

Hi all, it may be related to the driver but it also may be related to FS. I think - at least on some systems - FS does not like forced anti aliasing. I have problems with anti aliasing as soon as I set it to "on" in the video driver settings and "off" in FS's menu which is what is recommended almost everywhere. The Kneeboard won't work (scrolling) and also some dialogues. But when I set AA to "application dependant" in the driver and to "on" in FS all works as it should. Regards, Frank

Hi, it will remain registerd if you only replace the FSUIPC.dll in the modules folder with the new one. Don't touch anything else, especially the FSUIPC.key file. Regards, Frank

John, the most popular reason for this to happen would be a typo when entering the registration details. The best way is to copy and paste them from the notification email you received on purchase or from your old (backed up) fsuipc.key file. Regards, Frank

Mark, did you try what I suggested in my last post? You can change the font size in that dialogue.Regards, Frank

Hi Mark, what did you change to cause this? Also - have you checked there is no different setting for this in the display properties? Right click on the desktop, select properties and go to the tab where you can set the appearance of windows (don't know the exact terms, sorry, my windows is german). In the foreground you'll see a box with an OK button and some text in it. Click on the text and you see the settings for the colour, the font and the font size. Regards, Frank

Now that will be fun :lol: , hi, I have no idea about french language but I seem to understand that you are asking for other opportunities than credit card to pay for FSUIPC and WideFS registration? If you buy from Simmmarket there are other options. I have copied the info about payment from their website and hope it is of any help for you: Regards,Frank

Hi Richard, Pete is still away, but I can tell you that FSUIPC is fully compatible only with MS flight Simulator. It works - but not fully featured - with MS Combat Flight Simulator. It won't be of any use in other sims. Regards, Frank

Hi Rafael, I take it that you are trying to use the key you received when you registered FSUIPC on the new system? If this doesn't work the most common reason is a typo somewhere. The key and email adress must be exactly the same as in your notification email so take very good care there. A zero can easily be mixed up with a capital letter o as well as acapital i with a lower case L. Best is to copy and paste the details from a backup into the dialogue in FSUIPC. Simply putting the backed up FSUIPC.key file into the modules folder only works as long as the computer and the windows installation are the same so it's not an option in your case. But you can use it to copy and paste the registration details. Regards, Frank

Hi Arnaud, I don't think so :) don't know AI small world. If it is an FS problem I would tend to suspect a configuration error somewhere. Is FS set to the same resolution and colour depth as windows? Often when graphic cards or drivers are changed their entries remain in the FS9.cfg so scan this file for multiple [Display.device....] entries and remove the unneeded. Also you can try to delete/rename the fs9.cfg and let FS build up a new one with default settings.Regards, Frank

Hi Arnaud, I'm not an expert on that but I would suspect the graphics driver to be the culprit. It seems to have difficulties to display the colour gradient. Have you changed any settings there? Try another colour depth or try to reset every setting to its default value in the driver. Also try to set AA and AF to application dependant instead of turning it on in the driver. Just a few shots in the dark of course :) Regards, Frank

Hi Robert, I assume the hardware is OK and the controls are properly calibrated in windows game controller? Then go into FS menu and set sensitivity to max and null zone to min. Only then try to finetune the calibration in FSUIPC. From your ini file I see that the centre dead zones for all controls are set to zero, that means no dead zone at all. This way a slight noise or jitter on the joystick input will already give control movements and thus make the plane unstable. Calibrate again and make sure you set up a proper dead zone at each controls centre. The rudder entry for instance should then read something like Rudder=-16380,-512,512,16380. Regards, Frank

Hi, I think you'll have to wait for Pete to come back in order to solve this one. If FSUIPC works when unregistered and does not work when registered there may be something wrong with your user key. Pete will probably ask you to send him the FSUIPC.log and FSUIPC.key files from your FS modules folder for checking. Regards, Frank