Pete Dowson

ErI didn't ask that question. I asked if you used FSexpand (which is nothing to do with WideFS). It may also be relevant to know what else you have running on that PC -- not to do with FS, just other programs, background services, etc, running. Maybe there's some antivirus or firewall checker which is clobbering it. These sorts of problems are so rare, and so far each of the few there have been are different. In the end it all comes down to a process of elimination. In the end it may be necessary to go into the windows process list and kill each background process in turn until either the problem goes away or the system crashes. In the latter case, note that one, re-boot, and continue but leave that one running! This has found some culprits before. I think one was a Kensington mouse driver. Why I've no idea, but apparently it wasn't doing anything useful so it was easily dispensed with. Sorry, but it's no use, as you can probably see. ASV6 never ran. In the previous log at least WideClient sees ASV6 connect: "38636 New Client Application: "ASv6" (Id=3252)". That didn't happen this time. If ASV6 never connects then there's nothing to log. It needs sorting at the ASV6 side. I need to know why ASV6 doesn't see the FS window class Wideclient presents. How did you make it connect the previous time? Or is it that after setting "Log=Yes" you forgot to run ASV6? BTW why are you specifying a ServerIPAddr? Surely the ServerName would be better? Or leave both off altogether if you are running winXP both ends. Pete

There is certainly something wrong with one of your keys. Please Zip up and send me the FSUIPC.KEY file from the FS Modules folder and I will check them both for you. Please also attach the receipts from SimMarket. Send to petedowson@btconnect.com. Please remember to Zip the KEY file as it won't get through otherwise. Regards, Pete

Hi Thomas, I confirmed the problem and fixed it in version 3.709, now available above, in the Interim Versions announcement. Thanks! Regards, Pete

Okay. So now we must find out why it thinks it is "disconnected". It is a shame it is not more informative. In the WideClient.INI file (which I assume you have not edited?) change the Log= line to read just "Log=Yes". This should show us what it is reading, if anything, which makes it think it is disconnected. However, this part of your original report worries me: The last report of this type was from someone using FSexpand as well -- it appeared that FSexpand somehow stops Wideclient running correctly. Perhaps you'd like to peruse that thread too? http://forums.simflight.com/viewtopic.php?t=55723 That got to analysing huge logs, which showed that whilst Wideclient's Network threads were quite happily exchanging messages, and, in fact, the client application was too, there was no time left over for any windows message processing, which made Wideclient looked hung, and the client program inoperative. I currently don't know of anything else like that. But maybe checking the other things you have running may show a conflict somewhere? You say you've changed nothing, but obviously something has changed. Regards Pete

Eryou ran it for 30 seconds? When did you start ActiveSky? I think that alone takes more time than that to start, doesn't it? What did ActiveSky say? Where's the WideServer Log? What version of FSUIPC? Pete

What programs are you running on WideClient? what version of wideclient, WideServer, FSUIPC? Any Log files at all? What protocol are you using? And what did you change 'a few days ago'? Pete

What does the Wideclient Log say? When the programs "don't connect" what do they say? Maybe the WideServer Log would show something of interest too? What versions of wideServer, WideClient, FSUIPC? Pete

Did you buy the WideFS key with your new Email address and not ask SimMarket to match it to your FSUIPC key? If so then one or the other Keys will have to be changed. SimMarket could do that for you, or otherwise you will need to send me the receipts (notifications) for both of them (to petedowson@btconnect.com) and tell me which address you want to use. Regards, Pete

I don't knowI will check it here. But it will be tomorrow, now. Sorry. Regards Pete

If you have a file image, then you have a file called FSUIPC.KEY in your FS modules folder. That is a Text file with your registration details -- just cut and paste from there into the FSUIPC registration dialogue. If you don't have that file you'll have to follow the recommendations in the announcement/sticky above, as i said. Regards, Pete

No, no way I know. Even using a count is no use as you have no control over the timing of each increment, other than maybe the button scan interval. But to increment a count needs some button action, something held pressed. In the cockpits I deal with such needs are accommodated by programs like pmSystems, where you can program this stuff easily. If you can't find a way and still want this in FSX, let me know in a few months time when I should be ready to start adding new facilities again. At present, I am just too busy trying to implement the ones I already need to! Regards, Pete

Are you trying to say that you lost your registration key? You didn't make a copy of the FSUIPC.KEY file or keep a backup as advised? You just deleted everything? I don't keep any such information. in fact I don't have anything to do with the Registrations. Please review the announcements above. One of them tells you what to do. As for FSUIPC itself, it is where it always has been for the last seven or more years, http://www.schiratti.com/dowson. Regards Pete

Thanks. I'll check it here. I'm gradually working through the offsets but it's a long job. I was hoping for lots of feedback, but there's been very little -- that's either a good thing (most are okay) or bad (no one's looking!). Regards, Pete

WideFS does not split the FS program into little programs you can run elsewhere. WideFS is simply a Network extension of the FSUIPC interface. Anything which interfaces to FS via FSUIPC on the FS PC should run quite happily on a Networked PC running WideClient. Not sure. There are lots of external instruments provided by external software, as I listed for you. Anything that runs OUTSIDE of FS, providing it interfaces TO FS via FSUIPC, should run okay on a WideFS client PC. That's the whole idea -- there are lots of such programs. as well as instrumentation via Project Magenta, vasFMC and so on there are Weather programs like ActiveSky, ATC programs like Radar contact, tracking programs like FlightKeeper, and so on. If you are only running FS on your "main com" all you can do is turn down some of the sliders. Regards Pete

WidevieW only runs in FS. WideServer will run in the same PC with WidevieW, but of course Wideclient is designed only to be run on a PC which isn't running FS, so, no WidevieW either. You cannot run FS's own panels without FS. They are not complete or separate programs, only modules which drive FS graphics. If you want gauges and subsystems running on other PCs you need to look at programs like Project Magenta, FreeFDS, vasFMC (all FSUIPC/WideFS compatible), or maybe FSexpand which I think has its own networking system. Even then, really your throttle control needs to be on the FS PC, where your throttle is. Regards, Pete

No worries about crying out about problems. It could have been a real problem, after all. Thanks for confirming all is well with 3.708, and please don't worry about reporting things in future. I don't give out black marks! ;-) Oh, please make sure you left Lefteris know too, it was he looking to reproduce it. Regards, Pete

Not really looked. In the gauges which display these things they would normally be derived from an assortment of conditions, which of course should be shown on the six-packs and overhead. All the more advanced panels do their own logic here, just as I do for PFC.DLL and pmSystems does for Project Magenta cockpits. [Later] No, I don't see anything relevant in the lists of accessible variables for SimConnect. Best thing to check, when you get FSX, is the XML source for the gauges, assuming any of the default panels actually operate the annunciators. You should be able to see the logic used and variables accessed. To be honest I don't use FS panels (or any panels at all really) so I don't know if there are any default ones which do all this. Regards, Pete

For FSUIPC to see a Key released it needs to see the Windows message WM_KEYUP. For every WM_KEYDOWN there must eventually be a corresponding WM_KEYUP, otherwise the key is deemed "stuck down" and becomes unusable in windows terms. Make sure you understand what you are doing by trying programming keys on your real keyboard. If you understand that and make it work, yet still have problems with your emulator, then that emulator is evidently not emulating the keyboard properly. I'm afraid I cannot help with that, you'd need to contact the supplier. Regards, Pete

The FS message is nothing to do with anything of mine -- that's a warning for FS I expect. If you are a registered use of FSUIPC then it doesn't need a key for other applications or DLLs. Because you are registered as a user and therefore do not need ever to register any application separately. Since you refer to Page 7 of the documentation, why not also read the bits on page 3 under the heading What you get if you pay, particularly the item about access for application programs: Regards Pete

Sounds as if you have defined it as a Toggle switch, not a momemtary push button. With a toggle you push once for "on" ("press") then again for "off" ("release") -- these are separately programmable in FSUIPC's Buttons page. The "button" area in the display should change colour when "on". If you've only programmed the "press" part then the programmed action will only occur every second press -- i.e. in the "off" to "on" transition. A momentary button sends an "on" ("press") when you push it and an "off" ("release") when you release it. Again, separately programmable if you like, but only using one touch. If you don't understand, show me the section from your WideClient.INI file. Pete

That is very strange. Even according to the Actigate documentation (I went to the website/forum) says to try de-activating it in the Menu in some circumstances. How can you if it doesn't appear? Ah -- it's the "Help" menu. I see. Regards Pete

Thanks Lefteris. I actually compared my source code in the few areas which may have affected NAV data between 3.70 and 3.708, and the only changes I found were all for the added HSI data. The fix I made between 3.707 and 3.708 most definitely eradicated the problem I accidentally introduced with VOR2. There's a puzzle there somewhere, I assume, but I suspect it is down to something else in the sufferer's system. Best regards Pete

Thanks. Actually the aircraft isn't the default, but one called "SAG-EDITION" which I don't have. So I loaded the default 172 instead. Unfortunately, there is still no problem. I'm afraid I cannot really spare much more time on this, so I think I will just have to add some warning to my documentation. I have written to the Actigate author, Arno Gerretsen, to see if he has any ideas. Hmmm, even though you have presumably put the DLL back into the Modules folder by now? Maybe this is part of the problem. If I have Actigate.DLL in the Modules folder, not only do I see Actigate in the Modules menu, but I have TWO modules menus!?? In your picture you have a Menu entry with a name merely "?". What is in that? Regards Pete [/img]

I'm not getting any problems .. I installed the scenery, even placed my aircraft there, at a gate. Actigate is installed and says it is active, yet I can still reach and edit the Registration details. Obviously there's more to thiscould you possibly send me the FLT+WX files you were using at the time you tried to register? That will select the aircraft (hopefully a default one?) and the precise positioning in the scenery, which may well be critical. Thanks, Pete

Thanks! I'll try it now ... Regards, Pete