granathg

While recovering from spine surgery I haven't been able to set up FSUIPC7 adequately for the C172. Could anyone answer two questions please? I'm sure my copy of FSUIPC7 is grossly downlevel. Must I uninstall the old level before installing the current one? After assigning C172 axes (Saitek yoke, TQ, and rudder, no matter how hard I tried, control surface sensitivities were far too touchy. Might you have a basic axis assignment and calibration setup that I could use as a starting point? I'd really appreciate it if someone could give me a hand. Thanks and Regards, Gary

John, I haven't been able to respond to your latest recommendation (extended health issue). (I think we may have been in direct or private message mode. Can't find your recommendation.) In that thread, you asked me to upload my FSUIPC7.ini file so you could assist with classic Cessna 172 settings. Flight controls work now but way too sensitive. Have to find my most current file, then I'll upload it. The Cessna is all I want to work with. Could you have a look and either recommend changes or just modify it and return to me? Best Regards, Gary

And John, thank you very much for your help and patience.

Thank You! I never would have guessed. I didn't have to concern myself with this in FSX.

You have more productive things to do but please bear with me. I'm stumped. Your instructions are clear but please see uploaded screenshot. On the Welcome page I tap OPTIONS, then CONTROLS, and select the yoke. There is no PRESET MANAGER here. Perhaps something is corrupted. During the initial install I had a catastrophic power failure. I attempted a clean reinstall but I'm not confident that I got the right direction from MSFS support. Several ways of reinstalling are documented. I had to guess.

Thank you very much John. You and Pete excel at support. I flopped because even though I have always followed your U/G, I didn't look for one that gives me access to the controls/events exposed by MSFS. As I initially modified MSFS control settings, MSFS itself seems to have created different names for each device. Even now, not fully understanding what constitutes an MSFS profile, I don't clearly know what I must I do to create a new, empty MSFS profile. For the present, I'll leave all MSFS device settings untouched until I find the new guides you mention.

One contributing issue that remains unresolved is the lack of an MSFS User Guide. Without one, as many other users, I've had to guess at control setup. Each controller has two columns for its axes and button/key commands. Without an explanation, I've failed at customizing. As I recall, an FSUIPC4 'profile' applied to a category of aircraft, such as 'dual engine piston'. Now - the way I read your reply, a profile is something that can be defined within MSFS (not as defined within FSUIPC7) and applies to a controller, not to an aircraft category. But I probably misunderstand again (FSUIPC7 probably allows me to create aircraft profiles). It appeared that as I assigned axes and buttons in MSFS, it created a profile for each controller, each (oddly) with its own name. Tried to fly but - bedlam. Since I can't disable the app's control of the devices as I could in FSX (untick one box), I tried deleting the original options from the double-column lists under each controller. Bedlam of a new kind. Ugh. I'm no good at guessing. An MSFS U/G would be a helpful companion. Then, to see what would happen, I set all MSFS controls to 'Default' and didn't open FSUIPC7. I started a C172 flight, and as expected, all axes and buttons worked. The first time I tried to use FSUIPC7 to customize axis and button assignments the controls didn't work as I expected (based on my experience with FSUIPC4). Maybe I had too much extraneous info in fsuipc7.ini. Unless you have to correct me again, first I'll set all MSFS controllers to 'Default'. Then close it and start FSUIPC7 and MSFS. In FSUIPC7 I'll assign/calibrate axes and buttons, then see if MSFS can handle it. My ancestry prevents me from giving up until I go down and stay down. Kind Regards, Gary

Pete, My apologies. I wanted to search the forum for my userid anywhere. I misunderstood the search options and failed to tick 'members'. Probably should have ticked 'this forum' too.

I last communicated with John on 2/10/2021 about MSFS control settings for Cessna 172 conflicting with settings I was making in FSUIPC7. He asked me to upgrade to ver 7.0.4 but I've been ill and while I was recovering I saw that 7.0.5 is available so I just installed it. Has my topic been purged because I was late? I can't find it. John said to make changes to the ini file and I then realized just how bad it was (planes from FSX/FSUIPC4 that don't exist in MSFS). So I have created a new ini. I'm basically starting all over. I had conflicts with default MSFS' axis and button settings that I couldn't resolve, so if you could get me started I'll try to finish things. I'll do what you recommend - I'd like to reassign yoke and TQ buttons and axes. I want to avoid conflicts but don't know how to make it happen. I just want to start with the Cessna and try to understand what needs doing. I had no problem with FSX/FSUIP4 but MSFS is not my friend and I'm older now (81 in June). MSFS has bugs that may never be fixed (autopilot for one), but if I can get the Cessna in the air and keep it there at least I can look at the scenery. So can you assist me? I can upload the new (quite barebones) ini file and try to stay healthy. Thanks and Best Regards, Gary

I appreciate you trying to help this novice. I had no trouble at all with flaps in FSUIPC4/FSX. I'm perplexed. MSFS takes so long to open, start a flight and test my changes in FSUIPC7, that I've spent hours with what should be simple. For one thing, in the U/G aren't the two images on p. 41 in reverse order from what the last sentence on p. 40 says? That's how I understand it. Out of desperation I resorted to manually editing the file (unsuccessfully). In FSUIPC4 I had to disable FSX's controls to keep them from conflicting with FSUIPC. Must I do something similar with MSFS? I think I got FSUIPC7.ini uploaded this time so you can see what I'm working with. Thanks you, Gary FSUIPC7.ini

I think I misunderstood something vital when I had a registration/install problem. I was told to make a copy of my FSUIPC4.ini file and name it FSUIPC7.ini. I now question that. The copied file still has remnants for Maule M7 and Dehavilland Beaver, among other things. Agghh! I have uploaded a copy of my FSUIPC7.ini for you to confirm my error(s). My C172 profile name is single_engine_piston. FSUIPC7.ini.lnk

Really, this isn't working the way I understand the U/G. My mind must be wired differently. I do my best at following the U/G directions but very little is going as the U/G says it should - which column, which box, which button etc. For awhile when moving the lever from one extreme to the other, I couldn't get the numbers on either end to their highest values. But after thrashing I thought I had completed min, two detents, and max. When I clicked OK and went back to MSFS the flaps were at max (but the lever was still at the detent just before max. I moved the lever up to no flaps and the flaps didn't change. Then they started working backwards! What the! Back in MSFS' Control Settings, F5 thru F8 are still fully operational for flaps. Now then, in FSUIPC4 I was required to disable FSX's control mechanism so the FSX settings wouldn't interfere with FSUIPC's. Is that true here as well? I think I'm sane but nobody would believe it, given what's happening. Can I just cut to the chase by manually entering the values into the ini file? One final question. Might using offsets instead of "normal" axis assignment and calibration improve my chances? I'm completely perplexed.

May I please jump in here? I would prefer to use detents for flaps too (worked fine with FSUIPC4/FSX), even though on page 40 of the U/G you seem to recommend against it. I am using the Saitek/Logitech TQ. Please reference: U/G page 40, Calibrating Flaps With Specific Detentes, on page 41 Step 2 (copied below). I'm doing this for C172 steam gauge. 2. Set the lever to a position a bit before the Flaps Full position/notch (i.e. at the other end, but not quite ‘full’), and make this the maximum (i.e. click the right-hand ‘Set’). The zone for Flaps Full (currently #2, but that will change as we add more détentes) is now set. You don't change the maximum again (unless you need to adjust the Flaps Full zone on the axis). I slide the lever down as directed but the value in the box under the third Set button (Max column) won't increment to what I expect should be a negative value just short of -16384. It doesn't increment at all. Can you help me get the drift of what I'm doing wrong? Thanks, Gary

It's late and I'm tired but I made progress. I found the readme.txt that must be well known now and followed the link to microsoft answers where it says: ----- Uninstall the 2017 version of the C+= Redistributable, if that is installed on your System The 2017 version is not installed on my system. Does this mean I have to uninstall my current 2015 version, download the 2015 version from the link below, then find a 2017 version somewhere and install that too? -----Then from the link below, download and install the 2015 version, then once that is installed, download and install the 2017 version]-----Then, restart your PC . . . https://support.microsoft.com/en-gb/help/297700... Best Regards, Gary

I was directed here (for John Dowson) by tech support at simmarket, where I purchased FSUIPC7 for MSFS 2020. I have installed FSUIPC7 and have entered the registration information exactly as shown on the simmarket order acknowledgement page. Registration fails as shown in the screenshot I uploaded to dropbox at the link: https://www.dropbox.com/preview/FSUIPC Install Problem_2.jpg?role=personal Simmrket can't duplicate the failure so we're at a dead end there. They sent me to you. Can you give me any direction? Best Regards, Gary

On Windows 10 FSX with FSUIPC4 worked beautifully. Now I'm learning MSFS and I don't like its control of yoke, TQ, rudder, keys, buttons. I'd like to know if FSUIIPC7 will work for me. While investigating this, I read on the Dowson site that PC MSFS is supported but XBOX MSFS is not. I'm using Windows 10 on a desktop, nothing to do with an XBOX. Please clarify what XBOX MSFS means. The best I can do is guess. No sense in buying FSUIPC7 if I can't use it. I bought FS through Best Buy and during the install I was seeing "XBOX" frequently, and Microsoft Store Gaming is involved in this somehow. When launching MSFS , the screen displays: XBOX GAME STUDIOS, then ASOBO STUDIOS, then blackshark.ai. If that means I'm unsupported I can stop spending more time on this. Help please.

I had a system meltdown and lost everything. I am now reinstalling FSUIPC4. I downloaded the current version zip file from schiratti and clicked "Install FSUIPC4." A msg said: "FSUIPC4.DLL 4.957b installed into FSX ok." But the "FSXUIPC Install" file said: "Registration check for FSUIPC4 was cancelled or failed! (result code 10)." I have my license key information but how do I use it to reinstall? (As directed, I read the FSUIPC4 User Guide page 5, but saw nothing that would help me perform the FSUIPC4 reinstall. How can I proceed?) Thank You, Gary

Hello Pete, I use FSUIPC4 4.703 with FSX. After a long VFR flight in a Cessna 172 - using AP either in NAV mode, or in GPS mode with a flight plan loaded - during my approach, after deactivating AP I realize that rudder control no longer works. Once on the ground neither rudder nor differential brakes work. I opened FSUIPC and the axis assignments/calibration seemed normal (the IN and OUT box values changed as expected). When I exited FSUIPC and resumed FSX, the controls worked as they should. I use Saitek yoke/TQ and pedal/brake units. I can't blame FSUIPC because I also tried operating rudder and brakes using the keyboard NUM keys. That didn't work either. I can recover from this annoyance and land normally by opening FSUIPC shortly before beginning an approach but that's not really a fix. Ever heard of anything like this? Does FSUIPC log anything that might help me diagnose this bug? MH

Hi Pete, Good enough. Thanks for the information. With the FS Clock Synced unticked FSX runs smooth as silk. I am going to disable my AV and use alacrityPC to suspend some other apps and services and see if that will help too. My processor is only a i7 930 quad overclocked to 3.36 GHz. but it does a super job. Thanks again for your comments. Regards, Ga;ry

I think FSUIPC has something to do with this failure because if I run FSX with no add-ons I have no problems. If I install any addons other than FSUIPC, I have no problems. But if FSUIPC is the only add-on, I have problems. A reasonable person might suspect FSUIPC is involved and investigate further. As you said, I'm probably seeing a scenery reload, not a flight reload. You said a scenery reload is caused by a time correction exceeding one minute. "Keep FS clock synced" was ticked. I think that's what you're referring to. So it's possible that a "time distortion" occurred, by which I think you mean the system clock differs from the FS clock by more than a minute. But then you say that FS normally syncs on a 50-second cycle if it can, thus there should never have been a scenery reload. Why might FS be unable to sync on a 50-second cycle? Page six of the Advanced User's Guide defines ClockSync and ClockSyncMins (see next paragraph). It could be written more clearly and an example would help. Do these two options permit me to avoid the sync problem by going into FSUIPC.ini and manually setting ClockSync to Yes and ClockSyncMins to 1? Or am I just as well off to simply set ClockSync to No? ClockSync: This facility synchronises the seconds values with that of your PCs system clock. It is defaulted off (=No). Note that the synchronisation can only operate when the seconds = 0, and then it also has to set the miunte. Consequently, it will only attempt to make an adjustment when the minutes difference is less than that set by the next parameter: ClockSyncMins: The minutes difference within which FSUIPC4‘s ClockSync facility will operate. This defaults to 5, but note that if you want to reduce the occasions that FSX reloads textures, you will need to set this less. Conversely, if you want the exact minutes value to be maintained as well as seconds, set this to 59 or 60. I'm incredulous that you can't make head or tail of the screenshots. They clearly show that the flights had been interrupted and then restarted in midflight, with all evidence of the earlier portion of the flight obliterated. That seems easy to understand. I investigated GoFlight and VRi. Thanks for mentioning them. Their physical size and pricing make them impractical for the casual simmer such as myself. If I had $3,000+ USD burning a hole in my pocket, I would find a way to spend it that includes my dear wife. I think the type of simming done by most of us is not serious enough that we'd buy that expensive gear, use most of a room to build a 5-screen flight deck mockup with overhead instruments and who knows what else. At some point pretending becomes unreasonable. Many of us don't want to go that far. Anyhow, you haven't addressed the rudder and elevator going full limit and chattering. If you have any ideas about that, I'd be pleased to hear them. Perhaps I'll increase the dead zones for those controls and see what happens. The Saitek software, which I abhor, may be my best option. Too bad, I really like FSUIPC.

Would you care to send me a brief PM regarding the merits, or otherwise, of the most popular FS hardware?

Hello Pete, I have an interesting issue. I run FSX/FSUIPC4 on a Win 7 system. I have a Saitek yoke, TQ, and pedals. The problem: While flying, FSX reloads the flight repeatedly, resetting the flight in the logbook and map view, without any action on my part. It happened once as I was lifting off the runway. I was using version 4.57, so upgraded to 4.60 but the failure remains. It seems to occur more often if I am on Autopilot in my C172, occasionally changing heading and altitude during a long flight. In my test case I'm using no add-ons except FUIPC4. If I remove the FSUIPC4 dll file from the FSX Module folder the problem stops. Cockpit and VC modes both fail. I got desperate and did a complete reinstall of Windows 7 and FSX, but no joy. I even shipped the system back to the builder, who did the same, more professionally. The problem still exists. I have attached several .png files to show what FSX Map View looks like when this happens. I am able to use Saitek's software without similar failures, but FSUIPC4 offers many more options so I'd love to fix this. Another oddity - this morning while changing either altitude or heading in VC mode, the yoke chattered as if I were tweaking it rapidly. But I was moving it off-center very smoothly. And just after landing, when I began a taxi the rudder seemed to be jammed left. I could only move in circles. I clicked the key to center the rudder and everything was fine. Then I did Spot View and could see that the elevator was jammed down. I was able to get it moving somewhat well, but just off the center of travel it too would chatter as if I were moving it rapidly. I think I have adequate dead zones defined, spikes removed, and filtering on. The LED on the yoke has what I consider a non critical symptom. It flashes very rapidly. But I don't use it so I've written it off as something not worth fixing. I have a functional Saitek joystick that I could use - to eliminate the yoke/TQ/pedals, if you think it's worth trying. If I can provide additional information to isolate the cause, please ask. Perhaps there are log, cfg, or ini files or something to explain why it's happening. Thanks, Gary

Well... I've assigned an axis to the hat switch but it wasn't completely satisfying. Maybe I didn't do it correctly. I'm using profile-specific settings. On the Axis Assignment tab no matter which way I move the hat switch it shows up as Joy# Y, Axis# P. I assume you meant for me to make my selections from the left side of the window, although the right side says "This side to send button controls." The right side seems to be for buttons to be sent within a range for action. Am I correct? So on the left side of the window I tick Send to FS as normal axis, then tick the first text entry line and select Pan View. As long as I hold the hat switch transferred, the numbers in the In/Out boxes indicate the direction in which I've moved it. When I release, both boxes display -1. When I test my work, cockpit view works as it should but VC view is quite erratic. You said it would be smooth but it's not, so did I misread your directions? At least when I release the hat switch the view doesn't snap back to front, but I didn't expect the jumpiness. Does it sound as though I've done the right thing? MH

Didn't try Barrie's method. The U/G specifically says it reverts to the previous view upon release so I concluded that meant if I viewed right (90), then right-down(135), then down (180), then released... that I'd revert to right-down. But upon further thought the switch must perform a release when I move between positions so... I see it would work, but be jumpy as you say. The hat switch being a switch (not a lever of some sort) led me to believe that I couldn't program it in Axis assignments. If I can do that, it seems that would resolve my issue. On the Axis tab the hat switch shows up as Joy Y, Axis P - no matter the position to which I move it. If I select "Send to FS as normal axis" and "Pan View," is that the approach you're recommending? It will work for both modes - cockpit and VC? Switching between modes could be confusing but I find it helpful occasionally in viewing parts of the control panel. I'm sure I could polish my "technique" and eliminate the switching, but it hasn't been a problem so far. Hell's bells... I'm confused most of the time and my dear wife seems to get a kick out of watching me. I'm 70. It's part of the process. Best Regards, Gary

I just installed FSX and have FSUIPC4-coded my hat switch the same way I FSUIPC3-coded it in FS9. I've set things up exactly as shown in the example on page 35 of the FSUIPC4.57 User Guide. For example, I use PAN RIGHT on press (parm=90), to repeat, and PAN RESET COCKPIT on release. Cockpit mode works fine, the way it did in FS9. It snaps right on press, and snaps forward on release. In Virtual cockpit, it pans right correctly, but when I release the POV, instead of staying put, it snaps back to front view. I could delete the PAN RESET COCKPIT on release and get Virt Cockpit to work, but then cockpit mode wouldn't be right. I could code it per Barrie's suggestion, but I'm used to doing it this way. Any ideas? Thanks, Gary