Pete Dowson

Yes, but it is more flexible the new way -- you can disable each set of controls separately. Make sure you select them in the drop down to disable them. Joy 17 and 18 are activated by programs writing to the FSUIPC joystick interface (mainly used for PFC devices by my PFC drivers) at offsets 3BA8 to 3BC4. (Please see the offsets list). If your hardware driver is changing those, it is obviously intending you to assign through FSUIPC's axis assignments. So why don't you? No, because unless you assign them, there in FSUIPC's axis assignments tab, they are ignored. Regards Pete

No idea. Are you referring to this query of about three weeks ago? What's been going on all this time? Have you tried anything? What do the mouse macros look like? What version of FSUIPC4 are you using -- the latest is 4.522, from the Updates announcement. Have you tried that? Maybe the mouse action needs qualifying (see the notes in the docs)? I've actually never heard of something working with the "TAB" test and not working subsequently, when assigned -- because the TAB test does the same thing as an assigned key or button. I'm not going to buy and install an aircraft I don't want just to try things myself. I provide the tools and suggestions, the rest is up to you. If you want more help, you need to supply more information -- such as the macro files and the buttons section of the INI file. You also said Can you provide the link to that please? Because I don't know of anything outstanding for any of the PMDG aircraft. The mouse macros work for everything as far as I know. Perhaps I'll hear more from you in another two or three weeks? ;-) Regards Pete

Whatever you prefer. You'd use the detente facilities in FSUIPC in any case, so the notches can be where you like. I would have thought you'd make them where they should be. But you do have to ensure there's enough change in the input values from the axis, between each position. Pete

That may well be, but does it have the id "LGAV"? That's the point. If so, you need to tell Jeppesen and Microsoft, not me. I am not responsible for FS's weather station list. As I said, they still have LGAT listed for both FS9 and FSX. Sorry, i cannot help you any more. You know why it is happening now. What you do about it is up to you. Pete

Thanks, but I didn't really need such a full documentation on these parts of the aircraft, I don't need to know any of that. All I needed was to know how you are programming the ones that work and why you cannot program the others! If i knew you were successfully using mouse macros, for example, then maybe that could be explored further. Unfortunately, despite the long message, you didn't actually mention how you programmed anything! Regards Pete

Don't PMDG provide any keyboard shortcuts for whatever those functions are? They usually do. Otherwise, you'd need to see if a Mouse Macro might work. Are you push/rotate functions mouse macros, or keyboard assignments? Pete

Well the latter is a result of the former -- a flatter blade allows the rotor to spin faster, less air resistance. Well that is what I'd expect with the collective being controlled by the throttle control. If you have multiple inputs to any control, they certainly will interfere -- but only if they are seen to be moving (jittering, perhaps). Both FS and FSUIPC only take notice of changing inputs, not static ones. Regards Pete

The offsets for prop pitch are quite sensibly described in the offset lists as "prop lever", just as "throttle lever" and "mixture lever" are used for the other two. For each of the 4 engines they are in the very next offset to the main throttle offset. In the kneeboards and other operational assistance references provided in FSX (where it gives the keystrokes needed), after selecting one of those helos -- and then verifying this by actually using the prop pitch key presses and watching the twist throttle operating, and also logging events in FSUIPC to check the controls being used by the keystrokes. I suspect that is only because the code operating the helo model isn't operating when paused. The collective is surely the actual pitch of the blades? Oddly controlled by the throttle inputs. I simply do not understand why two pilot controls each contribute 50% to one helo control. That is surely wrong? How is that supposed to work? Perhaps you are referring to RPM -- obviously a flatter pitch will allow the RPM to increase, and vice versa, but that isn't throttle control. The throttle and prop pitch offsets are clearly labelled "throttle lever" and "prop lever". Sorry, I thought this was evident. Or am I misunderstanding your questions? Perhaps you need to exchange ideas with other Helo fliers. There are plenty around, I'm sure. I've never heard of anyone having so much difficulty as you, so I'm sure it must be all a bit of a misunderstanding. Have you tried flying the helos with normal assignments of controls rather than via offsets? (All FSUIPC does when you write to the offsets is send the controls to FS which your levers would do in any case if so assigned). Regards Pete

The weather stations are detailed in several files -- but not really editable by hand. The dynamic one, used by FS when downloading whether, is actually updated from time to time from the weather site. But such updates never add anything not already listed in the master lists in the FS Weather folder. In FSX, SimConnect does provide facilities to add 2temporary" weather stations -- used by ASA for Oceanic weather, for instance. It is actually possible to create one called "LGAV" via SimConnect, though I don't know if ASA bothers. Even FSX's weather station list does not include LGAV, which is why I asked whether there really was one with that ID. It does include LGAT. Regards Pete

You do know, I assume, that the throttle controls for the "true" helicopter models in FS are NOT the same as the throttle controls in other aircraft? I think the Bell is actually modelled in FS using the basic prop engine, whereas the others will be using the later-added helo model. Offhand I don't recall which controls are used in the helos, but I'll check now. [LATER] Yesits PROP PITCH to control the throttles in helos. The throttle controls operate the Collective. Regards Pete

Not version 3.0 I hope! The only supported version for FS9 is currently 3.90. there's a version 3.915 available in the Announcements above. Pete

In that case there's no weather station there. Let me check ... ... No, the Athens weather station in FS is still LGAT. If ASA is trying to set a weather station, by ICAO ID, in FS and it isn't registered in FS as a weather station, then ASA's attempts will fail. It should be able to detect this as FSUIPC will indicate it. You could enable FSUIPC's weather logging and take a look to see what is happening, but be warned, the Log will be huge! Only if ASA is actually managing to get and set LGAV weather. If it is doing it by setting weather at a Latitude/Longitude, and that point is near your aircraft, then the weather shown in WeatherSet2 for "weather at aircraft" should agree. But if any other circumstances apply, then it won't -- LGAV is not an FS weather station. Whether it is in real life or not I don't know. Maybe when they opened the new airport they didn't move the weather station? Maybe you really should be asking for ATIS from LGAT instead? Yes, that makes sense because LGAV is not an FS weather station. Regards Pete

Okay. It was a silly typo, easily fixed. Should have been tested years ago -- thanks for reporting it! Please download interim version 4.522 soon. The link will be provided in the Updates and Goodies Announcement above as soon as I've uploaded the build. Regards Pete

FSUIPC can only provide the weather which is actually set in FS. Why do you think it is wrong? You can cross check this by actually looking at and checking the weather in FS -- check the FS ATIS, for example. If there's any disagreement with what ASA provides you really need to deal with HiFi Simulations, who are the ASA publishers. Maybe you are simply not giving ASA enough time, once FS9 is ready to accept its inputs, before checking. It is not instantaneous. You also need to distinguish between the weather at a particular point on the airport with that at the designated weather station, which can in some cases be some miles away. WeatherSet2 is capable of reading the weather at the aircraft (its default mode) or at a Lat/Lon, or at the weather station. Try the latter -- enter LGAV for the location. Regards Pete

You are right! It doesn't work in FSUIPC4. I think you must be the first person who's tried it. I used this Lua plug-in: ipc.writeUD(0xD004, 1) timestamp = ipc.readUD(0xD008) ipc.writeUD(0xD00C, ipcPARAM) ipc.writeUD(0xD000, 0) while 1 do timestamp2 = ipc.readUD(0xD008) if timestamp2 ~= timestamp then tailnum = ipc.readSTR(0xD010, 48) ipc.display("Tailnum for " .. ipcPARAM .. " = " .. tailnum) ipc.exit() end ipc.sleep(10) end and simply assigned a KeyPress to it with the parameter (passed to Lua as ipcPARAM) giving the AI ID (the -ve of the Reference shown in TrafficLook). The above Lua program works fine in FSUIPC3 but not in FSUIPC4. I shall get onto this tomorrow - it is getting too late to investigate this tonight! Thanks. I'll get back to you. Reads by WideServer don't get passed to FSUIPC, they don't really act in the same way. when a client first reads something, WideServer gets it directly from the FSUIPC offset store, and adds it to a chain of offsets that particular client wants. Then, any time the value changes, an update is automatically sent to the client. The client application is actually reading direct from a local copy of an updated offset store. Because of this, there's always an enforced delay in responding to the first request for any offset, but thereafter it is instantaneous, being from local memory. Obviously Writes can't be treated in that way, so they get logged in FSUIPC. WideClient offset operations can be logged by the logging options in WideClient. Regards Pete

Sorry, but I don't know how a yoke comes into it at all. FSUIPC certainly isn't needed for any yoke I know, except the serial port ones made by PFC, but they also need a PFC digital control system. FSUIPC certainly isn't needed for any Saitek hardware. They provide their own drivers. Regards Pete

Why would you want that? That would preclude ever selecting an aircraft or flight when not parked on the ground with engines off. Why not, then, do it on the conditions I stated. Gear down, parking brake off, engines not combusting? If all those conditions are true, and the doors are not open, then open them. The Lua documentation supplied with the FSUIPC package gives you everything I can give. There are some working examples provided too. It also provides a link to the Lua website where you will find a complete reference section. There's also an Announcement above about the Lua facilities, in case you have lost some of your FSUIPC package. Regards Pete

Aha! Good! Pete

No, sorry. I don't know any way to get into the graphics side of things. The only reason there are some traffic provisions is that Microsoft actually provided a Traffic Tools DLL, and I was able to derive some of the procedure calls from that. Regards Pete

If that date was before your purchase of the FSUIPC Key, then that would look like an illegal or pirated registration, and would in turn make FSUIPC's service to the GoFlight modules erratic. They might then be attempting to renegotiate the connection to FSDUIPC in order to operate. Sounds like they do it on a one-second retry loop. Regards Pete

They might do with different actions in the parameter definition. FSUIPC cannot determine some of the mouse actions directly. Please check the documentation. If you can actually create the parameters via FSUIPC, you can experiment with the parameters (the number after the , at the end). Sorry, I don't have the aircraft so I cannot really help directly. Maybe other Wilco Airbus users might help? Regards Pete

Oh yes you can. FSUIPC can be used WITHOUT purchase. The purchasing only gives you access to additional user facilities. The main purpose, interfacing to other add-ons, if free, as it always has been. See http://www.schiratti.com/dowson , and the Updates and Goodies announcement here. There is no 64-bit version of either FSUIPC4 or FSX. Sorry, I don't understand this part. FSUIPC4 needs SimConnect -- it is how it interfaces to FSX for 99% of its tasks. If you have a problem, any problem, with FSUIPC4, I need to see both the Install log and FSUIPC4 log files, both from the FSX Modules folder. They'll be quite short. Paste them in your reply. Regards Pete

Cool! well done! ;-) Pete

Sounds like what they call a "dirty" or worn potentiometer. I have exactly the same problem, only probably worse, on my PFC cockpit, on the elevator trim. PFC have sent me a replacement pot, but I have difficulty fitting it (in the cockpit it is in a place I cannot reach, or even see) so I am awaiting an engineer's assistance for that. Contact PFC, see what they suggest. Regards Pete

No. The reference to the Module is the number after the R. The lines in a multi-line macro are obeyed independently, in sequence. One does not influence the other. The placements of the Module lines isn't relevant to the execution of the parameter lines. That could just as easily be: Module2="B767Afds.GAU" Module3="B767main.GAU" 14=MastercautionTT2 14.1=R2:X1cc0*X8bcc ;Mastercaution 14.2=R3:X4010*Xa1cc ;G/SInhibit However, I'm not sure I cater for comments ;xxxx at the ends of the lines. I'd need to check my code to see if I deal with that. Have you found it is okay before? If it doesn't work it isn't anything to do with the multi-line nature of the macro. Do the parts of it work okay on their own? Regards Pete