Pete Dowson

Yes 4.232 is over a year old now. The minimum supported version is 4.40, and there's a 4.428 available in the Updates in this Forum. Apart from this, your message merely contained a picture of some sort of APPCRASH which appears to have no relationship to anything of mine, and no word of explanation! I am not psychic, I cannot read your mind (especially from a distance! ;-) ). Regards Pete

Well not as complicated as you make it sound. Just an application program, a single EXE, which reads the joysticks and writes them, using the published FSUIPC interface, to the appropriate offsets. Then it will run on the same PC as FS or with wideclient on the client PC. You can either directly write to the elevator, aileron, rudder and throttle offsets -- but then you'd need to do your own calibration before writing the properly scaled values -- or just send the values you read as FS controls, like AXIS AILERONS SET and so on, via Offset 3110. You write the value first, to 3114 then the control to 3110 (or both together in an 8 byte write). Then you should be able to calibrate in FSUIPC. The numeric values for all the controls is provided in the Lists I publish -- one is installed in the Modules folder for FSX, otherwise you'd need to download one from the http://www.schiratti.com/dowson page. Regards Pete

No, only button presses. For good aircraft control the latency of joystick control over a Network is generally not good. It would be easy enough for someone to write a program to do this, through WideFS, but I don't know of one. Regards Pete

There's no menu there! Have you never got into FSX to fly? When you are ready to fly there's probably an aircraft control panel showing, and a view of the outside world? Did you not read any of the FSUIPC4 User Guide? Right in the first section after installation and so on, the one headed "Okay, I’ve installed, and optionally registered. Now what?", it clearly says, right at the beginning: With FSUIPC4 correctly installed, and Flight Simulator running and ready to fly, look at the FS Menu bar at the top of the screen. (Press ALT to bring it up if it is hidden). The menu is a normal regular Windows-type menu bar which appears along the top of the FSX screen when you press ALT. It is where you can do all sorts of things in FS, like select flights, change aircraft, select views and panel parts, and so on. Even terminate FSX. If you've not even flown FSX yet, I suggest you try before bothering about messing in FSUIPC. Then take a look at the menus and all the options you can explore in every part of FS. Regards Pete

I've no idea what any of this is about, but I don't think it belongs here, and I will not support such an old version of FSUIPC in any case. Regards Pete

Oh dear. Being a programmer or any sort of guru is nothing whatsoever to do with any of this. The file you posted IS the FSUIPC4.LOG file which you said didn't exist! The fact that is DOES exist, and even says "FSUIPC Menu entry added" means everything is working. So there absolutely MUST be an Add-Ons menu containing FSUIPC! Where on Earth are you looking? Do you know how to get to the FSX menu at all? The Add-ons menu will be the last item, to the right of all the others. The left most one is Flights I think. Pete

Because you don't read my replies? What documentation? Have you bothered to read the part of the Announcement I pointed you to? The part beginning "When first loaded, and each time the FSUIPC Options dialogue is used, FSUIPC will now scan the registry and make a list of the names lodged there ..."? This is a new facility. The User Guide is not updated yet. Please read the details for the update. If you don't understand it, ask questions by all means, but please don't profess such total ignorance without at least trying! It even tells you how to get FSUIPC to do it all automatically for you! There's no way to rectify your settings if they are already in a complete messre-plug in your joysticks in the way they work best, then follow the instructions, THEN do whatever you like and follow the instructions again. If you are really in a tangle the only way might be to delete your FSUIPC.INI file and start again from scratch, using the new facilities. Then they'll help next time you decide to reconfigure things. Everything that I can help do is there. I cannot stand behind you and watch what you do. I do not have your PC. Every one's installation is different. You have to take some responsibility for what you do with your hardware. I provide the tools and I try to improve them to help. The rest is up to you. Pete

Oh dear. You do not read my replies? I'll repeat from before with more emphasis: I made a lot of changes to both FSUIPC3 and FSUIPC4 in the last few months to help with this. Please take a look at the Updates announcement at the top of this forum. Read the section starting with: "When first loaded, and each time the FSUIPC Options dialogue is used, FSUIPC will now scan the registry and make a list of the names lodged there for each of those connected joysticks ...". Download the updated version and try it. I think you'll find it helps enormously, especially if you use the facility to assign letters to each device rather than use the Windows-assigned numbers. Windows does. Wrong! You simply ignore what I tell you! If you want help and ask for it, you should have at least enough respect to read the answers, please! :-( I don't do this for fun you know! I develop software and try to please everyone. I am well aware that unplugging USB connections and re-plugging them can play havoc with windows joystick numbering. Though FSUIPC has been fine with Windows joystick numbering now for 10 years and this sort of problem has only come to the fore in the last few months. I tackled it in the best way I could and provided a solution. I pointed you to it and you blindly ignored it. What else can I do? :-( If you cannot do anything I ask, I suggest you simply delete your FSUIPC.INI file and start again. Do that each time you unplug and re-plug devices. Otherwise use the facilities I am providing and let the software help you! After all that if you still have problems, then, and only then, show me the FSUIPC INI file so I can see what a mess it is in. Pete

Possibly. To change the status of a publisher you have to run Internet Explorer (it is the custodian). Tools-Internet Options-Content, "Publishers" button, Untrusted vs Trusted publishers. If that wasn't the problem, please obtain a SimConnect log as instructed in the "FSX Help .." announcement above. Regards Pete

I've tried, but you refuse to take my advice. Why? Pete

That means only "the latest version I saw". What is that, then? Please always state version numbers. The only way that is possible is that the joystick numbers are, in fact, the same, or that you have both sets assigned in the FSUIPC INI file, perhaps from earlier connections. In that case you have not yet assigned it. It is that simple. If you really want to check these things, the FSUIPC INI file is the place where ALL the assignments are stored. No where else. There's no magic. Look at that or show me the assignments there. If you'd move on to the real latest versions and read the reference I stated I'm sure you'd do better. Pete

I assume this PFC yoke is one of the USB-connecting types, not one driven by my PFC driver? All that is happening by the sound of it is that Windows is assigning the same joystick number to it, maybe because you used the same USB socket. Really any changes to any USB device connections plays havoc with numeric assignments because Windows seems to treat them as "uninstalled" when unplugged. I made a lot of changes to both FSUIPC3 and FSUIPC4 in the last few months to help with this. Please take a look at the Updates announcement at the top of this forum. Read the section starting with: "When first loaded, and each time the FSUIPC Options dialogue is used, FSUIPC will now scan the registry and make a list of the names lodged there for each of those connected joysticks ...". Download the updated version and try it. I think you'll find it helps enormously, especially if you use the facility to assign letters to each device rather than use the Windows-assigned numbers. Regards Pete

Hmm. That's weird -- you say you can see the throttle axis operating in both the Axis assignments and in the calibrations? It shouldn't have an effect, but just in case, check in the FSX Control Assignments settings that none of the sensitivity sliders are below maximum and none of the null zone sliders above minimum. Probably, if the PFC driver is also trying to drive the same throttle. Have you disabled the throttle action in the PFC driver? You shouldn't have separate sources for the same controls. That's akin to letting FSX operate the controls at the same time as FSUIPC. The only way to have both FSUIPC and PFC axes working is to disable the axes in the PFC driver and assign those, too, in FSUIPC4. Then for multiple throttles it will arbitrate (using the max setting), or you can make the axis assignments Aircraft or Profile-specific, so loading different aircraft automatically switches to different controls. No, no way. It can't do that. The only types of assignments which FSUIPC can intercept and take over are the Keyboard ones -- a keypress assigned in FSUIPC takes it away from FS. However, even if the PFC driver settings are a problem, what's really puzzling is that your log shows no Throttle axis actions at all. I don't understand that. Note that you omitted to show the Calibration section of the INI file this time, so I couldn't check that. I don't need the [General] section at all. In case it is specific to the actual axis on the device, could you try a test where you assign one of the currently working axes as the throttle and vice versa? Regards Pete

The install was good, nothing wrong there. The important thing is whether there's a file called "FSUIPC4.LOG" -- i.e. the run-time log from FSUIPC. If there is one, please show it to me. If not then FSUIPC4 is not being loaded, which may mean you have me listed as an "Untrusted Publisher" through telling windows not to load my programs at some time. Let's see if there's a run-time FSUIPC4 log file first. There should also be an FSUIPC4.INI (config settings) and, ofg course, the FSUIPC4.KEY file containing your registration (which you should backup for safety). Regards Pete

The interface provided by FSUIPC/ESPIPC relies on the application programs finding and talking to a Window with the classname "FS98MAIN", which is the standard FS classname used in all versions since FS98, including ESP. There's no easy way you can have the application talking to WideClient on the same PC as a real FS or ESP is running. You'd instead install ESPIPC or FSUIPC into that sim and connect to that. If the application program is of your own design, so you can change it, you could take advantage of a facility in WideClient to change the ClassName -- please read the section in the WideFS Technical document about the WideClient parameter "ClassInstance". Somewhere around page 11. You'd need to modify the application to find that new classname instead of the usual ones. The normal use of ClassInstance is to be able to use WideClient's other facilities -- mainly the ButtonScreen facility -- on a PC also running FS. In that case there's no application to worry about. Please note that ESPIPC is being discontinued. The current version expires at the end of this month. Before that there will be a new update of FSUIPC4 which will install and work in both ESP and FSX. Regards Pete

WideFS is in two parts -- the Server, which runs in FS or ESP (the Server is the WideServer module in FS9 and before, but is built into FSUIPC in FSX and ESPIPC in ESP)., and "WideClient", which is the client program emulating FS or ESP with FSUIPC installed on the networked client PCs. The reason for this is to allow programs which use FSUIPC to connect from a networked PC which is NOT running FS or ESP! Therefore there is never a need to run WideClient and FS or ESP on the same PC -- or at least, very few needs (button screen and button transmission really -- certainly no emulation of FSUIPC). if you want to run an FSUIPC client application on a machine running FS or ESP, you simply install FSUIPC or ESPIPC first. What is it you are trying to do. It makes no sense so far. Regards Pete

Sorry, FSUIPC isn't a mouse programming program at all. You are misunderstanding the term "mouse macro" -- the idea of that facility is to allow something to be controlled by keystroke or button which otherwise is only accessible by mouse. One of the prime aims in cockpits is to do away with both keyboards and mice -- in fact the only real reason for the keyboard programming facilities is to support those button-connection hardware boards which emulate key strokes (programmable) from button presses. If you really prefer using a mouse you are well catered for in almost all FS add-ons as many of them need only a mouse. No FSUIPC programming needed at all then! Regards Pete

When did you purchase your registration? I don't seem to have it on record (but my records aren't 100%). It looks like it isn't valid. There are two possible reasons for this: 1. The registration was purchased AFTER the date currently set on the PC. Please check that your PC date is correct. OR 2. The registration key is in fact illegal, one generated by a pirate key generator. If neither of these apply, please ZIP up the FSUIPC.KEY file, from the Modules folder, and send it to petedowson@btconnect.com. I will check it here. Do NOT post it in the Forum. Regards Pete

First, I need to be sure you are using a supported version -- 3.85 or later (3.867 is available in the Updates announcement above). If not, try updating yours first. Thendoes the FSUIPC log file (in the FS Modules folder) show anything? Are you using any options in FSUIPC at all? The only difference between registered and unregistered is that it offers more facilities for your use. It doesn't actually DO anything different unless you ask it to. And there's nothing normally on a one-second timing at all. Maybe you should do this, just so I'm sure I get needed information: 1. Remove the FSUIPC.INI file from the Modules folder, just to be sure all options are defaulted. 2. Load FS, run only enough to see the "stutter", close FS. 3. Find the FSUIPC.LOG ile in the Modules folder, and paste it in its entirety into a message here. Regards Pete

Well, using your settings EXACTLY (merely changing the joystick numbers to match mine, I cannot make it go wrong. Works fine. Question: you HAVE disabled the joystick with the throttle on it in FSX itself, haven't you? If not, then the reason it could be failing is that your are Reversing the throttle lever in FSUIPC4 (presumably your lever is mounted backwards?) and I suspect the two values from the two sources are cancelling each other out quite well! If you assign in FSUIPC you MUST be sure not to also assign in FS, unless you realy want some unpredictable behavious. Looking in more detail at the parameters in your file, these lines: show that you are calibrating two separate throttles, mixtures and levers in the other pages, as well as using the single all-engine values, yet you made no assignments to the separate ones! I would be concerned about what that might be doing to the path taken by the axis values, it already being rather circuitous because of the filtering. I would advise you to go through the Calibration pages and "Reset" all those places which are shoing as calibrated (ie have the Reset button on the left) which are not in fact being assigned in FSUIPC. Or just delete all the above lines before loading FSX. One lesser thing, in your Extras-specific assignments: You appear to have a spurious extra assignment to the elevator, from an axis "16Y". There is something happening in FSUIPC4 which does seem to occasional spot an axis on non-existent joystick #16, I am still looking for the reason***. But you shouldn't assign to it, and certainly not an axis already being used. Let me know how you get on after checking these things and having a tidy up. Regards Pete *** P.S. Just found the reason for odd Joystick 16,17 or 18 axes appearing. It'll be fixed in the next update. ;-)

Aha! The crucial information! The main thing I note which is probably different from most folks is the assignment to the Throttle/Slew combination, not the usual throttles. I'll check that now. Incidentally, I also note two things: 1. You aren't calibrating a reverse zone on any of the throttle/mix/pitch axes, but you are doing this by simply calibrating a zero reverse zone. You'd find it easier to simply set the option for no reverse zone which is added on the multiple engine pages in the recent updates for FSUIPC4, including the one you are using. 2. You appear to be checking the "filter" option on all of the axes in the calibration section. Why? Are you experiencing jitter? Filtering has disadvantages as well as advantages -- it slows the response, sometimes quite noticeably. Best not to use it blindly, only if needed. I'll get back about the como Throttle/Slew axis, later ... Regards Pete

SUCCESS! I got really annoyed about this, why I couldn't get it working, so I went and bought the Citation just so I could sort it out. (It's the most expensive aircraft I've ever bought for FS, and it's only FS9 which I don't even use. Sigh). The flag needed is number 11, not 17 -- when you release the button FS sends an 11 THEN the 17! The 11 means "LEAVE" (which I would have taken to mean move the mouse away from the switch). The 17 is the left-button-up. Anyway, this works: 21=APU Start=RX70280*X8bcc 22=APU Norm 22.1=RX70280*X8bcc,11 22.2=RX70310*X8bcc,11 23=APU Off=RX70310*X8bcc Assign Start to the Press and Norm to the Release of a start button, Assign Off to the Press and Norm to the Release of an Off button. I've found and fixed the bug with the Progress window sticking when you start a macro creation -- it was actually creating two identical windows because of the path being taken through the Macro filename request dialogue. I'll release an update later this weekend. The above macros will work with the current main release (3.85) as they don't use any newer facilities. I won't be able to offer the ,11 creation facilities anyway, they have to be by editing. Regards Pete

That's very disappointing, as that is the only thng I can see that would be happening with the real mouse. I'll scrap the whole attempt. Sorry. It just won't work. Ah, thanks. That's a good clue. I'll see what might be happening. Regards Pete

Hi folks, I can hardly move in my office and need to clear some stuff out that I no longer use. This is mostly PFC stuff (check http://www.flypfc.com for pix and other details, at least for the parts they still sell). For now it's a brief list, to see if there is any interest here. I'm pricing it all really low because I want it to shift, but I also want to raise enough dosh to pay for replacing the hard disks on my main Sim PCs (PFC 737NG and Aerosoft GA28R) with solid state ones. Just talk to me if you have an interest. Bear in mind I'm in the UK. I'd rather not have to pack stuff up well enough to survive shipping (I wouldn't know where to begin, to be honest), so this favours folks in the UK or close and willing to collect. If shipping is involved the costs will have to be added, because they could exceed the prices (as you'll realise when you feel the weight of these items! They are build to last, and SOLID!) Okay, here's the list, starting with the one item not from PFC: EPIC USB, cased, plus expansion board£ 50 (GBP) PFC stuff: Cirrus 2 Console + choice of one throttle quadrant .... £ 600 (GBP) (This is not the "Pro" version). Assorted other quadrants£ 50 (GBP) each (I have one of each type) Avionics stack + RIC£ 450 (GBP) (Connects to the Cirrus 2, or can be used alone) Throttle quadrant system (TCS) + choice of one throttle quadrant£ 150 (GBP) Cirrus rudder pedals, digital (not proportional) toe brakes£ 150 (GBP) (Wired for connection to Cirrus 2, TCS or Jetliner console, but could possibly be converted for Game Port use -- not USB though) Jetliner 737 style floor-standing yoke ... £ 200 (GBP) (Wired for connection to the Jetliner console, but could possibly be converted for Game Port use -- not USB though) Jetliner console with 737 quadrant£ 400 (GBP) (Include A/P controls, full radio stack, as well as throttle quadrant and sundries) MCP complete with pilot and copilot EFIS units and 6-packs£ 500 (GBP) (This is easily the most professional-looking and feeling full MCP that you could (once) get. It is the same one incorporated into the PFC 737NG (see "AATS" on the website)). Freestanding 737 style full size FMC incorporating mini PC and green mono screen£ 250 (GBP) (This needs Project Magenta CDU software running actually on that mini PC, and it connects as another PC on your network. There's a slight fault with it (which has been there ever since I got it) in that the switch on sometimes doesn't boot the PC. There's a consistent way around this, however). Questions? Offers? (Though please note that these are pretty much absolute minimums already -- they are all worth far more, as you'll see if you visit the website and check the pricing). Privately to petedowson@btconnect.com. I'm in no rush about any of this. I'm still far too busy to actually tidy my office in any case! . This is in the nature of forward planning more than desperation! Regards Pete Dowson

Right, and it is exactly what I said it probably was -- you are writing 256 bytes to 3380, not 128. Please please, you MUST take note of the sizes of each of the offset values! It is surely a trivial matter, but it is very important. Since FSUIPC lets you into the innards of FS, such bad errors can easily play havoc -- not necessarily doing nice tidy things like crashing FS, but other things which may be much more difficult to work out! I see you also got the size for 32FA wrong too. I think you need to go through all of your code and recheck every single offset size, make sure you correct them all! If I'd known you were still on such a very old version of FSUIPC I wouldn't have helped. That is so old it is unbelievable! I don't support anything earlier than 3.85 at present, and 3.90 will be released later this month. Please do try to keep up to date and ALWAYS check versions before asking for support! Anyway, now I've started I'll finish: here is where your write to 3380 is going awry: 406000 WRITE0 3380, 128 bytes: 54 69 6D 65 72 20 68 61 73 20 62 65 65 6E 20 73 406000 74 6F 70 70 65 64 21 20 49 6E 63 6F 72 72 65 63 406000 74 20 70 6C 61 6E 65 20 74 79 70 65 2E 00 00 00 406000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 WRITE0 3400, 32 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 WRITE0 3420, 8 bytes: 00 00 00 00 00 00 00 00 406000 WRITE0 3428, 16 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 WRITE0 3438, 32 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 WRITE0 3458, 16 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 WRITE0 3468, 24 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 406000 00 00 00 00 00 00 00 00 In fact the string you write is only 46 bytes, including the zero terminator -- providing the string is less than 128 bytes in total you would be better using the string length (+ 1 for the terminator). And here the incorrect 4 bytes, instead of 2, for 32FA: 406000 WRITE0 32FA, 4 bytes: 0A 00 00 00 And the code shows these errors clearly, even though I don't know the language: Dim fsuipc_writeTxt As Offset(Of String) = New FSUIPC.Offset(Of String)(&H3380, 256) Dim fsuipc_TextDelay As Offset(Of Integer) = New FSUIPC.Offset(Of Integer)(&H32FA) Please update your FSUIPC !!! Pete