teeb57

No need for appologies, It all works well now. Thank you again

this was from page 6 of the users manual: That‘s it! If you already use FSUIPC and haven‘t updated it for a long time (and I mean many months) you should probably remove your existing FSUIPC.INI file, found in that same folder, before running FS. This isn‘t usually necessary (and it isn‘t necessary now), but a number of entries in the older INI file are no longer relevant to FSUIPC and may lead to confusion later. By deleting the file you ensure that you start off with a clean default setup. next time I can assume I should ignore this step?

I updated & reread the manual to ensure I updated everything correctly. I deleted the old .INI file. After updating I noticed there's no new .INI file in the modules folder, or I'm not looking in the right place. I didn't change or do anything for this toggle cmmand to quit working. I'll check to see if theres any other commands interfering with the spoilers after I get this .INI thing figured out, thanks for your help, steve Disregard! I have it all working now as it should, I'm still not sure about the .INI file, but if i can't figure it out, I'll let you know. steve

I'm running windows vista, fs2004 & fsuipc 3.90. A button controlling "spoilers Arm Toggle" quit working. I alternated this same button to see if it was capable of using other commands, it worked fine. But when going back to the spoiler arm toggle function, this button wont work. I can see the spoiler lever wanting to move (a very momentary jump) but wont make it into its propper position. Thanks in advanced for any help. Steve

i wanted to write this update to the control problem that ive posted here just in case anyone else has the same or a similar problem. i hope someone else out there can benefit from the hours of tinkering that it took me with this problem that turned out to be a very simple fix. uncommanded control movements, in my case the rudder, were reoccurring. i thought the problem had been fixed several months ago but started again 2 days ago. the problem was due to the joystick being plugged into a "bad" port. after trying different ports on the computer, all was well. but when reconnecting to the suspected port, the problem reoccurred each time.

ty mt. after hours of trying to understand what could be causing this i decided to close fs2004, shut the computer down & disconnect the joystick. starting everything from a clean slate seems to have fixed the problem. one of these days i'll learn to start with the easiest fix 1st. but it all works great agin thanks for your input

after months of solving this problem, the uncommanded rudder trim issue has returned. all aircraft in fs2004 & pmdg are affected. after moving any axis or touching any button, the rudder trim mover full deflection. i took this log & would hope anyone can help me make sense of this. thanks in advance for any help, steve 119606 *** EVENT: Cntrl= 66279 (0x000102e7), Param= 0 (0x00000000) RUDDER_TRIM_RIGHT 119622 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=8, (Result 4) 119622 [buttons] 11=R0,8,C66279,0 119637 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=8, (Result 4) 119637 [buttons] 11=R0,8,C66279,0 119668 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=8, (RepeatOk sets 2) 119668 [buttons] 11=R0,8,C66279,0 119668 Repeating flag set: bRef=0, Joy=0, Btn=8 (RepeatDelayCtr=11) 119668 FS Control Sent: Ctrl=66279, Param=0 119668 *** EVENT: Cntrl= 66279 (0x000102e7), Param= 0 (0x00000000) RUDDER_TRIM_RIGHT 119684 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=8, (Result 4) 119684 [buttons] 11=R0,8,C66279,0 119715 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=8, (RepeatOk sets 2) 119715 [buttons] 11=R0,8,C66279,0 119715 Repeating flag set: bRef=0, Joy=0, Btn=8 (RepeatDelayCtr=11) 119715 FS Control Sent: Ctrl=66279, Param=0 119715 *** EVENT: Cntrl= 66279 (0x000102e7), Param= 0 (0x00000000) RUDDER_TRIM_RIGHT 119746 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=8, (Result 4) 119746 [buttons] 11=R0,8,C66279,0 119778 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=8, (RepeatOk sets 2) 119778 [buttons] 11=R0,8,C66279,0 119778 Repeating flag set: bRef=0, Joy=0, Btn=8 (RepeatDelayCtr=11) 119778 FS Control Sent: Ctrl=66279, Param=0 119778 *** EVENT: Cntrl= 66279 (0x000102e7), Param= 0 (0x00000000) RUDDER_TRIM_RIGHT 679275 System time = 11:29:09, FS2004 time = 17:58:59 (22:58Z) 679275 *** FSUIPC log file being closed Memory managed: 0 Allocs, 5562 Freed ********* FSUIPC Log file closed ***********

pete, i saw earlier where you said the "log" file. i 1st looked for the log file in the module folder then looked every where i possibly could in fs9.... no joy on any log file any where on this computer. no need to respond to this message pete. it will take me some time to get caught up with the rest of the computerized world. my shopping list looks nor sounds anything like this. maybe i should get my 6 year old to explain it to me. no ones fault but mine. it has worked great now for the better part of a week, so no complaints from me. good day to you

you betcha! i had never heard of goflight until i saw your post. great stuff

thats interesting. i suspect ill be learning a lot about all this for a long time to come. i have to say, what i thought was impressive was the control console and rado racks!! i was waiting to find a circuit breaker panel in there some where. very nice!!

i deleted this rudder trim assignment sometime back but still had the same problem. you gave me an idea i hadnt thought of before. i went back into assignments & deleted ALL assignments in fs. that took care of the problem. all is right with the world again! thanks for taking the time helping me out. that was getting to be a tad frustrating

thanks pschlute. yes i can see the rudder trim on all aircraft. when i open fs, the rudder trim is in the nuetral position. the moment i move any axis or push any button, the rudder will then move to full right deflection, i can watch as the rudder indicator goes thru this. when all this started i did a complete calibration of the joystick & everything checked out fine, so i dont think the joystick is the problem, but i dont know for certain. ive read & reread the users guide more times than i care to count trying to figure out how to apply the logging. your input is a big help. thanks for your time & suggestions.

ok, i give up. the unfortunate aspect of this is that i now have to confess that I’m a dumb **s. i still don’t know what or where I’m supposed to be looking. quote: "Try searching fro the English words "Rudder" or "Trim"! It is the rudder trim you said was going awry, wasn't it? So why not look to see if such events are actually occurring as a first step?" exactly WHERE do i look to search for the words rudder or trim? I’m not sure what is meant by quote "Best list all the add-ons you are running in FS too -- I've never heard of a runaway rudder trim problerm as virtually nothing uses the rudder trim in FS at all." i don’t have a clue of all this computer mumbo jumbo let alone what’s using rudder trim. that’s sure not your mistake pete, its mine. all i know is that i cant fly or practice emergencies or engine outs with no rudder trim. i sure cant use a rudder with uncommanded full deflection. All I do with fs 2004 is practice hand flying or emergencies until I’m recalled back to the airlines. fsuipc has been a great tool so far. thanks for any help. steve

i hope you enjoy! thanks for that quick response

yes, rudder trim is the problem. but where do i look to find what the trim is doing?

thank you pete. i have fsupic installed & checked off buttons, axis & event on the loggs page. after running fs, i went to the ini file but dont realy understand what im looking for in terms of button or axis commands. ive seen all the commands in the log files & tried to read what it is that im supposed to be looking for but im afraid i dont understand any of this yet.

im running windows vista fs2004. i have all buttons & axis programed using fs. today my rudder trim decided to grow a mind of its own. when i start fs everything loads fine except the right rudder trim. i get a full right rudder command & i cant correct with any amount of left rudder trim. i tried flying like this and now know the trim is actualy in its indicated full right rudder position. this is occuring in all aircraft, pmdg & 2004 aircraft, regardless of wether fsuipc is applied to that specific aircraft or not. i had this problem before but was easily corrected once i disabled the joystick in fs. thanks in advance for any suggestions. also, I have a saitek yoke as well. maybe thats where i need to start looking. steve

thanks pete, welcome back

thanks peter

im running fs2004, windows vista 64 bit & have programed all aircraft's buttons & axis using fs. i have everything programmed & am very impressed with how well things are working now. two exceptions, both on the pmdg 747. i cant program toga or auto pilot buttons. also, when i turn toga & the auto pilot on using the mouse, the assigned buttons will not turn toga nor the auto pilot off. no matter what i do, it doesnt work. theres no problem with the other 3 aircraft i have programmed. any suggestions would be appreciated. ive just recently become a "simmer" & am learning all the new stuff thats available out there. i'm very impressive & wish i had known about a lot of these programs sooner. if you had a choice in choosing a flight sim for yourself now which would it be, fs2004 or fsx? i hope its ok to ask this question here, but i would just like to know more about the pros & cons of both. regards, steve

i have windows vista & am running fs2004 with the saitek yoke. yesterday as i was attempting to program keys for a caravan using fsuipc. i was trying to designate the #7 button to control left rudder trim & the #8 button to control right rudder trim. this programing was successful for a few minutes. for some unknown reason, the #7 button quit working & began displaying the electronic kneepad each time the #7 button was pushed. the electronic kneepad is normaly activated by the F10 key. at the same time, the #8 button quit functioning, so now i have no rudder trim control. i then went to a different aircraft & tried the #7 button where again there was no rudder movement, only the electronic kneepad displayed. i then went to a pmdg aircraft & the same thing happend again. today i tried uninstalling & reinstalling fs2004 only to be met with the same result. i have the same programs set up on a laptop where the buttom commands perform their intended function. (the problem is occuring on a desktop). this makes me think that something has been programmed somehow internally onto the computer. has anyone else had this problem? can anything be done to reprogram the settings? update! i guess this post can be disregarded. it took me a few days but i just learned the hard way that fs2004 WILL revert back to its own control setting, bypassing the fsuipc all together. my controls were run by fs2004 just as the users guide said.

ok pete, thank you for your time & suggestions. ill try to reinstall. i just hated to touch or breath on anything if i had it working well as i do now. i assume this reinstallation is true for vista users & not necessarily xp users?

an update to my last post above. ive tried editing from the edit menu in notepad & now get a new error message. "cannot create the c:\program files (x86)\microsoft games\flight simulator 9\modules\fsuipc.ini file. make sure that the path and file name are correct".

im running vista. i want to edit the .ini file to read "useprofiles=yes". when i change the no to a yes & try to save, im given the following error message: "access to C:\program files (x86)\microsoftgames\flightsimulator9\modules\fsuipc.ini was denied". ive tried to edit every way i know with no luck. when i try to do the same thing on my laptop, which is xp, i have no problems at all. please disregard this & my next post. i worked with the editor for about an hour, called a so called expert on the subject & finally gave up & poted here. ive learned i had to click on 'compatibilty files' before i could edit. at least thats what i think! i must have hit the correct button somewhere because it all works well now

Andy, Pete, thank you both for that. yes pete, im looking at the .dll folder while its still in the zip file. ill try doing this another way. thanks again you guys