Pete Dowson

Yes, and you can assign your axes and calibrate them in Prosim. In fact since Prosim V3 it is important for Prosim to have the controls as it allows it to do what it needs more precisely. Pete

WideFS has never read and transmitted axis values. This is because of the latency involved across a network. Axis requirements are always best on the main Sim PC. The prime purpose of WideFS is to allow FSUIPC client applications to interface to FSUIPC on the sim PC. The transmission of button presses was added as an 'extra', but the need for axis transmission has never arisen -- for the above-stated reason. In cases where response time is not important, it is possible to have a Lua plug-in to read the device axes (and buttons) directly (using the com library Hid facilities) and sending the results to user offsets, or even directly to Sim offsets. Pete

FSUIPC has never been sold directly. It's always from SimMarket. As FSUIPC4 (the version for FSX, FSX-SE and P3Dv1-3) has now been available for 16 years, and in fact had development frozen a while ago, any upgrade discount from FSUIPC3 is long expired. Pete

As I said, 32-bit software runs fine with a 64-bit windows installation. It is the other way around, 64-bit programs on 32-bit windows, which doesn't work. If you update to Win7 I strongly advise you to go for 64-bit. Otherwise you are really restricting yourself unnecessarily. Pete

It does that automatically, following the list in the MSFS file "content.xml". MakeRwys generates a list too, showing what it processed -- see the scenerylist.txt file in its folder. The log file "runways.txt" tells you exactly what it is doing, so check that too. Pete

If you switch to Win7 I would recommend the 64-bit version. It is compatible with 32 bit programs too, and there's no point in restricting yourself unnecessarily. By default WideClient uses TCP protocol. You might find it slightly faster using UDP. But either way, its speed depends on the Server. It's 'frame rate' is limited deliberately to 24-30fps so it doesn't affect the Sim's performance, but MSFS tends to be a heavier load on the server than either P3D or XPlane, and the need to have FSUIPC7 as an external process from MSFS (unlike FSUIPC6 with P3D) will add to the latency. Pete

Strange. Perhaps I inadvertently set a different option in 7zip, as I’ve been using it for years with no such problems. ??? Pete

It downloads and opens fine here ... I've no idea why you both can't get it downloading correctly!??? 😞 I've attached the EXE file extracted from that same downloaded ZIP! Pete WideClient.exe

I'm sorry, but WinXP has not been supported by our software for a very long time. Try updating to at least Win7. If that isn't possible, you could try this old version of WideClient (5.500 dating back to 2003). It should still work even with FSUIPC7, but the facilities won't all be as documented in the current WideFS documents. Sorry, I don't have any old documentation to go with it. Pete WideClient5500.zip

I think ProSim support properly needs you to post a ticket, though I have read of cases where those take a long time to get a response too. I suspect the quickest solution will be to go for a game card. My choice would be a Leo Bodnar BU0836A http://www.leobodnar.com/shop/index.php?main_page=index&cPath=94&zenid=aa02107b108196223a817b90bf046c36 Reasonable price and works very well -- I use several. Pete

Yes, as John said. The INI file shows no axis handling whatsoever in FSUIPC. You need to assign and calibrate in ProSim. I think you need to go to ProSim support. I use ProSim and have all my control axes assigned and calibrated there, but I have them connected directly to the PC running ProSim. I do not use the 'hardware connector' part of ProSim. Maybe the problem is there. Anyway, you did say "All axis are assigned in Prosim configuration", so why is there a problem? Does that statement exclude your rudder and tiller axes? You really need to post your questions on the ProSim support forum. I expect John will lock this thread soon as it isn't going to get anywhere further. Pete

The calibration facilities operate without needing to assign in FSUIPC. But they aren't calibrated unless you SET them to! If you've pressed 'RESET' as I suggested then they are not calibrated. Of course they are scanned by the calibration facilities, just as they are shown at the top of the assignments tab -- otherwise how would you be able to do either? It doesn't mean FSUIPC is handling them. Pete

With Prosim v3 you must assign and calibrate all flight controls, tiller included, in Prosim, not in FSUIPC. Remove the assignments in FSUIPC by unticking those on the left side of the axis assignments tab, and remove the calibrations in the joystick calibration section by pressing the Reset button, top left for each calibrated control. Pete

Okay, I've tested this on my cockpit, with ProSim 3.18B1. The ZFW (and other weight components) change correctly when altering the pax and cargo loading in the P3D Fuel & Payload menu, and also when using FSUIPC to write to the payload station offsets. But nothing changes except the total pax or cargo values in ProsinIOS and the CDU when changing loadings via the IOS or CDU. Nothing is written to the payload offsets. I don't see how this can be down to FSUIPC, but I don't understand what ProSim is using to change the loadings in P3D. So I'm going to ask Humberto for more information. Pete

Transition altitude data is not available with MSFS. How are you managing to use Radar Contact with MSFS? To start with it needs menus which aren't supported in MSFS. Pete

Humberto kindly explained to me how ProSim computes the ZFW from FSUIPC offsets. He said: Prosim is calculating ZFW. It is getting gross weight from offset 30c0 and subtracting fuel from offsets 0b80(capacity) 0b7c(level) : example for 1 tank only, corresponding offset used for the other 2 tanks So, I made a Lua plug-in to compute it the same way, whilst changing the payload a number of times. This showed absolutely no difference between FSUIPC 6.1.7 and 6.1.8 for the offsets Prosim is using. For your information I attach the Lua plug-in. It logs the results in FSUIPC6's log. Here's the results for my office version of P3D5.3. Each loop is increasing the weight in the 9 payload stations by 100 lbs, so increasing the payload total by 900 lbs on each loop -- in the log the loop ends are denoted by the line with ******... For each loop the ZFW is being calculated in the exact same way as Humberto states for ProSim. This is shown in the lines like 796781 17024 LUA.3: Computed ZFW = 105715.36461655 I've also checked the values against those shown in the P3D Vehicle - Fuel and Payload display. 794500 17024 LUA.3: Gross before changes = 150867.65625 794500 17024 LUA.3: Number of payload stations = 9 796765 17024 LUA.3: Total payload = 14400 796765 17024 LUA.3: Gross now = 151767.65625 796765 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 796765 17024 LUA.3: Total fuel weight = 46052.291633454 796765 17024 LUA.3: Ditto from offset 126C = 46057 796781 17024 LUA.3: Computed ZFW = 105715.36461655 796781 17024 LUA.3: =============================================== 800796 17024 LUA.3: Gross before changes = 151767.65625 800796 17024 LUA.3: Number of payload stations = 9 801312 15996 Deactivated for PID=9580, "explorer.exe" 801312 15996 Lost focus to PID=9580, "explorer.exe" 803046 17024 LUA.3: Total payload = 15300 803046 17024 LUA.3: Gross now = 152667.65625 803046 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 803046 17024 LUA.3: Total fuel weight = 46052.291633454 803046 17024 LUA.3: Ditto from offset 126C = 46057 803046 17024 LUA.3: Computed ZFW = 106615.36461655 803046 17024 LUA.3: =============================================== 807062 17024 LUA.3: Gross before changes = 152667.65625 807062 17024 LUA.3: Number of payload stations = 9 809296 17024 LUA.3: Total payload = 16200 809296 17024 LUA.3: Gross now = 153567.65625 809296 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 809296 17024 LUA.3: Total fuel weight = 46052.291633454 809296 17024 LUA.3: Ditto from offset 126C = 46057 809296 17024 LUA.3: Computed ZFW = 107515.36461655 809296 17024 LUA.3: =============================================== 813312 17024 LUA.3: Gross before changes = 153567.65625 813312 17024 LUA.3: Number of payload stations = 9 815562 17024 LUA.3: Total payload = 17100 815562 17024 LUA.3: Gross now = 154467.65625 815562 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 815562 17024 LUA.3: Total fuel weight = 46052.291633454 815562 17024 LUA.3: Ditto from offset 126C = 46057 815562 17024 LUA.3: Computed ZFW = 108415.36461655 815562 17024 LUA.3: =============================================== 819578 17024 LUA.3: Gross before changes = 154467.65625 819578 17024 LUA.3: Number of payload stations = 9 821843 17024 LUA.3: Total payload = 18000 821843 17024 LUA.3: Gross now = 155367.65625 821843 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 821843 17024 LUA.3: Total fuel weight = 46052.291633454 821843 17024 LUA.3: Ditto from offset 126C = 46057 821843 17024 LUA.3: Computed ZFW = 109315.36461655 821843 17024 LUA.3: =============================================== 825859 17024 LUA.3: Gross before changes = 155367.65625 825859 17024 LUA.3: Number of payload stations = 9 828125 17024 LUA.3: Total payload = 18900 828125 17024 LUA.3: Gross now = 156267.65625 828125 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 828125 17024 LUA.3: Total fuel weight = 46052.291633454 828125 17024 LUA.3: Ditto from offset 126C = 46057 828125 17024 LUA.3: Computed ZFW = 110215.36461655 828125 17024 LUA.3: =============================================== 832140 17024 LUA.3: Gross before changes = 156267.65625 832140 17024 LUA.3: Number of payload stations = 9 834375 17024 LUA.3: Total payload = 19800 834375 17024 LUA.3: Gross now = 157167.65625 834375 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 834375 17024 LUA.3: Total fuel weight = 46052.291633454 834375 17024 LUA.3: Ditto from offset 126C = 46057 834375 17024 LUA.3: Computed ZFW = 111115.36461655 834375 17024 LUA.3: =============================================== 838390 17024 LUA.3: Gross before changes = 157167.65625 838390 17024 LUA.3: Number of payload stations = 9 840640 17024 LUA.3: Total payload = 20700 840640 17024 LUA.3: Gross now = 158067.65625 840640 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 840640 17024 LUA.3: Total fuel weight = 46052.291633454 840640 17024 LUA.3: Ditto from offset 126C = 46057 840640 17024 LUA.3: Computed ZFW = 112015.36461655 840640 17024 LUA.3: =============================================== 844656 17024 LUA.3: Gross before changes = 158067.65625 844656 17024 LUA.3: Number of payload stations = 9 846921 17024 LUA.3: Total payload = 21600 846921 17024 LUA.3: Gross now = 158967.65625 846921 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 846921 17024 LUA.3: Total fuel weight = 46052.291633454 846921 17024 LUA.3: Ditto from offset 126C = 46057 846921 17024 LUA.3: Computed ZFW = 112915.36461655 846921 17024 LUA.3: =============================================== 850937 17024 LUA.3: Gross before changes = 158967.65625 850937 17024 LUA.3: Number of payload stations = 9 853203 17024 LUA.3: Total payload = 22500 853203 17024 LUA.3: Gross now = 159867.65625 853203 17024 LUA.3: FuelC = 28798.32779259 FuelL = 8626.9819204323 FuelR = 8626.9819204323 853203 17024 LUA.3: Total fuel weight = 46052.291633454 853203 17024 LUA.3: Ditto from offset 126C = 46057 853203 17024 LUA.3: Computed ZFW = 113815.36461655 853203 17024 LUA.3: =============================================== As John says, there's really no change between 6.1.7 and 6.1.8 which could result in what you are observing and they certainly both behave the same with this test. I should be able to get my cockpit up and running tomorrow, and then I will double-check when actually using Prosim. I'll update first to 3.17B20 (or later if another is released). Pete TestZFW.lua

Sorry, but we are rather confused by your question. Don't you need three axis controls -- throttle, collective and cyclic? How are you proposing to use multiple separate controls on one axis? Shouldn't the fuel switch be just that, a fuel on/off switch? Do we assume that the prop pitch control operates the collective on your helicopter? Oh, and what do you mean by "collective throttle"? If you explain yourself in more detail (please assume we don't know much about helicopters) we'll get back to you either later tomorrow, or more likely on Monday. Pete

Thanks for letting us know. But if the title in the little progress window, and the first line in the log ("runways.txt") say it's 5.13, then you can believe it is actually 5.13. I'll fix the Properties version next time there's cause for an update. Pete

ff. is the standard abbreviation for "and following"! sorry if it misled you. I've no idea what telling Mobiflight "#FF" will do, and declaring the offset in ProSim as 8U (i.e. one byte) but 2 bytes in mobiflight seems wrong as well. It occurs to me, from the clues in your submissions, that the spoiler deployment only needs to be signalled for your servo to bring the lever full up. So I assume the simple setting of '1' does it. By using 0BCC you have the Sim setting that to 1 for "Armed" and 0 for "not armed". When the spoiler is automatically deployed on landing, the Sim will set that to 0, for "not armed". This is why the 1 is cleared to zero almost immediately on touchdown. If you have ProSim setting 66C0 rather than using 0BCC then you should see a 1 there for deploying the spoiler, and only changing to 0 when it is stowed again. You shouldn't need to include the 'on ground' check at all -- it is ProSim which is doing that before operating the spoiler. Anyway, that's all from me. I've been as clear as I can be with the flimsy understanding of how your setup works. Pete

Sorry, what do you mean "66C0 FF"? Choose just one offset. 66C0-66FF is the range of free user offsets (64 different ones, 64 bytes altogether). And where are you using it? In the ProSim servo assignment? If not, then what would be setting it? Pete

If a value of 1 sets the lever to 40% or so, then I'm just bewildered as to how your motorised TQ works, because a position value of 1 is nonsense. I also still think assigning any of the Sim-set offsets in ProSim as an output is wrong. Both the Sim and ProSim will be writing to the same place. You should consider using a separate offset, such as those free for users (66C0 ff). On my system 0BD0 reflects the actual lever position, even with the lever only assigned in ProSim as an input axis. The position value is 0 for down, 4800 for 'armed' and up to 16384 when fully deployed after landing. And it stays that way until manually lowered by the pilot after slowing sufficiently on the runway. You seriously need to consider this. The spoiler does not automatically retract after landing. Pete Pete

Why do you think you need FSUIPC4? That's only for FSX and P3D1-3. What is "these" and "them" in this sentence? If you have FSUIPC7 and have also purchased WideFS7 (not WideFS4 which isn't available in any case), then just download the wideFS7 package, and place the WideClient.exe program into a folder on your Pilot2ATC PC. When you run that it will connect to FSUIPC7 on the MSFS PC when the latter is fully running (ready to fly). Pete

Yes, I saw the video you posted in User Contributions. The lever is only moving a little. Surely you need the actual position of the lever -- offset 0BD0? If not, then, sorry, I don't know what ProSim and Mobiflight are doing. Surely for the throttles you use the throttle position, bot just a flag saying whether there's some thrust? Pete

But the offset for the lever position is 0BD0, not 0BCC or 0BC0. The 0BCC offset is merely a flag saying whether the spoiler is armed, it doesn't give the lever position. Pete

You'll need to explain how the servo for the speedbrake moves the lever to the correct position when only given the 0 or 1 in 0BCC. Surely it needs the actual position, the value in 0BD0 -- the same sort of thing you'd need for motorised throttle levers. Pete