Pete Dowson

Seems like your virus checker is holding it hostage. Right click on it and see if there's something there where you can tell Windows it's ok. Otherwise you'll need to deal with your virus checker being over-enthusiastic. i've never heard of anyone else with such a problem. Pete

Any FSUIPC client program can do almost anything to the performance of FS, because FSUIPC is just an interface into FS for those programs. I've no idea what FS commander does or is doing during this time, but that's where to look. Does it have some sort of moving map? Is it possibly doing something when connected which it isn't doing when it isn't connected? It may not be the connection itself, but whatever it is doing (eg screen stuff) when it is connected. Perhaps you can try changing options in FSC to see if there's something specific it is doing which causes the problems. Since I've no idea what it is doing I can only suggest you ask the author or FSC support for advice. But did you ever use this setup with P3D2 or FSX? If it's changed in P3Dv3 it might be yet another P3D problem to add to the list -- there seems to be quite a lot wrong with it at present. BTW I thought most FSC users ran it on a client PC via WideFS? Pete

What "line"? Why not use the whole INI file from v2 in v3. Nothing should be different. You can even share INI files from FSX. Well, surely obviously, if you had not previously assigned the throttle in either FSUIPC or P3D it couldn't possibly work! Nothing would be reading the axes! Pete

Okay. Good. Sorry if I came over too rough in my last message. I re-read it and was going to change it but you were too quick! Pryr

Oh dear. You STILL don't get it, do you? That comma is IMPORTANT. the file it refers to ONLY contains FSUIPC 4.948. Just the program. no installer, no documentation, no updated plug-ins. Just the program for installing all by yourself. It is truly "FSUIPC 4.948 only". And so it is for those already having up to date other bits. Obviously, if like you, one doesn't know what they are doing, one should ALWAYS download the Installer package. Pete

Yes, of course! With the Installer download, NOT the separate small file. You can ALWAYS install a new version of FSUIPC, even if you've not already got even one! That's how new users get it too! (How else?) Pete

4.946 is not available now there's a later one. 4.948 IS later than 4.946! It seems you haven't actually read what it says? Here, I'll reproduce it for you with the parts you missed in BIG RED text so you can't miss it! ;-) Install complete FSUIPC version 4.948 Install_FSUIPC4.948 for FSX, FSX-SE and Prepar3D versions 1.4, 2.0-2.5 and 3.0 See included document for main list of changes -- Automatically assigns missing joystick IDs (like JoyIDs) -- now improved! -- Fixes problem in Lua with keycode 135 used in event.key function -- Adds offsets for the three wheel RPM values FSUIPC version 4.948 only, for those with 4.946 or later already installed FSUIPC 4.948 --------------------------------------------------------------------------------------------------------- The only part you seemed to have read is the bit without the installer and documentation, which you can use if you already had 4.946 or later installed! Pete

According to your FSUIPC4 INI file you are not assigning any axes in FSUIPC. Therefore, because of the known fault in P3Dv3, you cannot actually calibrate in FSUIPC either. You CAN use previous calibrations, from P3Dv2 perhaps (just copy over your FSUIPC4.INI file), but until Lockheed-Martin release an update you might be better assigning everything in FSUIPC instead. This problem was described in one of the two important threads pinned to the top of the Forum. See where it says "IMPORTANT: FSUIPC calibration of axes in P3D version 3".

How do you have one button doing both flaps up and flaps down actions? You need two buttons or a two way centre-off switch! If you are only using the normal FLAPS INCR and FLAPS DECR controls, then it's simply what FS does -- same as using the F7 and F6 keys. In that case it's a PMDG bug. If you are using software which instead uses the Flaps axis control, or FSUIPC offsets, then the problem would be that the PMDG flaps do not change at the same axis values as the default 738. Pete

It acts like the FS rudder control, because it is using the FS rudder control! Since FSX there are steering controls built into FS itself: STEERING DEC STEERING INC STEERING SET That last will be like an axis control, using the parameter -16384 to +16383. FSUIPC doesn't use these newer controls in order to maintain compatibility with earlier simulators and folks' settings, but by all means try them. However, I'm pretty sure that FS's push-back is artificial, like slewing. it isn't very likely to be steerable. If you have enough reverse thrust you can get some aircraft to move backwards. The rudder/steering might work then, though the added resistance will probably stop the reverse motion. Pete

Did you read through the thread? I'm sure folks must have asked. I know there's stuff later on dealing with multiple (up to 4) engines). I don't know the Lua code there myself and I don't really have time this week to analyse it (off to South Africa on Friday). It looks quite sophisticated. I think the author is very helpful and so if the answer is not already there in that long thread he would probably respond if you asked him. The thread is not closed. Pete

You say you searched, but evidently not in the User Contributions subforum? I just searched there just using "throttle reverse" and found two threads which may help: "Aerosoft Airbus X Throttle Reverse + FSUIPC Resolved" and "Throttle Manager to Allow Axis Forward/Reverse Toggle" Pete

Thanks. The movement was so small I used 10x the values you had so I could definitely see what was happening, then inserted Sleeps of 2 seconds between each one. Both P3Dv2.5 and P3Dv3 do the same thing. EYEPOINT_SET_LONGITUDINAL does the same as the RESET. It doesn't do nothing, it resets the viewpoint altogether. Please report this for both 2.5 and 3. You can say i verified it on 3. I'll report it too, in the developer's area. Pete

Axes assigned in FSUIPC can be calibrated in FSUIPC. The problem is only when they are assigned in P3D because P3D isn't scanning them in modal dialogue modes. They've fixed it internally already I think. Axes calibrated before P3Dv3, or calibrated in FSUIPC using the normal controls assignments in FSUIPC, will remain calibrated if assignment is changed back to P3D. It's only the act of setting the calibration values which is affected, not the calibrated results themselves. Pete

You mean the FS pushback? I think that isn't dependent upon the rudder, which is what the FSUIPC tiller uses. Same probably for other pushback programs. I think they use a method akin to slewing. Pete

Are you sure? It would be very very unusual for any add-on aircraft to require FSUIPC registration. The only other sources of end user Registrations for FSUIPC are Intercraft, Japan, for the Japanese version, and Project Magenta for PM customers only. Nothing under that email address. I can't look up names, only email address or order number. Pete

I've scrubbed out what you call your "key" in case part of it is valid. NEVER publish any of your Registration details, otherwise I will have to invalidate the key in any case. And there never has been a 13-character key. All keys for FSUIPC and WideFS are 12 characters, no more, no less. You are not using the correct information for registration. Go to your SimMarket account and get them again. Pete

That's very strange indeed. I have no explanation at present. I need more information. Can you please add the following lines to the [General] section of the INI file: Debug=Please LogExtras=x200000 then run it twice again, as you have above, sdaving the FSUIPC4 LOG file for each. I need to see those logs to work out what is going on. Where did you read that? Using Joy Letters would certainly allow FSUIPC to maintain your assignments no matter what joystick ID numbers were assigned. But then you might not have noticed the numbers changing. I need to find out why that is happening in any case. Pete

Have you got a little Lua script I can use to test it here on V3? Pete

Yes. That's what I said. The letters identify the controller used in your assignments. It is that simple. Pete

There's absolutely no difference between FSX boxed and FSX-SE in anything to do with PFCHID or FSUIPC in those areas. Sounds like the add-on aircraft are the problem. PFCHid only has controls for default aircraft in any case. If add-on aircraft do their own thing you'd need to program their controls yourself using the macro facilities in PFCHid. Sorry, what is this intended to mean? The current PFCHid here in the Download Links subforum is 1.41 dated June 20014, and this is my only "website"! 1.32 must be from about 2012 I reckon? I have no trace of it here. What version does PFC supply? By all means stick to an older version if you wish. My PFC stuff is no longer developed in any case. But I can't help with old versions I'm afraid. Pete

ipcDebug.lua is an now obsolete way of tracing Lua plug-ins which is superseded by the built-in Lua trace/debug option. The ipcDebug.lua, (which is still supplied in your Lua plugins ZIP in the FSUIPC Documents folder in case you really want to use it), is only used when a Lua plugin is invoked by a "LuaDebug" command. Therefore whatever mechanism you are using to start those Lua plug-ins is using LuaDebug. You should check your LINDA settings I think. If you want to log Lua use the option in the FSUIPC logging tab. Pete

You need to change it to suit whatever hardware you are using. You'll need to go through it and program it as you need. It is not a beginner's job. The example is there to show how it can be done, but it is only an example. Pete

No idea what your "screen flashing" is. There is no 7-digit key for FSUIPC, only 12, a mix of numbers and letters. And the registration screen appears AFTER all the install process so there is no way you'll then get anything for FSUIPC then relating to installing, and FSUIPC never asks you to install anything in any case. It sounds like you are mixing it up completely with some other program entirely. You must enter the exactly correct details all three parts. You are making a mistake. Pete

The registration certainly does NOT expire. You are making an error. The name, email and key must ALL be correct, all identical to your original registration. Use cut and paste for your original, or if you have lost it, go to your SimMarket account and obtain it all again. FSUIPC has nothing to do with anything displayed on your screen. I've never heard of any "screen flashing" problem with FS. I don't make anything called "Wide Screen". WideFS is used to link computers in a Network in a way which allows FSUIPC client applications to run on separate PCs. Pete