Pete Dowson

Ahthere's something wrong with the Level D installation then, by the sound of it. If the computer is slowing and freezing then WideServer is too. WideServer cannot run if FS cannot run. They are limited to 22, but what are you getting with the level D? You just said the PC is slowing down and freezing. Surely it isn't maintaining 22 fps during those times? You aren't trying to say that WideServer is freezing the PC are you? Test without first. 1.8 seems very slow for processor speed with a complex aircraft such as the Level D. I assume you must have many features in FS2004 turned way down? Even my 3.4 GHz PC would struggle. Well, it's not quite the same as a Network printer, but it might be that the driver is doing something all the time across the link to the PC with the printer on it, so it would be a good idea to eliminate that possibility first. However, that would affect everything, not just the Level D aircraft -- there's no way the printer driver would know or care what aircraft you are loading. No, I've never heard of it being a problem. But we have no idea what you've changed to cause this except that you said the only thing you've changed was to install a printer. Therefore, logically, that's the first thing to check. However, uninstalling and re-installing the Level D aircraft seems like the logical next step after that to try, from what you've now said. Maybe something in that has got corrupted. Regards, Pete

No, the Server is seeing messages from the Client, it is the Client not seeing anything from the Server. That's why it says "Timed out response". The cause of the problem could actually be at either end. With only one client it is difficult to isolate -- with two it is easy because either both clients suffer or only one. The trouble is there are no errors being reported. It simply looks like the data is transferring okay Client to server, but not Server to Client. Something is stopping it. How do you mean? If you change aircraft it all springs to life? What sort of "general crash"? And we don't know that it's a Client problem. If there's only a problem when using the LDS 767, maybe it is taking too much of the FS processor and not letting WideServer run -- though I've never heard of such a thing before. What processor is it? What is your FS frame rate limiter set to? What are your frame rates? You said this started after you installed some driver -- for a printer? Try uninstalling or re-installing that. Was it a Network pronter by any cance? Regards, Pete

Well, apart from the documented conversion you need to apply to get them into degrees, yes, I think so. I don't know exactly what you really mean by "Earth - fixed - inertial reference frame", but I suspect you mean the attitude in FS's small and oddly-shaped universe (its Earth isn't a sphere nor a plane, remember, more a toroid if I remember rightly, with no poles). Anyway, in FS, the exact position and attitude of the aircraft at any time is given by the 6 values LLAPBH (Lat, Long, alt, Pitch, Bank, Heading) in the offsets 0560-0580. Please try using FSInterrogate, provided with the FSUIPC SDK. You can see these things actually changing in real time and therefore come to understand them quite quickly and thoroughly. Regards, Pete

This phenomenon is actually described in the documentation, and has been for years -- please see the section entitled "Running WideFS". I think the explanation starts in about paragraph 5. That's the Server log, which doesn't show a problem. It's the Client which is re-connecting, probably because it is timing out messages from the Server. Something is probably stopping them in the Server, but you need to look at the Client log to see what it says, first. Regards, Pete

Well, it's just the one I've been studying most and attempting to simulate thoroughly in my cockpit. A 737-700 to be specific. ;-) Sounds okay, but you'd have to logically 'or' the multiple conditions. And of course the indication wouldn't necessarily tell you everything was okay because if one Hyd system is down some things wouldn't work. Well in the default FS aircraft it does because it doesn't simulate the subsystem very much -- the cockpits don't have the switches. In my cockpit I have the four switches -- Electric and Engine pumps for system A and system B. Certainly you get no pressure if no pumps are on. But there are no pumps or switches in FS itself, only in add-ons. There's a reservoir for each system, including the standby, so you do still get some hydraulic pressure for a while after the engines are switched off, but I assume it will decrease quite rapidly if you actually try using anything. You have to take care not to switch on System A pumps even with engines off before pushback, because the nose wheel steering could become activated with remaining pressure, and that could be dangerous for both equipment and groundcrew -- pushback needs a "loose" nosewheel. Same goes for flaps and things moving when there are groundcrew around. Regards, Pete

They mean pretty much what they say as far as I know -- the angle to be indicated on the FD and AI insttruments. No, only to show what the stated aircraft instruments show! If you want to indicate the attitude to fly manually to follow the VNAV/LNAV path set for the AutoPilot, use the FD values -- that's what the Flight Director is for, to help the pilot fly the plane. If you want to make an Attitude Indicator use the Attitude Indicator values. If you want the current true attitude use the true attitude variables available elsewhere -- there can easily be a difference between the actual current attitude and the attitude indicated on the AI. It's to do with momentum and other effects, as well as power and vaccum systems availability. Pete

Answered in your private duplicate. Pete

Please see the PFC DLL documentation! In the section entitled Button Assignments (in PFC options) you'll find it listed in the table as "PTT Roger Wilco (local)". For SB3 running on a WideFS client use the one below that instead, and edit the WideClient INI file to suit, as described in the WideFS documentation. What does "unlocked" mean in this context? If you cannot achieve full reverse then you have not calibrated correctly. Always leave a little bit of slack at BOTH ends of the lever movement when clicking the buttons in FSUIPC to tell it where the minimum and maximum points are -- all these devices are subject to variation (heat, humidity, physical variations), and if you don't "waste" a little of the movement at the extremes the minimum and maximum values you achieve will vary every time. Regards, Pete

In an airliner I am pretty sure there are always at least two hydraulic systems, powered by separate engine-driven pumps and/or electric pumps, with the latter powered by different electric subsystems / generators. For example, in the 737's Hyd. Engine 2 pump and Hyd Elec 1 pump power Hyd. system B, and Hyd. Engine 1 pump and Hyd Elec 2 pump power Hyd. system A. This cross-over system allows two separate original sources for each system, as a failsafe. In normal configuration the hydraulic needs in the 737NG series are shared as follows: Alt Brakes, Left Flight Spoilers, Ground spoilers, Landing gear, Nose wheel steering, A/P A -- System A Nml Brakes, Autoslats, Autobrake, Right flight spoilers, Flaps, Yaw damper, A/P B -- System B Rudder, Ailerons, Elevator and "elevator feel" -- Both A and B. There is also a standby hydraulic reservoir and associated system which I won't go into here. For 737 stuff see http://www.b737.org.uk/index.htm. It doesn't really do a lot of the sub-system simulation -- I use pmSystems and program it there. But all this is, of course, very aircraft specific. I expect some of the more sophisticated models like the PMDG 737NG and the LDS 767 simulate this stuff very well. But I think you are mistaken about the hydraulics -- where there are multiple systems you get multiple pressure readings. In the case where two or more systems are feeding the same actuators I expect you can add the pressures, but why would you want to? Regards, Pete

Yes. In any case 3.41 was already changed to work with both FS9 and FS9.1. The current version of FSUIPC is compatible with FS98, FS2000, CFS1, FS2002, CFS2 and FS2004 (with or without the update). Once having achieved compatibility I try very hard to maintain it as I don't want to have to support more than one version. In any case, there's no risk on your part. You just replace the DLL in the FS Modules folder. That's all an "upgrade" is. You can easily keep old copies if you want to and revert just as easily (but just don't ask for support for them). :wink: In other words, it isn't a big deal. Just one little file being changed. Regards, Pete

Sorry, I don't understand. Add the IP address to where, what? Each WideClient only deals with one Server. It can't answer to two masters. Who would it believe for downloaded data? How would it know who to ask for what? Yes. If you set that non-zero then Wideclient will run on a PC with FS or other WideClients already running. It can then be configured to talk to a different server. The problem then is that the application program won't interface to it unless it is changed to find the different Class name -- and that's in the library folks usually use, so it means them getting inside the source (which is provided too, however). It wouldn't be a completely trivial task for them to undertake, and they would (probably quite rightly) ask why WidevieW isn't handling it better. After all, as I said before, it is really its job. "Runs the weather through ..."? I don't think that is relevant -- it isn't the data that FS needs. That goes through FSUIPC, not ActiveRadar. Of course not. Cloud textures have always been held in the textures folder in FS. It is only ASV which recently started doing that. I don't think there's anything else that'll handle textures -- I thought it was the actual weather you were concerned with. If it is only the textures, turn the texture part of ASV off. Regards Pete

Please upgrade to version 3.48. Version 3.40 is now very old (nearly a year) and there have been many fixes, changes and improvements since then. I cannot support old versions. Go get the FSUIPC SDK from http://www.schiratti.com/dowson and check the Programming document. That contains a large table of offsets which most certainly includes such information, but possibly not by those names. Regards, Pete

I'm afraid you'll need to change the conditions used in each case then. Let the values run from 0 to 2 and 0 to 3 (instead of 6), and change the conditions 12 to 18 accordingly. Delete the lines for the unused radios in each of the two device sections. Regards, Pete

No, sorry. The base is always zero. The parameter is just divided into two parts -- the increment and the upper limit. The lower limit is always 0. What sort of application needs 3, 4, 5, 6 and not 0, 1, 2 as well? Possibly you could use a cycle from 0 to 3 and just add 3 in whatever is using it? Regards, Pete

There is an elevator trim axis calibration facility in FSUIPC, if that's what you want. For the operation of this with A/P see the "Disconnect elevator trim axis for A/P" option in the Technical page. These things are described in the User Guide. BTW the current supported version is 3.48, not 3.47. Please upgrade. Regards, Pete

This is where I failed to make the association. Hmmmyou've lost me now! Where's what associated with what? Regards, Pete

Sorry, it was in no means a "technical" or "programming" term, but two ordinary English words juxtaposed in what I had (wrongly?) assumed would still make sense to you = "state of the shift" == "shift state". You wanted two states, shifted and unshifted, right? You yourself started using the term "shift" for a key you wanted to use to get two functions on one button. The "state" of that shift button is then obviously a "shift state" -- i.e shifted or not shifted, shift on or off, whatever. The word "state" is normal English. The word "shift" I thought you already understood because you started using it. :) :roll: :) Occam's razor? Yes, why not always take the easiest course? I myself should try doing that more often. It would sure save me a lot of development work. :wink: Good luck, Pete

Milliseconds since FSUIPC started -- in fact since the System and FS times loagged at the start. Regards, Pete

But Cowl Flap 1 is not assignable in the FS assignments dialogue. Whatever control you tell FSUIPC to use has to be one which FS is reading already -- FSUIPC is not a joystick driver, it does NOT read the axes at all. All it is doing is intercepting the controls which FS is using and changing them to do what you want. Probably the axis you originally had assigned to that lever was already assigned in FS. All you need to do is find the numeric corresponding to THAT control, then tell FSUIPC what it is in the "CowlFlaps1Control=n" line. I know. That is precisely WHY these facilities were added to FSUIPC. It is a "fiddle". You assign any otherwise unused axis control in FS then tell FSUIPC what it is so it can detect them. Assign any otherwise usused axis (the one it normally gets assigned would be fine). Then tell FSUIPC which it is. Regards, Pete

To start with do not use ANY string of numbers or letters. Use the Buttons page in FSUIPC exactly as I told you earlier. When you've followed my suggestions there, check the method for doing conditions THEN ask questions on bits you don't understand. You seem to have ignored the help I've tried to give so far altogether! Pete

This is nothing whatsoever to do with WideFS. All WideFS does is offer an FSUIPC interface on a client PC. I thought Aerosoft stopped developing the 747MCP firmware and driver long before the LDS767 came out? The support in the version I have is for Wilco's 767PIC -- is the LDS 767 the same? Anyway, you'll never get that working through WideFS or FSUIPC because the 767PIC (and prersumably also the LDS767) support by Aerosoft was via a special DLL Wilco provided which runs on the FS PC and bypasses FSUIPC altogether. I really cannot do anything with that at all, irrespecive of any strained relationships. Regards, Pete

This simply amounts to an attempt at toggling the value of 7B91 when the button is pressedbut the second the defeat the first. I cannot understand why you want to make it so complicated in the first place. Just use the toggle facilities. Delete both lines. Go into FSUIPC's Buttons page, and program the button as as Offset Byte Togglebits with offset x7B91 and parameter 1. "Toggle" means simply swapping between two values. You don't need to test them first then change them. And for such simple things as this you don't need conditions nor INI file editing. Regards Pete

Not FSUIPC? Doesn't WidevieW use FSUIPC these days? That's exactly what WidevieW is for, yes. A WideFS server could also be run in that PC, and you could have two copies of ActiveSky, one sending to one server and the other sending to the other. Each would need to be on a different PC unless you used the facility in WideClient for different Class Names -- but then you'd need to get the AS folks to allow the class name to be specified, or even to run one copy to send to both the standard FSUIPC classname and the additional one or two WideClient ones simultaneously. Or you can run an ActiveSky in each PC running FS, no WideFS involved, just AS talking to FS via FSUIPC, locally. Whether this would keep them synchronised better or worse than WidevieW I couldn't say. No, that's wrong. It just needs the FSUIPC interface, whether locally in the FS PC or remotely through WideClient. It is WideClient, not WideServer, to which it interfaces on a remote PC. Well, of course, ActiveSky could be changed to do all sorts of things, if the authors so desired. But so could WidevieW which already includes the networking software. You just need to be able to persuade the authors of the justice of your cause, or bribe them with lots of loot, perhaps? :wink: Why not more often? Having WidevieW only update every minute doesn't sound very good. Regards, Pete

All of it? Surely you can ask specific questions of specific bits? Most of it uses small non-technical words after all! Is English the difficulty? Anyway, I explained above how to do most of the work, all you need to do now is work out how to convert the lines to have conditions on them. Please try that. Regards, Pete

Sorry, it is hot and humid here and my body is also still on Madrid time, so it felt even later. You were just lucky to get my last response before I retired. Pete