Pete Dowson

For me too. Does the menu stay visible after a response is given? Surely it disappears (I don't remember). Anyway, I'll have a look -- there must be another call to the display routine which I missed. Pete

On a real 737 the Battery switch does it. FSX is in error. You probably have the avionics switched on -- try Toggle Avionics Master. There's no such switch on a real 737. Pete

Test with a default aircraft. It sounds like that specific aircraft implementation intercepts the Throttles at a higher lever, same as FSUIPC. When you calibrate FSUIPC has to stop those going direct to FS (and to your aircraft), do the calibration, then feed them back to FS. They will arrive ast a different level. It might also be that it doesn't like the type of throttle controls with a reverse zone, so try again with "no reverse zone" checked. If that doesn't work then there's probably no way you can calibrate for that aircraft. As I said, Airbuses are rasther different in any case. Pete

If yo do ANY assigning in VS, you should not do ANY in FSUIPC, and vice versa. You are bound to get conflicts! If you assign in FSUIPC you should disable controllers in VS. You can assign to the same VS controls in FSUIPC as those in VS --they're the ones in the VS controls list. Whether that gets around Aerosoft Airbus problems I 've no idea. I don't know much about Airbus but as I said earlier, I thought they had thrust modes not analogue throttles. You can try calibrating even with FS assignment, but again that might mess up Airbus. But one thing, going back to your original complaint, there's no way you can calibrate Synch Positions if you are not even calibrating. I don't really understand why you came here with such a question, in fact. Pete

Er, you have 3 A321's assigned to the Profile "AXE" with only these assignments: 0=0Z,256,D,23,0,0,0 =Flaps 1=1X,256,D,7,0,0,0 =LeftBrake 2=1Y,256,D,8,0,0,0 =RightBrake 3=1Z,256,D,3,0,0,0 =Rudder 4=2X,256,D,22,0,0,0 =Spoilers 5=4Z,1,D,23,0,0,0 =Flaps again! No assignment to Throttles at all! In fact your default assignments, for other aircraft to assigned to "AXE" are identical (there are no other Profile specific settings, so effectively you aren't making use of Profiles at all) So, with no throttles assigned, there can be no calibration and therefore no Sync Pos! You have no specific calibration for the AXE profile, so the default calibrations will prevail. Those are: Rudder=-13523,2176,2176,13952 LeftBrake=-9984,16383/16 RightBrake=-13696,16253/16 Flaps=-16256,9882/16 FlapStarts=-16384,-13952,14953 FlapEnds=-16383,-11520,16384 Spoilers=-16256,11442/16 agreeing with the assignments. Looks like you need to find a pair of throttle levers and actually assign them so you can calibrate. Only when it is all working and calibrated should you venture into doing more advanced things like "sync pos"!! BTW doesn't the Aerosoft Airbus use throttle "gates" or "thrust modes" rather than a continuously adjustable throttle? Pete

Er, yes, they are useful for things like, for example, setting trim to centre (use SET with a parameter of zero), or setting specific throttle values for different thrust modes. FSUIPC uses THROTTLEn_SET controls in order to allow axes to have a reverse thrust zone, because the later and now standard AXIS_THROTTLEn_SET controls do support support reverse. Same for Prop Pitch. You can also use specific parameter values to set specific fixed radio frequencies or transponder codes, etc etc. I see a lot less useful controls in the list than many of the SET controls. And all the AXIS controls are SET controls -- pretty much everyone (except keyboard pilots) use those! Pete

I've added the colour sleection option to the ipc.ask(0 function. It is in FSUIPC4939r.zip. I haven't had time to test it, so please download it and test it for me. It wasn't a complex change. The change is: Let me know how you get on please. Pete

Just use multiple spaces. It is only a complete blank "" or a single space " " which is inhibited. Pete

All the SET controls, like AXIS_XXXXX_SET, appear to take a value in the parameter field and set that value. This is in contrast to INC, DEC and TOGGLE of course. I didn't name any of these controls and only found out what they did by trying them. I still don't know what they all do, and some probably don't work in any case. Because SET controls act like this, I've included most, if not all, of them in the Axis assignments drop-down list. In FSX and P3D, FSUIPC has to use quite a few SET controls to set values which are written via offsets in the application interface. Pete

Keyboard assignments where -- in P3D or in FSUIPC? If in FSUIPC, please show me the log. There is no difference in FSUIPC between sending FS controls from a button press and from a key press, they are the same routine. Please also read the rest of my previous reply. Pete

Yes, this is a documented change (please see the list of changes in the download Links subforum, where it is explicit: -- The ButtonScreen now sends no button change for positions without a label or with a single space as a label. This was in response to requests because buttons used by other programs, especially Lua plug-ins, also use the virtual button system and accidently pressing an unassigned space on ButtonScreen should not cause unwanted actions programmed elsewhere. I think the new action makes more sense. don't you? Strange. I cannot reproduce that problem at all, and there's certainly been no change in the way the ButtonScreen window drawing actions work. The version I am currently using is a bit later (changes specific only to may cockpit implementation, not affecting user facilities). Try that and let me know. If you still get problems I need your WideClient.INI file. WideClient6999v.zip Pete

Please, next time, don't press the "Start new log" button. You only need to use that in a long session, to separate large logs into smaller file sizes. Interesting, this. The controls are definitely being sent ot P3D, but it isn't responding. It is not generating the events internally, that is why no action results. Do you get any events logged when using, say, the mouse or keyboard for these functions. Try and see. I can only think one of two things: 1. Some other add-on is intercepting the controls and stopping them being sent on, or 2. Your P3D is corrupted in some way causing this odd symptom. To find out try stopping other add-ons from running. i don't know what else you are using, but certainly, first of all, stop the non-functioning LINDA from starting (rename your ipcReady.lua file). Why are you still using P3D 2.4, by the way? Surely 2.5 is much better, according to all reports. Perhaps you should update now -- that might deal with 2 above. Pete

So, where's the log with Button and Event logging enabled? I can't help you without the information I asked you for!!! And which assigned buttons did you test out of the six? Pete

Hmm. why are they named FSUIPVC4.ini.ini and FSUIPC4.log.log? On disk they should be simply FSUIPC4.INI and FSUIPC4.log. I see you are using LINDA and that is logging errors. Are you assigning your buttons in LINDA? The LINDA errors seem to indicate that it isn't properly installed with all its needed parts. I can't support LINDA myself as I know nothing about it, but I think they have their own support. Apart from telling me about LINDA, the log isn't much use because you didn't bother to enable button and event logging and operating the buttons you are concerned about. Please see my earlier message. I also asked what you werer assigning to that didn't seem to work. I see also that you are using the PMDG MD-11. The PMDG aircraft do not use many FS controls. If you are using FSUIPC to assign to regular FS controls you will need to load a default aircraft to test your buttons on. Looking at the INI file, the only buttons you've assigned in FSUIPC are these: On the "generic USB joystick": 3=R0,2,C65607,0 =Elev trim dn 4=R0,3,C65615,0 =Elev trim up 9=R0,0,C65588,0 =Brakes On the "5-axis 12-button with POV" 8=R6,0,C65588,0 =Brakes (again?) On the Model 2120" 6=P7,19,C65853,0 =Spoilers arm toggle On the "Parking brake" 5=P8,0,C65752,0 =Parking brakes All of these are standard FS controls. Do they work on PMDG aircraft? Test on default first. Pete

Sounds like the touchscreen driver is sending mouse button down and mouse button up on each successive press. With the Lilliput touch screens I use (I don't recall the make of their drivers) the button press is sent when it sees the touch, and the release when you remove your finger, just like with a release mouse button or keyboard key press. Pete

Yes, use the scaling facilities for axis assignments, as described in the FSUIPC Advanced Users guide, about page 37 -- see under heading Additional parameters to scale input axis values. Pete

Did you not even look the the FSUIPC User Guide? In the contents it lists the chapter "Keeping track of multiple control devices ("Joy Letters")" It's only one page long, and tells you the simple way -- just change "AutoAssignLetters" from No to Yes! It really isn't much to read, and so simple to do. What on Earth would you need a "full walk through guide" for?? Pete

The FSUIPC tiller uses the rudder axis for steering. The only reason it is advised to assign both rudder and tiller "direct to calibration" is so that FSUIPC can manage the use of the rudder according to ground speed, whilst on the ground -- i.e. tiller more effective at low speeds, rudder at higher speeds. The tiller should work even with other ways of assigning or handling the rudder, provided that the true rudder input is not interfering -- i.e. is not sending changes whilst the rudder is not being used. FSX and P3D also support a steering tiller axis themselves, which doesn't use the rudder and is therefore not subject to interference, so you could also try that. It is called "Steering set". I've never tried it myself -- the FSUIPC one was added before FSX and therefore before FS provided the facility. Pete

Can you give more specific details, please? Assignments to what, for instance? Maybe you should try using the FSUIPC Button and Event logging options to see what is going on? If you want more help I'd need to see the LOG and INI files from the Modules folder. You can paste their contents into a message here. Pete

That crash is actually occurring in the GoFlight driver, GFDEV.DLL, but, oddly, during initialisation when it suddenly gets disconnected by the Server, so maybe it's some timing glitch there. The reason for the crash appears to be that the GFDEV.DLL driver was unloaded. at least according to the Modules list, which should be complete. I wonder why is it being disconnected so soon (300 mSecs) after connection was confirmed. Very odd. How does this compare with the log on the other PC, or with the log when you don't get the crash? 246451 Connection made okay! 246763 Connection closed by server! 246794 ***ERROR C0000005 at 70B57D42 Main WM_MYTIMER(0x00000000, 0x00000000, 0x00000000) Interestingly it does appear to continue and succeed in loading and using GFDEV AFTER the crash, whilst presumably the error message box was on screen waiting for your confirmation to terminate: 246965 Attempting to connect now 246965 Connection made okay! 247075 Using "C:\Modules\WIDECLIENT\GFDEV.DLL", version 2.2.4.3 247075 GoFlight GFP8 detected: 1 device 247075 GoFlight GFT8 detected: 1 device 247075 GoFlight GFRP48 detected: 1 device I'm not sure what to advise. Maybe try a different version of GFDEV.DLL, such as the one in the Download Links subforum? Maybe the error message box should offer an option to ignore the error and continue. That usually wouldn't work, but the way this has gone it may well work. I've not seen one like that before! Pete

FSUIPC really doesn't care when a device is closed, disconnected, reconnected or whatever, provided the serial port diesn't change. It would be up to the way it is handled. Have you asked the Linda folks? Better still, why not ask VRI support to help fix the device so it doesn't hang? Pete

Ah, you mean the synch positions in Calibration, where you can have many calibration points to make throttles match better? When you press OK to exit the options dialogue, all those synch positions are recorded in the [JoystickCalibration] section of the FSUIPC4.INI file. They cannot get lost, and are read during initialisation, when entering the Calibration dialogue again, and when changing aircraft -- the last matters if they are specific to one aircraft or one profile. If you think they are not being restored on restarting FSX, then maybe you made the synch positions when in a Profile or Aircraft Specific setting which is different from the one you then used on reloading? Certainly there is no difference to FSUIPC (or FSX) whether FSX is restarted or the computer is restarted. There's no way it can detect any difference in any case. If you want me to look at the INI and tell you what you've done, please just paste its contents into a message here. You'll find it in the FS Modules folder. Pete

Sorry, what do you mean by "I syncroized my two levers"? Nothing in FSUIPC changes, but the hotkey for throttle synch is only active whilst it is active, not forever. If you mean you set a number of synch points in the calibration, then these are all recorded in the INI file and never lost. Pete

And so it must be FSUIPC? Is that what you are saying? Pete

Hmm. Sounds suspiciously like they DO use it then. Who keeps it up to date for new scenery add-ons? Can you please point out what you think is wrong? Do you just mean this entry: *** Runway *** ZGNN0050 Lat 22.606976 Long 108.173378 Alt 420 Hdg 46 Len 8871 Wid 0 ILS 110.90, Flags: GS DME BC I'll look at the BGL data for that one, which I suspect is wrong or at least non-standard.You said "two examples". Where is the other? Note that the runway width field is the same data field for all relevant enties in the log. BTW I just ran the latest MakeRunways and these are the entries I get for those two default airports: *** Runway *** ZGHA0180 Lat 28.198427 Long 113.220970 Alt 217 Hdg 180 Len 8553 Wid 148 ILS 110.30, Flags: GS BC *** Runway *** ZGHA0360 Lat 28.174997 Long 113.222359 Alt 217 Hdg 360 Len 8553 Wid 148 ILS 109.90, Flags: GS BC and *** Runway *** ZGNN0050 Lat 22.606976 Long 108.173378 Alt 420 Hdg 46 Len 8871 Wid 148 ILS 110.90, Flags: GS DME BC *** Runway *** ZGNN0230 Lat 22.623917 Long 108.192299 Alt 420 Hdg 226 Len 8871 Wid 148 So, it isn't reproducible here, sadly. I can only conclude that either you are using an old version of MakeRunways (though I don't recall any error which could do this), or there's something corrupting data someplace. Maybe hardware memory or disk file problems or similar? Pete