Pete Dowson

No, that just makes sure it can access folders which might otherwise be protected. It's mainly a precaution for those who installed FS into the Program Files folders, when you need Admin rights to write to -- once the installer has access and creates the Modules folder, it turns the need for Admin rights off for that specific folder only. FSUIPC is part of FS once installed, so its rights are the same as FS's. Pete

No. That's only a problem if you have FSUIPC client applications running running wityhout admin rights -- everything needs to be at the same level of privilege. 1, as illustrated in the documentation. Pete

Let me sort the line order out so we can see what is going on. I take it these three are still in use, with assignments? 0=Saitek Pro Flight Yoke 0.GUID={4D2F9FE0-8C95-11E4-8001-444553540000} S=Saitek Pro Flight Yoke 1=CH THROTTLE QUADRANT 1.GUID={ADB870E0-5B98-11E4-8009-444553540000} T=CH THROTTLE QUADRANT 2=CH PRO PEDALS USB 2.GUID={ADB870E0-5B98-11E4-8008-444553540000} R=CH PRO PEDALS USB They look okay except, oddly, the R.GUID, S.GUID and T.GUID lines are missing. The names are unique so it doesn't matter a lot, but I'm wondering why they aren't there. The GUIDs are used to distinguish between devices with the same name. This one is very odd. Looks like it has no assignments and is not connected either. What is the history of this one? J=Saitek X52 Flight Control System And this is evidently the one now no longer used, but which has some assignments. Y=CH FLIGHT SIM YOKE USB << MISSING JOYSTICK >> No real need. It would be clearer in case any later changes proved troublesome -- the unused entries would just confuse. When using Letters at least FSUIPC knows to ignore the ones which are missing. When only the numeric IDs are used it doesn't know this and can get silly values for axis inputs. Pete

Looks like your P3D installation is all messed up. Not only are there no installation details in the Registry, but there are no SimConnect installations for applications to connect to. I know you've managed to get passed the former problem by using the FSUIPC Installer facility to allow you to point to the program, but to get around the absence of SimConnect you will need to find and run the SimConnect installer(s). Look in the P3D install package. There should be a SimConnect.msi file there somewhere which SHOULD have executed when you did the install. Evidently it wasn't, or it failed. Alternatively, and possibly more flexibly for the many other applications which use FSX SimConnect versions, go download the FSX SDK, here FSXSDK-SP2Update and you'll find the FSX SP2/Acc version of SimConnect.msi. and, probably, in "LegacyInterfaces" also the RTM and SP1 versions. There are programs which only link via the older ones. it does no harm to install all of them. In the end you might be better off in the longer term uninstalling P3D altogether and installing from scratch, hoping it goes right this time. If it doesn't, it's a matter for discussion with L-M I'm afraid. Pete

I honestly don't know. No idea what "Vistalizator" does either. All FSUIPC does is forms the full filename, replacing the * part with the same string it uses for its own files, and asks Windows to delete the old ones. Maybe my code bypasses "Vistalizator" and you need to use the actual German filepath? Otherwise, tell you what, I'll try to simulate it here. Send me a batch of those files, ZIPPED to petedowson@btconnect.com, and I'll try to place them in a similarly named place -- won't be C:|Users but I'll create a folder on another drrive with exactly the same pathname else. It that then works here it's definitely something going on in your system specifically. Not sure when I'll be able to do it, but within days not weeks! ;-) BTW, I assume you ARE using the very latest version of FSUIPC, aren't you? If not test with that first. I don't want to waste time if it's some old bug. You should be on 4.938b. Pete

Well something doesn't match then. Double, triple check that you have the whole path exactly correct. If it finds the files it deletes the old ones same as it does for the usual files, in rotation. It'd doing the same for them all, same exact code. There's really nothing to go wrong EXCEPT a mismatch (or inability to access that folder of course, but that seems unlikely if these were saved there). Pete

Oh no! We are starting all over again? You said it was already in the Modules folder. You were using it and that was why your PMDG aircraft were speeding up too much on idle thrust. If it was in the Documents folder then FSUIPC couldn't see it and it would NOT automatically list it in the LuaFiles section as you stated. In any case there are no "loose" Lua files installed by me in the Documents folder. All of the Lua examples are in one big ZIP file! I give up. You are going round in circles. Why don't you just do as instructed and then go fly? :sad: Let's end this farcical thread here and now, please please please! Pete

I don't know if it increases or descreases. I know little about frictions and don't play with them, but from what folks said (wasn't that you?) the PMDG aircraft accelerate too quickly with the WHEEL ROLLING frictions set by this file, so I would guess they reduce friction. I thought that was why you were deleting them? If you want more or less rolling friction you have to play with the number. I'm not the person to advise about that. Pete

Oh, you mean the 11 year old ones. Water under the bridge. I don't know why it was resurrected. :-o Pete

Sorry, I'm lost here. This is relating to ...? Pete

Ah, not seen the full file. in that case just delete the WHEEL ROLLING ones, i.e. the first batch -- those are the ones you don't want, right? It's your choice, after all. I assume you still want the sliding and braking effects improved? These things are just facilities or tools for you to use as you wish. This particular one was someone else's work. i just added the Lua commands to allow it to be done. Pete

It isn't my program, but is that all the lines left? What happened to the line at the beginning which restored the defaults? In the one supplied by me that line is certainly present to make sure you are starting from a known base. Pete

Sorry, I hadn't noticed you were referring to the [LuaFiles] section. Please DELETE all three lines. You do NOT edit the [LuaFiles] section! That's generated and maintained by FSUIPC, NOT by you! I cannot understand how you don't know anything about what you are doing when you said way back that you had followed someone else's instructions and added the frictions facilities. That is surely why the Frictions lua file was in your Modules folder! Macros to be automatically executed when FSUIPC starts are listed in the [Auto] section! Thus: [Auto] 1=Lua frictions If you are still very confused I suggest you visit the AVSIM FSX forum where I think there was a long discussion about all this stuff. Pete

Not "1=Frictions". The [Auto] facility executes macros -- lists of actions as assigned to buttons. It won't understand "frictions" as it isn't a command or control. You have to put 1=Lua Frictions If you look through the button assignments list you'll find it there too, once FSUIPC sees the Lua file in the Modules folder. Please, when you are following instructions from somewhere, do try hard to follow them properly, to the letter. Pete

Well, you didn't need to use PatchSIM1friction parameter either way, since the Lua will be overriding it. Otherwise, assuming you put the [Auto] section to run that Lua program into the FSUIPC4.INI file a way back (as you said you did), then it will be okay. Pete

Hmm. Interesting and ambitious. But to me it does seem a little self-defeating. Surely the point of having the indicators and so on on real hardware is so that you can get rid on the on-screen stuff? For this reason I don't really see such facilities as "a boon". My projected screen for my cockpit shows just the outside world. If you have a library which works, then wrap it into a Lua-compatible interface and provide some documentation and I'll either include a link to it in the Lua documentation, or, if there are no copyright attachments, make it downloadable in the Download Links subforum here. Pete

Back to the Modules folder. I thought you were already using it? You are only modifying the file you are already using, surely. Didn't you say you'd added it into the Modules folder, and the lines to load it into the FSUIPC4.INI fioe. Or was that someone different? [LATER] No, it was you, in a different thread: Here Driver170, on 05 Jan 2015 - 5:06 PM, said: and i said "You enabled the Lua friction file? that will explain differences in rolling resistance, for sure! You'd need to undo that, and also make sure that "PatchSIM1friction=No" is set in the [General] section of the FSUIPC4.INI file -- else default frictions will be changed automatically too." So you MUST know which file and where it is!!! Pete

There's absolutely no difference between you manually loading a flight and FSUIPC doing it. they both just call the same routine in FS. The same goes for saving a flight. Certainly there's nothing withing the flight data saved which is understood by or changed by FSUIPC. It merely supplies the filename. What is more likely is that the A2A aircraft is also saving and loading its own files when it gets notified (by SimConnect probably) that a file is being saved or loaded. Maybe, sometimes, it doesn't see this and therefore doesn't write or read its own data? That's the only area I think possible for such a discrepancy, but you'd certainly need A2A to look into that. Pete

You need to refer to the SimConnect documentation in the FSX SDK. Pete

Find the frictions lua file in your FS Modules folder. Load it into an editor. delete all lines containing "ROLLING". Save it. That's it. Can't explain it any simpler than that. Have you never edited a file before, ever? :-( Pete

Yes, that looks better. Pete

That's just the way it works. Levers only do anything when moved. It should be part of your initialisation when you get into your 'cockpit' -- move everything. In a real cockpit (well certainly modern Boeing airliners) there's a display available showing control surface positions and you'd use that to check all was well. Move everything the whole distance back and forth a few times. Helps keeps the measuring surface clean and smooth as well. (In the real aircraft you'd need to warn ground crew first of course, else it could be dangerous). You also need hydraulic pressure available first, but that will depend on your add-on aircraft simulation. Pete

You need to adapt the Lua program so that it only adjusts the sliding frictions. Just delete the lines which SetFriction for "ROLLING". The "RestoreFriction" at the start will put the FS defaults back for the rest. Take a look at the file -- it's plain text. Edit it with NotePad or similar, NOT WordPad or any word processing program. Pete

If it adds an extra . you have to as well, else the filenames won't match! Pete

That needs WideFS. Do you have that too? It's an extra purchase. Oh, and it isn't a "hotkey", it can be any joystick button or a keypress, assigned in FSUIPC to send a message (called "KeySend with a message number) over the Network to a WideClient installation which has a parameter in its INI file telling it what to do with that specific message. As well as keypresses this can start or stop an application on the client PC too. Pete