Pete Dowson

I wouldn't convert it the way you've done it. I'd use string.format("1%02X.%02X", STBYNAV2R/256, STBYNAV2R%256) And why are you bothering about the last 0 or 5. It's always understood that its a 25, 50, 75 or 00. All the normal radios only show 1xx.xx not 1xx.xxx. Pete

You posted the same thing twice, and this is the wrong place to reach me fast. Please be more patient and don't keep reposting. I am very sorry, but I do not understand the question. If you mean how to get the position of the plane, i.e. the Latitude and Longitude, then FSUIPC supplies these through offsets. You would need to write a program to interface to FSUIPC to read the Latitude and Longitude offsets. I'm sure Paul Henty's excellent .NET DLL would help you with the programming side. In future please entitle your threads with the actual subject of your question. Pete

Didn't you look at the Lua code? You have to edit it to address your specific device. As it is, it only works for the 1st GoFlight RP48 connected. And it is set for the 4 separate rotaries on that device! You can assign "Lua rotaries" to a button or keypress in order to start it for testing purposes, but once you have it working you should start it using an entry in the [Auto] section of the INI, so it just runs in the background all the time. I think you might need to read up a bit more documentation for this. Did you not find the assignment to both press and release sufficient? Pete

It occurred to me later that the stalling every 10 minutes could be some sort of Autosave being executed, either in FSUIPC or in another program. Could that be so? With PMDG aircraft (certainly the 737NGX and 777X), the aircraft add-on itself freezes the sim whilst collecting all of its internal data for saving in its own files. This is in addition to the normal FS flight saving action. Whether this freeze is long enough to cause the SimConnect problems is probably dependent on all sorts of things, like processor and memory speed, disk speed, virtual memory availability (for caching) and so on. If this is the case, you might want to try without the Autosave if it's enabled somewhere. I know some folks use it with the PMDG aircraft without problems, but it can be so variable as I've just explained. Pete

If the mode switch is not one of the standard joystick buttons, 0-31 (in FSUIPC, or 1-32 probably in Saitek programs), then FSUIPC can't see it in the normal way. If it is readable by Saitek programs, then it would be readable by a Lua plug-in using the com library HID functions. There are some examples of reading buttons from any HID device (even non-joysticks) and mapping them to FSUIPC's virtual button set. Once the mode switch is readable, then the programming of multiple functions on the other ("real") joystick buttons becomes a matter of conditional or compound button programming in the FSUIPC4.INI file. There's a section on that in the FSUIPC Advanced User's manual, and you might find some of the other user's efforts in the User Contributions subforum useful too. I'm surefolks have done this before but I've not been able to find one posted yet (the search abilities in the Forum are not too useful I find). I did find this which may also be useful: Toggle switches on X52 Pro stick Pete

No. FSX/P3D only provides nearest airports to the current user aircraft position. You'd need to search a database for your needs. Pete

Why did you post this support question under "FSUIPC Client DLL for .NET"? It has nothing to do with that. You are lucky I spotted it. Please always post support questions to the Support Forum. Here, in other words. SimConnect has crashed or stalled completely. Started happening about 58 minutes into the session. Looks like it was able to recover the first few times, but repeating about every 12 minutes or so for the next 2.5 hours! Those reconnections alone would have caused some pausing. Then SimConnect just died completely and FSUIPC was unable to reconnect. Your 8-10 seconds were those attempts, but it went wrong hours before. Looks like the system is way overloaded. Perhaps it was running out of memory? You can make FSUIPC a little more tolerant of an overloaded SimConnect -- increase the SimConnectStallTime parameter in the FSUIPC4.INI file. It defaults to 1 second -- ie. it allows up to 1 second to receive data from SimConnect. And that is a LONG time considering that it is supposed to be receiving all the aircraft flight parameters on a frame by frame basis! However that is masking the problem, maybe making it last longer, rather than solving it. Pete

Most rotary encoders send a "Press" for one click then a "Release" on the next. So you can usually get one iNC or DEC per click by assigning both Press and Release to the same control. That's be twice as fast. You can also use a Lua plug-in to get bigger increment/decrement amounts for faster turns without losing the ability to get a single increment with one click. See the "rotaries.lua" plug-in in the Examples provided in your FSUIPC Documents subfolder (in the Modules folder). It is actually programmed for any HID device, not just a joystick input -- I think it is currently set for a GoFlight RP48 unit which has 4 rotaries. You could either treat your device as a HID device instead of a joystick (joysticks are one type of HID) -- you'd need to look at the scanning part of the FSUIPC log (since version 4.947 joysticks have been logged with the details you'd need), or just re-program the Lua to read joystick buttons instead. There are ipc library functions for that, but, better, you can use events to call the routine on joystick button changes rather than poll on a timer event. Pete

FSUIPC4 uses SimConnect for 99% of its functions. SimConnect is installed with FSX and P3D automatically. You cannot have "no SimConnect" unless you go back to FS2004 or before, or Xplane! Pete

You don't buy a specific version. The SimMarket site sells just the Registration code. You must make sure only that it is for FSUIPC4, for FSX and P3D, not FSUIPC3 which is for FS2004 and earlier. The registration code covers all versions from the original 4.00 back in 2006, until whenever the last version 4 will be. You are not only entitled to keep it up to date, you are expected to -- especially if you want support, because I can only support the current version. So you can download and install from here (Download Links subforum), or using the link on the SimMarket site, and it will be the current version either way. Pete

You should be using 4.947c, the current supported version, or even 4.947d. Please see the Download Links subforum. FSUIPC does not "lose" assignments. They are all recorded in your FSUIPC settings (the FSUIPC4.INI file in the Modules folder. If the joystick isn't being sen by FSUIPC then it probably isn't being seen by P3D or Windows either. Did you check? I'm not aware of anything causing a sudden stop in a joystick -- there are many reasons for it to stop working whilst not in use, but it should "come to life" when used enough. When you say "assignments" do you really mean axis and button assignments in FSUIPC itself, or just calibration? Pete

You mean visually? Depends on how realistic the aircraft modelling is I suppose. But in terms of effect it should be like the real thing, probably just offsetting the position. What's the difference? Trim is trim is trim. No, it'll be a bug in the code. Primary controls are axis controls, not offsets. The elevator trim is an axis control too. Rudder and Aileron trim control is done by writing to SimConnect variables "RUDDER TRIM PCT" and "AILERON TRIM PCT" but there are FS controls too -- for INC DEC and SET (SET being effectively an axis control). FSUIPC assignment uses the SimConnect variables because the controls weren't available when those were implemented. Pete

Do you mean setting the Decision Height (DH)? Or is that orange bug something else? If so it is proobably local to the gauge. For the DH all you needed to do was search the list of FS controls, installed in your FSUIPC documents folder, for "Decision", as I just did, and it would find these two: INCREASE_DECISION_HEIGHT DECREASE_DECISION_HEIGHT Another way to find FS controls is to enable Event logging in FSUIPC, use the switches on the FS cockpit, and check the log. Pete

Sorry I don't know the answer to that either. If Saitek drivers write direct to FS then there will be conflicts. Pete

No, when you disable controllers the controllers are disabled! Assign buttons in FSUIPC. You can still use FSUIPC with everythnig assigned in FS, but FS offers only a subset and doesn't provide facilities for different assignments for different aircraft. Just install. There's never any need to uninstall, and in fact there's no option to. Pete Pete

Have you tried Saitek? FSUIPC doesn't drive panel indicators, you need a driver. Pete

Maybe other Saitek users can help here, because I'm sorry but I don't know. I don't use Saitek. Without paid registration there are no joystick assignment facilities available. The "free" installation is only an interface program for other programs. I assume they installed it because something else they installed uses it? Version 4.939u is many versions old. The earliest supported version at present is 4.947c. See the Download Links subforum. If you don't pay for FSUIPC, I would say no, as FS would receive conflicts. With a registered FSUIPC you can assign different devices for different aircraft types, using Profiles. No. If you disable controllers in FS then controllers are disabled in FS. Why would there be bits of controllers still usable there? When you download the currrent version of FSUIPC the ZIP contains the Installer. You run the installer to install AND register. Of course, there are instructions in the ZIP. Pete

What is the control? If it is a toggle you'd have to assign it to both Press and Release. If it's an ON with a corresponding OFF, assign ON to Press and OFF to release. But it means YOU holding the button pressed. Without writing a Lua plug-in there are no delay facilities built in to the button assignment itself. You can do it with a plug-in. Pete

It's one of the many bus in Version 3 of P3D I think. Please report it on the L-M forum. They are trims just like the more-used elevator trim, and used to offset small irredularities and asymmetries in thrust or surface movement. They can also help in crosswind takeoffs and landings to allow less side pressure to be used on pedals and airleons. Sorry, I don't really understand the questions here. What "raw" where? Pete

Sorry, but I cannot support old versions. Please first update to a supported version -- 4.947c is the earliest supported build. Incidentally your second crash is actually in SIM1.DLL, which is the main sim engine in FS. I would check the aircraft you are using is installed correctly. The first crash, the one in FSUIPC, would be useful data for me but only with the current version, so after installing 4.947c using the Installer, please update to 4.947d. Both are available in the Download Links subforum. Pete

Right. Good. I'm glad it isn't the worry I thought it might be. Hmm. Wonder why it has to be turned off for the hotkey to work correctly. Thanks for the information. Pete

If you press F8 yourself whilst P3Dv3 has the focus, instead of going via a button press and FSUIPC, does it work? I'm just downloading that utility -- seems it is shareware and I can test it without buying it. [LATER] Okay, installed it, changed its hotkey to F8, and it works both from an FSUIPC assigned F8 keypress and from the keyboard, both in P3Dv3 Windowed Mode and in its full screen mode. So something is different, either in your P3Dv3 setup or in Windows. That's a puzzle and a difficulty, because I cannot really help without being able to have it go wrong here. Anyway, if it doesn't work either when pressing F8 on the real keyboard then it obviously isn't anything specific to the FSUIPC assignment to a button, so you have real ground for reporting it to or asking advice from Lockheed-Martin. If it works direct from the keyboard then I'm stumped, because I cannot reproduce this. FSUIPC seds the keypress in a way which is supposed to emulate the keyboard, and there is certainly not something changed in FSUIPC. Pete

To find out if the helicopter control responds to an FS control, use FSUIPC's logging. Switch FS to Windowed mode and enable Event logging and the Console log in FSUIPC's logging tab. Then operate the switch in the FS cockpit display. If this invokes a standard FS control it will be logged, by name and number. Pete

It should. This sort of thing has already been reported in another thread. It looks like P3Dv3 is doing something different, but I don't know what. FSUIPC just sends the keypress in the same way regardless of the version of FS. I've just tested it in several ways and these are my findings: A program which uses the Windows Hotkey facility to detect keypresses and use them no matter what currently has the keyboard focus still gets those keystrokes even when P3Dv3 has the focus. So P3Dv3 isn't preventing such hotkey use. A program not using the Windows Hotkey facility will only receive the keypress if it is given the keyboard focus first (such as by clicking the mouse on it). I think this is the way it has always been, at least for hotkeys and normal keyboard focus changes. I am using Win7-64, so it's not a Windows version difference! So the question arises is "what is different about the program wanting the keypress". You said Now my screenshot program is "Screenhunter" from Wisdom-soft, and I normally use Ctrl+Function keys for its various options -- Ctrl+F4 for a full screen shot. I changed its assignment to F8 to match yours, and it worked fine. So I don't understand what differences are doing this. What it your screenshot program? If it is freeware maybe I can try it and see why it is different. I'd like to report it to L-M to see if they can fix it in P3Dv3, but without knowing why it isn't working for some programs only I wouldn't expect them to be able to do much. Pete

I don't remember the exact explanation for this, but It's to do with the way USB devices work, relative to an ordinary serial port device. The COM functions were designed for normal RS232 type connections (like my PFC equipment, and USB HID support added later. FSUIPC is effectively polling continuously for data, and most ordinary serial devices supply none unless there is some. But USB returns a packet every time, whether anything's changed or not. The readlast function was added to make things more efficient, rather than processing every single frame in a loop. You'd use your changed code for normal serial port devices.otherwise you could miss stuff. Why did you change a working program in any case? Pete