Pete Dowson

There is a known temperature problem in P3Dv2, but whether this is the same I don't know. Nevertheless it needs reportinbg to Lockheed Martin on their Forum, not to me. FSUIPC is simply giving you what P3D gives it. And FSUIPC most certainly does not set any temperatures itself. Pete

Internally Windows counts button from 0, and so does FSUIPC. It doesn't need "correcting", FSUIPC is correct. Pete

Yes, that's cirrect. That's if you choose to use the Title Bar. You can alternatively display in a window or just in the Log file. Pete

Good! I'm pleased you got it sorted. I'm not familiar with CAMERA definitions at all, or really moving the eyepoint. I used to use EZDOK for view positions, now OpusFSX. But because I don't have any cockpit views on the projected screen outside the 'real' cockpit I don't need to raise and lower the view -- I can just lean forward more and look down out the window! ;-) Regards Pete

There are some keys which will be seen by other parts of the system before FSUIPC can get them -- the ALT key is the main one to avoid. I'd guess keys like Print Screen, Scroll Lock, and so on might also be problematic too. Also some other things can get keys before fSUIPC. Other programs may make themselves intercept earlier in the queue, for example, and certainly things like menus and dialogues divert all keypresses to their own ends. Regards Pete

Yes. Pete

Do NOT add your own [LuaFiles] section. That is generated by FSUIPC automatically based on the Lua files it finds in the Modules folder. It is nothing to do with the [Auto] section, it is only used when assigning buttons or keys to L:ua plug-ins. Pete

I'm pretty sure that there are no rogue installers that will delete your settings. They are all help in the FSUIPC4.INI file and that need not be touched. However, you should re-install FSUIPC in order to get it back up to date. FSRealTime is a pretty old program and I'm sure any copy of FSUIPC it installs will be well out of date by now. You found a copy of FSRealTime which is designed to install FSUIPC into P3D 2? Wow! Where? I thought FSRealTime was no longer in development. Ah! That sounds like something done by a migration tool, which probably tries to fool installers by making P3D look like FSX. Try renaming those files back to their correct names. If you are lucky it's only the renaming which is messing you up. Otherwise you need to find support for the migration tool I think. Pete

Yes. The keypress or button is the instigator, whatever you program it to do is the reslut. That might be to send a control + parameter to FS, or, in this case to run a plug-in with a parameter. Yes. If the key is not assigned at all in FSUIPC, either in the Hot Keys section, or the Keys section applicable to the current profile, then it passes on to FS. I'm not really sure why your question arises? What else could it do? Pete

Are you sure this is not simply the repetition, just a single use hardly making any difference? With keyboard use you'll get the keyboard repetition rate. Multiple assignment of the control to a button would do the job. Try using the Event logging in FSUIPC to see what happens when you get the result you want, and simply emulate that. If you run FSX in Windowed mode, temporarily, you can enable FSUIPC's console log and see the resluts in real time on screen. Pete

Shouting? Which part? Do you mean the "NO" where it is merely emphasis. I was just too lazy to make it italisized. Sorry. If you are no programmer why are you so intent on making your simple needs into a Lua plug-in. Lua is a programming language. Why not simply use the assignment facilties as I keep begging you to do? You seem to want to baffle yourself, and I am trying to pull you back. I can't see how you looked up the KeyPress function which explicity showed one or two parameters with explanations, yet you tried something with 3 parameters not following the stated requirements at all. If you didn't understand what you read why not ask about it instead of making up your own versions? I can expand upon things you don't understand, but not once have you said what it is you don't understand. You simply want to forge ahead down a path I keep advising against. Agreed. So why not ask questions about it? Lua, not Lau. Sorry to correct you -- originally I thought it was a typo but I see you are consistent. Even then, such sequences suite multiple assignment or macros better. after all it sounds like a simple list of controls to be sent. Programming (which is what Lua is all about) can include decision making, lops, and other clever things, evidently not needed for this. Pete

Okay. So now they are standard joystick type devices, not PFC serial protocol devices? No. Where do you see any such notice in the FSUIPC screen? FSUIPC has no serial port handling software in it whatseover other than the GPSout output and the Lua COM library for plug-ins. No, PFC.DLL and PFCFSX.DLL are drivers for the older, original PFC serial port protocol devices, not the more recent USB ones. If they are standard joystick devices seen by Windows and FSX then FSUIPC4 sees them too. It uses the exact same DirectInput routines in Windows for such devices. Where are you looking? Why install it if you don't know what it does? It is the driver for the PFC USB-driven HID devices like the new consoles. Sounds like you badly need PFC support. I'm afraid I am not the support for PFC devices. I have no idea why you want this to happen. It is almost always the other way about, that folks need a COM port adapter to plug into a USB socket because modern PCs do not come with COM sockets -- that was needed for the older PFC serial devices which you say you've now dispensed with! Pete

There is NO [art of any of my documents which shows three parameters for KeyPress. There are one (for a normal key) or two parameters when you want to add shift actions like Control, Alt, Shift, Tab, Windows and Menu keys. The shift codes are simply added together. It is dead simple. i really don't understand what the fuss is about. If you read something and don't understand it, ask the question and I'll explain. but you have to look things up yourself and not invent your own formats. I find it absolutely baffling that you don't understand simple keycode values yet want to do over-complex things like use Lua when a simple direct keypress assignment would do. It's really weird. Pete

Yes, it is wrong. You could actually look in the FSUIPC4 log file where it would tell you so. That's where errors will be announced! You need to refer to the FSUIPC Lua Library document for Lua library function syntax. I would need to look things up too (I don't remember everything!), so really it would be quicker for you to actually use the documentation yourself. It is in your FSUIPC Documents folder, as you were informed in the FSUIPC "Installing and Registering" Guide. Once you get used to looking things up in the documentation it will a lot quicker for you too, with other similar queries. Regards Pete

Yes, that's probably the easiest way to use that plug-in. [Auto] sections are just ways of running macros and plug-ins automatically. You can have different [Auto.<profilename>] sections for different aircraft profiles too, for aircraft-ralted plugins and macros. All macros and plugins are loaded from the Modules folder by default. You can have them elsewhere but you then need to specify the path. Pete

Could you re-work it as a User Contribution, in that subforum please? It will be available to others more easily then. Just explain what it is for, too. If you leave it here it will gradually scroll way out of sight forever ... Thanks! Pete

The current Lua library facilities most certainly can read and write LVars. The facilities are in widespread use. If your call is "ipc.readLvar" then the error indicates that your version of FSUIPC is out of date -- you must always keep up to date. Facilities are added over a period, they didn't come into existence all at once. The function readLvar only exists in the ipc library, and it is one of those not implemented in WideClient.. Regards Pete

No, no, that's all the wrong way. :sad: All the "ShortAircraftNameOk=substring" setting allows you to do is shorten the name of the aircraft so it matches a part of the full name of all the aircraft you want to be covered by this Profile. So, in your example: [Profile.Twin_Piston] 1=Beech Baron 58 Paint1 2=Cessna 310 BB 3DAnalog 3=Cessna 310 N5225J 4=Cessna 310 N5077J 5=Douglas DC-3 Paint2 6=Cessna 310 Song3 freeradio 7=Cessna 310 SB freeradio you could have:just this: [Profile.Twin_Piston] 1=Beech Baron 2=Cessna 310 3=Douglas DC-3 or even just: [Profile.Twin_Piston] 1=Baron 2=310 3=DC-3 provided these shortened versions would not include anything you don't want included. "310" is probably a bit dangerous in this regard, but the others might be ok -- unless of course you have a "Red Baron Fokker". ;-) This merely ensures all variations of those aircraft would be automatically handled in this, the "Twin_Piston" profile. So, I think you are making out it is very complicated, whereas it is just as simple as that, an abbreviation for the aircraft so the little variations don't all have to be set individually! I'm not sure where it goes wrong in the documentation to result in such a severe misinterpretation. :sad: Regards Pete

Not sure why you'd opt for something more complex over something which would do the same job more simply. In any case you'd not "emulate key presses" as implied in your title, but simply send the appropriate control numbers, from the list installed in your FSUIPC Documents folder. Again, just another control assigned in a multiple assignment or in a macro. No, there are no offsets for the "eyepoint", which is what you are talking about. You have to use eyepoint controls -- EYEPOINT UP and EYEPOINT DOWN, in fact. You can send them from a Lua plug-in, of ocurse, but that's just a more long-winded way of doing via a straight multi-entry button or key assignment or a macro. Regards Pete

Just copy the FSUIPC4.INI file over from the FSX Modules folder to the P3D modules folder. If you also use any macro or Lua files (.mcro and .lua) then you need to copy those over as well. Pete

If you mean the Schiratti site, I have no control over that. I have asked Mr. Schiratti to update the wording, but he is not available at present. Nevertheless, the link on the Schiratti site does download 4.923. The link it to the same files as available here, in the site I can control, Download Links subforum. There's a pinned notice at the top pf this Forum and also on the Prepar3D Forum om AVSIM which tells you that you must use 4.923 or later for P3D v2. Any earlier version pre-dates the release of P3D v2 and cannot possibly work. Regards Pete

You don't need a Lua plug-in to do that, only a button or keypress assigned which has the right number of such keypresses programmed. Just program once in the FSUIPC options, then edit the INI file to replicate the resulting line with subsequent line numbers. It would be better (more efficient) to assign the actual FS control directly rather than the keypress which FS translates into a control. If you don't know what it is just enable FSUIPC event logging and the log will show the name when you use it. Anyway, if you just need a permanent change in the view, doesn't this get saved when you save a flight, so it is reinstated when you next load? Regards Pete

Maybe. The picture you posted show both axes stuck with high input values. I would really suspect dual assignment -- i.e. something else is also assigned to those axes. See if you can check through alternative controllers automatically assigned in P3D. It happens in FSX so it can no doubt happen in P3D too. It may be a controller that you no longer have plugged in but which still has an active driver. Regards Pete

No, because only Lua plug-ins can read L:vars. The thing to do is get your Lua loaded using an [Auto] section in the FSUIPC4.INI file, but wrap everything you've done in a function which is called by an event.Lvar call. Regards Pete

Why are you using out of date and unsupported versions of FSUIPC whenj only 4.923 and later will work on P3Dv2? Pete