Pete Dowson

Offsets? There are no offsets for views. You need to use FS controls. Do the Num7 and Num9 keys on the keyboard do what you want? I thought in virtual Cockpit mode those did panning actions too. Sorry, I know nothing about cameras and very little about views. Until i got TrackIR I never liked panning because I always got lost, didn't know which way I was looking. I've always stayed in 2D cockpit view to avoid panning -- till TrackIR turned up. On my main cockpit I have views but they are all done by EZCA which I really like. Perhaps posting the questions in the main FSX or FS9 Forums will elicit a response? Regards Pete

If you want to use the Lights through Lua, try these updates (which I've had to make for other reasons in any case): For consistency in the gfd library I've kept the lights numbered 0-5. Internally that's merely changed for the WP6 to address lights 1-6. So you change nothing. FSUIPC 3.997j or FSUIPC 4.718 or Wideclient 6.898 Regards Pete

Possibly. I think I've fixed it. It was a case of too much code, not something missing. i had a place where I needed a remainder from a division, and somehow I thought that if the value was negative I needed to make it positive first.. Turns out I should simply ignore negatives and treat them just the same as positives! A sort of odd reflection on life as a whole, really .. take the bad with the good ;-) Try FSUIPC 4.718 or FSUIPC 3.997j Regards Pete

It sounds like you mean 0 OR 16000, not a "range 0-16000", because that would also be progressive, not a "binary response". If that is truly the case there is something wrong with the Saitek installation. Maybe a setting in their driver? There is no way FSUIPC, or FS either, can be responsible for that. Try Saitek support -- I cannot support their devices. Maybe others have had such problems. Do they have a forum? Apart from the /32 for 2no reverse zone" those lines are completely default, as if you've not calibrated them yet. Regards Pete

That is really bad. It isn't a matter of SimConnect installations being a little messed up, they aren't even located! I told you the reason! You don't have ESP installed! The same applies to Prepar3D. Didn't you bother to read my reply properly? ESP and Prepar3D are other Simulators supported by FSUIPC4! If you want the Installer to actually find ESP you have to buy ESP and install it! (Problem there is that it isn't for sale any more, and it cost $800 when it was!) That's a log for FSUIPC version 4.60a -- the Installer log was for version 4.703, and even then SimConnect is not accessible, not any of them! I've never seen such a case before! so things are really screwed up. You could try simply downloading a later version of FSUIPC 4.7xx from the Download Links subforum, copying it into your FSX Modules folder, but I suspect that, even though it gets around some of the Windows side-by-side complications, it still won't work. I don't have a website. Perhaps you mean Enrico Schiratti's "Dowson" page, where he hosts most of my stuff? I think you need to reinstall FSX. It's in a mess. You could first try uninstalling SP2 then SP1, via the Windows control panel, then installing those again. Be sure to run FSX between each update -- it doesn't like it otherwise. If that doesn't work you might have to start again completely -- I know several folks who've somehow messed up the Windows side-by-side system for SimConnect and had to resort to a complete reformat and Windows re-install to get it sorted. You might just be able to get the latest FSUIPC4 updates working, but I doubt you'll find many other add-ons which use SimConnect being so tolerant! Regards Pete

Well I've only looked at your 747 stuff in the INI, because the others listed don't have a 4th throttle need in any case. As an aside, it seems you go to a lot of unnecessary work, having separate Calibrations and Buttons etc merely for a change of 747 livery. Why not make use of the ShortAircraftNameOk=substring facility to just have one set for all 747's?, as described in the Appendix to the manual? But apart from the work, you appear to have assignments in FSUIPC to all 4 throttles: [Axes] 0=0Z,256,D,22,0,0,0 1=0Z,B,4773,12384,66068,0 2=0Z,B,-16384,4773,1010,0 3=0U,256,D,9,0,0,0 4=0V,256,D,10,0,0,0 5=2X,256,D,11,0,0,0 6=2Y,256,D,12,0,0,0 7=2Z,256,D,23,0,0,0 Looking at the Joysticks connected: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Yoke (USB) 0.GUID={E68A2020-2F4E-11DE-8002-444553540000} 1=Saitek Pro Flight Rudder Pedals (USB) 1.GUID={E689F910-2F4E-11DE-8001-444553540000} 2=Saitek Pro Flight Throttle Quadrant (USB) 2.GUID={E68A9550-2F4E-11DE-8003-444553540000} Throttles 1 and 2 are on the Saitek Pro Flight Yoke (USB), device, whilst 3 and 4 are on the Saitek Pro Flight Throttle Quadrant (USB). That's fine, except in all cases, instead of calibrating Throttles 3 and 4, you've Mapped them from 1 and 2, as shown in these lines in every JoystickCalibration section: [JoystickCalibration.PMDG - 747-400 PW4000 Engines] MapThr12to34=Yes MapThr12to123=Yes Throttle1=-16256,-512,512,16256/32 Throttle2=0,0,512,16256/32 MapThrottle=Yes Also, in that one case also you have a weird calibration indeed for Throttle2. Compare it with another 747: [JoystickCalibration.PMDG - 747-400 GE CF6 Engines] MapThr12to34=Yes MapThr12to123=Yes Throttle1=-16256,-512,512,16256 Throttle2=-16256,-512,512,16256 The MapThrottle=Yes is also wrong because you have no generic all-engine throttle defined, and what that option does is map the one generic throttle to all 4 separate ones. The other odd thing is that in some cases you've checked the "No Reverse Zone" option (gives the /32 on the end) and other cases you haven't. You do have separate overriding Axis assignments for the Air France 747: [Axes.PMDG747-400 AIR FRANCE] 0=0Z,256 1=0Z,B,11094,16383,65597,0 2=0Z,B,1419,11094,65599,0 3=0Z,B,-7740,1419,65601,0 4=0Z,B,-15996,-7740,65759,0 5=3Z,256,F,65760,0,0,0 but no throttles assigned at all for that one! The same applies to this one: [Axes.PMDG - 747-400F PW4000 Engines] 0=0Z,256 1=0Z,B,11094,16383,65597,0 2=0Z,B,1419,11094,65599,0 3=0Z,B,-7740,1419,65601,0 4=0Z,B,-15996,-7740,65759,0 So, on those two you get no throttle action whatsoever, and on all the others you have Throttles 1 and 2 mapping to 3 and 4 fighting with the assigned Throttles 3 and 4 on your add-on quadrant. On your second posting: You have no assignment to those, at least in FSUIPC for the 747's (not looked at the others), so I don't know why you'd expect them to work? Quite honestly it is a complete mess. My advice would be to delete the INI file, run FSX again to generate a new INI file, then close it, edit the INI file to change "UseProfiles=No" to "UseProfiles=Yes", then make default button and axis assignments and calibrations for a generic (default) aircraft, then create a profile for the PMDG 747 (just one), and separate ones for your other main aircraft. Regards Pete

So, are you happy with the working update in CFS1? Pete

This is a sure indication of an error in the Windows Side-by-Side installation of SimConnect. I could get more details if you'd please show the Installer log contents here. Are you using the latest version of FSUIPC4's installer? If you aren't attempting to install version 4.70 or later, please do so first. I can't support anything earlier for FSX and there have been changes to make it less dependent on any tangle up in the Windows horrendous Side-by-Side DLL system.. If it then works you might get an operative FSUIPC, but you could still have problems with other SimConnect applications, depending how they connect to it. FSUIPC doesn't use and doesn't care about the SDK. It doesn't need it installed. Folks without the DeLuxe version of FSX don't get an SDK option in any case. No, ESP is another Flight Simulator, the professional version of FSX which is developed further by Lockheed Martin and published as Prepar3D. If you were using the correct and supported version of the Installer it would also have told you that Prepar3D couldn't be found either. Naturally, my installer will only find those supported Flight Simulators which you have installed -- just as the FSUIPC 3 installer looks for FS2000, CFS1, FS2002, CFS2 and FS2004. Sounds like you've made a bit of a mess with SimConnect, but, no, nothing of mine needs the SDK, and the relevant parts of SimConnect are automatically installed with FSX and updated with SP1 and SP2. The provision of SimConnect installers in the SDK is really just for use on Networked computers linked to the FSX one so you can run SimConnect applications like ASX or ASE remotely. Regards Pete

Okay. At least that simplifies the investigation a lot -- the filtering ins a bit complex. Yes. I'll check it later today. Odd that no one has reported this before. It must have been like this since slopes were added six years ago (version 3.50 in August 2005)! Thanks for picking this up. Pete

Ah, good. I should remember not to engage in technical support exchanges until the user is using the current version! ;-) I've no idea which of the many changes between 4.60 and 4.7xx would have been responsible -- there's a comprehensive list in the installed History document though. ;-) Regards Pete

No. that is very odd. The number of the light to simply passed on. Maybe, in this case, GoFlight have numbered them 1 to 6 after all. Number 6 won't get through my checks as being invalid for that device. I think more of this will have to wait. I suspect that this is also the first use of the GFDev.DLL facilities supporting the WP6 and there may be bugs in that. I can't really diagnose and fix all the problems you may discover without adding a lot more diagnostic code, and it could take ages and a lot of my time. i think, now I know a WP6 in on the way, it is best to wait. Thanks for trying! Regards Pete

So iFly gauges and PM do not conflict? That is most odd, because for sure PM and default A/P do so. Sorry, I'm lost here. What can disengage? What is this "PMoffset" setting? I don't know the references at all. But if the driver is running on a client under WideFS, there are only offsets for it to do anything with. Unless it has its own communication to the FS PC and another part of Cockpitsonic installed there? So, it is certainly using offsets. Are you sure it isn't simply using the 3110 offset to send FS controls? The only way is only offsets for an application program. The joystick buttons are only those it can read from Windows for standard joystick devices or from GFdev.dll for GoFlight devices. No axes at all through WideFS. If there were buttons being sent you'd see them in the FSUIPC Buttons & Switches tab in FS. Pete

You didn't need to post it if you've not changed it! ;-) I see it is only using the SetBright function in any case, which is passed more or less directly on to GFDev.DLL. So i think sorting that out will have to wait for my WP6. That's because, as with all indicators and buttons in GF units (and in FSUIPC generally), the lights are numbered from 0 (0-5 in this case) not 1. Your attempt to set light 6 is ignored. Regards Pete

Okay, from these: Aileron=-16192,0,16,16192/8 Elevator=-15680,256,16,16192/8 Rudder=-12288,0,16,12288/8 Throttle1=-16192,0,0,16192/40 Throttle2=-16192,0,0,16192/40 Mixture1=-16192,0,0,16192/40 Mixture2=-16192,0,0,16192/40 PropPitch1=-16192,0,0,16192/40 PropPitch2=-16192,0,0,16192/40 I cann see you are setting the Filter option on all of those axes. why? That is drastic. The filter facility was introduced to deal with bad power causing noisy interference on axes. Do you have very dirty controls or bad power supplies? Filtering involves sampling incoming values and attempting to smooth sudden changes out. To do so it lags behing by at least three readings. I'm not sure why this has the effect you show, and especially only on the negative parts of the ranges -- I will certainly have a look at that. The slope computations are completely symmetrical, so I can only assume it is the delay which is causing the readings to somehow get out of order in FS's message queue. Please try unchecking "Filter" on every axis, and please do tell me why you enabled it. I think I shall make the filter option only shown if you change an INI file option before starting FS. Regards Pete

I have no idea! The scanning in FSUIPC4 uses the same sort of DirectInput calls as FSX. It should see exactly the same calls as FSX. You haven't edited the FSUIPC4.INI file at all have you? What was all that earlier about "I have found 2 axis named N, and T and numbered 17 and 18"? T is a slider, N is a POV, but I've never seen either show up in FSUIPC before. And if you mean joystick numbers 17 and 18, then those numbers are used by the PFCFSX and PFCHID drivers. You haven't installed either of those in your FSX Modules folder, have you? I don't know any other way for those joystick numbers to be seen -- the DirectInput joystick numbers are only ever in the range 0 to 15 inclusive. I just looked again at the INI file you posted earlier: [JoyNames] AutoAssignLetters=Yes 1=Logitech Extreme 3D 2=PFC Throttle Quadrant Console The PFC device should show up, therefore, as joystick 2. What is a "Logitech Extreme 3D"? Pete

Sorry, I don't understand that. If Windows sees the axes, and FSX sees the axes, then so will FSUIPC. It can't avoid seeing them. Pete

If FSUIPC isn't seeing buttons on the device it isn't a Windows-style joystick device, nor a GoFlight or PFC device. Doesn't the Cockpitsonic driver just write direct to offsets? What exactly do you want to do? I can't really work it out from your message. Are you trying to use iFly's full cockpit model and PM together? I wouldn't have thought they were compatible. Regards Pete

But the Gear switch isn't an axis but a switch/button. And you've not yest explained any inability to assign, only to calibrate. That's why I need you to be more explicit. Groan! The options to ASSIGN axes in FSUIPC are in the Axis assignments tab. You have to have an axis ASSIGNED before it can be calibrated! Calibration doesn't know what axis you are using unless it is assigned!!! Pete

Ah, yes. In fact you'd normally have them the other way round, 0800 first, quite a way out then the then, later usually, 07FC. I think you should be locking onto the localiser earlier, waiting for the GS diamond to start moving (GS needle read-out) then enabling GS/APP. Pretty much as the pilot would do. Regards Pete

A lot easier than USB HID stuff. I've been using serial ports for all sorts of things for many years, starting with the Commodore Pet in the late 70's. Did they provide a calibration program? I think I've seem one. Ah, in that case it sounds as if your quadrant isn't like the one on my Cirrus console, but one made to look like a normal Windows joystick device with axes and buttons. It's because it is assigned to the gear toggle. FSUIPC can assign to both on (press) and off (release) actions. You want one assigned to GEAR DOWN and the other to GEAR UP. How did you assign it? If Windows and FSX can see all your axes then so can FSUIPC. And if you managed to assign it in FSUIPC then obviously it is seeing it! Please be a little clearer in your descriptions. Do NOT try to calibrate a spoiler axis on the ground! When the lever goes through the "ARM" position FS detects the compression switch on the gear, so deploys 100% spoilers, as it would on landing. You have to get in the air. do so then pause whilst calibrating. Pete

Interesting. There was a deliverate code line to stop scanning for CFS2 only. I've no idea why. I've removed it and it all seems to work okay now. I expect it was protection from the non-working FS assigned control scanning. With the later-added direct FSUIPC assignments it seems okay. FSUIPC 3.997h Regards Pete

That looks exactly the same as one I have here, dating back about 10 years or more --but mine is a serial port connection and uses my PFCFSX.DLL in FSX. I wrote a driver called PFCHID.DLL for PFC's USB "HID" devices. They've had it now for a couple of years. It was initially aimed at their new Cirrus Pro consoles, and that features a USB HID type quadrant too. I don't know what other devices they use it with, but I would strongly suspect the USB quadrant you have needs to use it too. They should tell you what to install, and point to where you can get it. (See the Download Links subforum. There's one there, probably a later one than on the PFC website). Does FSX itself see all of the levers? If so then so should FSUIPC without any other driver. That's the main test. And there's no installation instructions, no other driver supplied? The first two sound like FSUIPC documentation. Up to date copies of that are installed for you when you run the FSUIPC4 installer. See the Installation guide. Don't the PFC documents tell you anything useful? Pete

Where is the GS diamond on the PFD? Does it go solid? Are you below the GS at the IAF? I'm not really an expert on how FS does these things, but all FSUIPC is doing when you write to those offsets is send the exact same FS controls as you get sent when using the panel*. You can verify this by logging Events in both cases and compare. Maybe that will show what you are doing differently? * Actually, just checking: FSUIPC uses the ON and OFF controls whilst the mouse click obviously uses the toggling controls. Yes, that makes sense, because the logging of the SimConnect read only happens when it supplies a different value to the one already set in FSUIPC's memory, which you've just written. Compare events. Regards Pete

Sorry, I always need FSUIPC version number, and in this case also please paste in your INI file Axes and JoystickCalibration sections. Pete

Of course. That was the main reason for Profiles -- so you could have, say, a Boeing Jet profile using a quadrant and yoke, an Airbus Jet profile using stick and quadrant, a "Prop" one using maybe a yoke or stick and a different quadrant, a "Helo" one using a G-stick and collective control, and, yes, a "Fighter" one using a stick and military equipped throttle. Axes assigned in profiles are specific to those profiles, just as with calibrations. I don't understand why you'd question that. I'm actually rather surprised that folks have almost identical profiles for similar aircraft. Seems best to divide them generically. That doesn't bode well. I had thought it was only the calibration dialogue affected. It may not be possible, then, on CFS1. I'll take a look anyway. Pete