Pete Dowson

Thank you! Good, well done! Pete

Aha! This is what you should have said in the first place! 😉 It isn't just "*.PNL", it is *-FLT.PNL" you need! The Autosave only fills in the AUTOSAVE FRI 073515 part. It cannot guess the bit you missed out! Pete

I'm sorry, that is something I don't know and can't really help with. Ideally the aircraft author should publish these, but since they are really internal design matters that never happens. What folks do is experiment. On way to see what values they take is to use the Log LVars.lua plug-in supplied in the Lua plugin examples ZIP. Which put that in your modules folder, load the Sim, and assign a keypress or button to "Lua Log Lvars". Then, if you use that, it gives you a real-time log of the values on screen. You can operate the switches and see how the values change. Pete

Hi, As John asked, "what files are not being deleted?"? Although your thread title sweepingly states "AlsoManage not working ...", are you reallly sating "Alsomanage isn't working for this one add-on aircraft"?, because you seem to have quote a few AlsoManage entries. Do i assume this is the entry which you say doesn't work? AlsoManage11=QualityWings\QW787\PanelStates\*.PNL Do you think you could actually list the files which you think should be deleted and which were not. If there's a lot, just give a batch please. The LOG file, with the settings John gave you, would have listed an error if the deletion failed, which it doesn't, which makes me think you are really talking about some variations not covered by the *.PNL template, where the * is replaced by the usual "AutoSave Thu 204040" type of naming which is what Autosave generates (obviously with different days and times). Pete

What do you mean "still not working"? "Stil"l, as in "you tried before and it didn't work"? And what exactly is not working? Without knowing EXACTLY what you are doing I can't tell you what you are doing wrong. But if you saved those two lines above in a file called, say "CRJ.mcro", and this was properly saved in the Modules folder, and THEN loaded up P3D or FSX or whatever it is you are using, then the macro "CRJ:L:ASCRJ_ECAM_DOORS" would appear for assignment, in its correct alhabetical order, in the drop-down list for any Key or Button assignment. This would even be true if the L:Var ASCRJ_ECAM_DOORS didn't exist or the aircraft wasn't even loaded yet. You don't need to be a "code writer". The L:Vars are not JUST names. They must have values associated with them. It is the values which really mean something, whether it is simply 1 for "ON" and 0 for "OFF", or 545 for something like a throttle value. If you want to use L:Vars it is because you want them to do something, right? Well, to make them DO something you have to set whatever value that is needed to make that happen! This value is the "parameter", and I call it that because that is how the place in the assignments screen for the value is labelled. No, as I said, just add a new line for each in that one file. Use a new line number (the 1= in your file so far) for each line, so 2= then 3= etc etc). I really cannot explain this any more clearly. I am not a teacher, I am just anoother disabled guy (sight in my case) trying to help but I do have limits. Sorry. But for me to say what you are "doing wrong" you really do have to spell out what you are "doing". OK? Pete

Well, it is precisely as written in the documentation! For example: [Macros] 1=L:ASCRJ_FCP_WHEEL=Set saved as "CRJ.mcro" would add the entry CRJ:L:ASCRJ_FCP_WHEEL to the assignments list. The value you want to "set" would be the parameter in your assignment. If you wanted a fixed number make the MCROO file line show this, thus: 1=L:ASCRJ_FCP_WHEEL=Set,value where value is whatever you want written. (But if you have a fixed value like this bear in mind you can't use that same L:Var with a different value, unless you make another MCRO file with a different name (eg. CRJ2.macro). It is more flexible toput the value as the parameter when assigning. Pete

You'll need to make a text file containing macros and put it into the Modules folder. Say CRJ.mcro. Look in the FSUIPC Documents subfolder in the Modules folder. There you will find a document FSUIPCx for Advanced Users (where x is 4 or 5 depending on your version). Search for the section entitled Macros to Change LVars. That tells you exactly how to make macros to do what you want. Just number the lines 1=, 2=, 3= etc (the number isnt used. it is just part the the CFG/INI format used for the file). Then load up the sim, and in FSUIPC Keys assignments drop-down you will find all your macros listed as CRJ:name ... ready for you to assign as you wish. Try just one and test it first just so you know what you are doing thereafter. Pete

If you had perused the place you would have seen that this, like mst of the other little subforums, are reference places, not Support Forums (the exception being the one on the .NET DLL of Paul Henty). The main forum, where the vast majority of pasts are, is where support questions are asked. The problem with posting in reference subforums is that they are unlikely to be noticed until someone refers to them to find some answers not questions), but in the even of the post being from someone new, only the moderators would be able to see such a post. Hence the many hours you've been left waiting for an answer. You are lucky. Often it is so long since the post was made that it is simply deleted as probably or no current re;evance. Yes, assign on the right-hand side or the axis assignments tab to the Throttle Incr, set the range for the whole axis movement, and tick the UP option and the repeat whilst in range. Do similarly for Down assigning to Throttle Decr. All this is described in the User Guide, in the chapter of Axis Assignment, about 2-3 pages in. Pete

The [Programs] section is not part of the Profile arrangements, which are currently concerned only with assignments, calibrations and plug-ins. But the facilities you want have been requested already in another thread -- quite recently -- and is on the list for implementation in FSUIPC5 during 2019. I can't promise a timescale. At 75 I am retiring from FSUIPC5 development and my son John will be taking over. Pete

No. The plug-in Lua libraries don't offer any graphics facilities, and if you mean on the FSX or P3D screen, it would be very complex in any case with differences in full screen and windowed modes, docked and undocked windows,, etc. Text display via SimConnect functions is supported. They are relatively trivial. I don't think SimConnect offers any real graphics features. You might be able to insert objects, and design an object which just looks like a line, but that would appear in the 3D scenery view and not really be a line on the screen. You could also design a gauge with a graphic which is just a line, and have it loaded as part of an aircraft panel, but then again it isn't a "line on screen". You'd probably be able to do it using normal Windows programming, external to the sim program, and make sure it is "on top", though doing that with the sim in genuine full screen mode (FSX) might be difficult. Pete

Strange then that you have macros for 2 engines in one and 4 in the other? That was what I was going by. I know nothing of those aircraft.*** There's nothing I can do. According ot L-M, since the fixes they made for version 4.4., the same panels/gauges will always have the same rectangle numbers. If thst isdn't working it is an L-M problem, as i can't do anything about P3D internal coding. Please submit your evidence, including probably the Aircraft CFG and Panel files, in a bug report to L-M. There's no point in me acting as an intermediary. Pete P.S. I've just looked up those aircraft. I didn't reallse they are really sort of later versions of the BAe-146 "whisperjet" design. Nice to see that really hasn't died -- it was shocking to see photographs of so many lined up in that desert in the USA as unwanted and disused.

Good! Thsnks for confirming that all is now well! Pete

This is implemented in a limited interim version, FSUIPC 5.150a. Please download it via: FSUIPC5150a.zip. This is just the replacement DLL to go into your Modules folder. Pete

You posted pictures which appear to be complete screen grabs with images far too small for me to read. Please do not do that! Words are better, just type them. The only thing the pictures really tell me is that FSUIPC is installed okay, and is running -- so there MUST be an FSUIPC5.INI file and an FSUIPC5.LOG. Either that or your Modules folder isn't set to allow files to be written without the program being "run as administrator" Okay. That may show the problem: Attempt to set the ACL entries for Modules access permissions failed, error = 1332 This is a problem which only exists since Windows 10, and only when you let P3D install in Windows\Program Files. That folder is protected unless you run "as administrator". Now, for most installations, this isn't a problem because provided you run the Installer "as administrator" it is able to change the permissions (just on the Modules folder) automatically. But on just a few systems it is prevented and gets that Error 1332. So, first, if you didn't run the Installer by right-clicking and selecting "run as administrator", please do that now (no need to re-enter registration, just say not now). If there still is no FSUIPC5.LOG or INI after you run P3D, I can only suggest that you edit the permissions on the Modules folder yourself: Allow full access by right clicking on the folder properties: Security-->add Everyone as a user name, then check 'Full Control' access below. Back to the matter of the LVar logging. Rather than tell me the key combination you've chosen, I need to know what you've assigned to that key combination. Pete

What "windows log"?. What "touch conbination" are you using. It would be FSUIPC5.INI, and it always exists if you have ever run FSUIPC5. What did you hope to find in that? It's a record of your settings in fSUIPC5. If FSUIPC5 has ever run there would be an FSUIPC5.LOG file as well as an FSUIPC5.INI file. It creates both as soon as it runs. . So, it seems that FSUIPC5 is never running! Is there an FSUIPC entry in the P3D4 AddOns menu item? I think you need to show me that Install LOG so I can check the Install stage. Pete

I don't know SimBuddy. Don't they have a support forum? Ewhy not just stop using it until they can solve it? Pete

This must be a result of the way L-M have implemented the Mouse Rectangle numbering system. But in your highlighted differences, you have 23=ENG3FUEL=RX40000087,1 24=ENG4FUEL=RX40000083,1 17=ENG3ICE=RX40000093,3 18=ENG4ICE=RX40000096,3 So, one was a 2-engined aircraft and the other 4-engined, so I really can't believe all the panels are the same in both? Poor design if so. As I said, how can they be identical? The parts where the macros are the same will be those which are from the common gauges. FSUIPC has no control over how P3D numbers the mouse rectangles in the panels. I doubt whether the folks who design the aircraft could do it either. BTW what is a common "panel" file? Is it an added DLL? Normal panels are configured by a PANEL.CFG in the Panel subfolder of the aircraft, and it specifies which gauges are to be loaded from the Gauges folder (which I assume, with the new AddOns install method, can be outside the P3D folder). Pete

But since there's no change whasoever in any area associated with calibration between versions 5.14 and 5.15 it follows logically that something other than FSUIPC itself has changed or been changed on your system. This is also indicated by the fact that you are thje only one who has these odd results. That indicates that you somehow messed up your INI file, because that's the only place calibration information is stored (in a simple text format). You go on to say, mysteriously: Which makes me ask, what happebed to the FSUIPC5.INI file to llead you to do that? Updating from FSUIPC5.14 to FSUIPC5.15 simply replaces the FSUIPC5.DLL with the new one, and updates documents and exaples in your FSUIPC Documents subfolder. It never touches your INI file which would have still been the same. So you did something apart from simply running the Installer. I'm sorry, but this is wrong. Making wide dead zones does not override the fact that the numbers in the calibration boxes must increase (or, unusually, stay the same) from left to right. So this most certainly means the minumum muar be less than or equal to the centre values, and they in turn must be less than or equal to the maximum. You evidently don't understand this. min <= centres <= max Pete

But with a new install of P3D on a new PC, there shouldn't have been a DLL.XML. Whatever was there in that name was evidently a corrupted file in any case. Anyway, glad you fixed it. Otherwise I'd have asked to see the file. Pete

That error sound means the numbers don't read in increasing order left-to-right. The minimum needs to be less than or equal to both Centres and those must be less than or equal to the maximum. Change them in any order providing that is maintained. Pete

Sorry, as I said, I just don't remember. This is very original code, dating back a long time. There may be such good reasons I cannot simply remove that code. That could introduce new problems for many others who don't have them now. After all, in all that time, you are the first to encounter this. . I would need to work around it for your "mixed method" configuration. No, you want the opposite. You want the joystick input to get though to calibration, not to stop it.doing even what it does now. I'd need to add more code to by-pass the part stopping calibration if it somehow knows that the original value came from an axis input. That should be easy enough IF you assign "direct to FSUIPC calibration". I don't think it can be done otherwsie, but I don't see that as a problem. I'll sort out a solution, but it won't be before Tuesday. What do you think? [LATER] I have pored over the code, and at the time you want to "Set" calibration, there's no way I can detect where the input will come from. So I cannot make this automatic. The solution I think I will adopt is to make it a user choice. To allow the brakes to be calibrated you would need to set "DirectAxesToCalibs=All", or maybe less confusingly "DirectAxesToCalibs=BrakesOk". Can you think of a non-confusing parameter value? Or at least a sensible one? Pete

That’s just the problem, the Profile Specific box is grayed out, and it has a tick in the grayed out box.  I can’t do anything on this screen. That means a profile already exists for this aircraft! The name is shown in the blue bar at the top of the options window. As I already said, you can't create a new profile or select a different one for an aircraft which already has one! All of its assignments and so on are already loaded. You can edit those, of course, and that will affect all aircraft you assigned to this profile. Please refer back a message or three. This is one of the consequences of abbreviating the aircraft name in the [Profile.Bonanza] list too much. Ffr example, for a 737, folks using PMDG 73'7s would often use "737NGX" which is the common name part of all of PMDG's 737, and leaves other non-PMDG 737's to be easily assigned to other profiles, or new ones. I'm afraid i'm off-line for a few hours now. I've just finished quite big dinner, prepared by my lovely wife, and need to retire for a while. Pete

You should disable controllers completely in P3D if you are assigning in FSUIPC. Choose one or the other. I'm sorry, but i am reaching my limits in knowing how to explain things to you. i did step by step as you asked. i really think you may need some special turor, not me. I am a programmer, not a techer, and not a special needs techer for sure. I hope someone else will help here, but you may want to post in other Forums, such as AVSIM. Pete

You mean the small check box. You click that if you want to use a profile for this aircraft. The fact that it is empty also means there's no profile already assign to your current aircraft. You MUST have seen that and clicked on it before, else you couldn't have created any profiles at all, let alone 14! So, you've never assigned any axis on that new connection for an aircraft with no profile. ou have probably only assigned it in the profiles for the aircraft you've loaded since plugging it in! Of course. That's where you assign it! Why don't you click the Profile checkbox, then select your Bonanze profile, then see? Pete

I found time enough to look at the code (not to debug). It appears that in DirectAxesToCalibs=Yes mode the calibration is specifically prevented -- in the case of the brakes only! Now this dates back to the mists of time so I don't really remember why, but my guess is that a calibrated redult cannot override brake offsets being used. The code does not differentiate between data from FSUIPC offsets and that from axis assignments. I think the offset method was assumed to apply to all axis type operations not just the main two or three. That was probably the case for such app;ications around at the time. I think all I can do is to try to sort out a method to differentiate between how the axes arrive. For that it isn't merely a matter of checking assignments, but also NOT interfering with offsets being used in the sim if the corresponding axis is being assigned from a real device. It isn't quite as bad as it seems because this is only for brakes, but then should i prevent brake offsets being written to by applicatinos if the brakes are subject to axis assignment? It is not an easy question, either to resolve or implement. Pete