Pete Dowson

That was fixed in 4.927a, which is the currently supported release. Pete

Okay. Please place this version of FSUIPC4 into your FSX Modules folder. FSUIPC4927cTest.zip Then edit the FSUIPC4.INI file and set Debug=Please (if you don't already have that there) LogExtras=x8001 You can delete the TestOptions line if that's still there. Run FSX and try the FSUIPC mernu, how ever many times. If or when it doesn't work, say, twice, show me the Log file. no need to ZIP and email it, it won't be too long. Paste it here. These are the log lines you should get for every entry into the Menu and out again: 231396 ### MENU: EV_MENU [15] received: dwMenuEvent=0, fInScanJoy=0, fInOptions=0 231412 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 231412 ### MENU: ST_DLGMODE received, stt->dwInteger=1, dwMenuEvent=15 231412 ### MENU: ST_DLGMODE: fInScanJoy=0, fInOptions=0 << the menu is open here (not a log line!) >> 233642 ### MENU: PropertySheet call returned 1 233689 ### MENU: ST_DLGMODE: ending dialog mode 234048 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N Regards Pete

You don't actually need to install or reinstall FSUIPC at all to run ASN. ASN does not use FSUIPC. What's all this about "several times"? All the installer does is update documentation and the FSUIPC4.DLL itself. nothing else is ever changed by the Installer. Re-running it does nothing at all. The installer cannot overwrite a later version, so you must have deleted something for some strange reason and then run an older installer. Two things: 1. You NEVER EVER have to delete ANYTHING at all when updating or installing FSUIPC. There is no point. It is futile. 2. Apart from the presence of FSUIPC itself there is nothing in the Modules folder which will in any way affect whether FSUIPC appears in the add-ons menu. That is simply dictated by whether FSUIPC is running or not. If it is not running, there will be no menu. Check whether you even have a DLL in the modules folder! Pete

There is no change in WideFS with any release since a long time ago. What was your previous version? Which log or info would I need to provide for help getting this issue resolved? Oddly enough it would be the ones called WideServer.log on the Server and WideClient.log on the Client. Show me those please. Pete

Well that is completely mystifying then, because the only difference between 4.927a and 4.927b is one value in one instruction which affects large INI files causing a crash on FSX first loading. No ther change was made. And the person who started this thread did so long before 4.927b was released. And the change most certainly doesn't affect anything on your system. I 've just got that too, but I won't have time to install it for a day or two. Wait a minute. "When FSUIPC goes wrong"? In what way does it "go wrong"? I thought the problem was only that when selecting the FSUIPC entry in the Add-Ons menu the options dialogue does not appear, that the FSUIPC entry appears to do nothing? What else are you now saying? What else 'goes wrong'? What other "add on items are there which don't work. Or are you merely saying that the Add-Ons menu lists all the correct programs but none of them are selectable? If so that is certainly a SimConnect problem. There is no way FSUIPC can make SimConnect not respond to other programs. I'll see about adding more logging to see why FSUIPC's options doesn't appear, but this is now sounding like something outside my capabilities. I cannot fix Simconnect itself if it gets courrupted like that. Pete

And what version were you running before, and did that not show the same issue? There has been no change in how the menu is invoked in any version of FSUIPC since the original 4.00. I need to know whether you are seeing a change, or not. Unfortunately the log file doesn't show me what is going on as I'd hoped. I've been trying all week to get something useful from the original poster, to no avail. now i see I will have to add more logging to see why SimConnect is going wrong here. Sorry, i don't understand. Are you implying that with FSUIPC installed something goes wrong? what? Why remove FSUIPC to see if the FSUIPC menu will then work? How could it? I'm not sure that I will have time to do anything further now before Christmas, and then I am away till january 10th, so there may be a long delay. I'll see what I can fit in between family commitments. Pete

The problem is that Delta value. The Delta specifies the smallest change in the input value which will be used. It defaults to 256, giving 128 distinct values in the full range -16384 to +16383. with a value like 7520 you are limiting the possible values to the 4 you get! Please do read the sections of the FSUIPC User Guide which describe the facilities you are using, and especially before messing with something which you evidently didn't understand. Just set the delta back to its default. Pete

Actually I don't agree. I would always prefer the one file. Just consider the complications if you reinstalled Windows or changed your controls. Using joy letters to overcome the change of joystick ID is easy to manage programmatically for one file, but trying to sort it out on who knows how many files could be a nightmare. However, I like your last idea a lot better than the others, so I will consider it. But even if I did it, it would not be enforced because I think most users of Profiles really don't need so many variations. I want to keep it simple for simple use, and I don't think multiple files does that. Also, even if the option were taken i don't think I'd want to implement any automatic conversion. The difference between those Profiles placed separately and those kept in the INI would need to be denoted by something in the Profile section name in the INI, i.e. a reference to the file, maybe even a pathname so you could, if you wished, store them with the aircraft. But for the present my mind is boggling. I'm going to leave all this till late Jan at the earliest. I had my easy solution in mind and was prepared even to do this before Christmas, but I can see this will not please everyone. Really, I admit that I don't understand why there is a need for so many different settings. When I implemented Profiles I had in mind siimple classifications like "Prop", "Turboprop", "Jet", "Helicopter", "Fighter", "Stunt". I'm not getting the picture where almost every model of every type needs some subtle differences. I can see that the odd aircraft might be so different it needs really different settings, but most, surely not? Oh, BTW, that "60 years" was a typo -- 50 years not 60. Sorry. I an only 71 next year. We didn't really get married when I was 11 years old! ;-) Regards Pete

Glad you sorted it, but it is very strange then that it only affects P3Dv2, not FSX or P3Dv1. It would never have occurred to me to check this option because the emphasis was the difference for P3Dv2 only. Pete

Does the aileron axis exhibit this behaviour in Windows' own Game Controllers calibration window too? If so then it must either be a setting or problem in the joystick driver, or an actual fault in the device itself. What are the specific numeric values you read in the Assignment tab? In that tab check both the input and output values seen. Oh, and the 'Delta' value, in case that has been changed. Pete

It means exactly what it says -- when assigning your button in FSUIPC, select the entry from the drop-down llst called "Keysend ...". Have you never used FSUIPC for assigning actions to button and switches before? Best to read at least that part of the FSUIPC User Guide! Pete

And I say there is absolutely no difference in FSUIPC for joystick recognition with P3D v2 compared to any other version of FS. There is absolutely nothing I can investigate or do about this. Something in your system is presumably blocking the joystick access somehow, I don't know how. Sorry. I have had no other similar reports whatsoever, and there is nothing in my code I can change to help. All of that part of FSUIPC knows nothing about the FS version and doesn't care about it at all as it is completely irrelevant. It is purely an interface into the Windows DirectInput API. You certainly need to look elsewhere. Pete

Yes, FS does automatically reassign axes IUNLESS you disable the controllers in its controls options. This sets "joysticks=0" in its CFG file, and then it normally does not do its automatic reassignment. Simply unassigning axes in its assignments options does not work -- each time you run FS without telling it thus, it assumes the controls are newly attached and does its automatic reassignments. I'm pretty sure this is expalined in the FSUIPC user guide someplace. It has always been the case, for all FS versions as far as I can remember. I assume you do realise that you do NOT have to actually assign axes in FSUIPC just to calibrate in FSUIPC? The calibration works for the control surfaces and so on no matter how you assign them. If you cannot fathom out how to stop dual assignments, just don't assign in FSUIPC. It is quite easy to determine the names of FS controls asigned by default -- just enable event logging in FSUIPC logging, use the control, then look in the Log file to see what it did. I think in FSX F11 does something like "VIEW_CAMERA_SELECT_3". (If not it is certain to be one or other of the camera selections). Of course you can always use F11 assigned to a button instead of the controll itself. FSUIPC does actually allow both keypress and control assignments to buttons and switches. BTW I do not support old versions of FSUIPC. Please update before posting again. Pete

See XCOREZ's answer, but also bear in mind that the file to edit is WideClient.INI on the Client! Nothing on the Server!!! Pete

Calibration. You have insufficient dead zone on brake release. Either that or you still have the brake axes reversed. Pete

There is absolutely no reason whatoever what any axis can be "more jerky" in FSUIPC that in any other way. It sounds exactly like dual asignment. If you assign axes in FSUIPC you MUST disable all controller assignments in FS. Pete

General options are not really relevant. Why on Earth are you not connecting your control till AFTER you run P3D2? FSUIPC is doing absolutely nothing different with joysticks in any version of FS from FS98 to P3Dv2. It ids nothing to do with the version of FS. From what you've posted I've no idea whether you are assigning axes and buttons in FSUIPC or in P3D. There is no way I can help. I really don't know what you are doing, nor why you could possibly say "something in FSUIPC isn't working well". What are you expecting FSUIPC to do? If you are assigning in FSUIPC and it sees the joysticks, it will work. If it can't see them, it won't! It is that simple! Regards Pete

4.926b? Are you sure? Can you tell me where it shoes 4.926b rather than 4.927b? I've never released a 4.926b! Pete

That's version 4.921 then. You've not installed either 4.927a or 4.927b! :-( Then that's the file you need in the FS modules folder. Maybe you have UAC enabled and aren't copying the file to the real (protected) FS Modules folder? Pete

The INI file is called FSUIPC4.INI and is in your FS Modules folder, next to FSUIPC! It would be better to find the cause of the FSX overload which is giving the problem in the first place. Allowing more time for things to stall is only as an experiment or stop-gap. Pete

Hmm. I managed to reproduce your exact problem here, but only with your INI -- and it's the same all the way back to very old versions of FSUIPC, FSUIPC3 on FS9 included! It's a very old, original bug, dating back I don't know how many years, but it seems to be completely innocuous EXECPT, for some reason I can't fathom, on your specific INI file. I can't see anything odd about it at all, but I don't have the time to track through FSUIPC's processing of every section and line in it. I just wish I'd got this before yesterday's reease of 4.927a, as that was supposed to be the last full release till I return from holidays Jan 10th. 2014. I'll post the fixed version, 4.927b, DLL only, in the Download Links subforum n a short while. Please download it from there. Regards Pete

I'd need to see that Log. Paste it here please. In your ZIP you supply everything but the Log! When you run the Installer it only replaces the FSUIPC4.DLL in the Modules folder, and updates the documents in FSUIPC Documents folder. None of the other files are touched. So the INI file used by 4.927a is exactly the same one as that you copied in your backup Modules folder. So all the above sequence means is that you don't have a problem with 4.921 but do with 4,927a. However, you also said: So 4.921 also gave the same problem, according to this? The differences between 4.921 and 4.927a are relatively trivial and almost all only concerned with P3Dv2. Pete

It's "Dowson" actually, but folks call me 'Pete'. I don't think Ivap uses FSUIPC at all, though I don't know for certain. WideFS extends the FSUIPC interface to other PCs, that's all. It cannot help other applications which don't use FSUIPC for their operations. Pete

I'm afraid I've not got time this side of mid-January to read and understand this long missive. All i can do is print it out and try to read it some time soon. But first, let me just ask this one question: You emphasise MANUAL setting. Do I take it that if someone takes this toute I can thenceforth prohibit him from using any of the in-program option facilities for Axes, Buttons, Keys and Calibrations. He would then only ever ecit these 'cFG' files directly? If not then it is too complex and worrying support-wise. Folks won't know what's going where or when -- me included! And do I take it you do not like my proposal using "Library" sections, for the common stuff? I already have in mind exactly how I would do that. And it might only be a day or so's work. In fact it would take longer to test properly. I might shelve all this till next Summer, when I'm stuck at home because the dear wife has lots of gardening to do. Much of next year we are otherwise travelling. Part of our "retirement" plan -- see and do as much as we can whilst we are able. And next year we will have been married 60 years, so there's extra involved. Regards Pete

No, the parts are almost all made by manufacturers. Most of it (all really except the overhead) is by PFC (www.flypfc.com), who made about 15 of these 737NG cockpits. I did the FS software for PFC. The overhead is part Cockpitsonic, part Sismo. The whole thing these days would probably cost you around £100,000+ if you could get one, which you can't. I've had the main cockpit for years now. Pete