Pete Dowson

Well, it isn't a Windows operating system error. These errors are all to do with the Visual Basic run-time library (which is huge of course and has thousands of errors, none of which seem to provide any useful information in their default reporting mode). I really do not know VB (and I don't like it so I'm not likely to find out much either), but I think VB programmers can include error trapping, in much the same way as I can in a C program, and actually extract more information. Perhaps Enrico hasn't done this yet? Sorry, none at all. The best I could do is try to find "error 380" in my reference material. First off, under "run-time errors" I found this, which confirms what I said above: But that's the best I could do -- I couldn't find an actual list of error codes any where. And I don't know what "invalid property value" means -- I guess it's an incorrect parameter in some call, but I really can't get any further. A brief search on the 'net with Google seems to indicate that this error can mean almost anything, from a missing font to a screwed up file path -- it apparently simply means the program has called a library routine with a bad parameter. The only way I can see of finding out more is to trap the error in the program, which is what I would do if it were mine -- these days both FSUIPC and WideFS have such traps in. I couldn't solve problems without them. Regards, Pete

Yes, that is best. Did you check the announcement I mentioned? Actually I think it is listed as a "sticky". It is called "New version of FS-Interrogate in the works". Regards, Pete

Yes. That too is documented -- didn't you look? See the DOC files in the WideFS package. These documents are written to try to help, you know. ;-) If you download the Beta FSUIPC and WideFS versions available at the top of the Forum it is even easier -- please read the details there. Both FSUIPC 3.50 and WideFS 6.50 will be released next week in any case. Pete

I know very little about Delphi, but there are one or two Delphi programmers who visit here occasionally. One is Pell Liljental, the author of the FSInterrogate program (which is written in Delphi) -- see the announcement near the top of the Forum. Maybe he will see your messge. Regards, Pete

Yes, there is a pair of special controls in the drop-down list in FSUIPC's Buttons option page -- one for PTT on, the other PTT off -- you just assign the On for the Press and the Off for the Release. The documentation does mention it. This facility uses direct messaging to SB2 and SB3 and needs no specific keypresses assigned. Regards, Pete

Yes, there is something strange about the way that gauge is written. It works perfectly with the freeware Key which was issued for it on many systems -- I personally checked it here on three separate installations and there were no problems. I think it is doing something strange, possibly with threads, and there is some interaction with other installed add-ins and even other programs running on your system. The number of actual reports in not huge -- one sufferer did get rid of the problem by reinstalling Windows and FS, so there was evidently something else interacting with it. Assuming you have definitely registered the gauge as an application (and not as some have done, entered the key as a User key! -- please look in your FSUIPC.KEY file) there are only two solutions without going as far as trying to reinstall everything: either purchase a user key for FSUIPC, or try to find an alternative TCAS radar gauge which works properly, such as one of the freeware ones done by Lee Hetherington (gauges named ILH). Regards, Pete

Okaybut it is not 'solved'. Previous PMDG aircraft have certainly had assignable key presses. I don't know what they have changed, or why, but I have asked PMDG themselves to have a look and let me know. It may take a week or two as my main contact is away at present. Regards, Pete

Either via FSUIPC's programmable interface (i.e. from a program) by writing to the Sim Rate offset (0C1A), or by using the FS control "SIM RATE SET" with a parameter of 0. The latter can be assigned to a keypress or joystick button in FSUIPC's user options. Regards, Pete

Well, I know about quite a lot of FS stuff, for sure, but not, I'm afraid, about NetPipes nor record and playpack files. I think thast others who've synchronized two or more PCs have either used FSUIPC in them to read and write the data, and put the slave PCs into slew, pause or zero sim rate mode, or possibly managed to do it fast enough to stop FS's sim engine taking over noticeably (not possible anyway before FS2004), or they've used Luciano Napolitano's WidevieW (good for synching views more than actual simulation), or even just the straightforward in-built FS multiplayer facilities with the clients in "observer" mode. Regards, Pete

So? What's playback mode to do with anything? I never mentioned it? You are confusing me! (Not hard perhaps). Are you using record and playback data? I know nothing whatsoever about that i'm afraid. BTW none of this is remotely connected to the software I support in this Support Forum, is it? Pete

Calibrate properly in Windows game controllers and ensure FS sensitivity slider is max and null zone slider is min. Pete

In Options Controls Assignments there will be a drop down list of all the joysticks it sees connected. You select one, make all the assignments on that one, then select the next, make different assignments, and so on. How do you get the idea you can only use one? BTW, this isn't even a recent feature of FS -- way back in FS95 and FS98 I was assigning buttons and axes on the 16 joysticks emulated by the ISA-based EPIC board of the time! ;-) Pete

Where have you seen that? As far as I know there's no small limit on the number you can have. Not directly at present as it doesn't transmit axis values, only button presses. You could write a program to transmit joystick axis values of course. However, I don't see why it is necessary. There are even facilities in FSUIPC for allocating multiple joysticks to the same FS controls for pilot/copilot use. I know they are used successfully. The problems of single joystick devices were in the old Game Port days. The whole point of USB was/is to do away with all those restrictions. Regards, Pete

Only by putting it into slew mode, or pausing it, or setting the simulation rate to zero. Regards, Pete

Are you talking about the user's aircraft or the AI traffic? The AI traffic state is provided in the TCAS tables (for FS2004 only, not FS2002) as documented. There's no "boarding" state. You'd have to pretend they are boarding when sleeping or initialising and getting clearance at the gate. For the user aircraft you'd have to ask the user, or derive it from observing what he's doing with the aircraft. Regards, Pete

I should think it would be on Luciano Napolitano's WidevieW website. Don't you have Google or some other search engine installed? I just tried it and the first entry immediately tells me: http://www.wideview.it. Pete

Okayif you want to show me the [buttons] sections from your INI, I can check them here too. Also, remember, you can make button programming aircraft-specific (you'll get "[buttons.]" sections too then), so one button can do different things with different aircraft. Don't confuse yourself with that, mind! ;=) Regards, Pete

Sounds like the panel in question is getting its keypresses some way other than by intercepting the Windows keyboard messages. Maybe it is "hotkeying" them -- do the keypresses work in the panel even when FS doesn't have the focus, i.e. you've windowed FS and are using some other program? Check that you can use FSUIPC button programming to send keypresses to FS, with default panels. e.g. G for Gear, Z for autopilot. If so, then it isn't FSUIPC but the specific panel which is not allowing this. Regards, Pete

You still don't say what version of FSUIPC you are using. Sorry, what is the point the that huge picture? It shows nothing wrong. What do you mean by "greyed out like the default"? If you want to re-program the button, just press the SET button, just underneath where it shows the currently programmed keypress. If you want to clear it, press the CLEAR button. That is what they are for and why they are named that way. I really don't understand what the problem is that you are reporting. Regards, Pete

Thanks for letting me know! Pete

You aren't getting ANY button presses saved, or just those involving three keys? What version of FSUIPC are you using? I've just tried Shift+Alt+1 here and it is saved fine. If you aren't using 3.48 upgrade, if you are try the Beta release from the announcement at the top of the Forum. If you still have problems show me the FSUIPC.INI file. Regards, Pete

I always start it after FS. I thought the business of running it before was for its initial loading of cloud graphics. Maybe you have it set to use a different set of clouds for each FS session? Maybe that's the reason? Well I'm afraid I still can't really help without information. At a minimum I always need to know the version numbers of my programs, and at least relevant parts of the Log files. Regards, Pete

So, what have you changed? I can't do anything at all without information I'm afraid. First off, what versions? If not 6.47 at least, update first. Try the Beta versions available at the top of this Forum. Secondly, both WideServer and WideClient produce logs telling you what they are doing. Check those. I notice you have a VERY off start up sequence in any case: ASV needs Wideclient and FS running. Why not have WideClient load up automatically in your Client PC (place a shortcut in the StartUp folder), and have it load ASV when FS is ready, via "RunReady1= ..."? Then you only need to switch the Client on and leave it alone -- all the rest would be automatic when you start FS. I don't know what "autostart on FS" means. Pete

Interesting. I wonder what it actually does? The Beta version of the GPSout package provided in the Forum (see top announcement) includes a little freeware virtual serial port link program which may do the same job, if it is onlya port problem. It works well with the new option in WideFS to distribute GPSout data around a Network. Regards, Pete

An aircraft initialisation failure is normally recoverable. It means it tried loading the aircraft specified in the default flight set by your FS9.CFG file but couldn't because some essential part was missing. FS will then simply revert to the default flight. The default aircraft installed include a Skyhawk 172 but I think it's the 172SP not the 172R. When you uninstall FS I don't think it uninstalls the personalised bits like your saved Flights (in your "My Documents\Flight Simularor Files" folder), or the main FS9 configuation file, FS9.CFG. For a clean, initial-state, FS9 you must delete the FS9.CFG file before you boot FS9. To do this, find it in Documents and Settings//Aoolication Data/Microsoft/FS9. In fact if you really want a completely clean install, delete that folder before installing FS9 again. No, FSUIPC paid registration has been in operation for over two years now. Six months ago in FS2002 you must have been using a two-year-old unsupported version of it. Regards Pete