Pete Dowson

Go to the FSUIPC options, Logging tab, and check both the Buttons and the Events logging. Reproduce the problem (but other wise keep the session short), then show me the Log file from the Modules folder. Regards Pete

I can't see from that what was happening during normal running and what only in the menu. How many times did you enter the menu? There's one "stop" entry from SimConnect, and seemingly no corresponding "Start", so it seems the whole session was in a menu? Or what? This line shows you weren't actually in flight mode very long: Average frame rate for running time of 94 secs = 13.2 fps Where are those 94 seconds? Are all of those NAV2_RADIO settings and " Macro: mouse action" entries false, or some genuine, and how many whilst in the options and how many outside? You need to help me see what you see, please. With the Console Log open (you'd need to put FSX into Windowed mode) you will be able to see exactly what happens in real time. Please do that and explain what it is you are doing and what you see happening which may be wrong. You never need to do that as FSUIPC4 always replaces the log file on startup. Right, so it is this line being activated: 9=CZ,B,-780,2816,M1:33,0 Yes, I saw all that and quoted the relevant line to you, but I don't understand it. This is why I asked you to explain what it iss supposed to be doing, please. What are you intending to happen on your right throttle lever as you move it? It seems very odd to me, but maybe that's because i don't know or understand Airbuses -- they are very different from Boeings it seems. If you can halp me understand what it is you are doing with that throttle axis and why, then maybe I can work something here to compare it with, but I can't really do that without understanding what I'm doing. I don't have the MD-11 to start with, so i'd need to simulate it another way. Regards Pete

No. I think you misunderstand FSUIPC. It is a tool, an interface, providing the means for folks to get data in and out of FS. It is not an application in the way you are thinking, but an underlying layer which can help service such applications. As far as I know the sort of program you are thinking of is already quite a common thing in the Virtual Airlines world, where many enthusiasts have implemented PIREPS as well as ACARS systems. FSUIPC doesn't actually know anything about multiplayer aircraft at all. The "radar" data it provides is actually for AI traffic. There have been programs which inject the MP traffic into FSUIPC's tables as if they are AI so that TCAS systems can operate with them, and some MP implementations on FSX use AI aircraft to represent MP fliers in any case. But FSUIPC itself is not aware of any of this. Regards Pete

I think you must have it assigned (probably by defalut) in FS as well. You could have searched the INI file yourself for "0,4", as I had to. The uses you have of Joy 0 button 4 are: in [buttons.PMDG 737-700] 194=P0,4,CM12:2,0 in [buttons.Cessna 206 Amphibian 2] 4=P0,4,K87,9 which is a little odd as you also have button 5 assigned to the same keystroke: 3=P0,5,K87,9 in [buttons.C172N Skyhawk II BLUE] 4=R0,4,K8,9 None of those seem to be conflicting, so I must presume you have it assigned in FS. Regards Pete

Yes, it is better. Hmm. I must have forgotten to put the TAB property on that button. There are lots of examples like that I expect. As the dialogues have grown more complex i have become lazy. Not only that, but really the TAB order on each dialogue should be logical -- e.g. start top left and work to bottom right. But that is very messy to achieve, reordering everything. If you like I can check through the dialogues and make sure every button and field hand dropdown has a TAB property. But i cannot guarantee that they'll operate in any logical order. when I first posted the Lua announcement above i did suggest that some sort of library could be built up. Maybe I can start a new "Goodies" Announcement with download links to ZIPs containing such things, providing each has some sort of rudimentarty text file explaining the contents. I think it best, when ready, to email me the finished ZIPs and i'll upload them to the server with links in an ongoing Announcement, like the Goodies ones. "Contributed macros and plug-ins for Add-Ons" or similar. My email address is petedowson@btconnect.com. But post a note here first, please. Oh, I wouldn't want a huge support load as a result, so I'd very much appreciate your email address or some other way for questions to go direct, if that's okay. If not, then the ZIP must have an "unsupported, at your own risk" type of warning. ;-) Thanks for all your efforts, by the way. I am working on more Lua improvements now I know there's some interest. It stood apparently quietly unused for some time after I first released it last year. Regards Pete

The only action FSUIPC does when you OK out of the FSUIPC options is save any changes you made to the INI file and restore all of its internal action tables according to the changes you made. And this has always happened, with all aircraft? Or is this something you've changed? Sorry, I'm not clear on what that means. Do you mean aircraft-specific / profile assignments? They won't change unless you relaod the aircraft. No. As I say there's no mechanism is FSUIPC to apply changes to anything in FS unless it detects changes on the inputs. It must be seeing such changes, maybe through something you've programmed somewhere? If you want me to help further I'd need more information. Axis logging would be useful as well as the relevant parts of the INI file. Your own analysis on what you might have changed to induce this would be useful, assuming as I must that it hasn'yt always been this way! Regards Pete

Ouch ouch ouch! I must have had little sleep that night, and it was a morning change! I normally check if I've already covered folks' requests and search first. But in this case I assumed (!!! never assume !!!) that the user was correct and I had not yet implemented them. So I implemented them again! How stupid of me, and what a waste of time. :-( I will withdraw the new ones in the next increment. The code is identical for both pairs, so two of each is just a waste of time and space. Thanks for spotting this! Regards Pete

There are no compatibility changes at all in the INI file -- your settings can always be carried forward from one version to the next. The whole point of FSUIPC has always been onward compatibility, with new features never changing old ones! I take great pains to ensure this. You are most certainly misinterpreting something quite seriously! If you have any problem it needs reporting and fixing, not retreating to older, more buggy and unsupported versions! It will be nothing to do with FSUIPC, for sure. But until you update to a supported version I'm afraid you get no support. Regards Pete

Where was that parameter? So it was down to something internal in FDC? Sorry for the questions, but it helps me to know on case others ask. It also seems odd that it changed by itself? Regards Pete

At the start, even after the first connection, the server is timing out the connection "due to lack of demand" -- it's a safety measure to delay with stalled clients. However, the log shows that timeout to be coinciding with the first connection attempt from the client: The timeout is 10-15 seconds initially (extending to 20 after first connection). For some reason you are starting Wideclient at just about the wrong time. Why are you starting it a good 13 seconds after FS is ready? Best to have all your clients running, ready and waiting, really, before you even start FS. I have my clients loaded as part of Windows "startup", so they automatically connect as soon as FS is ready, every time. I suspect something has changed in the way you do things on the client, and this has managed to get the timing just wrong. A few seconds earlier and it wouldn't have fallen foul of the timeout, and few seconds later and it would have connected on the restarted Server attempt. As it is the client sees the timeout and tries to connect again, so WideServer sees two subsequent attempts. The third one works. It isn't critical, but the answer is to start WideClient earlier/ Regards Pete

Thanks. I'll take a look. Pete

Hmmm. Yet you have wideFS running? why not move them onto a separate PC? FSX isn't very good at releasing any of the processors, unless you manage force it to (e.g. by severely restricting frame rates or reducing settings). Well, it doesn't show a code signature pproblem. How did you reolve that? What does the last FSUIPC Install log show? There's nothing wrong in the FSUIPC4.LOG. I don't really think its a problem with FSUIPC specifically, perhaps more just a resource sharing problem -- maybe too many demanding programs? That's not relevant as it isn't being used. There's no firewall relevance to any of this. With the SP2/Acceleration version of SimConnect only pipes are used by FSUIPC, not TCP/IP. Windows always thinks things are non-responding if they aren't processing messages. It sounds like there's a problem with your sound drivers -- they should not be holding up the processing of messages in either program. Sorry, when I said you'd missed a bit I meant you'd left out part of the story you were relating! HOW did you fix the code signature problem? Where is the Install log I asked you to show me? Yes, I know, but that's not the point. You carried on and managed to run FSUIPC4 in FSX, which isn't possible if the code signature fails. I wanted to know the part of your story you missed out. IE manages authorisations for software publishers. It is is charge of all of the code and webpage signing certificates. That is why you are referred to it to sort such problems out. Regards Pete

Okay, glad you are happy. Sounds like you are basically, in certain cases, turning an axis into a simple up/down spring loaded switch, ignoring its values and merely using the direction of change. Regards Pete

Sorry, I think you missed a bit there. Was SimFlight listed as an untrusted publisher? How did you get past the error? Can you show me the Install log for FSUIPC4, please -- it will be in the FSX Modules folder. What firewall is this? Are you using WideFS and running these programs on a separate PC to FSX? So I guess you are using WideFS? You really need to state such things, and where the RC and FDC programs are running. If so, have you checked the WideClient, WideServer and FSUIPC4 log files to see if any problems are being reported? Regards Pete

Wow, that's impressive! I'm glad I'm not wasting my time adding these things! ;-) Pete

The computer date and time have no affect at the Registration stage. If the key you purchased was definitely for FSUIPC4, and not for FSUIPC3 or WideFS, then the only possibility is that you are entering something wrong. The name, email and key sections have to match exactly to what you are told. Try using cut and paste to be sure. Every character must be correct. same case, same spelling, same spacing (if any). Pete

There's no file called "Lua_download.zip". The Lua download zip file is obtained from the links in the Updates and Goodies Announcement and also in the separate Lua announcement. Try clicking on the links, that will download the zip and the files are inside. These are simply updates for the ones installed by the last Installer release. The examples are inside the inner Zip called "example Lua plug-ins" (the Payload737 and Fuel737 lua files) and the facility is documented in the Library reference pdf. Well, not blind, but the reverse perhaps? Able to see things that don't exist, like a "Lua_download.zip" file? How /where did you get one of those? Not from me, for sure! ;-) Pete

No. It sounds like something is wrong on your system. Is FSX struggling to start? Maybe FSX is taking so much processor time in the initial stages that WideServer or the network side isn't getting a look in? What have you changed recently? WideClient, WideServer and FSUIPC4 logs are needed. No INI files please. Close the session first, both ends. Keep it as short as possible, paste the logs into a message here. Regards Pete

Not sure how you reach that conclusion. Flight Sim has full range operations possible on all three axes -- throttle, prop pitch and mixture (or conditioner). The normal assignment, via FS, uses FS controls which only provide POSITIVE values for all these, running from 0 to 16383 (100%). But there are different controls, not assignable in FS itself, which provide ther negative portion of this range too, from as much as -100% (-16383). FSUIPC offers the ability to use these other controls. As it says in the documentation, it does this automatically if you map the generic control (the one-for-all-engines control) on its first Calibration page to the 4 separate controls, on subsequent pages. Each of the generic control sections feature a "map to 4 xxxx" checkbox. Thast makes the one-for-all control map to the 4 separate controls, one for each engine, and on those pages you can calibrate a reverse range, with a central "idle" or its equivalent. Yes, I understood that, and pointed out the the F2 key is using "Throttle Decrement" which simply moves the throttle control into its negative range. This can easily be done the way I said, and the way documented in the FSUIPC User Guide. Ah, so you want a separate Reverser instead of a reverse region on the same (throttle) lever? Yes, of course this can be done too. There are two ways. One is really only suitable for jets -- that is to calibrate the reverser in FSUIPC, which by default in fact takes over the mixture assignment in FS. This was done because many folks preferred to use the throttle + prop levers as dual throttles, leaving the mixture lever at one end as the reverser. However, there is a parameter which can be changed in the JoystickCalibration section of the FSUIPC INI file to select a different control to act as reverser. But the control so assigned will then not be able to perform its normal function -- folks normally choose some other axis-type control they don't need in any case. The other way is to use FSUIPC's axis assignments instead of FS's. Then, by selecting the "direct to fSUIPC calibration" option for the axis, it can be assigned directly to the reverser (or to one of up to 4 separate reversers). However, again, whatever axis is assigned cannot normally also be used for some other function simultaneously. If I understand you correctly, now, you wish the prop pitch lever to act as a prop pitch lever in its forward part, but as a throttle reverser in its rear part, because the aircraft model you are using in FS uses throttle reversing, unrealistically, instead of prop pitch reversing. Is that right? This is also possible in FSUIPC, but it is really a fiddle using facilities in an unintended way. In the axis assignment facilities you can assign the same axis to both prop pitch and to throttle reverser. But you'd need to then calibrate the two in such a way that there is a dead zone in the reverser action in the area where you want prop pitch actions, and vice versa. I've not tried this sort of thing myself, but it should be easy enough. You create "dead zones" by simply calibrating the maximum and minimum positions far away from their real positions on the lever. Well, a large number of folks seem to manage okay. If you really want a gate, I would suggest glueing a little piece of rubber next to the lever's slot, something which just rubs enough on the lever to tell you where idle is. You also need a reasonably wide idle zone so that you can always be sure of parking it there, even allowing for any jitter or temperature variations in the axis readouts. Regards Pete

Good! Strange, that. I assume other commitments have overtaken the developers. Regards Pete

Good! Well, all that's beyond me too! Phew! Good job you know a person who knows! ;-) Regards Pete

The F2 function operates on the THROTTLE axis, not on the PROP PITCH axis. It sounds like you have things a little mixed up within FS rather than FSUIPC. If you use F2 for reverse thrust, to switch to using an axis instead you need to have a reverse zone on the throttle axis, not on the prop pitch axis. Actually it's FSUIPC you mean. I suppose UIPC (Universal Inter-Process Communication) is okay for short. Sorry it is a bit unweildy -- historical, from FS5IPC and FS6IPC before it, from FS95 and FS98 days. ;-) Hmm. Maybe, but in this particular case I think it is more that you are confusing FS functions rather than FSUIPC functions, as it sounds like you have those sorted okay. There's nothing about FSUIPC which changes throttle to prop pitch or vice versa. To use controls in FS you need to know about FS, not really about FSUIPC. FSUIPC just offers extra ways to apply the controls, that's all. From your second message above: You are missing the fact that in FS (all versions, in fact), by default F1 is "throttle cut" and F2 is "throttle decrement", so you need to calibrate your throttle with a reverse zone. That's all. You seem to have confused yourself with prop pitch thinking? Or have I misread your words? Regards Pete

Erare you getting mixed up between FSUIPC3 and FSUIPC4? There is no registration capability in any FSUIPC4 option screens, and hasn't been since version 4.00 -- you must register using the Installer! There is no "legend" in FSUIPC4 about administrators, only in FSUIPC3 (for FS9 or earlier). The installer automatically runs in elevated administrator mode, which is the privilege level needed to register. Please update to a supported version of FSUIPC4 -- 4.53 -- and register during installation. You'll find a useful document that tells you how to install and register inside the ZIP. The latest version of FSUIPC3 also has an installer to get over such problems. Regards Pete

No, there's no trouble there. The only reason the IPX server option fails to start is that you haven't installed the IPX component in Windows -- it became optional with XP and so on. Since you will not be using that protocol it doesn't matter. The files certainly point to that rogue IP address as the culprit, so the solution I suggested is really the work-around, unless you know where that strange IP address is coming from, and can fix it. Regards Pete