Pete Dowson

Ah, well. that's not a software question. I'm afraid I can't answer that. doesn't sound so difficult though. Well "joy to key" isn't anything of mine, so I can't advise. But why go to all that trouble instead of just programming a button on the FS PC? Regards Pete

Yes, because that says 256 gives 128 steps. 128 would give 256 steps (32768/128 = 256), so obviously each step would then be smaller. At the extremes 1 would give 32768 steps, and 32768 would give none. (well just the one you are on). ;-) Pete

You can only do it with multiple aircraft NAMES. It isn't about making copies of folders and so on, only editing the AIRCRAFT.CFG file to add another version, just like another livery. For example, in that CFG file there will be a number of sections headed like so: [fltsim.0] title=Boeing 737-800 Paint1 ... Just make a copy of the complete section like that for the aircraft you want, and paste it in as [fltsim.N] where N is the next unused number. Then edit the title to distinguish it. eg for the default 738: [fltsim.6] title=Boeing 737-800 Paint1 Controls 2 Regards Pete

Good. That is the elevator trim control input. The 256 in your parameter is NOT "the number of increments"!!! It is the AMOUNT of increment. It means on each button press ADD or SUBTRACT 256. Obviously the trim action will be fast with a larger increment and slow with a smaller one! How did you get the completely wrong idea here? I'm sure it is clear enough that the value for an increment/decrement control is the increment/decrement value. Pete

First of all I need to understand what part of this message is asking a question. So what are the questions? I don't know what software you have doing this, but WideFS only sends button presses from a Client, not axes like the yoke aileron and elevator. Without wiring there is no way to connect a switch on one device to a switch on another, even on the same machine. Switches are physical things. Perhaps you means you want a "push to talk" button on the yoke on the FSX PC to operate softeare (Teamspeak or Ivap?) on the other PC. For this you'll need information on how to configure TeamSpeak or iVap. I'm afraid I don't know either. If a keypress will do you can make WideClient send keypresses to programs in response to a button assigned to a "Keysend" in FSUIPC. This is documentated with notes and examples for different programs in the WideFS documentation. The yoke must be plugged into the FSX PC. Sorry, I've no idea about iVap. I don't think it uses any of my software. You cannot without writing a program. Plug yokes into the main FS PC. Why not? Pete

Using which offset? Well, in default aircraft the FS implementation of trim has the same effect as the elevator -- the same range as well. The most obvious thing you could do is change the 256 incrememt/decrement you are using to something you find more acceptable. Why 256 if it is too much? Try 128 or 64 or 32 or something! The repeat rate for button scanning defaults to something like 20/sec, but is adjustable in the INI file as documented in the Advanced Users guide. If you do reduce button scanning, bear in mind that this will affect any rotaries. Pete

Sorry, no. You might try the support forum for the Airbus Extended. Some of these add-on aircraft do so many of their own tricks that it really is difficult to know what works and what doesn't, or why. And the airbus throttle system is very different from other aircraft. Pete

Wideclient was still running. The current log is WideClient.log, the previous one Wideclient0.log. It saves the previous one so that when needed it can be restarted without loss of information. This shows that Broadcasts from the Server are not reaching the Client. This only usually occurs if you have different Workgroups. Did you check that your Workgroup name was the same on both PCs? You could also actually try specifying the Server name and the Protocol, as suggested in the documentation. Please do refer to the User Guide, the section marked Configure your Network IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! There's a reason it is so highlighted! ;-) Pete

Well so many others seem to find my email address without any problems. petedowson@btconnect.com. But don't expect such a quick response as I try to give here. Pete

You only need the first one. I've never put two in there. I've always set the DNS IP address to that of the router (your "gateway"). I've no idea why you would ever need to do anything differently. Sorry. Pete

No need for any of that for WideFS. Files aren't involved. Though you probably need to share some folders for FS commander. They are not talking to each other. To see why I need to see the Log files -- WideServer.log from the FS Modules folder on the server, and WideClient.log from the folder in which you are running WideClient. You can paste the text from files into a message here. Pete

Well, as Windows has been developed and improved this is less of a problem than it used to be, especially of course on multi-cored PC processors as most all of them are today. Described where? No no no! It is simple really. By default IP addresses on the network are assigned automatically by a central part, usually the Router. But this is optional. The change is done via Control Panel - Network and Internet - Network Connections (select your Network), then In "Local Area Connection X Status" (or whatever), select Properties, then In the Properties select "Internet Protocol Version 4 (TCP/IPv4) and click "Properties" You'll see it shows "Optain an IP address automatically". Check "Use the following IP address" and enter it in the IP address boxes. The first three numbers MUST be the same as your router IP address first three. The subnet mask should be 255 255 255 000 The default gateway must be your router's IP address Finally "Use the following DNS server addresses", first entry should be your router IP address also. Just click OK and you are done. Pete

In what way, "check"? See it move? As far as I know, aircraft with tillers have cockpits from which there's no way to see the rudder. So, how are you checking? Airliners like the 737 show the positions of the control surfaces on a page on the lower DU. With programs which display this by reading data through FSUIPC, the rudder position which would otherwise be set by the rudder pedals can be fed to them instead of the true FSX rudder position. This is automiatically done for the software I use, but otherwise can be faked through the Lua spoofing facility. Do you get out of the aircraft to do this, or have you got large mirrors on the the outside of the cockpit? If you are outside who is operating the tiller or rudder pedals? I don't know much about other aircraft, but even at taxi speeds, the 737 limits rudder deflection to 7 degrees when the pedals are pushed completely over. It isn't possible to do full deflection of the actual rudder, only full readouts of the intended position. No. It's a result of using a tiller control which is implemented by operating the FSX rudders. You can't have smooth changeover from tiller to rudder if the rudder is operating fully all of the time in any case. Don't you see? What you are wanting just isn't logical.when FSX is doing steering by rudder input. Why not just stop assigning your tiller to FSUIPC's steering tiller and instead use the FSX steering tiller control? Then tiller and rudder are independent. You won't get the smooth changover of effect, that's all. It is either using FS's tiller, or using cockpit software capable of reading the FSUIPC offset for the actual rudder pedal position. I use the latter method. Regards Pete

And did you leave a definite gap, a dead zone, when clicking the idle point during calibration? In other words, do NOT set idle when the throttles are fully back but when pushed slightly forward. That is the only way to guarantee a zero value being sent when they are fully pulled back, and it exactly wty this is part of the numbered steps to good calibration in the FSUIPC user guide. Depends how your reversers are controlled. Basically the FSX revesre facility is by a negative value for the throttles, so such a value would replace the positiive value in any case. Some aircraft, however, seem to be programmed to ignore the controls which allow negative throttle values, but then these accept "Throttle Decrement" controls to allow both throttle reduction to aidle and into the reverse area. So repeated use of Throttle Decrements should always get you reverse not matter what throttle position you left -- provided the throttle axes aren't jittering and sending positive values which override this. That can't happen if they are parked in the calibrated "dead" zone for idle. You can nest conditions as much as you like. No, there's no error reported there. There is this: *** LUA Error: E:\FSX\Modules\Thr1Idle_NGX.lua:31: 'end' expected (to close 'if' at line 5) near '<eof>' which is surely self explanatory? You certainly have a missing 'end'. Count the "if'" and the "whiles" and see if they match the number of "ends". There are 9 ifs and whiles and only 8 ends! I think there is a missing end between lines 14 and 15, to end the first if on the radioalt. BTW this seems a complicated way of fixing what shouldn't be a problem at all. How are you assigning reversers? Pete

Oh, right ... thanks! Which FSUIPC is that with BTW? Regards Pete

If this is with an add-on aircraft? How are you programming that lever? For cutoff/idle on normal FS aircraft you assign the cutoff position to the appropriate Mixture Lean controls and the idle position to the Mixture Rich control. Sorry, I have no idea what PMDG uses for reverse. Test FSUIPC settings with default aircraft. See if you can get support for PMDG aircraft from the PMDG forum. I don't have or use any PMDG aircraft. Regards Pete

No, but please update to at least 3.999z4, the earliest supported version. Purchased of FSUIPC3 is a once-only action and covers all updates. FSUIPC4 (for FSX and Prepar3D) is a separate purchase. Pete

If you mean the PMDG 737NGX on FSX (you haven't even mentioned which FS), then it has complete subsystems programmed on top of the base FSX sim, and many parts are not controllable using FSX controls. There are many alternative controls you are able to use instead, as listed in their SDK. I've just checked -- thePMDG_NGX_SDK.h file lists these: #define EVT_CONTROL_STAND_ENG1_START_LEVER (THIRD_PARTY_EVENT_ID_MIN + 688) #define EVT_CONTROL_STAND_ENG2_START_LEVER (THIRD_PARTY_EVENT_ID_MIN + 689) from which you can compute the actual control numbers using this earlier line: #define THIRD_PARTY_EVENT_ID_MIN 0x00011000 // equals to 69632 Regards Pete

There is no way this can be a problem in FSUIPC -- it does nothing by itself. You have some dual assignments or something else like a stuck axis, maybe. Try using the logging facilities in FSUIPC to see what is going on. You cannot, and it would not make any difference in any case. The only difference between 4.9 and the previous version is the removal of the signature. I can help you sort your problem out, but you need to provide more information. For instance. what IS an "RSP throttle", how it is connected, how is everything assigned, to what and where? Axis logging in FSUIPC will help show what might be going on. Pete

Yes, I did suggest that at the start. Whenever the time is changed by more than a minute, FSX reloads traffic. The time sync option is NOT defaulted on in FSUIPC, so you must have opted for it at some stage. Glad you sorted it. Regards Pete

Well, until then you might want to assign the left toe brake to both left and right brake axes so you get symmetric braking! Regards Pete

The latest interim version of FSUIPC4 (4.905) includes a facilty for diverting those messages -- provided they come from an application program via SimConnect -- to a WideFS client. You could use this to simply stop the messages appearing altogether, effectively just losing them, if you wished. This only works with FSX SP2 or Acceleration and requires the addition of a parameter to the INI file. The "changes" document in the download ZIP gives you the gen. However, the messages won't be suppressed on screen unless FSUIPC is made to think that a WideClient somewhere on the connected network is capturing them. You can fool it by setting offset 333D to 1. You could do this with a button assigned to "offset byte set" with offset 333D and parameter 1, or maybe by having a macro automatically run (via [Auto]) to do the same thing. Regards Pete

How often are you polling? FSUIPC uses that same interface. It is a "conversion layer" to adapt SimConnect to the FSUIPC interface, for compatibility with programs written for FS2004 and all the way back to FS98. SimConnect is a subscription system where you ask for data when it changes, and it supplies it. The FSUIPC interface is a synchromnous system -- you ask for it when you want it and it replies with the last value it received from SimConnect. If you are using the values for real-time actions you would also need the data time along with the data so you can adjust for the different periods between each reading. The time data is supplied in offset 0588 with flags in 0584 indicating which of these offsets were changed at that time: Offset 0560 latitude Offset 0568 longitude Offset 0570 altitude Offset 0578 pitch Offset 057C bank Offset 0580 heading This way folks have been able to achieve good smoothness. Of course if you are only aiming at FSX and Prepar3D, why are you using FSUIPC in any case? I tend to expect all such applications to be using SimConnect directly really. Regards Pete

C800 is the offset for the setting the weather in the binary data format as defined in the New Weather Interface documentation. See the ZIP in the FSUIPC SDK. If you want to write METAR strings the offset is clearly defined as being B000. The messages go to the log file as well, so you can find where your atttempt was done and analyse the results. That's the point of logging. Just search for the line starting "Setting Metar". For example, I've just sent more or less your METAR but for EGCC and a QNH of 1019 hPA (I think yours works out to 1007 hPA): 796541 Setting Metar: "EGCC 260608Z 27015KT 7SM +TSRA BKN055CB 30/17 Q1019" 796822 Weather Read request (Global set) to area 1: ICAO="GLOB", Req=0 796822 Weather Received (type 1 request, (null)): "GLOB&A0 000000Z 00000KT&D985NG 27020KT&A2001NG 27025KT&A6001NG 100KM&B-448&D3048 2CU057&CU001FNMN000N 6CI393&CI001FNMN000N 15/05 Q1013 @@@ 66 15 270 20 | 197 15 270 25 | " 796822 WX Received in (0 mSecs), WX request type 1, ICAO=GLOB 796822 Results: FS98 Pressure=1019.0 mb 796822 Results: FS98 AmbientWind at PlaneAlt=266: dir 317M, vel 15 796822 Results: FS98 CurrTemp at PlaneAlt=266: 30C 798850 Weather Read request (Nr Station) to area 5: Lat=53.35, Lon=-2.29, Alt=0.0, Req=1 798850 Weather Received (type 5 request, Nearest): "EGCC&A77 260608Z 27015KT&D304NG 11KM&B-1577&D3253 7CB055&CB001FHHR000N 30/17 Q1019 " ... 803155 WX Received in (0 mSecs), WX request type 5, Lat=53.3456, Lon=-2.2919, Alt=0.0m 803155 >Change: Pressure=1019.0 mb 803155 >Change: Surface wind: to alt=1250ft, dir=270T, vel=15.0, gust=0.0, turb=0, shear=0, var=0.0 803155 >Change: Wind layer 1: remainder cleared 803155 >Change: Visibility[0]: range=6.8sm (11008m), from=-4920ft, to=5750ft 803155 >Change: Cloud[0]: type=10, from 5700ft to 35700ft (+/- 0ft), cover=7, turb=3, topshape=0 803155 >Change: Precip=1, base=0ft, rate=4, icing=0 803155 >Change: Temperature[0]: alt=250ft, Day=29.0 C, NightVar=0.0 C, DewPt=16.0 C 803155 >Change: Temperature[1]: remainder cleared You can see my write to B000 recorded at time 796541, and getting confirmation back that it is set at time 798850, i.e. just over 2 seconds later. The "change" stuff later is the eventual result as placed in the assorted fS98-style offsets. (Cloud type 10 is thunderstorm, or CB, cumulonimbus). To interptet the extra METAR encodings supplied from SimConnect you'll need to refer to the SimConnect SDK. No, as the SimConnect description states: "this parameter is ignored when setting weather data.". Of course not! Logging is just a process of writing to a file the details of what is read and written in order to work out what is going on. It wouldbe futile if it changed what was going on! No. FSUIPC simply sends your METAR string to SimConnect. It is then all up to FSX. Only the log will show what is going on, so you need to locate the relevant section. BTW, LFMN is Nice, in France, and the barometric pressure is measured in hectopascals in Europe, so I'm assuming that is a METAR you made up for yourself? Oh, also of course the visibility would be in KM not SM. These things don't matter, but the read back will be metric as you see from my test, above. Pete

PArking brake is a simple button assignment. What are you trying? Engine start levers for jets need to be assigned to MixtureN_Rich (for engine N "idle" position) and MixrtureN_Lean (for Engine N "cutoff" position. What are you trying? Pete