bobsk8

OK. but it is working perfectly now, did 3 flights yesterday, zero problems.

It works now... I redid everything from scratch. I installed older version into a fresh folder, updated it to latest version with a new download of the update file. I then replaced the exe in the updated version with the one you sent me, and now everything works. 😃

Unfortunately , this didn't work at all. I installed the file, I booted up MSFS, and all my settings in Assistance went to easy, and everything was jumping all over on the screen, with loud clicking noises. I had to restart PC, go back to my old version of FSUIPC, and reset all the settings. Scared me for awhile till I got everything going again.

Thanks, I appreciate your help in this.

This is a log file of the one that works. I sent two commands with 0 and two with X. Question, how do a assign a button release to key release.? FSUIPC7.log FSUIPC7.ini

I use FSUIPC to just generate a keypress on my keyboard, the number 0 and the letter X. The ATC program is set to pick up those two keypresses. I was using 7.0.4 which still works perfectly. The files I am sending you are the updated FSUIPC where it does not work with the updated version. Hoping that is sufficient. FSUIPC7.log FSUIPC7.ini

I have worked on this update all morning. I only have two things I use FSUIPC paid version for, When I press one joystick button, I want it to send a 0 ( zero) key to my PF3 ATC program. When I press the next joystick button I want it to send an X keypress. My former version of FSUIPC does this perfectly. The new version will not. I have a backup of the older version on a Macrium drive, and if I reinstall the older version everything works perfectly. I run the update of the latest version, and the 0 and X keypresses again are not transmitted to the ATC program, I have done this several times. I have even tried replacing the new ini file with the one that works, and still it doesn't work. I cannot figure out why this doesn't work InstallFSUIPC7.log

I had the same problem. I think I may have unchecked Mobiflight. Will try later and see if it works this time.

Guess I am just not very bright.

Read that user guide several times, and didn't seem to find the answers to my question. Will look at it again tonight when I get home.

On the axis calibration screen , to the left of the set buttons, there are two boxes labeled In and Out. What is the actual purposes of the numbers in these boxes and what do they affect? The other question is, when calibrating an axis, let's say the joystick in one position reads +16,000 and the opposite reading is -16,000 . Now I move it to center, and sometimes it will not read zero when hitting the center set button. Also, below that center set button, there is another box, and if you hit the set button again, that number in the lower box changes. I am not quite sure if both center boxes should both read zero, or if I have a problem if they don't. Bob

Pete, I followed your advice and disabled controls in P3D, reset up everything in FSUIPC, and now all is well, the copter and my aircraft are working fine with no problems. Thanks.....

Ok, something you mentioned, I do have controllers still enabled in P3D, since one of the A2A controller config assignments will only work with it enabled. That may be the problem. I will disable that and give it another try. I will update FSUIPC, although I thought I just did that a couple of weeks ago.

I purchased a Milviz 407 copter yesterday, installed it, and ran the configurator that sets up a control for trimming the copter when flying, using a joystick button to trigger this action. Anyway, after I did this, I went back to my A2A constellation aircraft, and a few of my FSUIPC settings had been changed. I am running the elevator axis and some switch positions, and these got scrambled up. The first thing I did was to use a back up FSUIPC .ini that I keep updated on a backup drive, but this didn't fix the corrupted settings, so I had to redo the settings one by one in FSuipc. Today I ran the Milviz config program again, and the same thing happened. It actually coupled one of my joystick elevator settings to the throttle, and again disabled some switches I use for prop adjustment in the Connie. I decided to unistall the Milviz 407 and place it in the digital trash bin after this happened the third time. Now , the reason for my post is, why doesn't the backup ini file keep all the correct settings, so that I would be able to just delete the new file and use the backup ini, and everything would be back to normal? I was under the impression that all the settings for FSUIPC are stored in the ini. I will include the ini that I just set with everything working correctly. Not looking for a fix, just wanted to make sure I wasn't doing something wrong. Thanks, Bob bobsk8 FSUIPC4.ini FSUIPC4.log

Not everyone has this problem. I have no idea why, I am not a software programmer, just a pilot. Another very experienced simmer suggested that I add this line to the FSUIPC.ini. and when I did, and it fixed the problem instantly. Two other people emailed me that they had the same issue, added the line, and their problem went away. All I know is it is fixed now.

I found the problem with the slow shutdown of the PMDG 737 NGX in P3D Version 3.1 that I was experiencing after moving from P3D version 3.0 to version 3.1 with the PMDG 737 aircraft. Others have had the same issue with the PMDG 777 and version 3.1, This closing of P3D could take up to 30 seconds and while waiting for the final screen that gives the prompt " are you sure you want to close P3D" , P3D say's it is not responding. With the help of a forum member in the P3D forum on Avsim.com I found what is causing the slow shutdown with the PMDG aircraft, It is the latest version of FSUIPC 4.949 and it's default of saving the last flight. Apparently saving the last flight with the PMDG aircraft takes much more time than any other aircraft, and the screen that says " are you sure you want to exit P3D ( or something similar) will not pop up until this save is finished by FSUIPC. I do not have autosave checked in FSUIPC, so this is the default condition of paid FSUIPC. What I did was to add the line SavePreviousFlight=no in the FSUIPC.ini file under modules in the P3D folder under [General]. Now the shutdown is immediate. This probably would affect the PMDG 777 also.

Airbus A300 series and Fsuipc joystick calibration. I did it yesterday on my A320 and clicked the smoothing checkbox after I calibrated the yoke for aileron and elevator controls. I then lost all control of the aileron and rudder for that aircraft, I double checked the calibration and it was correct, and all the settings in the A320 were good, but I could not get the aileron and elevator to move at all. I then unchecked the smoothing check box, and everything returned to normal. I tried checking it again to see if that was actually the cause of the problem,and it definetly was. Just an FYI in case you ever run into this issue.

Thanks.... BTW I think there is some different programming on the Majestic Q400 that is not typical in FSX and P3D, for instance the throttle when set to full, only goes to a green line in the engine control which is around 70%. When I changed the axis in FSUIPC I got some overspeed of the engine and an indication on the engine panel of 130% throttle, and when I went back to assigning the throttle in P3D, the overspeed instantly went away. Apparently that is at least one function that is controlled by the aircraft.

I just got the paid version of FSuipc yesterday and have a question. II tried for hours to program the axis settings in P3D on my Majestic Q400, and each time I had a problem. I watched the tutorial videos and read a couple of manuals, that included disabling the joystick assignments in P3D, but still had erratic results when finished. The only reason I wanted to do this axis editing was to use the slope function on the joystick to tone down the responsiveness for the elevator and ailerons in the center region. I finally discovered, that if I left the control settings for each axis assigned as normal in P3D, and just calibrated the Joystick using FSuipc, including setting the slope for those 2 joystick functions, it seems to work properly when flying the aircraft. My question is, is this an acceptable way to use FSuipc to get the outcome that I am trying to achieve?

I installed an updated Airac in Pro AtC and the instructions say to install Make Runways in your main Flight Simulator folder, in my Case P3D. I installed the new Airac into Pro ATC and now trying to align runways in which Pro ATC uses the Make Rwys exe. When I click on the align selection, is says it can't find the makerwys exe. My question is, exactly where is makerwys supposed to be installed in particular what folder, for it to be able to be found by Pro ATC? I have tried installing make runways in the P3D folder that has the scenery .cfg. but Pro ATC still can't locate it.