Pete Dowson

Oh, right. I am not familiar with their products at all I'm afraid. Well, I can look at and interpret logs from FSUIPC if you like, but I do not actually have any Elite devices nor do I know the least little thing about them. They don't seem to need my support, but since they presumably wrote the driver to work with FSUIPC (or had it written?), they would know something about it. And why aren't they responsible? Regards, Pete

You don't mention the version number, but I assume you are talking about FSUIPC 3.40? Didn't you keep your FSUIPC.KEY file -- it would have saved you re-registering, unless you also reinstalled Windows or moved to another PC. There's no change in the registration system, and hasn't been since about version 3.02. In all cases like this it has turned out to be a case of incorrect entry. All three parts (name, email, Key) must be exactly as per the original notification. Cut and paste to be sure. If you still have no joy, send the details to me at petedowson@btconnect.com and I'll check them here. Regards, Pete

It is not only the key which must be exact, it is the name and email too. Cut and paste all three entries. If you still have a problem, send the details to me at petedowson@btconnect.com. But all cases like this so far have turned out to be incorrect entry of the data. Regards, Pete

Thanks. Send it to petedowson@btconnect.com please. Regards, Pete

Not that I know of. I never fond any way into that part of the system. Yes, only one visibility layer is implemented throughout. Although FS's weather structures have long had provision for any number of layers, in practice when I have tried to use these everythnig has gone horribly wrong. They don't work. Well, not at that time. THE GLOB weather is merely the default weather set for a Station that has no specific weather set for it, but weather stations only get 'populated' as needed as far as I can see. Naturally, if you ask for weather for a far-off station (or any point far off) this would invoke routines in FS to compute the interpolated weather there, and it would need to assume the GLOB weather. Of course, as I've argued and demonstrated before (see discussions in this forum and my documentation), GLOBal weather doesn't stay global forever. The air mass is dynamic and things change. I think it only actually computes and progresses the weather stations around your position - not sure how many, but something in the order of 50-100, probably depending where you are. However, it can store weather *ready* for computation for all of the METAR stations in its list -- you'll find a file containing all the 4-letter ICAOs in the same folder as your FS9.CFG file. It is called "wxstationlist.BIN". It is there rather than in the FS9 folder because it can change -- when you download weather using FS the stations may be updated. Sorry, I don't know. Refresh scenery after clearing the weather? There is an assignable control to refresh the scenery. Regards, Pete

Sorry, but I don't have anything to do with Elite or its panels. You need to talk to Elite support. They have never talked to me or asked me to support anything to do with any of their products. Why do you think FSUIPC or anything else I produce is in any way involved? Please let me know if there's something which I can help with, but at present I cannot see what. Some Elite products are actually made by PFC (http://www.flypfc.com), whose digital products I do effectively support through my "PFC.DLL" driver for FS, but I think all those supplied through Elite use their own proprietary protocol, not the PFC one supported in my driver. Regards, Pete

This sounds the same as FSUIPC's "extend max METAR vis" option. This interprets 9999 and 10SM as meaning "something beteen 10kn/10SM and max vis", and generates a skewed random visibility instead -- for weather injected by third party programs only, of course. What did this replacement WEATHER.DL convert the "9999" to, then? Really? I've not noticed that! What does it set for the visibility in these circumstances, then? Thanks for the info! Regards, Pete

Oh, rightwhat benefits did this one provide? I didn't know anyone had been modifying it! Not to worry, I;m glad it is now all sorted out! Regards, Pete

Only the buttons on the joystick. So far I've not implemented any form of joystick axis reading, either in FSUIPC or WideFS. The whole business of axis assignments and calibrations and so on needs addressing at some stage, and it is on my long list of things to do, but it is not at the top. Sorry. If you are a programmer, you could do it by writing a little program to read the joystick values, scale/calibratre them, and write them to the appropriate offsets via the FSUIPC/WideFs interface, but even that isn't trivial -- because of the calibration/scaling needed. You'd effectively be by-passing FS's and FSUIPC's own joystick calibrations. It may be possible already using a third party program. I've an idea that FS Communicator provides such facilities? Try http://www.flightsimulator.at/frm_fscom.htm Regards, Pete

Hmm -- they are the FS9.0 DLLs. Your FS9.1 update didn't work properly! Don't try to correct the date! It isn't the date that is the problem, but those dates show that your FS9.1 update did not work. I think you need to refer to the Microsoft "read me" documentation that came with the update package, or look at the website, to see how to trouble-shoot this, unless you want to stay with the original 9.0 version and not enjoy the benefits of Microsoft's recent work. If you look in the FS folder there should be a BACKUP folder. Is there? Does it appear to contain backups of all the files, probably renamed with odd insertions? If so you may be able to run the FS9UpdateUninstall.exe program (in the FS folder), then delete the BACKUP folder, and try to apply the update again. For the English FS9.1 update, the dates and DLLs listed in my Announcement at the top of this forum are correct. Check against the list there when you think you've managed an update. No, with all the 2003 original DLLs you are running FS9.0, not FS9.1, that's all. But it means you don't get whatever fixes Microsoft have made. Regards, Pete

Another thought here. Some folks with non US/English versions of the FS9.1 update have reported incomplete updates. Can you look at the FSUIPC.LOG file (in the FS Modules folder). Are there access errors with some details of internal registers listed? Please check that your FS9.1 update has actually worked properly. To do this, look in the announcement about the 9.1 update at the top of this Forum. You will see there a list of those modules which should have been changed by the FS9.1 install. With a non-US/English version the dates on some may be different, but they will all be September 2004, not the 2003 date of the original release if FS9. The problem already reported with a couple of non-English updates is that the WEATHER.DLL is not replaced when it certainly should be. There have been a number of corrections in that module. Trying to run FS9.1 with the FS9.0 version of the WEATHER.DLL will actually cause FSUIPC to crash continously, as it has intimate connections into that DLL. These crashes don't crash FS itslef as FSUIPC traps them and logs them, but it will stop FSUIPC from working. Regards, Pete

Are these access errors with some details of internal registers listed? You can ZIP up the file and send it to me at petedowson@btconnect.com, but please first check that your FS9.1 update has actually worked properly. The only cases like this I have heard of were the result of a partially installed FS9.1 update. Look in the announcement about the 9.1 update at the top of this Forum. You will see there a list of those modules which should have been changed by the FS9.1 install. With a non-US/English version the dates on some may be different, but they will all be September 2004, not the 2003 date of the original release if FS9. The problem already reported with a couple of non-English updates is that the WEATHER.DLL is not replaced when it certainly should be. There have been a number of corrections in that module. Regards, Pete

Sorry, you will have to ask the author. I cannot understake to support all add-on programs for FS. If you have an FSUIPC.LOG file you want me to look at I will, but take a look yourself first, see if there's anything odd. By "the upgrade ACOF" do you mean the FS9.1 update? If so, I assume you did install FSUIPC 3.40? Incidentally, I do have FSMetar 1.5.3 here and that seems to work fine with FS9.1 and FSUIPC 3.40. Regards, Pete

N1 and N2, along with EPR (where calculated) and EGT are, like many other things, results and not causes. The only control over N1 you have is via the power adjustment -- i.e. throttles or thrust levers, call them what you will. To set a specific N1 you adjust the throttles and read the results, allowing time to 'settle' (and perhaps a little predictive calculation based on change rates). Via a sensitive feedback loop like that you should be able to maintain any specific possible N1 setting. Regards, Pete

Sorry, I am not understanding any of that. What "Build 145 Beta"? There's nothing I'm aware of with a build 145, and I have no Betas out ar present. Can you clarify? What note of mine are you referring to? Some wires here seem crossed. Are you sure you posted to the right forum? Is "AS" ActiveSky? If so, did you mean to post there? If you are getting black screens or hangs when swapping modes in FS9, you should try updating to FS9.1. Microsoft have fixed a lot of things and these may well be events of the past. Regards, Pete

Best technique is to get the weather started whilst you are at the gate still working on your plan. Then have a key or btton hooked to FSUIPC's "Traffic Density Toggle". Toggle it off, then on , and wait a little while for it to wake up again. Ah, yes, I see. That indeed can be done since FSUIPC 3.40 -- before that the internal FSUIPC additional controls weren't available to applications through the FSUIPC interface. It can be done now. Go ahead. Regards, Pete

Well, it's never been a function of FSUIPC, nor is it really a natural candidate for one, though it would be nice, if it were merely a matter of asking FS. Maybe there's a way of doing that by calling routines inside FS itself, but I'm afraid I've not found it. I would never consider a facility which would entail FSUIPC scanning files or even looking up a database. That is certainly an application job. Well, I did write a program for FS98/FS2000/FS2002 which built up a complete airport and runway database from a user's scenery installation. It operated by scanning the SCENERY.CFG file and searching ALL of the enabled BGLs for the airport data. Took quite a while, but you only needed to re-run it after changing (installing/deinstalling) scenery. The database it produced is included in my FStarRC package, and other variations are used in Radar Contact and, I believe, FS-Meteo. Unfortunately, the formats are all changed in FS2004 and I've not yet had time to investigate, let alone re-write the program. I suspect that most of the data you need is in the AFD files, not just any old BGL, but even they can be spread around. And I don't think they have to be in their own file. It is quite possible, I think, for an add-on scenery designer to make one BGL with all the bits in it including this data. I also think that the "SCENERY.DAT files inserted into the scenery owner folders, may contain the results of FS's own scan and probably give a short-cut way into the data. There again, the format changed between FS2002 and FS2004 I think, but I don't know either of them in any case. I know there are already a number of programs around which do need and use airport data from FS's installed BGLs, so someone should be able to help you further should you need it. Regards, Pete

This is the wrong place, as explained in the Sticky thread above (which you missed perhaps?) "Application for FSUIPC PRogram Access Keys" You need to write to me by email, as stated there. First, however, it would be a good idea to get the FSUIPC SDK and check the Access Registration document you will find inside. Section 4 onwards is relevant. Then you can email me the details I need to make you a key, and also prepare to build in automatic access (far less troublesome than asking your users to key thing in). Regards, Pete

Well, Active Camera has nothing to do with FSUIPC, it is another add-on altogether. The problem it may have with FS9.1 is published in the read me for FS9.1 and, indeed, on Microsoft's web site where you got the patch. I really don't think FSUIPC can have anything to do with the problem you are having either. Maybe the patch didn't install correctly. You can check that all the correct FS9.1 DLLs are installed -- I have added a list of those changed by the Install to my FS Update announcement at the top of this Forum. If you are going to try reinstalling the patch, run the FS9UpdateUninstall program you'll find in the FS folder, then delete the BACKUP folder -- but don't do the latter first or you'll probably end up having to reinstall FS altogether. Regards, Pete

Ahwhat is probably happening there is that the last value seen on that axis was 0, and only changes are actioned, so sending it a 0 again didn't work. I should have thought of that. 1000 will be close to idle, and maybe you've calibrated enough of a null zone to make it equivalent to idle in any case. Well done! Good flying now! Regards, Pete

I think something you've installed, probably a video driver, but perhaps an application, has replaced one of the standard system libraries with an older version, or one not 100% compatible with your version of Windows, or at least other libraries. Dialogues like the options in FSUIPC are not sized in absolute terms in the application, but in ways which allows the library to scale them to suit whatever screen resolution, font sizes and other differences there may be. The odd thing noticeable here is that the row of Tabs at the top is correctly scaled to fit the window size, but the standard dialogue part inside is not. Probably one is handled by routines in one library and the other (being simple standard old-fashioned dialogues) is handled in another, and the two you have installed aren't compatible. The thing now, though is to identify them and see how you can re-install. The most likely library is one called COMCTL32.DLL. This is used to actually create the overall window (called a "Property Sheet"). Find that file in your Windows folders -- for Win2K and WinXP is should be in the windows\system32 folder. Check the version and date, and maybe try re-installing it (you'll probably need to get Windows to do that for you as it may be in use all the time). I am using WinXP Pro, SP1 (not dared install SP2 yet!), and my COMCTL32.DLL is Version 5.82.2800.1106, 29th August 2002. I have Win98SE on an older PC and that has COMCTL32.DLL in its Windows\System folder, version 5.81, also 29th August 2002. Both work fine. I am using nVidia drivers in both, completely different versions however. You could also try to use Windows System File Checker. In Win98 this is by using Start-Run and entering SFC. That program also provides the way to reinstall a selected file which may be your best bet. On WinXP, SFC seems to be a DOS program which needs command line parameters, and I can't see it providing the same service, so I'm not sure what you do. If you are using WinXP then maybe Katy Pluta over in the FS2004 Forum can tell you how to sort it out. She is a good Windows expert. Good luck! Regards, Pete

Please calm down. It does no one any good talking like that. Hmm. You didn't bother to read the Microsoft website notes, or the Read Me text which Microsoft provided and displayed at the end of the update? What do you mean "when i go to the website for it it just opens up a bunch of files with little programs like wide fs but there demos"? NONE of my programs ever came as or with demos! There are NO DEMOS of my software, none at all! Why do you think this? The file you want is called FSUIPC.ZIP. Download it, then take FSUIPC.DLL out of the Zip and put it in your FS modules folder. There, that's it. What's so hard about that? If you don't use FSUIPC and don't want it, just delete the FSUIPC.DLL file from your Modules folder. However, since it is already there I assume something you've added has installed it, so it may still be needed. Regards, Pete

What's being a young 58 year old got to do with it? I'm 61. :wink: There was nothing technical at all about what I said, so which bits didn't you understand? All I can try is to puit the same words in a different order, will that do? Here goes: I don't know what the error is in Active Camera, but ithe symptoms of NOT updating it for FS9.1 seem rather similar to those you describe. There are threads about it in the FS2004 forum. I really don't know how else to explain it. I have no other ideas about anything else which can cause what you are seeing. This is why I suggested to look at forums where they are reported. If you don't use Active Camera then you will probably need to start looking at other add-ons or possible driver problems. You said some other stuff I didn't comment on because I didn't understand it: viz What does a "file with 9.1.9.40901 underneath" mean? I cannot picture that at all. (BTW, you cannot duplicate files in a folder, Windows only allows one of each filename). And why are you "annoyed" at me and blaming FSUIPC? Have you any grounds for this. Quite honestly I don't see any connection between you loading a flight and it going wrong, and FSUIPC. Can you elaborate on that for me? I get the blame for many things, but it seems better when at least someone can offer a reason, however slight it may be. Okay? :wink: Thanks, Regards, Pete

I know nothing about USB. Those things I have plugged into USB stay plugged in. Why would you keep moving them? Luckily I also still have REAL serial ports, so I can use those too. Maybe, if you unplug ALL your USB stuff, then boot with only the PFC gear, get that onto its "first available COM", then connect all the things wihch you like swapping about a lot, it will stay put? If there was a way to automatically identify where the PFC gear is connected then I would find it for you, but it isn't a real USB device, and it has no identifying signal. Also, playing about with all the COM ports I can find can cause problems with modems and other types of gear folks may connect. Incidentally Win98 was much worse. I think it might have assigned different things to each USB connection each time it was booted! Maybe Katy Pluta over in the FS2004 forum can help. She is a good WinXP expert. This is really more of a Windows question I think. Regards, Pete

You are making two BIG erros. 1. WidevieW is a program by Luciano Napolitano. It is nothing to do with me, and is not supported on this Forum. You are completely in the wrong place! 2. WidevieW is for linking multiple networked PCs running FS. To do what you want to do you simply create windows in FS and undock them. There is no additional program involved whatsoever. Regards, Pete