Pete Dowson

A flattened slope in the calibrations should be all you need. It reduces sensitivity in the central, most used, area without sacrificing the ability to reach the extreme positions when needed. There is no other sensible way. If you change the calibration numbers in the INI file, say doubling the max and min numbers (eg +65000 and -65000 instead of the 32000, -32000 type values there) then the whole axis will be half as effective, but you won't be able to get to full deflection, only half. When I flew a real C150 or 172 I found the rudders very sensitive too, so maybe you should take A2A's word for it? Regards Pete

There are no assignments in the default Buttons section! It is empty. Look: The logs show the same. I'm afraid FSUIPC cannot apply assignments which don't exist! Pete

Is that all with hands off? i.e. you weren't touching the yoke? If so then it certainly has bad jitters. It will be hardware somewhere. Did you try a different cable, a different USB port? Actually, the fact that it is mainly airleron jitter probably just means a dirty pot on the aileron axis. Use a switch cleaner on it and move the ailerons from one extreme to the other to get the surface completely cean. If there's still a problem it is probably worn. You should be able to replace it. Naturaly, do all that with no power, i.e. disconnected. After than, calibrate in FSUIPC with enough centre zone to handle minor jitter -- which can arise in any case, often from poor power supplies. The elevator errors are different: They are all the same as this one, and they are all "spikes". There is a spike eliminator option you can use for this -- look in FSUIPC options, I think in "miscellaneous". However, these spikes are an indication of a dodgy connection -- when the signal is lost the reading zooms immediately to the max. Check the wiring for the elevator inside the unit. Regards Pete

This is exactly what I have been doing for years. This is why FSUIPC offers up to 4 separate assignable reverser axes. (as well as a generic all-engine reversers for those less provided with levers). Regards Pete

It's 4.926 now, both in the Download Links subforum here, and linked on the Schiratti web page. (The text there will be out of date though. I can't control that). Pete

Are all those axes (X, Y, R, S, T) shown as being on Joy 0? R is a rudder axis usually, S and T are usually sliders. If there is only the elevator and aileron axes on the device and FSUIPC is receiving these other axis values then it certainly sounds like hardware -- could be a bad USB connection, or the USB port in the PC (try another), or, most likely, the USB electronics inside the yoke. Same for the spiking, which might also just be dirty pots (use an electrical cleaner spray). By the way, your FSUIPC is out of date. 4.926 is the current version. Pete

There must be something wrong with the INI file -- there can't be any difference for P3D because all that stuff is pure FSUIPC code, nothing to do with P3D. I need to see your INI file and hopefully the log which proves what you are saying -- ie with the Button and Key logging enabled. You can paste the contents of the files here, but please enclise them using the <> button above the editing window. Pete

Okay. I'll take a look when I get some time. It may not be till later in January, but we'll see. Could be earlier. Pete

Maybe, maybe not. But it's not a simple job programming the complete MCP. It isn't just a matter of assigning the switches and dials, it's dealing with the displays. You'd do it in a Lua program using the GFD library, and you'd have to disable the Goflight driver or it would conflict. I really think you should first look for a solution from GoFlight. Regards Pete

You need to use GoFlight's own software. Why are you trying to assign in FSUIPC when Goflight does it all for standard FS aircraft? If you mean complex add-on aircraft not using standard FS methods, then you'll need to be a lot more specific I'm afraid -- they are all different! Pete

FSUIPC4 is best last, and that's where the installer puts it, though it isn't absolutely essential. The ASN module must come before FSUIPC. Otherwise there's probably not much to worry about regarding the order, though I suspect some things might just work better in different relative positions. Pete

Ah. Sorry, I don't know any way in FS9. It was added for FSX because SimConnect offered the facility. Pete

I've moved this out of the "Download Links" subforum (as it is not a list of download links), into the Support Forum. It is Dowson, actually. But follks call me Pete. Sorry, I don't know. SimMarket handle all of that, I am just the technical person for the software. If payment information is not available in SimMarket then perhaps you need to open a account and submit a Problem Ticket. [LATER] I see payment options are found on SimMarket, here: https://secure.simmarket.com/paymentoptions.php, and include bank transfer. I expect you have to tell your bank to pay in Euro and they will do the conversion and add their fees. Regards Pete

See FSUIPC documentation, and the tab called "Logging" in the FSUIPC options. Pete

Thanks. I'll have a look at that. Thanks, Pete

Three minutes? I really don't understand that! It all works fine here. It's not to do with ASN running or not, but the AS_Connect stuff loaded into FSX. The update from HiFi allows FSUIPC to test whether ASN is running with no time lage whatsoever. Before then FSUIPC has to search every top level window in Windows. But I really can't see how that possibly takes 3 minutes. Even with 100 such windows it should be a matter or millisseconds! And it iis only doing such a check once every 30 seconds! Anyway, I am release 4.925a imminently. Please try with that and let me know. Until HiFi release and update, this revised version will not allow FSGRW to work correctly unless the ASN module in DLL.XML is disabled. Regards Pete

Please see reply in other thread. Pete

Sorry, can you be a little more specific here? Are you talking about something in FSUIPC? Pete

There is really no way that will occur once the update to ASN is released. Before this, the only thing which is done, once every 30 seconds, is that FSUIPC checks the top-level Windows to see if any have a title bar starting "Active Sky Next". Until HiFi provided the faster solution in the as_connect modules this was the only way, and the suppliers of FSGRW were upset about the existing situation which demanded an immediate solution.. Unfortunately there is no way this intermediate method will work with the copy of ASN running on a client PC instead of the FSX PC, so it is to no avail it actually does the search. However, I would be surprised if the time taken to determine whether the window was present was noticeable. Perhaps you have very many top level windows open or minimised in your Windows setup? Even so, I would have thought that even just one or two milliseconds per Window would be excessive. What obviously will not work in this scenario is the FSGRW direct wind control, because FSUIPC has no way of knowing ASN is actually running. Maybe it is this aspect which is causing your pausing. All this will be fully sorted when HiFi release the next update for ASN. Regards Pete

MakeRunways is only a data extractor, producing files for other programs. It doesn't change anything FS can see. I'd report your problems on the P3D site if I were you. Pete

You can tell from the Install log. The P3D version 1 path is being found here (see emboldened part):: BTW version 4.923 is no longer supported. Please try the 4.925 installer in which I have made a small change to make sure the error refers to the correct verrsion (1 not 2). Pete

Yes, some things are read only, some are read/write, and some are even write-only (for special commands in FSUIPC). The offsets you mentioned earlier work. What offsets do you need to use which you think you cannot write to? If you have a problem, did you bother to try using Logging to see what is happening, as I suggested? Pete

[Moved from Download Links subforum to the Support Forum, where it can get attention] The current version of MakeRunways, 4.674, works fine on P3Dv2. Here's the title in the Runways.txt log file it produces: Make Runways File: Version 4.674 by Pete Dowson Reading SCENERY.CFG ... CFG file being used is: "C:\ProgramData\Lockheed Martin\Prepar3D v2\SCENERY.CFG" What is the problem you have? Pete

Seems you didn't read all of my reply? I did say "If you want to show me files, best to paste their contents into the message. You can wrap them up using the <> button above to differentiate them and make longer ones scrolable in their own right.". And the INI file isn't really relevant. As I said in my last reply, the Install log is quite important as it would show things about your installation which do look relevant. (I said "Better files to show are the Install Log and the main run-time FSUIPC4 log"). Anyway, even without the Install log there are some relevant things which indicate that your FSX + Simconnect install is not good: Exception 5 is bad. This is returned by SimConnect when things are mismatched, as it says. But there's no reason why it should do that shown in the log -- version 61472 of FSX is SP2 and version 61259 of SimConnect is the SP2 and Acceleration version of Simconnect, so they should match! I can only think that there's some corruption, or some mix up in modules, between these which doesn't show up iin the reports it is giving. The first thing I would try is to reinstall the SimConnect part -- run SimConnect.msi from the FSX SDK. If that doesn't work, or you don't have the SDK, then you could try running the SP2 update again. Maybe it will repair FSX. I don't know how FSX could get into such a state. Have you had other problems and tried reinstalling things at all? I know that uninstalling FSX doesn't work well on SimConnect installations and seems as likly to make things worse rather than better. I assume there were no records of FSUIPC4 actually crashing in the Windows event viewer? Regards Pete

Radar Contact support is over in the RC Forum on AVSIM. I'm afraid I've no idea what those messages mean. Someone there will help. It won't be anything to do with the version of FSUIPC, and I've never heard of anything called "fsuipc.rv4" even though I've been an RC user since it began. Sorry. Pete