Pete Dowson

I thought you had to be logged in to post messages in any case? Pete

The wrong log is shown. This one, from WideServer, shows the connection occurring: As you can see, the connection was recognised at "22:33:35.281 + 963.921", or 22:49:39.202 and disconnected 127 seconds later. The only WideClient log you show is a later one, with no connection: To see what is happening, the current (relevant) logs from both sides need to be viewed. There's no error seen by the Server at all, it sees a connection, then a couple of minutes later, a disconnection. It is that simple. Please also always show the complete logs, including the performance summary which is given at the end, when both FS and the Client are closed down. If the session you have just run and closed failed, then the relevant logs are named "WideServer.log" and "WideClient.log". The ones with a "0" in the name are the previous logs -- they are saved to allow folks to restart FS or the Client after a problem (eg an FS crash) without losing information. Regards, Pete

I have no website, so I cannot give "direct links" other than those this forum supports, which is what that paper clip and its associated link represents. for now I'll send you it as an attachment by email, but please find out why your browser isn't working correctly with these Forums. you are missing out on any interim releases I post as well as anything anyone attaches in any of the Forums here. Maybe a message in the general forums, near the top of the list, which are overseen by Simflight folks, will elicit some help. It is probably down to something you have blocked. Regards, Pete

Another quick question. I notice: I hope you are not Opening and Closing on every cycle too? Only do this at the beginning and end of your program, or at least only when you want to connect to FS. Oh, and why bother storing the result of each Write and Process operation in different "Result" variables if you don't check them in any case. If you are ignoring them they may as well all be ignored in one variable. If you do get an error in any you shouldn't continue in any case, or you can but it would be rather a waste of time. Pete

It isn't "around the attached file", it is just below the paper clip, which is way over to the right, right of the description, filename, everything. Maybe your window isn't wide enough. use the scroll bar. Regards, Pete

Why have you posted the exact same message twice? Is this related to your quadruple Process calls, three or which are for nothing? ;-) Pete

Well, I wouldn't use VB to start with. But after that, as far as FSUIPC is concerned, provinig you keep to the minimum number of process calls needed to do the job, everything else is irrelevant. By this I mean one process call for everything you want to read or write per cycle. Sorry, I'm not delving into code to find out, but what "short" are you trying to deal with? Aren't you getting enough resolution? If FS only deals with 16k steps for whatever value it is you are talking about, what does it matter about the rest? [LATER] I'm not delving into yuor code in detail, but what on Earth is going on here: One "Process" call will deal with ALL queued requests, the others will do nothing at all except waste time switching processes for nothing. That will be wasting 75% of your time! Regards, Pete

Just a further note on this: You did UNCHECK the first option (the one asking for the FSUIPC multiline display), and then, when the one below appeared (asking if you want to suppress the multiline messages going to FS's window), CHECK that, didn't you? That's the correct way for ShowText only. However, there should be no combination which actually prevents ShowText receiving the messages -- it simply reads the FSUIPC offsets, which are not actually affected by these options. Let me know please. also, did you uninstall Advdisplay, or is that still installed? If it is is it enabled or not? Regards, Pete

Really? Ouch! I cannot make that happen here. This is the reason these new facilities are made available for folks before a formal release, so I can sort out any oddities. You really needed to report this, not try to work around it. As it says in the announcement it is all designed to work well with or without ShowText -- I use ShowText all the time. So I need to know much more about how you manage to get ShowText to fail, please. Step by Step, so I can reproduce it. I'd rather we got the thing working as it should first, please. The hot key facility is simply intended for those who want to be able to view the wnidow when THEY want to, not as a work-around for a possible bug which needs fixing! Thanks, Pete

Ah, not like Squawkbox then? I know Squawkbox builds itself into FS quite thoroughly. IVAP stuff is all external to FS then, no menus or windows in FS? Well, if it is all external to FS I'm not surprised. It cannot possibly make threads hang from thereunless of course it is the Multiplayer interface which is hanging. Is IVAP properly closed BEFORE you close FS? Then it does sound like it is either hanging onto the multiplayer connection, so keeping that thread active in FS, or, possibly, there is an Ivap-used DLL installed which also doesn't let go. Perhaps there's a proper way of closing IVAP down and you aren't following it? I think you may need to go talk to someone in the Ivap support forum, assuming there is one. Regards, Pete

Of course. Didn't you read the release notes in the announcement above, or spot the extra checkbox on the FSUIPC front options page? See this: You say: Oh dear. Sorry, but it drives me a bit nuts too the way some folks never even read what I say or look at what's available. Especially for interim versions where you'd think that would be the first thing they would do? You evidently didn't even notice the new options or read much if any of the text? Even using the Advdisplay hot key to turn it off would be permanent until you turned it on again -- see this part in the Announcement: Best before going nuts just to have a brief look, okay? Regards, Pete

Okay, so whatever is getting FS into that state hasn't been triggered yet. Well, though that does possibly suggest that one of the Ivao modules is the culprit, it may simply be that by then enough other things have started doing things. The usual cause of everything appearing to close yet the process not terminating is a thread which has been created to do something and then, somehow, never been told to terminate. But identifying whatever it is that is doing it is not easy. The only way really is trial and error. You could try temporarily removing the Ivao DLL(s) and see if that stops it, but ... ... this seems to indicate that it may be something else (unless you've updated some Ivao part recently?). Have you any other add-ins you can try without? The reason FSUIPC performs this check is that if both processes (the new one and the "apparently closed" one) were allowed to continue running, there would be two FSUIPC interfaces operative, and it would be pot luck which of these would be attached by external programs using FSUIPC. The end results would be even more confusing than this is! Regards, Pete

Something is actually stopping FS closing correctly. Its Windows may have gone, but it is still there. You can check this for yourself -- after closing FS, use the Windows Task Manager (ctrl-alt-del) to look at the Process list (not the Application list). You will see "FS9.exe" still listed. Select it then end the process forcibly using the button below. The last add-in DLL that I know did that for a while was an early version of Active Camera for FS2004, but that was fixed quite quickly. If you use that make sure you have the latest version. And check the assorted non-Microsoft DLLs you have in the Modules folder. One of them is likely the culprit. It could be a gauge, but that is much less likely as they are rather more restricted in what they can do. Regards, Pete

Where they've been since FS98: 0BB6 and 0BB2. Please use the search facility in your word processor. A search on Elevator and Aileron would have found them very quickly. Pete

That would be 3.553. There are no FS controls for PMDG's way of doing things. You cannot use controls as you have been trying. You know the keystrokes, you just told me them. Program your buttons to send those -- it's still done in the Buttons and Switches part of FS, but look at the left-hand side! Possibly, or they are not actually arming because you haven't put the lever in the right place. Try making the Arm zone wider to make it easier. Regards, Pete

No, mine does too. You need to move the mouse to the word "download". click there! Pete

Doesn't the PMDG 737 "do its own thing" for A/P and A/T operation? You'd probably need to find what keystroke combination they've assigned for this, then program your button to send that. That shows button 1 (I count from 0, so that would probably be your number 2) assigned to FS control 65861, which, if you check in the FS controls list packaged with FSUIPC, is "AUTO_THROTTLE_TO_GA". So, yes, you've assigned the button to FS's TO/GA facility, but in all probability (and this is a question for PMDG, as I don't know), the PMDG 737's don't use FS controls. Have you checked PMDG documentation to see how to operate its TO/GA via keyboard? Once you know that you can re-program your button to send that key combo. Regards, Pete

Well, I gave up trying to do it, and instead found a way to use FS's displays instead. How do you change the font or font size in FS? If you can find out how to do it then I'm sure it will work with the FSUIPC one -- it is another FS display, it isn't mine. This is why all the sizing, docking and saving (in the FLT files) is handled by FS. I thought I said that. Let me know if you know how to change FS fonts. Regards, Pete

I don't know. I've never heard of anyone not being able to download from here. I supply many files this way, including new interim versions of my programs in the announcements above. I've just clicked on the download and it works. The file is very short -- are you sure it didn't just download so fast you didn't notice? Pete

Well, if you scan through my list of FS2004 controls (availble on the download site or within the FSUIPC Zip) you'll certainly find enough FS controls for buttons. I would have thought they'd all be listed someplace in the FS assignments dropdowns? These are they: ALL_LIGHTS_TOGGLE LANDING_LIGHTS_OFF LANDING_LIGHTS_ON LANDING_LIGHTS_TOGGLE PANEL_LIGHTS_OFF PANEL_LIGHTS_ON PANEL_LIGHTS_TOGGLE TOGGLE_BEACON_LIGHTS TOGGLE_CABIN_LIGHTS TOGGLE_LOGO_LIGHTS TOGGLE_NAV_LIGHTS TOGGLE_RECOGNITION_LIGHTS TOGGLE_TAXI_LIGHTS TOGGLE_WING_LIGHTS All FS controls can be assigned in FSUIPC, and there are a lot of additional controls too. The "TOGGLE" controls above aren't so suited to toggle switches -- you need separate ON/OFF controls for those, but that can be done using FSUIPC "Offset" controls to manipulate bits in a set of light switches in the FSUIPC interface. That's a little more complicated, and needs a document from the FSUIPC SDK for reference, but it can all be done pretty easily from the in-FS options dialogues. Well, I've not heard of spikes like that, but it is quite normal for two potentiometers to be less than absolutely identical. Obviously more accurate calibration may help with that, but normally some amount of sensitive adjustment with the feet is needed to compensate. And your personal foot pressure may be the same in both left and right, but not many folks could swear to that, so it is by visual feedback surely that you operate? I would have thought that to be the case in a real aircraft too (when I was learning in a real Cessna I could never keep a perfectly straight line under braking!). FSUIPC will help with more accurate calibration, but I don't think it will answer a subtle difference in pressure. If you never want to use the brakes separately then the latest interim FSUIPC will allow you to make them both operate left and right simultaneously. Ah, you mean you are using something in CH's driver to operate FS's "F2" (throttle dec) control? Certainly there are many folks using part of the throttle lever range to control reverse thrust proportionally. FSUIPC has always provided facilities for that. There are also facilities for up to 4 separate reverser levers, but obviously you need the extra levers for those -- they are for cockpit builders with proper quadrants. Regards Pete

There should be no interaction between your separate levers whatsoever. That sounds suspiciously like a hardware problem. Ask in the CH forum. Regards Pete

FS2002 contains no such message. FS2002 doesn't need FS2002. You must mean something else. What, exactly? Well, you don't need to buy FSUIPC for PMDG planes normally, but I don't know about their FS2002 versions as they precede the date FSUIPC needed any registration. But if you want to buy it you will find plenty of help and instructions in the announcements above, in the FSUIPC documentation, and on the FSUIPC download site http://www.schiratti.com/dowson. I'm not sure how you can miss all of these! ;-) That's out of date. The current version is 3.53. Check the announcements please. Why? You don't need to register it unless you want to use its user facilities. Please check the documentation. To purchase FSUIPC, please just see the announcements above, or see the documentation, or see the download site. It is very clear in all three. But please be sure that you want to first. nothing you've said seems to indicate that you need to really. Regards, Pete

Can you explain what that means, please? I would need to know what you have actually done. What version of WideFS are you using? Is the connection okay? Reverser axes have been supported in the Joystick Calibration part of FSUIPC for a long time. The only extra in the interim release above is the axis assignment -- previously you had to assign them to some other FS control (in FS) and tell FSUIPC which they were via the FSUIPC.INI file. Regards, Pete

There are no facilities for using client-based axes at present. Sorry. Pete

Yes, of course. You'd need to disconnect the PFC axes from FS whilst you need control, using the programming facilities for this described near the back of the PFC.DLL documentation, then control the elevator and aileron directly via the appropriate FSUIPC offsets. You need the FSUIPC SDK, available from http://www.schiratti.com/dowson. Regards, Pete