Pete Dowson

FSUIPC is a toolkit with many facilities. You need to decide what you want to use it for first. The no general way to tell you how to use it, you do not have to use any of it at all -- it's prime purpose is just an interface into FS for many application programs, so you just ignore it. You don't "program" a yoke. Just assign it. Use normal FS assignments if you don't understand FSUIPC. Why do you want to use FSUIPC in any case? Sorry, there's no helpful information here. What do you mean by "axis settings"? Since neither FSUIPC nor FS takes any notice of the yoke position unless it changes, it sounds as if you either have something else entirely assigned to the ailerons, or your yoke is severely faulty. Check it in Windows' game controllers. Pete

There's a limit in the internal coding of the controls assigned to Lua files -- only 7 bits are available for this, and to alter this would be pretty much a rewrite of so much code it would seriously jeopardise stability. This in turn means that a maximum of 127 Lua files can be assigned -- the first 127 in the list in the INI file. You can have other Lua files, preferably in other folders, which can be called by any of those, or directly in [Auto] sections. I think I will add something to FSUIPC to make it log a warning when more that the accepted number of Lua files are present, and exclude the extras from the INI list. Pete

All of those devices are simple standard joysticks and do not need the serial port PFC driver. Just use normal FS assignments, and you will be fine. Only use FSUIPC if you really want to, and then if so just follow the SIMPLE steps in the relevant chapters of the User Guide. They are all listed separately in the contents list! The ONLY reason it is 59 pages long is because it is a big toolkit with lots of facilities, but you simply pick the bit you want to use, or none at all. If I thought it would have frightened folks to have one document of 59 pages split into Chapters with a contents list I would have produced it as 10 or 20 separate documents, but quite honestly I can't see the real distinction! :-( Pete

The problem is more serious than that. If WideServer is not starting then pretty much nothing in FSUIPC is starting. It means that FSUIPC has not recognised that FS is ready to fly. The only times I have ever seen this is when there is a problem with the start-up flight. or the way the start is being configured, which somehow causes essential signals from SimConnect to be omitted. I would like to solve it for you even though you say it doesn't matter, but I need more information. This is why I asked for the correct and corresponding logs, which you never managed to supply. Once I see those I can suggest some additional logging options which will give me more precise information in the specific area where it is needed. Pete

11B8 is simply populated at the same time as 11BA except when the on-ground flag (0366) is set. Because notifications from Simconnect are aynchronous, the on-ground and G-force values may not correspond exactly in time, so initially the 11B8 copy may refer to a bounce (hence -ve value). However, there is code in FSUIPC to keep updating 11B8 even after the "on-ground" flag is set, but only whilst it is increasing. This should get over the problem of bounce, but it does mean you may need to have a short delay after seeing on-ground before trusting 11B8. If you are reading both offsets together, don't. Only read 11B8 when you have separately read 0366. Pete

Without seeing the complete Install log I can't help you there. Why not paste it here so I can tell you? Is it running at all? i.e. is it listed in the Add-Ons menu? And if so, does it show the options correctly when selected? Does it generate a LOG file? Show me that if so. With precious little information so far provided I cannot help more. Pete

Judging by the feedback, the user interface is already too complicated for many otherwise intelligent users, so making it more complicated for something very seldom needed is not at all warranted. This is the problem of a general toolkit. A specific tool to do a specific job is easy, but a generalised one which can be used by anyone to do almost anything gets complicated. This is exactly why I stopped adding facilities via either the user interface or INI file editing and provided the Lua plug-in script way of allowing anyone to add anything they can imagine, with only the need to learn a little programming first. Pete

I don't know VB6, but it seems to me that you have a fundamental error here: dwOffset = CLng(&H3210) + (4 * n) For n = 1 To 55 gvRetVal = FSUIPC_Read(dwOffset, 1, VarPtr(Text1.Text), 1) That "dwOffset = ..." line should surely be within the for loop, NOT before it. Otherwise no use is made of the value n in computing offset! Also, the loop should start with value 0 not 1 otherwise you are already missing testing the first slot. Didn't you try using FSUIPC_Write? BTW, where is the FSUIPC process call needed to send the requests over to FSUIPC? For VB6 users I would think Paul Henty's DLL would make things easier -- please see the SubForum above for this. I can help directly with C/C++ but not easily with VB I'm afraid. Pete

Yes, but you would need to edit the FSUIPC INI (FSUIPC4 INI) file. You can assign any number of things to the same keypress in the INI file, you just can't do it directly in the options screen itself. Just find the entry in the [buttons ...] section for your assigned button, and add another with the keystroke assignment. The format for these lines is described in the Advanced User's Guide. If you have difficulty, just paste a copy of your [buttons ...] section(s) here, and I ll show you what to do. Pete

See my reply above yours, crossed in the aether!

kay, your FSUIPC4.INI: 1. You are still using 4.928. The currently supported version is now 4.929. However, there is no difference in this area. 2. You have a section called [JoystickCalibration] and another called [JoystickCalibratio]. The latter will be completely ignored, so I suggest you delete it. I've no idea how you managed to get such a file corruption. 3. Your (proper) [JoystickCalibration] section contains these three lines, which toally destroy any use of the main three controls: Aileron=0,0,0,0 Elevator=0,0,0,0 Rudder=0,0,0,0 That nonsense can only arise from calibration everything at zero. The numbers should give the min, centre min, centre max and max respectively. There are another 19 axis calibrations listed (where do you get them from?), most of which are also completely nonsensical. Take just these two as examples: Throttle1=16383,16383,16383,16383 Throttle2=-16384,-16384,-16384,-16384 This shows Throttle1 calibrated with all values stuck at full reverse, whilst Throttle 2 has all values at full forward thrust! How on Earth have you achieved this? It is a complete nonsense! Most of the others are just as bad. Similar things are going on in your [JoystickCalibration.Cessna 182q] section. Again you have: Throttle=0,0 PropPitch=0,0 Mixture=0,0 and the other values appear either wild or not even calibrated. Your [JoystickCalibration.maule orion] section has these as well as other nonsense: Aileron=0,0,0,0 Elevator=0,0,0,0 Rudder=0,0,0,0 as does your [JoystickCalibration.C172 SP] section. To be brutally honest, I've not seen such an awful mess, ever, in the 16 year history of FSUIPC! Please start again. Delete the INI file completely. And before doing ANY calibration, please read the calibration section of the manual. Then, when calibrating, follow the detailed numbered steps one by one. Don't "do your own thing". Follow the steps. Good luck. i'll see how you got on when I return in a couple of weeks or so! Regards Pete

I find this message extremely confusing. First, the rudder. If the rudder pedals are not working with default aircraft then they are plain broken. It wouldn't matter how you assigned them. I can't believe you managed to calibrate them if they are broken, so perhaps you need to tell me more about that. What EXACTLY do you see, and where, and what EXACTLY are you doing? Second, what "INI" file are you checking for a 172? What on Earth has any INI file to do with anything? And what do you mean by "seems the aircraft in the FS selection is off"? If you are messing with FSUIPC's Profiles, DON'T for now. To start with you should simply assign and calibrate all of your normal controls for default aircraft. Do NOT create any profiles until you've done that. The Profiles are for DIFFERENCES from the "norm". Only create a specific profile when you need something different. But, meanwhile, check that your rudders work properly if assigned in FS. Note that you do NOT need to assign in FSUIPC in order to Calibrate in FSUIPC. FSUIPC's calibration works on FS controls no matter where they come from. I am getting a strong feeling that you are trying to use FSUIPC for things you do not yet actually understand, and would be better off doing things the simple way until you need to do something more complicated. I'm afraid I'm off on holiday at 4 am and will soon be signing off here until I get back, on March 2nd or 3rd. [EDIT] I've just noticed you posted your INI so I'll respond to that in a new message .... Regards Pete

Well, the FSUIPC log shows you are a bit out of date -- version 4.929 is the currently supported version However, I also see that the FSUIPC4 log file is starting two days ago (12th Feb) at 14:12:04. so it doesn't correspond to the WideServer LOG you supply which starts at 11:33:38 on the same day. Additionally the WideServer log shows a perfectly good WideFS session lasting 37 minutes, with no problems whatsoever. You have also, yet again, supplied a copy of the default (as installed) WideClient.INI file, which I don't need (because it is the one I supply), and you have still not supplied the WideClient LOG file for the same session So, all you've achieved so far is to show me that WideFS is working fine. If you REALLY have a problem, and that is fast becoming doubtful, I need the FSUIPC4 LOG, the WideServer LOG and the WideClient LOG for the SAME session in which you had problems. It is absolutely no good supplying a file from one session and another from another session. How can I possibly relate those? Also logs, even ones which correspond with each other, are not relevant if everything worked fine -- because that's all they'll show, that everything is fine. And please STOP supplying the WideClient INI file -- it is the LOG file you need to show me! I've no interest in seeing a file which is actually included in the WideFS ZIP which you downloaded. I am going on holiday at 4 am in the morning, and so probably won't now be able to respond till I get back on March 2nd or 3rd. Sorry. Maybe if you do ever manage to post relevant files someone else may jump in to assist. There are many thousands of happy successful WideFS users. Regards Pete

ALWAYS always test your assignments and calibrations on default aircraft first. FSUIPC deals with FS, not with Add-Ons. If it works with default aircraft then you know it's okay, then with add-ons you may have to make special arrangements because a lot of them do their own thing entirely. I don't know what you mean by "only aircraft I have done". Surely you assign and calibrate all the basic controls generically? You only need to do specific things for different aircraft if they need specific things doing. Some add-on aircraft won't like that as they look specifically for the FS controls. Also check whether the rudder moves when you move the ailerons. If so you have the AutoRudder option enabled in FS. What driver? Saitek? You said the rudder input worked because you'd calibrated it in FSUIPC, so what did you think was wrong with the driver? Pete

I don't know, how can I tell from here? Does the rudder work okay in other aircraft? That's the first thing to check -- I did ask this before, didn't you notice? It was my first question. There are several methods for assigning things in FSUIPC and not all suit all add-on aircraft. That's why I asked my second question, which you also appear to have missed. I can't help without information. I am off on holiday soon, then not back till March 2nd or 3rd, so you may have to wait a while or hope someone else can help. Pete Pete

On the same PC you would have no problems. You would also have no problems if you'd used Joystick Letters to identify your controls. What is happening is that your controls are plugged into different USB sockets and therefore have different joystick numbers! Hence the mixup. If you still have your old PC with FSX then enable joystick lettering, make sure your devices are plugged into the exact same sockets as before, then run FSX and after it is ready to fly, close it, THEN transfer the INI file and you'll be fine when the devices are connected as then FSUIPC is able to identify them by name and unique GUID number. For details of Joystick lettering please see the Chapter in the FSUIPC User Guide entitled "Keeping track of multiple control devices ("Joy Letters")". Pete

Does the rudder work okay on other aircraft? Are you assigning in FS or in FSUIPC? If in FSUIPC, which method -- direct to FSUIPC calibration, or to FS control -- and if that, which FS control? There are several choices, you see. Maybe that aircraft needs a specific one. Pete

Not sure why you are posting this here, but whilst an unregistered FSUIPC can't do anything about it, you can still use its Logging tab to see what is going on if you think it might be control interference. But a normal and expected cause of throttle racing is wind or cloud turbulence. If the airspeed is varying a lot because of rapid wind changes, the A/T will be trying to compensate. Pete

LOL! Well spotted. F next to G on keyboard. Fixed now. Pete

I get the Beta versions of course -- the only reason I'm able to get an update out so soon after the LM release is that most of the differences were known from the Beta. But the difference between build 9790 (the Beta) and 9936 (the release) are still enough to need a check through and a recompile to suit. Pete

I think that's to do with the way the Saitek driver or registry entries are set up. Check it in Windows game controllers. You should find specific answers in the Saitek support forum. Pete

Ah, sorry. In my haste I left all the debugging and testing ocde included. I'm uploading a replacement build now. You may need to refresh/clear the cache because it'll have the same name (if you download from the Schiratti page). Here I'll add "_updated" at the end. Regards Pete

Anything before FSUIPC version 4.929 (which I'm just about ready to release) is VERY likely to crash P3Dv2. The hook positions have all moved and some defeat my safety cross-checks. At the very best there will be things that won't work even if it doesn't crash! Pete

After the uninstall had finished, the "Programs & Features" applet showed it was gone, but still the installer complained. However, after I re-booted, the entry in the applet reappeared. I did another uninstall from there, and this time the installer worked. Weird. Anyway, it does mean I should be able to check and implement whatever changes are needed today for release later today -- look out for it in the Download Links subforum. Pete

You can reload a selected Flight via an offset, but not, separately, an Aircraft. It isn't a facility supported by SimConnect. Pete