Pete Dowson

I'm not familiar with "BBI". Is it a standard USB HID device with buttons etc seen in Windows drivers? If so i don't know why it wouldn't be recognised by Vista. By "servers" here I asume you mean "clients"? WideClient will automatically send any recognised joystick buttons to FSUIPC for assignment there. It doesn't handle axes, that's all. Your encoders will just look like pairs of buttons so they're okay. EPIC? That's going back a bit! I haven't supported EPIC for many years. Simply connect your buttons, select the Switches and Buttons tab in FSUIPC, operate the buttons or switches and program them as desired. With a working WideFS link it is no different to connecting them directly. What special instructions were you after? Pete

You mean updating the INI file? Why, if there are no changes? There's no "reset/restart/reload of FSUIPC". It doesn't do anything specific on entering or exiting the menu -- excepting just a rescan of joysticks on entry. The only thing which might be doing something for you is effectively completely pausing FS. Most FS menus do that too. But that has these bits in it: ME: "Could you please download FSUIPC 4.859f test and test this with your method? I've added the wind setting to other palaces. Maybe this will overcome your detected omissions? Let me know, please." OP: "Just finished my standard testflight EDDL-EGLL and wanted to give a brief result: No more wind deadlocks!" So what's changed since December? Apart from actually stopping the sim and starting it again, how do you think this "event" can be done. To trigger an "entering menu and exiting" you'd need to actually enter the menu and exit.! surely no one would ever want that happening automatically? Pete

That links to a site which is offering version 4.09 (!!!), which was a VERY early version, soon after FSUIPC4 was made and released and which certainly wouldn't work with an updated FSX and probably wouldn't install by iteslef in any case. The "readme" appears to be a quote from a FAQ entry which used to be here, long ago. I don't know who put that ZIP together, and i don't know why that site is still hosting such an out of date and invalid version. Seems really daft. Most such sites simply link to the proper one. It is always best to go to official sites. It seems I cannot stop folks putting things elsewhere, but then I can't support stuff downloaded from those places. Glad you got it sorted now in any case. And thanks for the info. Pete

You can have multiple assignments to button presses or key presses, but to do this you either need to use a macro file, constructed in an editor, and assign to that, or, easier for just two assignments as in this case, simply add the 2nd assignment line in the [Keys] section of the FSUIPC4 INI file. The format is described in the Advanced Users guide. Just add the additional engine "ThrottleN_decr" commands with the same keycode to another uniquely numbered line in [Keys]. The complete list of FS controls is installed in your FSUIPC documents folder, and gives the numbers you'd need to use. Regards Pete

Sorry, I can't confirm one way or the other, though it seems unlikely. I think originally SimMarket instigated the discount for folks upgrading from FS2004 to FSX within the first 6 months. I know they did extend this, but I don't know if it still applies. it may do, just by default. You'd probably find out by selecting it and going to the checkout. Pete

There's no separate "freeware" and "registered" download. They are one and the same. The only difference is whether you actually register or not. And there's only two proper sources for downloading FSUIPC: the www.schiratti.com/dowson page, which is the official place as linked to in the SimMarket purchase pages. The other is here in he Download Links subforum, where you can get the same thing AND, often, later interim updates. Except for some products in which a copy of FSUIPC is bundled, there are actually no other places where you can legitimately obtain FSUIPC. I'd be very interested to find out where you got that one with your "README" file, if you can remember, please. Yes. FSUIPC installation never deletes anything, it only replaces the DLL (if it the install version is the same or a later version) and updates documentation. Okay, that's good. If you do get stuck I am here much of the time. Pete

You posted what appears to be a support request into the "Download Links" subforum, which is for download links. I've moved it here so it will get an answer. "Didn't work" in what way? What was your purpose in buying it? For many uses it doesn't need purchasing and registering, and you could have read everything about what it does beforehand just by installing it and browsing the extensive deocumentation. But one thing it certainly doesn't do is "build key shortcuts" for you -- I don't even really know what that means. Are you talking about assigning keypresses? Er, sorry, but you need to explain what you mean by all that. What is this "readme" you are talking about? As clearly stated in the Installation guide included in the ZIP (no "readme" there), the documentation is placed with lots of other "goodies" in the FSUIPC Documents foder in your FS Modules folder. The User Guide is the place to start (and which might have been a good thing to read BEFORE purchase?) Again, what "README file" are you talking about? The ZIP contains the Installer and an Installation and Registration guide (a PDF). That document points you to where the main User Guide and Advanced User guides are. There's no README file! FSUIPC doesn't need to be "got working". It is a tool. By itself it does nothing. It is either used by other add-ons, in which case you don't need to know about it, or it is used by you in whatever way you want to use it out of its assorted capabilities. If you are reallly meaning you've had some installation problems or something else which stops you even progressing to the menu, then please actually say so and describe it. There will then be information I need from you to find out why. So far you've unfortunately provided no useful information at all, so I can't even start to help. Starting off here with your first message phrased is such an suspicious and accusatory tone isn't a good start . Let's calm down and be reasonable, stating what the problem is in a clear fashion. As a "newbie" you might not yet understand that being friendly is likely to get you a lot more enthusiastic help in your chosen hobby. Regards Pete

The only relvant parts to axis assignments are these: [JoyNames] AutoAssignLetters=No 1=PFC USB Yoke 1.GUID={39A30D90-716C-11E2-8002-444553540000} 2=PFC USB Pedals 2.GUID={39A30D90-716C-11E2-8001-444553540000} 4=BU0836X Interface 4.GUID={60CF4030-75E2-11E2-8008-444553540000} 5=PFC USB Yoke 5.GUID={39A30D90-716C-11E2-8003-444553540000} 6=BU0836X Interface 6.GUID={60CF4030-75E2-11E2-800A-444553540000} 7=Virtual Joystick 7.GUID={0626C430-8002-11E2-8001-444553540000} 0=BU0836X Interface 0.GUID={60CF4030-75E2-11E2-8009-444553540000} [Axes] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0R,256,D,3,0,0,0 3=1X,256,D,1,0,0,0 4=1Y,256,F,65694,0,0,0 5=2X,256,D,1,0,0,0 6=2Y,256,D,7,0,0,0 7=2R,256,D,3,0,0,0 8=3X,256,D,8,0,0,0 9=3Y,256,D,7,0,0,0 10=3R,256,D,3,0,0,0 11=5X,256,D,1,0,0,0 12=5Y,256,F,65694,0,0,0 You have 4 assignments to ailerons. I can understand 2 assignments for your two yokes, but 4? 0=0X,256,D,1,0,0,0 3=1X,256,D,1,0,0,0 5=2X,256,D,1,0,0,0 11=5X,256,D,1,0,0,0 As you can see, there's one on each PFC yoke, but also one on a Bodnar board and even one on your PFC pedals (device 2 axis X)! For elevators, you've got three assignments: 1=0Y,256,D,2,0,0,0 4=1Y,256,F,65694,0,0,0 12=5Y,256,F,65694,0,0,0 one "direct to FSUIPC" on a Bodnar board, and the other two using FS controls instead (why, when all the others are direct?) on the two yokes. You have three rudder assignments: 2=0R,256,D,3,0,0,0 7=2R,256,D,3,0,0,0 10=3R,256,D,3,0,0,0 One to the pedals, one to a Bodnar board, and the other to a non-existent device 3. And you have three toe brake assignments, one (left only) to the pedals, and both left and right on the non-existent device 3. 6=2Y,256,D,7,0,0,0 8=3X,256,D,8,0,0,0 9=3Y,256,D,7,0,0,0 Oddly, you have no throttles assigned at all. So how do you fly? I can only assume you assign throttles in FSX? Altogether, it adds up to a real mess. I think you must have been disconnecting and reconnecting your many devices into different USB ports on different occasions. This will make Windows assign different IDs to them, and consequently the FSUIPC assignments to one device now become applied to another. If i were you I'd do these steps: 1. Delete the entire [Axes] section in your INI 2. Set the AutoAssignLetters=No parameter in the [JoyNames] section to 'Yes', as advised in the User Guide for those with several devices and who might swap them around (please read that chapter too!). 3. Load up FSX and reassign everything from scratch. No need to recalibrate if you are happy, but looking at your calibrations i also see most values have been left at defaults, so I would still recommend recalibrating everything properly following the numbered steps in the User guide. Don't forget throttles somewhere, especially since you are going to disable controllers in FSX. Pete

To eliminate possible conflicts with FSX simply disable controllers. No need to check any "configs". But I was also meaning possible dual assignments in FSUIPC. That's why I suggested showing me your INI file. If you use FSUIPC for assignments, do so with the hat as well. Axis assignments, "pan view". Pete

What does 'last registered' mean? Please always quote version numbers. That sounds very much like either dual assignment, or even more likely a connection problem. When an axis device becomes disconnected the input spike looks exactly like a maximum deflection. You could try enabling the spike detection in FSUIPC -- see bottom of left-hand side of the Miscellaneous tab. The facility was originally introduced because of a software bug in one of the add-ons in FS9. It ignores exact maximum and minimum values. That can only be either conflicting / dual assignments, or hardware interference. I never understand why people thing replacing a DLL with the same DLL can make any difference. There's nothing else installation does except also replace the documentation in the FSUIPC Documents folder. Well if there are dual assignments in the INI, certainly deleting it will cure that because you then won't have any! But let me take a look first. Paste it into a message. And disable controllers completely in FSX. If you don't, FSX will tend to automatically reassign them, and you will certainly get conflicts then. You only want things assigned in one place or the other. Keys don't matter -- if you assign a key in FSUIPC it overrides the FSX assignment in any case. But merely not assigning axes and buttons in FSX isn't really any good. Either do ALL assignments in FSX and none in FSUIPC, or disable controllers in FSX. It's the only safe way. Pete

Sorry, what do you mean? When doing what? Using the tiller or rudder? Via FSUIPC or directly in FSX? Since the FSUIPC steering tiller is done by driving the FSX rudder, how would allowing the rudder to operate at the same time as the tiller help? You'd get both tiller and rudder doing the same thing! I thought you said you liked the effect FSUIPC is giving you. If you want to use the rudder then just don't bother with the tiller assignment, then FSUIPC won't be doing the blending or transfer.. So why on Earth do you want rudder operating whist taxiing? The only possible use would be to see the deflection on the lower DU page showing the surface positions. You certainly can't see the actual rudder from the cockpit. This is getting very confusing. Regards Pete

You posted this twice. see my reply to the first one! Pete

Installing FSUIPC, any version, NEVER EVER deletes any of your assignments! Just run the installer, never delete anything! All your work is saved in a file called FSUIPC.INI file. That is not touched at all by the Installer. The installer merely updates the actual program module (FSUIPC.DLL) and installs new documentation etc into the FSUIPC Documents folder. Please do read the supplied Installation document some time. It does tell you exactly what it installs. Pete

How are you trying to assign? If it does look like a real "hat" ("POV" in DirectInput terms -- 'point of view' or something similar), then for the Virtual Cockpit panning action, assign it in the Axis assignments (NOT the Button assignments) to "PAN VIEW". It will never be quite a smooth as the direct FS assignment because it has to go through SimConnect, which operates asynchronously, but it isn't at all bad. Pete

I've obliterated your key. NEVER post private keys openly like that! However, I can confirm it is not and never has been a valid FSUIPC or WideFS key. Also, when entering your details, your name and address or email must be EXACTLY as it was when purchased, even if it has changed since. I suspect you are making an error in the key entry in any case. There are several characters in it easy to get wrong, like S and 5, i and 1 0 and O and z and 2. Best to use cut and paste for all three fields from your original notification, or go to your SimMarket account and retrieve them again. Regards Pete

No, none at all. Neither of those use FSUIPC and there's no conflict. I use both of them. Also EZCA, OpusFSX, GSX, AES, etc etc. One important question, though. You said "I have my ailerons and toe brakes assigned via FSUIPC and not through the FSX controls". Does that imply that you have other axes assigned in FSX instead? So you are mixing the control inputs from devices between FSX and FSUIPC? If you are, then that is a very bad idea. Even if you unassign axes in FSX, it will often automatically reassign them next time it starts up if it things the device is newly-attached, which it can easily do if they've either been detached or "gone to sleep" because of USB power management. If axes (or buttons) are assigned in both places there will be conflicts which may have any odd effects, including preventing either moving. You should consider either assigning everything in FSX or everything in FSUIPC4. In the latter case disable the controllers in FSX to stop it reassigning them. Note that you do not need to assign in FSUIPC4 to make use of its calibration and other facilities. FSUIPC will calibrate FSX-assigned axes too. Pete

Installing FSUIPC does nothing except put the FSUIPC DLL into the Modules folder. Replacing a DLL with an identical DLL cannot possibly influence what then happens. If when you "reinstall" you are actually deleting things, then you are making a big mistake. ALL of your FSUIPC settings are in your FSUIPC INI file in the Modules folder. Unless you want to start with a completely unused FSUIPC with no assignments, nothing, never delete that. I think you'll need to look elsewhere for your problems. As I say, reinstalling does nothing whatsoever to change anything. Regards Pete

Do you know Java? I don't. If you know Java then perhaps you know what the error means. The only language section of the SDK I know anything about is the C/C++ part. The sources are provided, so if you get stuck in the language you choose I'm sure you could sort it out. With the C/C++ side it is usually simply differences in the version of the Compiler or Development System folks are using. I expect when the Java example was being compiled, many years ago now, it was a different version of Java. Before I leave you to it, though, one striking thing is noticeable: All of the DLLs and so on provided will of course be 32-bit, just like FSUIPC and FS itself. Perhaps that's one setting, at least, you need to correct? Regards Pete

It's too short for me to read it, but if it only referred to traffic and nothing else, it is something to do with traffic loading for some nearby airports. That could be due to a time shift, or a traffic injection program like UT2. Time shifts usually cause some scenery reloading too because of differences in shadows and tones. And in any case it's nothing whatsoever to do with any G3D.DLL crash prevention. There's no way you'd notice when FSUIPC catches one of those, it simply forces an early exist from some scenery processing. The most you might notice is a piece of scenery not finished drawing correctly, but that would be okay on the next frame in any case. FSUIPC is simply getting around memory corruptions caused by faulty scenery processing. The ONLY way you'd ever notice this is after your flight when you check the FSUIPC4 log file. It counts them too and gives you a summary at the end. Pete

That's very strange. Why does it ignore that part? It's the enclosure for the complete airport record and the ID is part of it. Maybe the use of fields within the <> parentheses needs a more sophisticated XML processor? Sorry, I don't know. I've never used Access nor any XML programs. The file was created in that format to meet requests received. I do have a version of Access on my PC but it doesn't recognise XML files -- was this added in a later version or are you using a 3rd party plug-in? Maybe there's a better one? I thought XML table formats were more the province of Excel than Access, and my old copy of Excel does recognise the format -- AND it puts the ICAO code in a column called 'id' as the first column ("A"). Maybe you should import it into Excel and output it as an Access database? Interestingly, even my (newer) version of Microsoft Word reads it successfully, and displays each entry in a very fancy graphic format, but it does omit the ICAO id part -- and the Runway id2 part. So it is definitely a function of the XML formatr which isn't universally accepted. BTW it takes Word a long long time formatting the whole thing in its fancy way. I started it before replying to your message and it is still in "not responding" mode, presumably doing more and more pages. Just one record takes up a complete screen in its format. Maybe there's an option in Word (and Access?) someplace for it to use imbedded fields, like Excel does. [LATER] I saved the Excel loaded version as an xlsx file, which is then recognised and loaded okay in Access, which includes the id and id2 fields. Regards Pete

Found it, but you said there was an example of your problem near the beginning. I saw none. And if it then hangs as you say, how does the video manage to continue? Pete

My last answer. I understand all of it, as I already said. But 0B52 is the indicator which says the generator is ON and supplying power. You should not use that to light the AVAIL light as I keep saying. By the time 0B52 is set the AVAIL light should be out. The AVAIL light only lights when the APU is running and ready to supply power once you operate the generator switch. Using the generator switch status to light it is wrong. Use the APU RPM as I said. I keep explaining this but you persist in repeating the same thing. You are right in that the operation is as you say, but you are interpreting it and the offsets incorrectly. You are the most obstinate person I've ever had the misfortune to deal with, and you ignore everything I tell you so that's it. BTW, the only thing that's different in the FSX Lear45 implementation is that the APU switch not only starts the APU but also the generator. You CAN switch the generator off afterwards (using the off control or offset 0B51), and that's probably the only time you'd ever see any "Avail" light light, because if the APU on and APU generator on switches are both turned on together there's never otherwise a time for AVAIL, which simply means the APU is ready to supply power when you need it. There's no AVAIL light I see in the FSX implemntation in any case, and for good reason it seems. Good night and good bye. Pete

Several. there's a sync option in the Aivlasoft EFB data provider. There's FSRealTime. And there's the option in FSUIPC. All are optional as far as I know. Maybe you have others. I can't tell from here. I'm afraid your YouTube link doesn't work. Pete

There's no need to quote that. I know this stuff. Why? Do you think the APU IS the generator? The APU is a small jet engine used to provide both bleed air and electrical power. You have to start the APU and when it is running properly (which takes some seconds) you can swutch on the generator. you do not switch on the generator until the AVAIL light comes on which says the APU is ready to drive it. Exactly! As i've now said several times. you are STILLnot reading what I write!!!! Your problem is that you are lighting the AVAIL light when the generator is ON, which is certainly incorrect. I've given you the answer. Drive the AVAIL light ON when the APU is ready and the generator is OFF. Turn the AVAIL light off when the APU is off or the generator is on. Simple. And i've said it twice before. This thread is getting really stupid. You ignore everything I say and simply repeat things which you don't even appear to read yourself. You accuse me of not understanding what you are saying, but it is you who don't understand what you are saying! I try my utmost to help, but you persist in ignoring everything. It is futile to continue. I give up. This is not the first time this has happened, and I am not wanting it to happen again, so in future I will leave any messages from you for someone else to answer. Maybe they'll have enough patience to suffer your refusal to read their answers properly. Good luck! Pete

Yes, exactly. All of that is just as in the 737, and as I said to you. But that is your problem! That is plain wrong! The APU generator running does actually mean the APU generator is running, not just "available". How many more times do I have to tell you? You just said clearly yourself, above, that "two LEDs in it and one lights up to say AVAIL when the APU is running"! Which is EXACTLY correct. The AVAIL light says the APU is ready to drive the generator, NOT that the generator is running!!!! You do not read what I write, and you do not even read what you quote from the aircraft manual. If you did you'd know the answers, as i have given them to you already. I cannot keep doing this with you. You seem to have a regular habit of not reading what is written, either here on in the arcraft manuals you refer to. Please do try harder to pay attention. It is very frustrating for both of us! :-( Pete