Pete Dowson

And here is an up-to-date copy, the text from which i'll also put into the FAQ subforum. Missing In FSUIPC5.pdf

The FSUIPC5 facilities for moving SimConnect texts and menus to another PC are still awaiting facilities which L-M have promised. I'm afraid they won't give me a timescale. This omission affects me seriously as well, as I have a 220 degree FOV curved screen, and the menus and messages are almost impossible to read. I have managed to move them lower and to one side (so I can view them imposed on the scenery background out of my cockpit side window), but with P3D3 and before I had them all on a small screen inside the cockpit. When the facility is implemented it will certainly feature in the Changes notice supplied with the relevant FSUIPC version. There was a document "Missing in FSUIPC5.pdf" which was packaged with FSUIPC 5.0-5.10. I've just checked. It didn't get updated as things changed, and not included in later releases. That was an error on my part, for which apologise. I attach a copy, as it was then. I'll update it for the next release. Meanwhile note that these changes should be noted: 1. Delete this, GoFlight64.dll became available. 3. Amended: multiline messages use a different window from SimConnect. 4. Not implemented. May never be, but I have some ideas to follow up. 5. Pending P3D4 facilities which L-M have promised. 6. Not implemented, not possible, probably unnecessary (if not, report as bug to L-M). I'll make the appropriate changes and include it on the next update. Pete Missing In FSUIPC5.pdf

I've no idea what any of your message is about! I cannot read minds. If it is about FSUIPC, WideFS or another software program of mine, then say which, state the version and the context (FS4, FS5 .... P3D4) and what you are trying to do and what is going wrong. From the title I think you are talking about FSUIPC5, so presumably P3D4. But what does "windows or FSUIPC5 you choose" mean? And what is this: FSUIPC doesn't provide an "icon". It is merely shown as an entry in the P3D AddOns menu! Pete

Ah, so you are using a Goflight driver. I'm not sure FSUIPC will play any part then. Do Goflight drivers support the PMDG aircraft now? Doesn't GoFlight support those? FSUIPC has no built-in display control facilities whatsoever. They are too variable, between hardware and addon Aircraft. With FSUIPC you'd need to use a Lua plug-in the open the Goflight HID device and send appropriate commands to it. I've just checked, and if you look in your FSUIPC Document folder, in the Lua Examples ZIP file, you'll see an example for the WP6 (called WP6test.lua), which does things like setting lights on and off, changing colours, altering brightness. There should be enough there to get you off to a good start! The states of the indicators you want in the PMDG aircraft should be all available in the PMDG offsets. Again, check the PMDG offset list for your aircraft in the FSUIPC Documents sub-folder. Pete

I don't remember what the WP6 is. Are you talking about assigning button presses? If so, for the PMDG aircraft, you'd need to work out the appropriate control number from the ".h" type file in your NGX's SDK folder, then use that number in a <custom control> assignment in FSUIPC. Pete

That is probably equiva;ent to a real value near 0. But there's no easy or consistent way of deriving the indicator number from the actual trim percentage of proportion (16383 = 100%, up or down). The only way would be for you to make a little table equating one to the other, byt operating the trim and noting the equivalents. But note that it will be different from aiircraft to aircraft (though usually similar for related aircraft, like all Boeing 7x7 types). If you want a display showing the same number as on the indicator you'd need to make a little Lua plug-in script which used such a table, or possibly a formula you might derive (like add so much, multiply by some factor). I don't know. You'd need to look through the details for the NGX. There's an offset list for that aircraft in your FSUIPC Documents folder. Pete

What are you actually doing? Did you look up the offset for the elevator trim control input (because that is what the wheel controls). What are you seeing? The FSUIPC monitoring will show the value in the documented units: there's no conversion. In fact the usual markings on real trim gauges are in some scaled units fairly specific to the aircraft, really only reflecting the sort of markings they can make in the hardware. Here are the entries in the FSUIPC Offsets list (a document you'll find in your FSUIPC Documents subfolder): 0BC0 2 Elevator trim control input: –16383 to +1 6383 Ok-SimC Ok-SimC 0BC2 2 Elevator trim indicator (follows input) Ok-SimC N So, as you see, both are 2-byte values (sign 16-bit, or "S16"), with values -16383 to +16383. Pete

You'll need to buy an FSUIPC5 key. Pete

No. You can assign throttle normally, in the way I said. You can calibrate in FSUIPC, but PMDG aircraft in particular might not play nice -- they tend to read the joystic directly themselves, and it can conflict. If you do calibrate, then just check the "No reverse zone" (NRZ) option on the calibration screen. That will also give you your range of forward thrust from -16383 to +16384. The reversers on your TQ can be assigned direct to the Reversers in FSUIPC (in the "direct to FSUIPC" drop down list). Pete

The FSC support person is wrong and understands little it seems. The max reverse FSUIPC sends is the max reverse allowwd by FS, which by default in 25%, as defined in the Aircraft.CFG file. If it were 50% then that -4096 would be scaled to -8192, and so on. But 25% tends to be the normal limit. The -16383 that support person refers to is NOT the FS throttle value at all, it is the default range of Windows-calibrated axis inputs, which run -16384 to +16383. In that range, for throttles, -16384 is in fact ZERO thrust (0), and reverse is simply not allowed for! PMDG aircraft throttle control do not allow for -ve throttle -- they do reverse differently. Many folks are using FSUIPC assignment, and even the full reverse facility, but in general you need to assign throttle control to the Axis Throttle Set controls, and NOT calibrate them, then assign reversers to the separate Reverser controls. Pete

It's possibly normal for that PMDG add-on. FSX and P3D only save FLT ot FXML (flight or scenario files) and .WX (weather files). Maybe, in FSX case, an FSSave file too. But many add-on aircraft save many other files at the same time. So you will need to ask in the PMDG support forums. Pete

BUT as the documentation also states, you should use the AddOnOrganizer --- that is, unless you are careful never to install any add-on scenery which uses the new Addon.xml method to add to P3D! What you needed to read was the VERY FIRST LINE telling you what to do for FSX, FSX-SE and P3D, the part I just quoted t you. So if you read every line 5 times over (and why?), why, every time, did you skip over the very part telling you where to install it? Sorry, but you are not making any sense! :-( Pete

Only if you use FSUIPC which isn't needed or used by MakeRunways. for FSUIPC, maybe, not MakeRunways. MakeRunways has changed little since Radar Contact first used the results back in the days of FS2000 or so (I think). You can "just drop Makerunways" into the P3D folder. AddOnOrganizer is onlyneeded for those asson sceneries that use a new method of notifying their existence ot P3D -- FSDG and FlightBeam only at that time (this new method exsited with P3D3 as well). You still evidently have NOT read the documentation in the Make Runways ZIP file then, where it clearly says: For: FSX, FSX-SE, Prepar3D v1 to Prepar3D v4 inclusive Place the EXE into the relevant main FS folder. ... That is on the first page, less than half way down. You obviously have still not bothered to read any of it! PLEASE GO AND READ IT!!! :-( Pete

Offset 946A is not one maintained of set by FSUIPC, it will be set by whatever you are using with a TCAS. If you know of the offset, howcome you don't know its values? Aren't they documented. You could always monitor the value whilst you operated the knob -- see the right-hand side of the FSUIPC Logging Tab. Pete

I don't think TCAS modes are simulated in FS at all. Pete

I was only saying that the values you seek are already available. Pete

Those are internal simulation values, NOT "gauge variables". SimConnect Variables ("SimVars") are the basis of nearly all of the data you find in the FSUIPC Offsets! You will find all those there -- try serching the document! The list is in your FSUIPC Documents folder! Pete

Well, it can, so those utilities may be one way of using the other 32 buttons, if LINDA isn't any help and you don't wish to adapt the HID plug-in example plug-in. Pete

Good. any information on this for others? Pete

Okay. Yes, it can be used "out of the box" for the first 32 buttons. Otherwise it needs a plug-in or other software. It might be worth checking out LINDA. I don't know whether that handles Bodnar boards or not. Max 32 buttons, 6 normal axes (X Y Z R=Rz U=Rx V=Ry), 2 sliders (S T), and 4 POVs (P Q M N). To utilise more (your 64 buttons) you need to either use a plug-in, as I already told you (even pointing to an example), or a program to handle the card. Please do read my replies. Seems you don't. Pete

That's not a good way. Best to have logging running then simply stop it soon after it occurs. Simply extract the last portion illustration the "spike". And which line shows a "spike" ? It all looks good to me, except that you've turned off Axis logging, which is also needed to see what P3D received. You need Axis logging enabled as well! When you click on "new log" the previous is renamed with the .1 Well, as you must have seen if you looked at it at all, there's no sign of that in the log, so either it isn't covered by this section of log, or it isn't anything FSUIPC which read from the axis, and is nothing else FSUIPC is doing with axes. Because of the omission of Axis logging I can't tell what P3D is receiving though. BTW, you cannot "stop" the log except by terminating P3D. So I'm not really sure what you meant there. You can de-select the logging options. but there's really no need to do either. If there's a spike recoded in the log it will stand out as a line with much larger numbers (16383 or -16383) occurring on the axis than those shown in your fragments. Anyway, assuming you have "captured" the time of the spike, the only other thing I can think of, apart from a serious and unlikely bug in P3D itself, is aileron trim axis spiking. Do you have anything assigned to that? Check your P3D assignments -- it isn't in FSUIPC at least, according to the log (as far as it goes). BTW large log files ZIP up real small for attachment. Pete

If you want FSUIPC support you MUST post to the FSUIPC Support Forum. Apart from the support for the .NET DLL the subforums are repositories for reference information, not query and response. I moved it for you. What does this mean? At the time FSUIPC's button and axis assignment facilities was added, DirectInput only supported so many axes and 32 buttons, and all of the software design was based around that. Even now there are very few "joystick" type USB devices which exceed the numbers of either supported by FSUIPC, and the severe design upheaval to support further additions (and current DirectInput now goes up to 128 I believe) is excessive for the demand, and would jeopardise the established stability of the product. To allow for all sorts of future expansion, instead of messing with the original design I added ways for folks to do it themselves using plug-ins scripted in Lua. All HID (human interface devices) can be supported via such scripts, including devices with 64 or more button inputs. And it is made easier for Joystick type HID devices which are mostly decoded for you. The documentation for these plug-ins is provided in your FSUIPC Documents subfolder, and there's even an example in the "Example Lua Plugins" collection -- HidDemo.lua. BTW I also use Leo Bodnar boards, but multiple BU0836 ones. These are all easily supported natively by FSUIPC without the need for plug-ins. Pete

I will still have to, in ProSim V2, because nothing in my cockpit is standard hardware. It is all handled by my own drivers, which use offsets. My ProSim setup is programmed completely via offset assignments. Why not just use the ProSim V2 FSUIPC option, as beflore? I saw nothing funny in what I suggested! Pete

Actually, unless you are assigning to the F control for sterring tiller, that isn't true. FSUIPC's own steering has always used the rudder. I know, but it IS how FSUIPC does it. The "steering set" control is an FS facility, not an FSUIPC one. When flying? That isn't right. Sorry, no. I simply haven't had time to fly at all since I upgraded to ProSim v2. I have read that you can get ProSim to use SimConnect or FSUIPC. Have you tried both? And why not use FSUIPC and not assign rudder/steering tiller in Prosim? Surely that is still an option? Pete

I'm not really surprised, I am pretty sure CockpitSonic hardware does not emulate joysticks. Without extra software FSUIPC only recognises DirectInput "Joystick" type devices. Did Windows recognise any switch in its "Game ContrllerS"? Did FSX recognise any of its switches in its assignments? They are joystick type devices, that is why! I don't know LINDA, but the whole point of it is to enable more hardware. Ask LINDA support why it works. So all you need is to write a program to read the switches and write to the offsets! I would have thought CockpitSonic would do that! You may be in the wrong place here. Have you tried Cockpitsonic support? It is their hardware. Ask if they have any software which does what you want. If the overhead is a HID device (Human Interface Device) recognised as such by Windows, and connected via USB, you can write an FSUIPC Lua Plug-In to read its switches and do things. I expect this is what LINDA is doing. It uses many Lua plug-ins. Pete