Pete Dowson

Looking at your settings you've made a bit of a hash calibrating Throttle 2. Compare the two entries: Throttle1=-16143,-512,512,16383/32 Throttle2=-8192,596,596,745/32 If the full range of values supplied by Throttle2 is only -8192 to +745, as you've calibrated here, then there's either something seriously wrong with that part of the unit, or you've got some driver installation or Windows calibration issues. For modern USB axes the normal range is -16384 to +16383, and whilst I always recommend that you leave a region at either extreme free, to allow for small variations such as humidity, temperative, voltage changes, your numbers are very bad. However, nothing here wouild explain "erratic and jumpy" if what you mean by that is that they go back and forth, or "jitter". If that is the case then you either have faulty hardware or a very dirty device. You have different calibrations in profile "be56" which you use with the Baron: Throttle1=-16143,-512,512,16383/32 Throttle2=-7745,-512,512,1340/40 Throttle=-16380,16380 There you have a conflict in any case, with the generic all-engine Throttle calibrated as well as two separate throttles. You should reset that. Here your Throttle 2 calibration is just as bad -- -7745 to +1340. Worse, you appear to have enabled the "Filter", which is a desperate measure indeeed, especially if applied to one throttle and not both as they will behave asymmetrically. I see you also have a profile called "g1000"., used with the Mooney. There you don't have throttle 2 assigned, but: Throttle=-16380,16380 Throttle1=-16143,-512,512,16146/32 again you have the generic throttle calibrated as well as the seperate throttle1. Reset that. Pete

So, it isn't SmartCars, and not FSUIPC ... time surely to visit PMDG's forum? Pete

I think you must be in the wrong place. Why not try a support forum for "SmartCars" (whatever that is), or PMDG? Pete

No, there's no difference whatsoever in FSUIPC's treatment of axes between FSX and P3D. Did you copy over your FSUIPC4.INI file, so you had the same settings? You provide no information I'm afraid. Are you assigning in FSUIPC or P3D? If in FSUIPC have you disabled controllers in P3D? Are you calibrating in FSUIPC? Is FSUIPC anything actually to do with it? And what IS the latest version which you have installed They have numbers. Folks often say "latest" and mean "the last one I noticed". The current one, the supported version, is 4.944a. The version of FSX or P3D is not relevant to FSUIPC's axis and calibration support. Pete

No. Plug-in support has only ever been available for registered users. Pete

Hmm. Very strange. I'm sure that if it were a general problem there would be a massive thread or multiple threads about it here. The only usual problem with using FSUIPC with PMDG aircraft is in the area of the Throttles, where calibration in FSUIPC can't be used because their aircraft take the throttle value directly, and FSUIPC has to bypass that in order to calibrate and feed in the modified vales at a different level. The throttles can still be assigned in FSUIPC, but to the normal FS controls ("Axis throttleN set"), and then not calibrated -- i.e ensure the calibration tab for them says "not processed". This is effectively the same as assigning them in FS itself, but doing it in FSUIPC allows you to turn off controllers in FS so that there are no conflicts for aircraft assignments in other profiles. Hope you find out what is wrong in your system! Pete

There are very many FSUIPC users also happily using the NGX, so I've no idea what is different on your system I'm afraid. Reinstalling FSUIPC makes no difference because all that does is replace the DLL and the documentation. Did you delete the INI file so it started with default settings? I think PMDG recommend that. Of course, if you use it for other aircraft that's not the best solution. In that case you should have your NGX settings in a separate Profile. Pete

Sorry, I no idea at all. I don't know either of those things. Does FSUIPC see the Emuteq G1000 at all? Does it come with any software or drivers? And does the G1000 in the Carenado add-on aircraft allow keyboard, L:Var or mouse macro control over its buttons? Without such information it is impossible to answer your question I'm afraid. Maybe the guys at Carenado could help? Pete

Well, as far as I can see, the Lua program will be doing what you ask of it. so you need to debug the actual offsets. Have you logged them? You can use the FSUIPC Monitor facilities on the FS PC, or the Monitor parameter in the WideClient.INI file. Also always check the Wideclient folder for a Log with the name of your Lua file. That will (1) show when it last ran, and (2) contain details of any errors which stop it working. Pete

Hmm. I've never heard of "Comodo" or "sandboxing" I'm afraid. Some sort of "stop the user doing what he wants" program? Well, the Installer program actually found the files where it knew they should be, as this shows: So it seems all this "sandboxing" does is prevent YOU seeing them, but other programs can? Strange. Yes, thanks for getting back with the answer. Glad it is resolved. Pete

Well I can't imagine why the folder is hiding from you, but honestly there's no way the installer could find the existing copy of the DLL in the folder in which it should reside unless it is really there. You do know there's a "repair" optionin the FSX-SE options. Right click on FSX-SE on the left in Steam, and check the drop down options offered. Not sure what it does, but I doubt you'd need a full re-install. Also you could try actually CREATING the Modules folder in your Steam FSX folder. If it refuses then you'll know there's one there. When you run FSX do you use the Steam window to select it? What happens if you go to the D:\Steam\SteamApps\Commom\FSX folder and double-click the FSX-EXE file there? Does it load? Also, check your DLL.XML file, found here: C:\Users\Jim\AppData\Roaming\Microsoft\FSX Despite the name it can be viewed as a normal text file. In case it is corrupt, so stopping FSUIPC4 loading, try renaming it or saving it elsewhere, and re-running the FSUIPC4 installer. It will create a fresh one. If this gets you an Add-Ons menu entry, then the original DLL.XML was bad. You could paste it into a message here for checking if you wish. Pete

You cannot be looking in the right place, then. Please see my previous email for the full path. Also I'm not getting the drop down in the addons Possibly your DLL.XML file is corrupted. There are some installers around which make a mess of that. That picture also shows a "missions" folder. I have no "missions" folder for FSX-SE. How did that get there? everyone I know has managed to get FSUIPC working fine, so they have the folder of course. The folder absolutely MUST be there, this section alone is proof: Checking if there's already a version of FSUIPC4 installed in: D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL ... Version 4.944a found. FSX-SE Modules folder already exists. You simply MUST be looking in the wrong place! Pete

You have an ATR 72 profile containing this: [Keys.ATR 72] 1=B66C0=12 187,9,M2:29,0 2=B66C0=12 189,9,M2:28,0 3=B66C0=11 187,9,M2:26,0 4=B66C0=11 189,9,M2:27,0 5=B66C0=14 187,9,M2:30,0 6=B66C0=14 189,9,M2:31,0 7=B66C0=13 187,9,M2:45,0 8=B66C0=13 189,9,M2:44,0 9=B66C0=10 187,9,M2:30,0 10=B66C0=10 189,9,M2:31,0 11=90,8,M2:2,0 See the last assignment? The profile assignment overrides the general assignment. Pete

All the FS controls are listed in a document in your FSUIPC Documents folder called something like "List of FSX controls". It lists them by name and number. Just use the number for the one you want. Pete

That looks perfect. Nothing wrong at all. Why do you think it isn't istalled correctly? Yes, you do have that folder. Where are you looking? See this line: Okay -- installed FSUIPC4 into "D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL" and of course all of the documentation is in the subforlder, thus: Now installing additional files into the "Modules\FSUIPC Documents" folder: Where does 10gigs come into it? the Modules folder is created by FSUIPC's installer. It isn't part of the default FSX or FSX-SE. You need to explain what this "issue" actually is. You haven't so far! Pete

Ah, there's no facility for historical weather? Hmm. That is a shame. You'd need to hunt for somewhere in the world currently giving you the desired conditions. Have you asked the author for such a facility? I've always thought he was very amenable to suggestions and requests. Pete

Really? Well, that's good then. So what's the problem? I'm confused now. Pete

Er, but WidevieW surely isn't a weather provider, and FSGRW isn't a multi-pc synchroniser. They do different things. Surely WidevieW's synch would work with any weather provider! Why not FSGRW, if that's your choice? (I love ASN myself). Are you confused, or it ist me? ;-) Pete

But it would receive conflicting data. Don't forget it is designed to share offsets. it is reproducing the FSUIPC interface on the local PC. You could run another copy of WideClient on the same PC. You have to change the ClassInstance value, eg to 1. No applications can connect to it (unless they are programmed to talk to more than one install of FSUIPC) , but it will run Lua plug-ins. You'd need a plug-in on the one to dump data from the plug-in on the other to read and send. i.e. it comes back to a similar problem to the first. I still don't understand why WidevieW still doesn't synchronise the weather across the Network. Would make it useless to me -- seeing blue skies at the sides when overcast ahead. Pete

The ServerIPAddr and Protocol (or ServerName and Protocol) parameters in the WideClient.INI file. If left to automatic connection, as defaulted, it would be anyone's guess which of the two running Servers would be used. Please read the bit in the WideFS User Guide about configuring your Network, the bit with a bit read plea for folks to at least read some of it! ;-0 Pete

petedowson@btconnect.com. But I don't do support via email, so unless your message is genuinely needing to be more private I shall most likely ignore it. Pete

Control lights? Yes. I read about that. Not sure what exactly they did, but though messy it is doable. What has that to do with weather? If you mean use Lua pugins on the two PCs to read the weather from one PC and send it to the other, yes, I suppose you could do that. You'd need to have networking code in the Lua programs so they can talk to each other, or use files which one writes and the other reads, and basically read the METAR string from one and send it to the other. But it is fraught with difficulty, because the way SimConnect does METARs is very strange and very complex, and the input format is NOT identical to the output format! You'll need to refer to the SimConnect SDK. Doesn't WidevieW deal with weather synchronisation? If not, why not look at OpusFSI? I have heard that's really good with multiple PC systems. Pete

Each PCs connecting WideClient would need explicit parameters telling it which Server to connect to. Each client can only connect to one server. Pete

That's something WidevieW would have to see to. I don't know what options it has for weather synchronisation. Have you checked? I haven't used WidevieW since FS98 days and I'm sure it has changed enormously since then. One thought, why no wind synch on the clients? The wind affects cloud movements and windsocks etc. Don't you want them synchronised? Pete

The value in a _SET control is a value in the range of the thing you want to set. The forward throttle range in FS is 0-16383, so 25% is 4096. 10% would be 1638. 100% full forward thrust is always 16383. When you assign your axis to the throttle it will be using either AXIS_THROTTLEn_SET (which actually runs from -16384 (idle) to +16383 (full thrust), with no reverse range, or, through FSUIPC only, THROTTLEn_SET which can run from -16384 to +16383 too, but with idle at 0 and negative values giving reverse thrust. The reverse range is normally limited by a value in the Aircraft.CFG file to a percentage -- often 25% by default, so max reverse would be -4096. Where there is no reverse thrust the percentrage would be 0, so negative values would be ignored. Pete