Pete Dowson

I don't know much about these things, but I think programs need you to have admin rights to be able to change the registry, or do much installing in certain places. I think even having FS in its default place (in "Program Files") can present problems unless you have Admin rights. If you are the only user and haven't restricted your access deliberately, it sounds like something has. Best ask over in the FS2004 forum. Katy Pluta visits there occasionally, and knows a darn sight more about these things than I. Regards, Pete

No. In the US most if not all of those beginning with K do, but a lot of the lottle ones don't. World-Wide it varies. There's a list in the Weather folder. How did I prove that? By saying, as you just repeated again, that "FS stores a "base" elevation in this area as, for example, 600' MSL. With a surface wind layer altitude set to 1000', this will result in a surface wind layer of 1600' MSL. Whether I'm over a mountain, a low point in the valley, or a high point in the valley, the surface wind layer altitude stays at 1600' MSL." Since 0B4C is the ground altitude beneath the aircraft, not this strange "base altitude" you've found, how can both statements "0B4C + 0EEE" give the wind altitude AND "Whether I'm over a mountain, a low point in the valley, or a high point in the valley, the surface wind layer altitude stays at 1600' MSL." actually be true at the same time? They appear to contradict each other. Exactly. You've said it again. And 0B4C is therefore changing all the time. If 0EEE + base (600) always = 1600 .... well, I surely don't need to go further? Oh, you are saying the 0EEE changes all the time tooAh, that's different. Sorry, that changes everything. But in that case .... where does this base altitude of 600 come into it? I'm now even more confused. :-( Anyway, at this stage, three full years after FS2004 and FSUIPC3 were released, I can really do no more than document this for anyone still concerned with FS2004 after FSX comes out. Incidentally, some checks with FS98, FS2000 and FS2002 are necessary really, to see when and what changed where. Thanks! Pete

What does the FSUIPC Log file show please? All the details are in there. Pete

Very good! Thanks for letting me know! Regards Pete

You cannot insult me by asking straight-forward questions ;-), But I am sorry, I am really too busy to take on additional work. I am actually hoping to reduce my workload so I can do some flying one day! If you want a programmer to help you write software for your cockpit, though, I certainly think that you may find others here, in my Support Forum, who might be interested, especially if it means getting their hands on some nice cockpit hardware. I suggest you word out your plans, in as much detail as you can without revealing anything you shouldn't, or committing yourself to anything you can't keep to, and post again. I could make such a post 'sticky' for a while, if you like, to keep it near the top. You should also consider the same in the cockpit builder's Forum, near here, and possibly in Project Magenta's support site. Have you also thought about the possibility of talk to PM's Enrico Schiratti, who currently does support a variety of advanced cockpits with his software? Good luck! Regards, Pete

Erno it wasn't. The first message, just above, contains only this: This seems to assume some earlier messages in the thread, but there are none. Maybe you started a new thread by mistake? Oh, that problem. Right ... Erwhy the "?" on "outside window". The window that shows the outside -- the scenery, the view through the front window? How have you hidden the menu bar if you've never found out about the right-click menu? You can edit the FSUIPC.KEY file (in the FS Modules folder). Just add a line in the [Programs] section (add that line too if it isn't there). The registration line to add is =KEY For example squawkthing=ABCDEFG12345 No spaces, just the name and the key as listed in the Freeware keys list. But please do try to unhide the menu -- I can't understand how you can possibly not know about that FS facility? Regards, Pete

If they are short enough, just, show them here. Otherwise ZIP them, with your INI files too, and send them to me at petedowson@btconnect.com. Pete

What "DrWatson" log? It is the FSUIPC Log that is relevant, and that is in the FS modules folder. It is a plain text file, you can look at it and show bits here. In any case, if your only problem is access permission, please use the freeware key provided -- check the announcements/stickies at the top of the forum. Pete

Described before where? This is the first message in this thread!! This simply means that you have failed to enter the Key to allow Squawkbox to talk to FSUIPC. See the Freeware keys list above, and refer to the FSUIPC user guide for how to enter it. Pete

I might be able to help, but I need to see the Logs. Why are you so reluctant to provide the information to help? There is absolutely no point in reverting to old versions, they really will NOT make any difference if you have a Network problem. And you will never get any further help from me if you don't keep to latest versions. So, please just do yourself a big favour and help me help you. Pete

No. FSUIPC is entirely irrelevant. it has no bearing whatsoever on your Network. In WideFS there have been no changes to the Network protocol actions in a very long time, only the addition of UDP support a few months ago. If you aren't going to show me any logs I cannot help. If you don't want to use supported version I cannot support you. Please re-consider. Pete

As I said, let me see the logs. Something is wrong with your Network. Pete

Sorry, but I only speak English, C and ASM. Perhpas someone else will be able to help? Normally nothing needs changing or entering at all, expecially if both systems are running Win2000 or WinXP. This is with the current version I notice that now, in this message, you have changed your story. Originally you were only saying that the PTT didn't work at all. Now it is far worse! ... This sounds most definitely like a Network problem. This is NOTHING like a "failure of PTT" you originaly reported. What has changed? I cannot with no information. ALL information about what is happening in WideFS is provided in the LOG files. Please show me the WideClient LOG and the WideServer LOG files. PLEASE DO NOT MESS ABOUT WITH THE INI FILES! Pete

Hmm. Everywhere? Did you try looking in the FSUIPC user guide at all? I do't know if you are a Registered user or not, but it is possible either way. This part of the section "Message Window Options" is relevant (it's about the 7th para): Pete

Please update. that is very old. Current version is 3.70. There's no sensitivity adjustments as such in FSUIPC. For that sort of thing go to FS's menus -- Options, Controls. FSUIPC does offer a response adjustment for axes calibrated in its "Joystick Calibrations" section. It is all fully documented -- you can choose between settings with difference amounts of flattened (lessened) centre responses. It is done with a graphic showing you the response curve. There are pictures in the User Guide, even, please take a look. I don't know the aircraft you are using, so I have no idea if these facilities will truly help. Regards, Pete

Ah, so it is in 100ths. FS will be scaling it then, on the input side. Thanks for the info. It is stil really only a bunch of 8 buttons! ;-) Pete

Okay, the logs show that the connection of the Hat to FS in this was generates exactly the same sort of controls you are doing with the assignments to PAN_VIEW with the parameters 0, 45, 90 and so on. I think that if you enabled Repeat whilst held then the results should be indistiguishable. The DLL itself cannot be patched or changed internally with causing failures when it is run. It is protected against hacking, if that's what you mean. With FS2004 and before it cannot be stopped from loading by FS even if it is hacked -- I think that is likely to be changed in FSX though. If you merely mean to stop another installer installing an older version, well, you could try making it read-only in Explorer. but programs can remove that attribute in any case. If you are frequently installing such packages with bad installers like that I would recommend that you simply right-click on the FSUIPC.DL after each installation and check Propeties Version. Obviously dong this 10 times an hour wouldn't be convenient, but i wouldn't think you were installing or re-installing packages so often unless you are in a shop demonstating such processes. It's just a little free-standing utility originally provided by Thrustmaster for checking their joysticks. Anyway I don't think you need to use it now. The logs show everything. The Hat is NOT a continuous axis providing values 0-360, so it doesn't really justify axis treatment. It is merely 8 buttons with a common "off" position. I think the provisions in FS and FSUIPC are fine. I think the log shows it can and does if you program the 8 positions using PAN_VIEW with parameters 0, 45,315 and enable repeat. Yes. You have a little more flexibility with FSUIPC in that you could even program the 'offs' differently, eg to choose to execute "VIEW_FORWARD" to return to a normal view, as you might wish. Regards Pete

Good! Just before you posted this I found the message here that I "dimly remembered", about why Broadcasts may not work. Here's the salient parts: Do you know if any of this applies in your case? Else i'm rather mystified as to why the Broadcasts weren't seen by your Client. Regards, Pete

Okay, the Logs show nothing but that the Client never ever sees a broadcast from the Server. With an all Win2000 or XP setup I think that's only possible if the PCs are on different subgroups (i.e. the subnet mask, often 255.255.255.0, when applied to the IP addresses of both PCs shows a difference) -- or there's a Firewall in the way. I do have a dim recollection of someone else who had a problem with broadcasts -- it may be worth a search through this forum to see if you can find something. Meanwhile, if you are sure your Firewall isn't in the way, you could avoid depending upon a Broadcast from the Server by using the normal Server and Protocol parameters in your Wideclient.INI. ServerName=FLIGHT Protocol=TCP I notice that you also have the IPX/SPX protocol installed on the Server: 18797 Initialising IPX/SPX server 18797 ServerNode=0.0.4608.38167.23325 Maybe you were using that before, thus getting around many of the TCP/IP restrictions? If so, and if you have IPX/SPX installed on the Client, try this in the Wideclient INI instead: ServerName=FLIGHT ServerNode=0.0.4608.38167.23325 Protocol=SPX Regards, Pete

Are you sure this is not simply the elevation of the Weather Station reporting that particular wind? FS2004 is different from previous versions in that there is NEVER a "global" weather setting -- no matter how the weather is set, it it local, controlled by the weather station locations. The problem arises is when away from the weather stations. Then the weather is derived from three WX stations via interpolation. What actually then happens to your AMSL/AGL for the surface wind I don't know. It is almost impossible to find out for sure unless you have loads of time and patience on your hands. Isn't there an airfield there with a weather station at 600'? But you just proved this was only true whilst over an area of terrain which happens to be at your "base altitude". That isn't relaible -- all those formulae do is assume it is TRULY AGL, using the terrain altitude as it changes. But I can't really believe that from what you've said in this very message! There's a consequent problem which you have (conveniently?) avoided by having no higher wind layers -- that is what happens to the next layer up (and so on) as the ground one "bulges" upwards over terrain to meet it or even overlap it. Does it simply disappear, or rise too? If the latter, are all of the upper wind altitudes AGL? I really don't think they can possibly be. Regards Pete

So the values are neither AMSL nor AGL. AGL must be related to the actual ground altitude below. if it isn';t you cannot compute the AMSL -- I'm afraid don't know what your local "base" elevation is now how to find it. This all sounds really horrible, and certainly a change from FS2002 and before. I don't know how to advise you to proceed. I shall certainly document the uncertainly of those values in the next SDK update. In FSUIPC it is the other way round. In FS2004 the NWI corresponds most closely to the information I can get out of FS. That information is then maped onto the older interfaces, like the NWI and those old FS98 vaslues you are looking at. So, if that's all you are looking at I don't thik you are gaining anything. How can you compute the AMSL -- where do you get this "base elevation" from? Regards, Pete

At first sight it looks like a firewall problem, which would affect WideFs but not Explorer. Try disabling WinXP's firewall (which is enabled by default since SP2), or at least giving permission for WideClient and FS9 to talk. Otherwise, please show me the WideServer and WideClient LOG and INI files. They will contain the first pointers. Pete

Sorry, I've no idea what you are talking about. This is the first message in a rather anonymously entitled thread, so there's no history at all! :-( That's the version number of the FS2004 original release, some three years ago. If you are using the FS9.1 update then the number will be later than that. It's actually "Dowson", not "Dawson", and none of my programs are downloadable from SimMarket at all. You can get them from http://www.schiratti.com/dowson, as always (for the last 10 years or more), and if it is FSUIPC you need there's only ever one supported and current, and the package for that is named FSUIPC.ZIP. It currently contains version 3.70 which works with both versions of FS2004, as well as FS2002 and FS2000. Regards, Pete

Yes -- but again easier to set in the on-line options. And really this is where I am still not following you, I'm afraid. If you want each of the 8 positions to give you one fixed 45 degree view, why not simply use the direct controls that give you those? i.e. the "VIEW FORWARD, VIEW FORWARD RIGHT, .... through to VIEW FORWARD LEFT controls? Those are made for the purpose. The same 66416 value (= PAN_VIEW) is there because that's what you assigned. FSUIPC isn't in the habit of ignoring what you ask for and putting its own ideas in place. Hats have a centre 'off' position -- when you release them they return -1. Please update to 3.70. I don't support old versions. Er .. for some reason you are logging IPC Reads. Why? The logs for reading C000 are from a Module you have installed which is reading the Weather data. It most definitely is NOT 3.65. There are three ways for checking version numbers: 1. Right click on the DLL, select Properties -- Version. 2. Run FS, go to FSUIPC options, look at the first Tab displayed. 3. After running FS, look at the first line in the Log. There's also a 4th but less reliable way, and that is to look at the User Guide in the Zip, first page. Either you downloaded the wrong version (your ISP probably hadn't updated its cache) or you have installed something since which has overwritten the later one. Probably because instead of checking the option to Log events you were logging IPC Reads, which are not relevant here at all! None of this is going to tell me how the Hat behaves. Please re-program it as a POV to do as you think you want it to in FS, delete (temporarily remove) your FSUIPC programming for it. Then enable both Axis and non-Axis Event logging in FSUIPC. Test all hat positions USING FS. It really isn't so useful programming FSUIPC and then showing me FSUIPC doing as you programmed. Nothing is actually learned that way (well, by me at least ), do you see? We need to know what it is doing in FS, not in FSUIPC! Didn't you ever look for JoyView? Regards, Pete

There would be little point unless the hat is providing continuous changes. If it is only giving 8 discrete values then it can be fully programmed already. Really? That has never been reported before, and certainly, years ago when I did have a joystick with a Hat I could obtain the 8 positions separately. I need to know what your hat is doing to achieve that, please. Where's the logging? That would likely be either because you assigned the wrong controls, or the right controls with the wrong parameters, or you have the FS CFG "pan_in_cockpit_mode" parameter set incorrectly for what you want to do. Because it is NOT an axis, not even for FS, it is a "POV", and the only POV support FSUIPC offers in as 8 buttons. I thought we went through this? You can assign parameters in the options, on screen. Why do you want the syntax (but, yes, it is in the Advanced Guide, and anyway you've already been using it, haven't you. You showed me in your previous message -- you just had 0's for all the parameter values). I really cannot help much without information about how your hat works. Did you not get any, not do any logging, or look for that Joyview program? Pete