Pete Dowson

Okay. They've not arrived yet. I'll have a look later. Maybe tomorrow now. One wonders where they get the "ambitent wind" data from, then, as the values in Shift+Z always correspond to the SimConnect variables for these two settings. All three aircraft, or are you back to only the PMDG now? That's not the point. Turbulence, variablility and gusts could be part of what is being set as part of "real" ASX weather. There are facilities to suppress all this in FSUIPC's wind options. Regards Pete

Got them. In your email you said: I'm not surprised. You have the aircraft on the ground and the surface level wind (up to 2995 feet) is set for Turbulence at level 2 (moderate) AND on top of that a directional variability of 60 degrees! How do you think it should behave? Are you sure it is excessive? I might be looking at tuning it further, but you seem to think you should get no effects whatsoever. Should the effects be half as much, or more, or less? In my experiments they seemed reasonably, but probably I didn't test combinations of disturbances such as you have set here. BTW optionally FSUIPC can be asked to suppress both Turbulence and Gusts (see the Winds option page). Variability is also suppressed if you suppress turbulence. Regards Pete

As with all my packages, the documentation is included in the full official release ZIP file which you presumably must have downloaded from http://www.schiratti.com/dowson. The details about configuring PTT buttons are in a section in the WideFS Technical document. Pete

Can't you program it in FSUIPC at the same time as having the original action in GF's software, or doesn't that work? Sorry, I have no GF stuff now so I don't know. Normally it is up to the user to make sure he's not assigning stuff twice. In this case you actually want to. Pete

Maybe this is because FSUIPC alone cannot do it. It is a WideFS function, and has its own section in the WideFs documentation. FSUIPC itself can only perform things on the local FS PC, it runs inside FS. Pete

At the time this was happening were there additional wind or cloud settings like turbulence, variability or gusts? Without knowing what was supposed to be set I can't really do much with such a report. It is possible that the simulation I've added for these phenomena is not quite right, but I cannot really adjust them without knowing what is happening. If you cannot use WeatherSet2 or similar to check the wind and cloud at the aircraft altitude, and see if these things are set, then the next best thing would be to save a flight so I can check, as suggested in my previous message in this thread. Regards Pete

I've now checked this. The "Attitude Hold" mode isn't turned on at all. I can't find any way to detect the DC3's attitude hold mode. The only A/P detection I can see if A/P master and Heading Hold, both operating together with the "on/off" switch. I think the only way for you to operate the trim disconnection is to program a button or key to do it. In fact you could, by editing the INI file, combine switching the AP with disconnecting the trim axis. Just have multiple assignments to the same button or keypress (you can't do that without altering the INI). The control to use to do it by a button or keypress will be one of Offset Byte ToggleBits (to toggle) or Offset Byte SetBits (to disconnect trim) or Offset Byte ClrBits (to reconnect trim) with the Offset set to x310A and the Parameter set to 32 (0r x20). Regards Pete

Aha! There's the reason -- currently I don't look at "attitude hold" because it didn't work in FS9 or before. I'll add the check for that (and "vertical speed hold" which I don't think works, but maybe it might ...). This change will be in the next incremental release, 4.218, probably tomorrow or Friday. Look for it in the FSX Downloads. I'll leave this to you for testing if I may (I'm a bit lost in the DC3), so please let me know. Regards Pete

You have an analogue trim wheel assigned how and where, please? This user facility only operates when the A/P is in a vertical control mode -- i.e. Altitude hold or Glideslope hold. (There is another mode, "attitude hold" which probably should be applied too -- this was never operable in FS9 or before, but maybe it is in FSX?). Since the A/P won't be manipulating the elevator or trim in other modes they don't matter -- you still need control of the trim axis. I'll check now ... ... OK, I give up. Where's the DC-3 A/P? How are you enabling any vertical hold mode? Regards Pete

Did you check the actual instated weather, via WeatherSet2 for example, to see if this was due to simulated turbulence, variability or gusting? I really need information on any such reports because it might just be doing what it thinks it ought to given the input values. If you don't want to look at these things, could you please save a flight at that time and ZIP the FLT+FSSAVE+WX files for me (to petedowson@btconnect.com -- but don't move this thread to there! ;-) ) so I can look at the weather which was set myself. Maybe my simulation needs a little adjustment, but I cannot tell from these reports as there's no information about what should be going on. It would be nice also to know what other wind and cloud options you have set in FSUIPC (so maybe also include your FSUIPC4.INI file please). Regards Pete

Oh, lovely! I'm so glad you got yourself all sorted. Well done! Regards Pete

Joystick axes have never been supported through WideFS. Where did you get an idea they were? I really don't think it is worthwhile. For flight controls the latency is just too annoying. It is always far better to connect axes direct to the FS PC. There is nothing at all to be gained from client axes. Regards Pete

I'm waiting for a reply from PMDG first. I'd like to know what is going on. Are you sure it isn't related to my simulated turbulence or variance or gusts? Can you use WeatherSet2 or similar to view the weather settings when you get this -- see if turbulence, variance or gusts are set for the level you are at? You could try suppressing them in any case, as a test. Maybe my simulation isn't good? In the wind smoothing on FS9 I just smoothed it outright, but this has the unwanted side effect or removing turbulence et cetera, so i thought I was being clever adding it back in using my own algorithms, but maybe they are not so good? [LATER] Oh, check for turbulence in any cloud layer said to be close to the aircraft altitude too. I try to simulate that as well! Regards Pete

"It" in this case is a COM port? Sorry, I have no idea what the "Lowrance 1000 emulator" is, or whether it accepts any inputs from a COM port at all. But first things first. You do need to check which pair of COM ports are being emulated by MixW. Have you done that? What pair is it emulating? And of course you need to set parameters in the Wideclient.INI file to enable GPS reception there and to tell it which MixW port to use there. have you done that? Regards Pete

Okay. That's odd. I'll write to my contact in PMDG and ask him about that. It looks like I'll need to document the warning that you can't use FSUIPC4 wind smoothing with PMDG aircraft ! Shame. Well, it took me 100's of hours of hacking to develop this solution, which basically is the same as it was in FS9 -- the time was in finding the same variables. I don't think it is very likely that I'll find a way that suits whatever PMDG have done with their autopilot. I'll have to ask them. Pete

Please test with the wind smoothing turned off then, and let me know. The variables being controlled in FSUIPC4 for wind smoothing are similar to those in FSUIPC3, where PMDG aircraft worked fine, so I can only assume they've changed their methods significantly if what your saying is down to this. If this is what is happening it looks like PMDG users will have to do without wind smoothing, but I would really surprise me, so please also test with your joystick/yoke disabled. And did you miss all the increments between 4.200 and 4.217? There's been a large number of changes! Pete

Not that I know of. What was the previous version of FSUIP4 you were using? I don't think PMDG use anything in FSUIPC for their autopilot these days. It is all done via SimConnect directly I think. Could it be due to the way you have your joystick configured or assigned? Regards Pete

The interface to be used has not changed since FS98. It has been extended, but not changed. After all the whole point of FSUIPC is ongoing compatibility. That is why it exists. There are some updated files in the FSX Downloads announcement above, including FSX-specific data about the values which can be obtained. Sorry, no. The examples and so on in the SDK should be sufficient. It is all trivial compared to your task of sending it all to another program over a Network and then collating it all that end. Pete

WideFS allows you to access all those FS values from any PC on your network (provided it is running Windows 98 or later and not running FS at all) through the FSUIPC interface, which is documented in the FSUIPC SDK. WideFS does not have anything whatsoever to do with multiple FS installations on different PCs. If you want to collect information separately from each PC running FS you can write a program to do this, interfacing to FSUIPC on each one, and attend to the sending and collection of it in whatever way you like. WideFS cannot help you with this. Regards Pete

Another way to check whether it is a rogue joystick driver is to download the latest interim version of FSUIPC3 (3.777) from the "Other Downloads" Announcement above, install it into the Modules folder, then edit your FSUIPC.INI file by adding PollInterval=0 to the [buttons] section. If you have no [buttons] section add [buttons] PollInterval=0 This will stop FSUIPC looking for button presses altogether, just as a test to see if this is the cause. Regards Pete

When you uninstalled it, did you delete the My Documents\Flight Simulator Files folder and the Documents and Setting\\Application Data\Microsoft\FSX folders? For if you didn't you did not remove the main parts which contain data about FS9 and its behaviour. When it was uninstalled, did you check there was nothing left it its folders? For its uninstaller only removes what IT installed, not what you may have since added. I don't think any of that makes any difference at all. The registry doesn't come ito it. Why have you gone back to an unsupported version of FSUIPC? I cannot help in any case with old versions. Without deleting the files which are possibly causing this it isn't so surprising. Sorry. It still could be a file you are creating based on a previous "default" which was bad. Are you now absolutely sure there are no add-ons at all apart from FSUIPC? You left nothing else added in the Modules folder, nor any aircraft or gauges added. Just the basic FS9? If so then it has to be a bad joystick driver I think Please, in Windows, look at the Game Controller. See if it lists any joystick type devices you no longer have connected. Also run the attached program, "Joyview" and check in each of its section to see if there is any device which you aren't aware of. Also, in case there really is some access by another add-on, add LogReads=Yes LogWrites=Yes to the [General] section. Then try again. Show me the log please. Regards Pete joyview.zip

Aha! That's what we thought at the beginning! :roll: Glad you have it sorted now. :D Pete

It will say that until you have the Server operating -- i.e. FS running and ready to fly. Where's the comparable WideServer log? The same as before. At least these are both consistent. They both say the FS PC is either not running FS + WideServer, or it is not in the same Network. There never is any "wideserver.txt" file anyway (nor a WideClient.txt on the client). The files you want are LOG files. If you do really mean there is no WideServer log file, what on Earth happened to the one you showed me earlier? Did you delete it? And each time you run it it saves the last log too, as WideServer1.log. If no WideServer.Log is being produced when you run FS + FSUIPC4 with WideFS enabled, then WideServer is most certainly not running at all. Please double check. Is there even an FSUIPC4.Log file? If not then FSUIPC4 isn't running either. You seem to have stopped making any sense! If WideServer is running in FSX the title bar of FSX (in Windowed mode) will say so, and will say either that it is waiting for clients or will say how many clients are connected. Everything in this latest message of yours points to a total absence of FSX running or WideFS being enabled in it. This could go on forever if you keep going backwards. :-( Pete

But surely you will be using that on the Client in any case? What's the point of having it on the same PC as FSX? Sorry, you'll have to be much more specific as to the names of the controls you are using. there are so many similarly named in FS. Write down the actual names. Calibration? Where are you looking? there's no "calibration" for buttons. you either assign actions to them or not, same as in FS's own Assignments. Regards Pete

Well, the WideServer log, yes. And that shows things okay too, excepting of course it never sees the Client (I assume you DID try to run the client during the 5 minutes this FSX session was running? If not it might be a good idea to try again and then show me the log). What does this mean? Sorry im so confused lol :roll: . You need both PCs to be in the same WorkGroup so they can work together. "WorkGroup" = "group for working together". Your WorkGroup name is set in the computer properties -- on Windows XP, right-click on "My Computer" and select Properties then Computer Name. You'll see it. To change it click the "Change" button. For Vista it is somewhere similar I believe. Well, it would have helped to show the WideClient log from that attempt too, just so i can make sure the broadcasts from the FS PC are getting through. Please, whenever changing anything,, show BOTH logs, each time. If it isn't due to having the PCs in separate WorkGroups, then it must be a firewall problem. Regards Pete