Pete Dowson

WideFS doesn't use and doesn't care about drives or mapping. It's only concerned with the Network connection. I need to know the version numbers of FSUIPC and WideClient, and you need to paste the WideServer.LOG file (from the FSX Modules folder) and the WideClient.LOG file (from the WideClient folder) here so we can see what it says. That is what logs are for, so we can find out what is going on. Regards Pete

Right. Er .. so the brake pedal axis is NOT working correctly? If you keep the brake pedal depressed it should brake all the time, until you release the pedal. If it is not braking when you turn the tiller there is certainly some interference or double assignment. It sounds as if your brake pedal is NOT assigned to the brakes axis, but the "BRAKES" control (the same as pressing the . key). That is not correct! Not really. I think you need to tell me what you've assigned these things to and where! Pete

Yes. Received 5/5 okay. Seems something's blocking the other IP address, but it isn't at my PC. Pete

Sorry, I don't quite understand. Are you saying that your steering tiller axis and your toe brake axes are interfering with each other? Do the brakes work okay when you are not using the tiller? Do you perhaps have dual assignments -- maybe the tiller axis is being assigned to brakes in FS? Sorry, you need to explain what you mean by that. Send what sort of action? What do you mean "while hold"? Regards Pete

Okay. You can use that -- I can't support it, but then I can't support FS98 either without a copy. But I would like to have a stab at fixing 3.998h if you could try to get the info from that for me, please. Regards Pete

Strange. Neither has arrived. I'm getting Miguel's okay -- he sent me a copy of one of yours. I'm not blocking them this end. Must be something my ISP doesn't like about them, but if that were the case it would normally replace them with a warning. Regards Pete

Sorry, no. This is reading in the PFC.DLL's throttle quadrant calibration window? Naturally you can calibrate to that range, you'll just get less resolution. You must have a superb device BTW: I've never seen any PFC axis which returns the full 0-127 possible. they usually range about 6 to 110 or so. Regards Pete

That may simply affect the timing of things inside FS. If you wish me to check further you'll need to enable ipc write logging in FSUIPC's logging tab. But if the ACARS program is only reading things (which I would assume -- why would it write anything?), I doubt this will show anything different. By all means post the log here if there are any writes leading to the crash -- it is easy to cause a crash by writing incorrect values. You could also try the latest version of FSUIPC3 (3.998h) -- see the Download Links subforum. Regards Pete

No, it isn't a problem between those two. FSUIPC is okay -- it just becomes unable to respond to your ACARS program because it is running inside FS9, and FS9 is crashing. FSUIPC cannot continue on its own without FS9, it is not a freestanding program. Since FS9 is crashing always at the same place when you are flying, it is 99% likely to be a bad scenery element. You'll need to isolate different add-on sceneries until you find the culprit, then re-install that. Regards Pete

If I can find my FS98 anywhere I'll check what's up. Haven't had time to look yet. I'll repost here if I do find it. Perhaps you can help me fix it anyway. Show me the FSUIPC log, from the FS98 Modules folder, please. It might at least show me where it got to. If you first add "LogExtras=Yes" to the [General] section of the INI file then it will show me more. Paste the log into a reply here. Pete

You posted this twice. I replied to the one in Paul's thread in User Contributions. Pete

Sorry, I cannot help with C# or the code for the DLL -- perhaps Paul can comment on your code if you show him some -- but what exactly are you expecting to READ from C800-CBFF? That is the weather WRITING area. If you cannot write weather successfully, you need to check that you are following the protocol laid down. Best, if you want my help, to use FSUIPC's logging facilities so I can see the results of your code, not the code itself. And of course you can use logging to compare what you are doing with, for example, WEATHERSET2.EXE, which uses the same interface. Regards Pete

The EXT library run functions use the same methods as the FSUIPC INI RUN parameters. It's the only way I can offer the other options. A shell execution doesn't give me so much control. But it could be done without returning a handle (i.e. so no use in closing whatever you started, or doing anything else with it really). I'll add a "shell" function, just with pathname and command line parameter options. Maybe tomorrow, but more likely over the weekend. It isn't hard, but i'm a bit tied up most of tomorrow. Regards Pete

What crashes? The aircraft, FSX (or FS9 or FS2002 or what?) or your ACARS program? You need to provide more information if you want assistance. I need to know what crashes, what version of FS, what version of FSUIPC, and why you think it is FSUIPC. FSUIPC never disconnects as it never makes the connection -- other programs connect, FSUIPC merely responds. If it isn't responding it will be because FS is hung or crashed or whatever. FSUIPC is part of the FS process so if it hangs so does FSUIPC. That's not my program so its log is no use to me at all. Where's the FSUIPC log? Pete

Sounds like the problem fixed a while ago. Check that you are using the current FSUIPC4 release -- 4.745. There's also a version 4.746 available in the Download Links subforum. Regards Pete

As a test I've used your details here and registered with the 3.998g installer with no trouble. I'm afraid that if your entries are immediately met, after entry, with a message saying they are invalid, you are most certainly entering something incorrectly. The check is made on all three entry fields. You have at least one wrong. Maybe spaces at the end or something not quite so obvious. No, because how can that make any difference? The one sent to you is fine. If you are making a mistake, a new one will make no difference and it will just make things complicated because I'd have to get the good one you have disabled! Regards Pete

If this is a needed facility I can add a new function to the new Lua EXT library added recently to do a "ShellExecute". It looks like this can run anything in the same way as double clicking in Explorer can do. It doesn't give me enough information back to offer all the other options in the Run category, but should certainly allow "vbs" to run. Paul, please advise. Regards Pete

Okay, so it presumably won't execute by calling "CreateProcess", which is what I use. Maybe it would run with a WinExec call instead? I don't use that because it is deprecated (spaces in the parameters are ambiguous to it even if in quotes), and it doesn't provide the process and thread IDs I need for some of the run options. I suspect that executing scripts and the like needs a Shell call instead. BTW, now you are here, Ian, could you tell me why I see that I have 3 pending topics to approve, but they are not visible to me -- they usually appear in pink? I can still see pending posts in existing topics, but not new topics. This started happening only today. I can't approve them if I can't see them! :-( Regards Pete

Harmless in what way? If I knew how to change the ATC Flight Number in use, I would do. But that offset is just set be reading a token variable, as I said. Regards Pete

Hmm. Odd that, when it works okay in FS2000. There must be some other function I'm using which didn't exist back then. Unfortunately that tells me nothing useful. The crash isn't even in FSUIPC. No. That'll be all about other things in your system. I've really got no way of finding out why this happens now. And I lost my FS98 discs some years ago. I will have another look for them, but meanwhile can you not update to a known supported version, like FS2000, FS2002 or FS2004? I'm sure you can get FS2004 really cheap these days. I think it might be quicker. If not, perhaps you can ask the author of the program you are trying to use why it needs FSUIPC. For FS98 it realy should use the official interface, FS6IPC -- that was the proper interface back then. Regards Pete

Yes, as it stands at present, that is true. The changes in 310A/310B merely tell FSUIPC what to do with further incoming axis values. They don't invoke any action in themselves. Axis inputs are only processed when the axis value changes, as you've noticed. They are write-only offsets used instead of writing direct to 088C etc when you want those inputs to be disconnectable. Offsets 310A/B do NOT stop software controlling the throttles via 088C etc (which would defeat the object), so another offset was needed to allow programmed throttles using offsets rather than axis inputs to send their values in a way which could be disconnected by 310A/B. This mechanism is used, for example, in the 737 simulator by Andras Kozma and now at Budapest. In fact it was Andras who requested the facility. Regards Pete

Windows error numbers are meaningless to everyone I should think. Google them as I have to. That one comes up with "not a valid Win32 application". Why? none of mine are run like that. You should only need to do that during installation. "vbs"? That is not a known executable -- you need .EXE, .COM, or .BAT. A "vbs" file is probably a script executed by some other program. I've no idea how one can execute a vbs, sorry. If you know the EXE which runs the vbs then you could probably do it with ".....exe" follwed by "RUN_A2A_BAK.vbs" as a parameter. Regards Pete

Well, whilst it was originally designed for FS2000, not FS98, it was originally made to work in FS98 only in order to check the offset mapping between FS98 and FS2000, to make sure I retained compatibility. The only other use on FS98 was for the logging. It had very little other purpose. The current version of FSUIPC3 is actually 3.998g (and there's a 3.998h in the Download Links subforum. There were some changes after 3.99 was released to make it work again in FS2000 and CFS1 and 3, so perhaps yuo could update and try again. Otherwise I need more information. If a Windows error is coming up then you can get more information, and in particular the Module offset and error code. But only with 3.998h please, otherwise it won't match what I have. Regards Pete

Unless you have changed FSX's options to stop it loading a flight initially, it will be too late once you get to the initial menu. Find your FSX.CFG file and add or set "DisablePreload=1" in the [Main] section. It's worth doing this in any case if you always select from the Menu, as it makes FSX load quicker. Regards Pete

I've never heard of FSX losing the setting for whether controllers are used or not. I think your FSX did not close properly, but crashed at the end instead. There are several add-ons which can cause that. If it happens then any changes you make, anywhere in the FSX settings, aren't saved into the FSX.CFG file (unlike FSUIPC, FSX only saves the settings when it closes). Two things you can try. Either load FSX, go direct to Settings - Controls and untick the Controllers selection, and then immediately close FSX. Hopefully nothing will have happened by then to cause it to crash instead of save an updated CFG file. Or simply find the FSX.CFG file yourself (in your user AppData\Microsoft\\FSX folder) and change the option directly. It's in a section called [CONTROLS]. change JOYSTICKS=1 to JOYSTICKS=0. Pete