Pete Dowson

Usually many of the actions you have the Lua doing are similar, if not the same, across many or most aircraft. Even if they are different you can of course check in the Lua code which aircraft it is before determining what to do. I am interested in what applications you have for plug-ins which need so many separate scripts. Can you explain so that we can understand, and possibly suggest more efficient ways of doing things? The problem with expanding the number is the amount of error-prone work involved in changing the method of encoding the assignments. The limit is due to the number of bits available in the 32-bit value used -- 8 bits for selecting between 127 Lua plug-ins and 127 macro files. And any change in this encoding would render all existing FSUIPC configurations incompatible. There would have to be a conversion program or a complete restart for existing users, even if they don't use plug-ins or macros. Such an upheaval is really not a good idea during a period of continual development needed for MSFS. But, as I said, if we could understand how you are reaching this limit we could look at better ways. Pete

Well, as John implies, that error is listed as "Error 740: The requested operation requires elevation" so it is still an access problem. Seems odd though. Why would you need Administrative rights to access those folders? Take this folder: D:\User Programs & Data - Bruce That doesn't sound like somewhere which should need elevated privileges. So presumable all those programs need this instead? Anyway, I think you need to double check you have that setting correct for the shortcut you are using to start P3D5 -- Right click, Properties -- Compatibility - check "run this program as administrator". BTW I have never had any problems running anything without elevated privileges (except for AddOnOrganiser (and hence MakeRunways) which need it for access to places like AppData and ProgramData). But I always install the Sim away from any system folders, as indeed you do: FS path = "E:\00 - P3DV5\My P3dv5\" Pete

As well as posting your Log as John requests, check your INI file -- make sure there's not another [Programs] section. Pete

Well Windows drop-down lists don't work like that. It would involve building a new list completely each time. Maybe John will consider it for a future version, but it seems odd that no one has requested this in the 20 year history of FSUIPC. And John has a lot on his plate at present with MSFS developments. Thanks for the suggestion though. Meanwhile you can always make use of the provided lists (okay, not for your Lua add-ons, but you are more likely to remember those names anyway). Most text editor/viewers provide the sort of search you describe. Pete

There's a way of doing this described in the User Guide. Check the boxed section entitled Offset Increment/Decrement Controls on page 25. Pete

You hadn't made any settings in the Honeycomb Yoke profile, so any profile made from it would also have no settings. Default button (and keypress) settings apply in all profiles unless you make a different setting for specific buttons or keypresses in that profile. This is as described in the User Guide. Pete

You can start typing, just the initial part, and the list moves to the first control starting like that. I never have trouble that way. What exactly do you have in mind? Pete

Sorry, I don't understand this bit. What exactly doesn't detect it? Do you mean SerialFP2 or whatever it is called? So have you used LINDA with the MCP before? I don't know LINDA -- maybe you should ask their support? If the device isn't detected, how do you know it is COM3? Have you referred to the document about using VRInsight devices in your Documents\FSUIPC7 folder? Pete

If it isn't in the drop-down list at present, then the only way I can think of is to assign your button to a keypress instead. I don't think you can use ALT at present (a SimConnect problem), so you'd first need to assign a different keypress in MSFS. Pete

We are hoping (expecting?) all of the controls to be connected up one day, and have requested this of Asobo / MS. Currently the only way I know for views is by assigning the appropriate keystrokes (making sure they are assigned to the view action you want in MSFS of course). For those involving ALT I think you need to re-assign tham as ALT combinations can't be sent via SimConnect at present. So, for simple look left / right /up / down try assigning your button or POV to either Ctrl+Left, Ctrl+Right, Ctrl+Up, Ctrl+Down or maybe the Shift+ versions. I'm not sure off-hand which does what of those two sets. Pete

That's why these things are explained in the Installation Guide. FSUIPC6 and FSUIPC7 installers now follow the proper Windows 'rules', where documents go in your Documents folder under the product name. It may seem odd to put documents into the "Documents" folder, but that's now the way it is! 😉 (I was in revolt with my products, liking everything together. But I'm an old codger and now in retirement). Pete

It's alongside all of the other documents installed with FSUIPC7, in your documents folder in the subfolder called "FSUIPC7". Does this mean you have not even looked at the FSUIPC7 User Guide yet? The places where things are installed is explained in the Installation guide supplied in the original ZIP you downloaded. Pete

LOL! Same here .... just ask John! 😞 Pete

ONLY with your own programming. No. it recognises the connection, and receives commands from it. What it does with those would have to be determined by a Lua plug-in which you'd pre-load via an [Auto] entry in the FSUIPC settings (INI file). For full details you need to read the "Lua Plugins for VRInsight Devices.pdf" document which you should find with the rest of your FSUIPC documents. Pete

Okay. Thanks! Pete

Ah, I think the "functionality" you can check is just that it connects to MSFS okay, that the Logging works, and that the interface for FSUIPC applications (its main purpose, after all) is all working okay. Those things are free in any case. Maybe the wording on the sales page could be clearer. Pete

Not really. Why do you understand that? Best to make an FSUIPC7 foler so you know where it is and can find it easily. That can be on any drive. You are missing Registration. Either you have not purchased it and so have no registration key, or you are making an error when entering the details. Are three parts (name, email and key) must be exactly as set by SimMaket. Pete

I don't know if the FSL A320 responds to the normal FSX controls. Have you checked your controls with a default aircraft? That's the first thing to do. The more sophisticated add-on aircraft tend to supplant the systems in the flight sim with their own, for added realism rather than the more generic treatment. As a result some of the regular controls simply don't work. If you prove to yourself that your controls are okay (by checking on a default aircraft), then the next step is to find out what works with your choice of add-on aircraft. It might be that you have to use Mouse Macros or L:Vars (local panel variables). Pete

The only picture showing anything by PFC is the one of the Cirrus console, not just a yoke. You have the incorporated throttle quadrant so why aren't you making use of that? I've never seen a Cirrus with a slider on the yoke and I don't see one on yours!? And the only Cirrus I had was the one I needed to develop the PFChid.dll driver, as it was a USB HID device. Did they make serial port Cirrus before that? I'm sure they must mean the default throttle AXES -- i.e. the Axis ThrottleN Set controls. They can't expect folks with 4 lever throttle quadrants to control all engines with one lever! That is just not PMDG! Anyway, the problem with your question here is that you've proven that your controls work fine with FSUIPC and all other aircraft. As we can't support PMDG's aircraft we are unlikely to be able to solve it. and as PMDG sound, if not unhelpful, perhaps misleading, it seems your only recourse is to try the various options till you find what works, starting with the main advice we have to give to all PMDG users: Assign only to AXIS THROTTLEn SET controls, and don't calibrate in FSUIPC. Pete

I don't know. Might be a good question for the AVSIM forum -- not sure when I'll get time to fly to Madrid! Still doing ground testing mainly, with the the updates which I've been getting -- not just the P3D ones, but ProSim and its ancillaries, Active Sky and others. Also MSFS 'compulsory' updates which often mess stuff up we've done before. But I've made a note to do some shorter flight llke Valencia to Madrid in the near future. Pete

Which aircraft is this with? you've not yet said! The PMDG dedicated offsets are all READ ONLY as i said. But none of these PMDG offsets are read by the PMDG. They are only places where the PMDG settings are stored for you to read. Whatever you write there will be overwritten (corrected) next time anything in the PMDG aircraft is changed. For PMDG aircraft you have to use the CONTROLS they define, not any offsets. Please read what I write in my replies. you appear to have simply inored the last replay! 😞 Pete

Well, I've been involved with PFC for many years, and i've never seen anything about a yoke with a throttle slider! Are you sure it's PFC? Can you show a pic? So your yoke is a regular joystick type device recognised as such by Windows and not needing any PFC module loaded in FSUIPC? Right? Now that doesn't match what you said about P3D seeing it. "Using PFC" means you have a PFC dll loaded by FSUIPC. The two things can't both be true, surely. And what do the other throttles on that page say after you calibrate? They should all move together! Sorry, but your post is rather confusing. Please be much more specific on the detail next time you post. Pete

I'm afraid I don't understand what you are talking about,. What's a "belt signal" and what offset are you talking about? If you mean you are trying to write to the special offsets added for a PMDG Boeing aircraft (unspecified!!), then, I'm sorry but you can't. The interface provided by PMDG doesn't work that way. You need to look in the SDK folder installed by PMDG for your aircraft. There's a file there of type .h. Look at that. The first part lists the data, the read only data supplied for you in the FSUIPC offsets if enabled. The end part lists all of the custom controls which you can use in FSUIPC assignmens to operate your PMDG cockpit. Ah! Well, in that case you definitely haven't programmed your system for PMDG aircraft! Those just do not use the same controls or offsets which default and simpler add-on aircraft use. PMDG implemented their own systems, bypassing those in the default sim. Pete

Sorry it wasn't clear. "Rounding down" is the same as truncation if you mean just discarding the fractional part. Pete

Just put your comment BEFORE the FSUIPC annotation. The latter is always added to the end and replaced at the end. eg: 0 = PC, 6, K117,8 ;flaps -{Key press: F6} - ; flaps Of course, if you used the relevant flaps control instead (the one invoked by default with K117) then the automatic annotation would remove the need for your comment. And it would be more efficient as well of course. you are using a keypress which the Sim then looks up to determine the action to use. Or do the flaps controls not work in MSFS? The INC and DEC ones seem to work for me, but maybe not in all aircraft? Pete