Pete Dowson

No, not without any information. WideClient and WideServer haven't been changed in anything but ancillary user facilities for years, so it isn't the update. What's this "Benchmark Test" you are running? What has that got to do with it? Please refer to the Log files, both Client and Server, to work out what your problem s. I'm afraid I'm now off for a long weekend (steam train tour in Ireland). I'll be back on Wednesday next week, and will look at any logs then if you've not sorted it out. Regards Pete

Why aren't you using an axis (potentiometer) for trim adjustments, and calibrating them as such? It would be much nice that using two buttons. 0.3 of what? A radian? What is the limit in that measure? Where are you reading it? Are you saying on the next push it does nothing at all. Where's the logging? PLEASE ENABLE BUTTON LOGGING too (one check mark on the left) so i can see exactly what you are pressing! That makes no sense whatsoever. At 500 per repeat and the default Buttonrepeat=20,10 setting you have, there will first be 1/2 second delay (in which time you should have released the button), and then 20 repeatets per second, so needing 3 seconds to get from 0 to 16k. Or maybe your "InterfaceIT" program is so slow it is not able to send the "release" for 3 seconds? That woud explain it. I'd need to see the log to believe that though! I'm afraid I'm now off for a long weekend (steam train tour in Ireland). I'll be back on Wednesday next week. I'm sure you'll work out what is going wrong using the logging. If you ask me, that software you are using seems to make things very complicated. A set of buttons connected via a Bodnar board, with some axis / pots too, would be soooo much easier! That's what i use. Regards Pete

On the latter point, I think your assignments are all saved in any case. You don't actually need to de-assign anything, just disable controllers. One switch, on or off! On the first part, I'd recommend starting by editing the FSUIPC INI file. Make sure these settings are like this: In the [General] section: ShortAircraftNameOk=Substring UseProfiles=Yes In the [JoyNames] section: AutoAssignLetters=Yes The latter will make FSUIPC use letters (A, B, C, etc) for your attached controls instead of their Windows ID numbers, and this will be safer if you ever unplug them or move them. Then, you say you have 4 aircraft. If they all need different assignments and calibrations, you would create 4 Profiles -- eventually. but first you should select a good default, typical of your 4, and make a good set of default assignments and calibrations. That's without a Profile. then when you load one of your "special 4" you can create a profile with a suitable name and let it inherit the basic default assignments and calibrations. Only then start tailoring them specifically. Same with each of the other three. Load, assign/create Profie, assign and calibrate differences. Lastly, close FS and edit the INI file again. Assuming you use assorted variations (different liveries perhaps) of those 4 aircraft, you can go to the [Profile.<name>] sections and abbreviate the aircraft name listed thereunder (i.e. as "1=name") to something which will select all the variations of that aircraft but without including anything you don't want under that profile. The abbreviation can be a bit in the middle of all the names if you like. That's about it really. Start like that, try it as you go. Save the FSUIPC INI file as a safeguard. If you want to revert just remove it and re-enable FSX controllers. Regards Pete

So what was all that about using the offset and programming inc and dec? Why can't this FDS program handle the correct offsets in the corerect way in any case? As far as i know they are a competent company and should know what they are doing. Don't they have any support? Yes, I understood that. But nothing of what you supplied in the last message really had any relation to your original questions. It is totally baffling when you do that to someone who is trying to help. How can you say so much that is plainly not true? :-( Aren't you trying to do something in the most complicated way possible? What are you using the FDS software for if it isn't suitable and has to be perverted so much? Pete

Okay, so you aren't doing all this by assignments as I assumed from what you said: "I used the example from page 31 of the User Guide (the box with Offset Increment/Decrement Controls examples for elevator, rudder, and ailerons)." but instead a program running on a PC called "AVIONICS". But anything you do there is surely being overridden by the program running on "AVIONICS"? And in any case thee is certainly no assignment there to any offset control handling either of the offsets you were asking about. What is going on? Nothing here is in anyway reelated to anything you were saying you were doing or what you were asking about!!! Pete

Let's stop there a moment. When you run the installer, a window appears in which a scrolling log of all the Installer activities appears. It only stops when either there's a problem which it states in a message box, or it successfully INSTALLS the FSUIPC module and all its ancillaries and documentation. When you press OK it then goes on to ask if you want to register, check registrations, or simply cancel out. The installer has been like this, doing these exact same things, for years, so you must have seen it before. Now which part of that did you NOT see? There is absolutely nothing in the FSUIPC installer which ever DELETES anything whatsoever. I think you must be looking in the wrong place! It sounds exactly like you have two (or more?) installations of FS9 and you are looking in the wrong place altogether! Please take a more careful look. If you want assistance i will need to see the Install log, which if you cannot find the correct FS9 modules folder, can be saved when it confirms installation by using the "file" menu on the log window. Regards Pete

The elevator control, or the elevator trim, which you said in your previous message was working? If the latter, what have you changed? I still don't have enough information. Perhaps you should show me the actual assignments in your INI file, else we'll go in circles for a while! You also haven't shown me any of the logging reults. Are you shy? ;-) Regards Pete

0C04 maps onto the SimConnect variable "RUDDER TRIM PCT". That's all I know about it really. Are you writing a program to do this? Or what? I really need to understand what you are doing if I'm to help. Try using the FSUIPC logging facilities. If you go into the Logging tab, and on the right-hand side add "0C04" as an offset to be monitored, of type "S16" (signed 16-bit), then check "Normal log" below and enable the console log on the left, then on OKing out, change FSX to Windowed mode so you can see the log in real time. Then run your program or whatever it is and see what happens. If you think it is wrong, show me the log itself. Regards Pete

Yes, sorry. I thought you wanted the individual slider settings not the global airliner one. There's just no equivalent in FS9 of those offsets. If you were able to access the offsets you wanted in FSUIPC4, then you can access offset 3110 too in either FS9 or FSX, and send any control you wish -- including those. The numbers you need are listed in the Advancxed User's guide. Pete

I'm afraid this is nothing whatsoever to do with FSUIPC. REX does not use FSUIPC for weather, and FSUIPC is not doing anything with weather unless it is asked to. Clicking "clear all weather" in FSUIPC is thesame as selecting the clear weather theme in FSX's own weather menu. Regards Pete

As the Installation guide tells you, you don't need to re-register if you are already registered. Just press Cancel. Or you can check that your existing registration is correct. Please just follow the course which suits you. It isn't complicated. Regards Pete

Why uninstall? How exactly did you "uninstall"? Sounds like you deleted something you shouldn't! There's no error remotely like that than can be induced by any add-on or lack of one, it is more to do with missing critical parts of FSX itself. It is never necessary to "uninstall" any part of FSUIPC. If you want to test something without it, just move the FSUIPC4.DLL or rename it FSUIPC4.DLX or something. Additionally, the Modules folder in FSX is not a part of the base FSX installation, but created by FSUIPC's Installer and other add-ons which like to place things there. It sounds like in your haste to uninstall things you started to work on the DLLs in the main FSX folder, all of which are essential parts of FSX. I'd recommend you take heed of what FSX is telling you, and run its repair. You'll probably then need to rerun the SP1 and SP2, or Acceleration, updates. Regards Pete

You can also do it via the added FS controls for this -- see the list of added controls inthe Advanced User's guide. Sorry, no. That would need hacking into the FS9 code and I'm not doing more of that at this stage. Regards Pete

You posted what is obviously a Support question and not in any way a "contribution" into the User Contributions subforum, where it won't get answered. I've moved it here for you. Please always use the Support Forum for Support. Well, these two lines: 1=P0,0,C65641,0 2=P0,1,C65640,0 are unconditional -- you forgot to put any condition on them, so they will always activate. Don't you see? If you want them not to activate when button 0,8 is pressed you have to have the condition that it is not pressed, thus: 1=CP(-0,8)0,0,C65641,0 2=CP(-0,8)0,1,C65640,0 Didn't you see the inverse condition at all in your studies? Regards Pete

As it clearly says in the Installation instructions (didn't you read them?), if you are already registered or don't want to register you can just cancel the Registration page. The installation process has already been completed by then as it would, in fact, have told you! If you want to Re-register because you have gone and deleted your previous installation (why would you do that?), or moved to another PC, then it WILL be accepted if you do as it says and enter ALL THREE SECTIONS correctly. If it is being rejected you are most certainly making a mistake. Use cut and paste if you are unsure. You cannot spell your name or your address differently. Pete

Okay. 4.88 is the same as 4.90 except the latter has no Code Signature checking, ready for the time, soon I expect, that this signature revocation reaches PCs. Pete

Well, that's good, but you still have only one exact centre for the three main controls, at 0, with no leeway in case it doesn't centre always there. Maybe the controls are that perfect, but it's unusual. And the brakes have no "off zone", so if they don't read precisely -16384 when released they will be on slighly. Normally, without any leeway on the toe brakes it is difficult not to apply some brake when applying rudder. Most folks prefer that the toe brakes don't apply for at least the first inch or so of travel. Regards Pete

They don't look like properly calibrated values at all, but almost no difference from defaults There should always be a small dead zone at each end to make sure min and max settings can be reached and the dead centre is very rarely exactly 0. In the case of the aileron and elevator you haven't even got a central zone, so the hands-off central position could easily be biassed. You should follow the numbered steps for calibration clearly laid out in the User Guide if you want to make proper use of FSUIPC's calibration capabilities. They are very bad, poor. Just do the calibration again, properly, and following the steps. That's why the documentation is there. ;-) Pete

Sorry, where do you see a reference to 4.86? Pete

Using FSUIPC's "aircraft specific" or using Profiles? If the former case it would only do that if you actually assigned to the aircraft by its name -- they must have dfferent names. If you used Profiles, then the names are added to the profile when you ask for them to be. It is NOT automatic. It sounds like you must have actually edited the INI file and shorted the name to F/A-18 so including both aircraft! The same as what? Sorry, you need to be more specific. You do not SELECT aircraft in FSUIPC. It offers no such facilities. You select aircraft using FSX's menus! What for? You never EVER need to use that facility unless you want different FSX.CFG files. FSUIPC has easy to use Profiles to separate all your assignments and calibrations. This is probably the biggest and most well-used facility of FSUIPC! FSX creates a new FSX CFG if there's not one there already. You obviously masde an error, but you really shouldn't be messing about like that in the first place unless you wanted different FSX configurations completely -- e.g. a DX9 and a DX10 load. It seems you've gone off half-cocked doing all sorts of odd things. I'm not surprised you got problems! Your FSX.EXE is not named caorrectly. You have a space after FSX!!! I'm not surprised nothing has worked properly. Why are you renaming it from the correct name? This shows that there most certainly NOT an FSUIPC4.KEY file in your FSX Modules folder. The Name and Addr fields will ALWAYS be shownhere if there was one. Is this where you looked? D:\Programme\Microsoft Games\Microsoft Flight Simulator X\Modules Why are you re-registering in any case? did you delete your previous FSUIPC4.KEY file? If so, why? Did you make a backup? Because of the renamed FSX, other files will be wrongly named too. In your Install log I also notice: Why are you using the Loader? What was the problem which suggested you should install that? I think you have been making very simple things very very complicated, and then made things worse. I would suggest you start again with a clean everything. Regards Pete

Even the Registry repair option? It sounds like your FSX.EXE was corrupted! After you did the repair, did you also update FSX with the SP! and SP2 updates, or Acceleration? Also, check your system date -- if it is incorrect it may make the registration look incorrect. If it isn't either of these problems, I need more information! Please paste both the Install log and the FSUIPC4 log into a message here. Close FSX down first. Pete

You posted twice. I replied to the first one. Pete

Well you've proved it isn't a change in FSUIPC, so I can only assume either something's changed in your settings or something else is interfering with the axis control (Steering Set). Have you checked? You should always test on a default aircraft in any case. But maybe there's something left of the Dash8 installation which is intercepting and stopping Steering Set? Does it have a DLL or EXE running? Pete

Windows 7 is fine, I use it on all my systems. That doesn't sound like anything that's in my Installer. And you need 3.999z2, not 3.99. Sounds like you have a bad download. Try downloading it from the Download Links subforum here. It would have produced quite a lot of logging before it could get that far, in a Window on screen, and would come up with an Explorer window or you to locate FS9.EXE, so I don't think that diagnosis is likely to be correct either. But if you think your Registry might not be pointing correctly to your true FS9 installation, try this repair program: http://www.flight1so...stry_Repair.exe Pete

Good. Thanks for letting me know. Pete