Pete Dowson

It's info obtained from the Registry. you'd need to use the Registry access API calls. Check these keys in HKCU or HKLM SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\ for names, and SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\ for GUIDs. it's not simple. Pete

That's the WideServer.INI file.("configuration settings". It is called wideSever.log. If there is no such file then WideServer hasn't been run. Did you install it at all? Okay. So it looks like you don't have the Server installed at all. Regards Pete

LogS? You only showed tnly the WideClient log -- the WideServer log would laso help as it it half of the connectin! Is that really the IP address of your FS PC? The 192.168 part looks okay, but I'm not so sure about that 178. Please check. If you know the correct IP address it may be better to enter both the Protocol= and ServerIPAddr= ... parameters in your WideClient.INI file. Pete

Not in the INI. Run FSX, go to FSUIPC options, select Axes assignments, and assign the hat to "pan view". Pete

There isn't any 'cfg' file. All FSUIPC settings are stored in its INI file, which is in the FS modules folder next to FSUIPC itself, unless you are using FS9 on Vista or Win7/8 and have not set FS9 to run in XP compatibility mode. Then you'd probably find it in the FS files folder in your documents -- this is because of Vista/7/8 restrictions. Pete

You can have a Lua which loads Luas by whatever criteria you need to apply. Or simply have the other Luas set some Global variable which the unwanted one tests for and terminates, or just goes quiescent. But best is to not use a generic [Auto] section at all and simply load whatever you want for every Profile -- just always have a Profile, even if "default". It doesn't need to have all the other things in it, like buttons, calibrations, etc. Pete

If you turned it off and "okayed" out of the options, there's no way it gets turned on again unless you have some program forcing it on. No, sorry. But I can't really read pictures like that. All the settings are recorded in the INI file, so it is more productive to paste that here rather than take such rather yucky pictures! Pete

I don't believe that VB prevents you making an array sufficient to hold two values like that! If VB cannot support arrays it isn't a proper programming language! Use a 64-bit variable instead. It is much much easier. How it is addressed in your version of VB I don't know, but see http://www.aivosto.com/vbtips/datatypes.html Regards Pete

i've no idea what is causing that, but try QNH smoothing in FSUIPC. Pete

No, it is entirely automatic. It sounds like you are using a VERY old version! Current version for FS9 is 3.999z. Pete

Sorry, I don't know. You'll need to raise this with SimMarket. I don't handle any of that stuff. I always thought that offer ended years ago. Raise a problem ticket. Regards Pete

No. There's nothing in common between them. Pete

Check the options. Doesn't ASE provide you with a "direct wind control" (DWC) option? That invokes global mode. Oh, wait a minute. I'm not sure that applies to FS9. It was added into FSX's facilities by Microsoft on my request, because contrlling the weather accurately and consistently in FS9 was virtually impossible. So I'm now thinking you are stuck until you move on to FSX or P3D. Regards Pete

A white screen? Never seen one of those. What else does it say apart from "fatal error"? What was your previous version of FSUIPC? Can you look in the Windows error log and get the crah information, please. I need the module name, the offset address and the error code. You can get to the error log by entering 2event viewer" in the Start-Run box and pressing Enter. Look in the Windows logs, application logs. You appended a log showing that FSUIPC is actually loading and starting, so you shouldn't use the Loader, and it isn't thge usual problem with SimConnect load checking. Judging from how far the log has reached I would guess that it is a weather file corruption (WX file). FSUIPC always reads weather through SimConnect and corrupted WX files, which can arise from a previous crash, can do nasty things to SimConnect's weather interface. Go into this folder: C:\Users\Dave\Documents\flight simulator x files\ and see if removing or renaming the file named Lauda air @ gate 548 Default.wx helps. Also, make sure the file IFR Heathrow to Stevens Anchorage Intl.PLN is okay, because that's the last thing loaded before the log ends. Pete

I think it is, then, an inevitable result of the weather refreshing action. i haven't used FS9 for about 7 years, so I can't really advise further. Can't you run ASE in global mode ("DWC" I think they call it). You've really narrowed it down to the weaknesses of FS9's weather engine. You can try running FSUIPC without ActiveSky, and ActiveSky without FSUIPC, but I don't think you'll have the weather control you want. All you've really concluded is that changing the weather makes FS9 flicker. Seems that the increased flicker rate in ASE compared with 6.5 has merely made you aware of something you possibly didn't particularly notice before. All FSUIPC is doing here is allowing ActiveSky to set the weather. I really don't know any other way to tell you this. Regards Pete

Ah, sorry, I missed the point that it is contnuously switching. That can only be because you have the button press action set to repeat whilst held! NEVER use that option for a toggle switch, it is only intended for a momentary button, obviously. It's absolutely NOT necessary to even look at the INI file!! You simply ASSIGN, in FSUIPC options, to the "Offset Word SetBits" or "Offset Word ClearBits" commands in the drop down list, then enter xD0C for the Offset part, which you will then immediately see, and the value for the switch in the Parameter field. For that value you only need to convert the Bit Number listed in the Offsets document to a decimal value -- 1 for bit 0, 2 for bit 1, 4 for bit 2 and so on (multiply by 2 each time -- for a guide on bits and bytes and numbers, please see the FAQ subforum). I don't really understand why you get defeated by something so easy? It is my English which isn't clear? Pete

~Oops. No network, no possibility of using WideFS for its intended purpose! Pete

There is nothing in FSUIPC which knows anything about the screen, and certainly nothing in it which could cause flicker. All it is doing is acting as a conduit for the weather commands from Active Sky. Sorry, I'm now confused. Are you saying it's okay with 6.5 but not ASE? Since the weather interface is identical (it is just FSUIPC) then the difference must be in what ASE is doing compared to 6.5. Certainly HiFi would be the ones to identify that. It sounds like you really need to find ASE settings which make it behave more like 6.5. Regards Pete

Okay. Do you have a working network between the two PCs? Are they both running the same version of Windows? Do you have a firewall set up which could block things? Don't forget Windows by default will set up its firewall. An old timer being what, 70, like me, or older? There's no point in running WideFS then. Neither of those use FSUIPC, and all WideFS is doing for you, when it connects, is providing an extension to the FSUIPC interface on your Client PC. What are you hoping to do on that PC? Why did you buy WideFS if you have no add-ons capable of using it? Regards Pete

Yes. FS uses normal ASCII encoding with is an 8 bit = 1 byte code per character. Pete

Why on Earth are you offering such an opinion on a thread which has been dead for nearly a year? Are you going to go and review and criticise all my contributions here over the many years I've been here? What exactly is the purpose? Just to raise my blood pressure? Don't you realise how such comments as "lighten up" affect folks? Are you so insensitive? I am 70 this year and really could do without such pressure over irrelevant matters from folks who seem to have some agenda just to stir things up. If you have a proper contibution to make, then make it. Otherwise you really aren't welcome. Pete

Ah, the multiplication of wind layers at silly small height differences is the problem I found when FSUIPC was set to update weather via its filters. This is why that is defaulted off and warnings are provided about it. The filtering was intended to operate by reading the weather, making changes, and writing it back. Alas, no way this works well with this problem occurring. I do have algorithms in place which tries to combat this by deleting the spurious layers. One of the problems is that the total size of the METAR string eventually goes beyond the SimConnect limit of 2048 bytes, after which crashes occur in the SimConnect interface. FSUIPC records this size problem. Have you tried setting weather the other way around, distant stations first, local ones last? Pete

The weather is dynamic in any case, irrespective of the change rate setting. After all, if there is any wind at all, things have to change, to move. That's what wind is -- an equalisation of pressures. And clouds move with the wind. However, disappearing cloud layers is something I've seen reported but not really noticed myself. I can understand them moving away in favour of an area with less layers from the other direction, and maybe they can "dissolve" if the temperature/dew point setting for the layer they are in dictates a dry air situation. But simply getting lost for no good reason doesn't make sense to me, and isn't something I've seen. If this is in an area with quite a few weather stations close to each other, like around Chicago and some parts of California, I would tend to think it due to conflicts btween those nearby stations, being resolved. I doubt that the range is relevant to this issue. There are a lot of bugs in the FSX weather engine, as there was in FS9's for that matter. This is why the more successful weather programs now choose to use Global mode -- making the weather the same everywhere -- and adjusting it dynamically by program. This solves a lot of these sorts of problems and certainly eliminates interpolation errors. Of course for ATIS reports on destination airports it means things are wrng -- the weatrher reports really then need to either be obtained from the same source as the weather setting program, or from that program itself. This is what I do with Active Sky -- you can either read its weather file or use the direct interface it has supported since ASE. Regards Pete

"work it"? You don't "work it". Do you mean WideClient, on your client PC? Is it linked on a Network to your FSX PC? Have you started FSX? What "fancy boxes" in which Manual? There aren't any "fancy boxes" associated wth WideFS. It usually operates invisibly, or nearly so, behind the scenes, simply linking your FSUIPC application add-ons on your Client PC to FSX on your FS PC. What did you buy WideFS for? What programs are you wanting to run on your Client PC? Pete

It is acting as a digital (on/off) device. This is a well known bug in Saitek's driver installation which is fixed by a small change in the Registry. You'll need to go to the Saitek support forum to find the details. It is software in the sense it is the installation of their driver which goes wrong, and they should know that. The answer is somewhere in their support Forum as others can attest to. I think it dates back to before MadCatz took over Saitek. They've been poor since then. Regards Pete