Pete Dowson

The Pan view axis assignment is only available in FSUIPC4. The Pan view assignment is a bit smoother. It is how FSX itself uses it. The Pan view assignment is easier to program as it is only one assignment. The 8-button assignmnent is better for 2D panel use, for selecting specific outside view directions, rather than panning. Pete

No, I really won't be able to do anything this week. Wait for 4.60, test with that. Let me know if it is still a problem and we'll go from there. I have simply got to get this finished today and tomorrow, then I am away till Monday. Regards Pete

But surely you park it in the centre of the calibrated zone for 13. Why are you nudging it into different zones? surely you only want to do that when you actually want to select different zones! If the lever wouldn't move into those zones it would be pretty useless to you, after all! In other words, you can't expect to have a moveable lever programmed to select something for you and then not have it do so when you move it. After all, that is what it is for. If you want to be able to waggle it about as you please with no effect whatsoever you need a little plug-in to disconnect the throttle input for you until you press a button to reenable them. That's easy enough to do in Lua. It would be started by a button press, loop setting the throttle inhibit flags in offset 310A every few seconds until you pressed another button, then clear those inhibits. Change it to do what, exactly? Operate like a normal aircraft? Sorry, maybe I'm missing your point entirely, in which case I apologise. You simply set the zone entries and exits, one at a time, with the levers lined up as you do so. Use a straight edge or clip them together. Regards Pete

But you already do have that button programmed to send Shift+3. It is part of your default assignments for all aircraft. There is nothing "aircraft specific" about it. Are you saying that with a button already assigned to do something, having it ALSO defined as aircraft specific cancels BOTH actions, until you go into FSUIPC options? I'm really not clear why you'd pick specifically on a button which you have programmed as Shift+3 for all aircraft. Do you get the same problem with genuinely aircraft-specific assignments? If it is only with such dual assignments then that might be why I cannot reproduce it. I'll try that. [LATER] No, I cannot make it go wrong at all, even with a duplicated assignment like yours. sorry. It's a bit weird. The routine FSUIPC uses to load up the settings when you go into the Options is exactly the same as that used when it detects (and logs) the aircraft name. I'll see if I can make it happen with something closely resembling your original button assignments, as you posted earlier. [LATER STILL] No. With identical assignments to yours, but different aircraft names as I don't have those, it all works as expected. Sorry, I am at a loss with this. I would love to fix it before finishing the major Release I've got almost ready, but I'd need to reproduce it. I've pored over the code too and as I say it is identical both ways. All I can suggest for now is that you try 4.60 when it is avialable, before the end of the week (hopefully tomorrow in fact), and if you still get a problem I will have to start adding more logging to special test copies for you to run. As it only happens on your system that's the only way I can think to do it., but I cannot afford to hold up this release at this stage. Regards Pete

Easiest is to paste into your message, as you have done, but then use the "code" button to enclose it for selection and scrolling, thus: (See that it also preserves indents, which I've put back in for you). -- "Display radios" example LUA plug-in, by Ed Fairchild, December 2009 -- Loop forever: to stop this you'll have to use the LuaKill control on it. while 1 do -- Converts a decimal value in bcdnum to a string of the form "19.90" function nav2mhz(val) c1=tostring(val) c2=string.sub(string.format("%x",c1),1,2) c3=string.sub(string.format("%x",c1),3,4) c4=string.sub(c2,1,1) c5="1"..c2..c3 if c4=="8" or c4=="9"then c5="10"..c2..c3 end c6=string.sub(c5,1,3).."."..string.sub(c5,4,5) return c6 end -- Get all of the data we want to display com1 = ipc.readUW(0x034E) com2 = ipc.readUW(0x3118) com1sb = ipc.readUW(0x311A) com2sb = ipc.readUW(0x311C) nav1 = ipc.readUW(0x0350) nav2 = ipc.readUW(0x0352) nav1sb = ipc.readUW(0x311E) nav2sb = ipc.readUW(0x3120) adf1 = ipc.readUW(0x034C) adf2 = ipc.readUW(0x02D4) xpd = ipc.readUW(0x0354) adf1a =tostring(adf1) adf1b =string.sub(string.format("%x",adf1a),1,4) adf2a =tostring(adf2) adf2b =string.sub(string.format("%x",adf2a),1,4) xpda =tostring(xpd) xpdb =string.sub(string.format("%x",xpda),1,4) stat = ipc.readUB(0x66c0) co1 = nav2mhz(com1) co2 = nav2mhz(com2) co1s = nav2mhz(com1sb) co2s = nav2mhz(com2sb) n1 = nav2mhz(nav1) n2 = nav2mhz(nav2) n1s = nav2mhz(nav1sb) n2s = nav2mhz(nav2sb) -- test for stat if stat == 0 then reply="Throttle" elseif stat == 1 then reply="COM" elseif stat == 2 then reply="Panels" elseif stat == 3 then reply="Lights" elseif stat == 4 then reply="NAV" elseif stat == 5 then reply="XPNDR" elseif stat == 6 then reply="ADF" end -- display it all in an FS window ipc.display("\------------------------------".. "\n** Quad keys = "..reply.." **".. "\n------------------------------".. "\n COM1 = "..co1.." <- "..co1s.. "\n COM2 = "..co2.." <- "..co2s.. "\n------------------------------".. "\n NAV1 = "..n1.." <- "..n1s.. "\n NAV2 = "..n2.." <- "..n2s.. "\n------------------------------".. "\n ADF1 = "..adf1b.. "\n ADF2 = "..adf2b.. "\n------------------------------".. "\n Transponder = "..xpdb.. "\n") -- Sleep for 50 mSecs so the update gets done roughly 20 times per second ipc.sleep(50) -- end Regards Pete

I see it in the subsequent post. Thanks! That may be only related to mouse detection. If you can first program the mouse macros without moving the panels then it doesn't matter if you move them or even remove them afterwards, because the mouse and the position is then not relevant. FSUIPC records and uses the internal code positions directly, it doesn't care about the displays thereafter. Regards Pete

You do realise you are adding to a thread entitled "FSUIPC on FS9: Deny write acesss", don't you? This subject was dealt with and resolved. You'd be better off starting your own thread with a more appropriate title. 2F80 is indeed the FS autobrake control and indicator offset, but it might have been easier for you to simply assign to the added FSUIPC control, available in the FSUIPC assignment dropdowns, called Autobrake Set. That's what it was added for, to make things easier! ;-) It may well be for PMDG aircraft as they tend to implement their own systems completely separately to those in FS. Sorry, I don't have access to the PMDG aircraft now. Hazarding a guess, mouse macros for PMDG usually work, but with a rotary switch like the autobrake one there'll on by two operations -- turn clockwise or turn anti-clockwise. That means to select a specific position you'd been to turn it 5 times left then n-times right or vice versa. Pretty horrible. I'm sure someone would be able to help, but you'll certainly need to post with a more explicit thread title, as I said. You might also want to try posting in the MyCockpit forums as there are a lot of folks there who have built cockpits around the PMDG aircraft, especially the 737NG. http://www.mycockpit.org/forums There's a much updated version available in the Updates announcement here. I'll be releasing 3.98 this week. Regards Pete

Do you think that's illustrated in the Log someplace? Here's what I see: 49016 Aircraft="de Havilland Canadian Twin Otter Loganair (flybe)" The aircraft is the one with only these specific assignments (the rest being the generally assigned ones): 0=R0,22,C65880,0 1=R0,20,C65879,0 2=P0,6,K51,9 You pressed button 23, which isn't specifically programmed for this aircraft, so the general assignment is used: 71729 Button changed: bRef=0, Joy=0, Btn=23, Pressed 71729 [buttons] 8=P0,23,C66860,0 71729 FS Control Sent: Ctrl=66860, Param=0 Then you pressed button 6 (which, though not relevant, coincidentally has the same specific assignment as in the general section in any case): 74865 Button changed: bRef=0, Joy=0, Btn=6, Pressed 74865 [buttons.de Havilland Canadian Twin Otter Loganair (flybe)] 2=P0,6,K51,9 74865 SendKeyToFS(00040033=[shft+3], KEYDOWN) ctr=0 Then again: 77127 Button changed: bRef=0, Joy=0, Btn=6, Pressed 77127 [buttons.de Havilland Canadian Twin Otter Loganair (flybe)] 2=P0,6,K51,9 77127 SendKeyToFS(00040033=[shft+3], KEYDOWN) ctr=0 I can't see anything wrong with that. Can you explain? What is actually going wrong? I can't make anything odd happen here which necessitates going into FS options (which you didn't do during the course of the log). Please, if there's a problem, I need to know how to reproduce it and I need to know pretty qiuickly as I've just about wrapped up the next major update release ready for Wednesday. Regards Pete

I'd need to see all the relevant parts of the INI file too, please. Pete

Yes, of course. I've been using Windows 7 since it was first made generally available in its Beta days. Nothing special, but I would advise you to install FS in its own folder, such as C:\FS9 or, even better, on its own hard disk drive. If you let it install in its default place, in "Program Files", then its folders are protected and aliassed and this will make life more difficult for you and add-ons generally. But that was the same with Vista, too. Regards Pete

Good. Thanks for letting me know. Pete

According to your advanced user guide it says Error 19 is "The C.r K or M needed for Control,Key or Macro is missing" is that saying then that button 4 on joy 1 is missing? No, it is pointing out exactly what it says, you omitted the "C" saying that the large number is a Control, not a Key or a Macro. Please take a little more care copying things and you'll be okay. Pete

I'd need to see the log file -- FSUIPC4.LOG, from the FSX Modules folder. Close FSX first, then find it and paste it into a message here That's correct. I've no idea what "Addon Manager" is, but it isn't a standard part of FSX nor anything to do with FSUIPC. If FSUIPC's menu entry is there in the FSX AddOns menu, then it is loaded and running. [LATER] It occurred to me that you may be running FSX "as administrator" but not FS Commander, or vice versa. Both must be run at the same privilege level or Windows stops them talking! Regards Pete

No, that's not possible. There is always a joystick number. That's a section from my [buttons] bit, if you noticed its not actually saying a joystick number like you advanced guide says you need too Yes it is -- your joystick number is "1". What else do you think the "1" means?? The button definition in those four lines are 1,14 1,21 1,19 and 1,9 in that order. How are you not seeing the joystick number? It will also appear in the place on the Buttons & Switches tab where the joyystick number shows. There is ALWAYS a joystick number. Pete

Sorry, that's a little ambiguous to me. The same for the specific device, not the specific port? Well I could make the GUID part of the checking when matching names to letters. It would be like an extension to the name. Isn't that what you mean? Regards Pete

You seem to be distorting the documented format somewhat. First, the format has button numbers in the form "joystick number, button number". So your "b2", "b15" and "b16" would really be something like "1,2", "2,15", "2,16" assuming b2 was on joystick #1 and b15 and b16 were on joystick #2. Of course if you are using letters for joystick identification you'd use the letters instead of the numbers, but the comma is still needed. Second, the condition (the part inside the () parentheses) needs a + or - character to start with to denote whether the condition is with that button PRESSED (+) or UNPRESSED (-). It isn't valid to omit that. Only if you are talking about having the action occur repeatedly whilst you are holding the activating button (15 or 16) down. I don't think you want that for light switches, though you might for a radio or dial adjustment or trim. Pete

That sounds very much like a corrupted file problem, not FSUIPC but possibly the weather file for the default flight. When the crash occurs can you get the details? The address of the crash would be helpful. Does it specifically identify FSUIPC4.DLL there too? If mot, which module? First of all, try replacing the FSUIPC4.DLL by the latest update -- 4.593 from the Updates and other Goodies announcement here in the Forum. There's been a lot of changes since 4.57 was released (in fact I'm preparing 4.60 for release this coming week). If that doesn't help, find the default initial set of FLT files FSX is loading, from the My Documents\Flight Simulator X Files folder and move them elsewhere, so it can't load them. Finally, if that doesn't help, try renaming your FSX.CFG file so FSX makes a new one. That will reset your FSX settings to default. If none of those help we have to start looking for interaction with other add-ons which might be loading at the same time. I'll need a SimConnect log for that: see the FSX Help announcement for details of how to make one of those. Regards Pete

Actually, you may be right. Looking at the code it is rather complex, because different programs get messages into different windows -- single line, scrolling line, multiline, and some special treatment for Radar Contact, which was the original multiline window customer and what it was implemented for. I think I had to make the 3380 area write-only because it's meaningless reading it -- the stuff doesn''t really stay there long enough to be useful, and goes to other places not part of the offset system. Sorry for misleading you. Regards Pete

I'm not surprised. You need the IP address of your FS PC, not any of that stuff. That is all to do with Internet access. You are NOT trying to connect WideFS via the Internet! You certainly don't want to do that! I repeat, you need your LOCAL IP ADDRESS for your own PC, not the IP address of your router, nor the IP address used by your Internet provider to talk to you! I don't know how you got into this mess, but something is really set up wrong somewhere for Windows to convert your FS PC's name into some Internet address belonging to someone else in the first place. I've absolutely no idea how that can happen, but I am equally positive that if you can override that with your correct FS PC IP address you will overcome it. BTW did you ever even try to make the Workgroup names the same on the two PCs? That should have been far easier! That address is also an Internet IP address. It is part of the range owned by: OrgName: EARTHLINK, INC. OrgID: EARTH-22 Address: 1375 PEACHTREE STREET Address: LEVEL A City: ATLANTA StateProv: GA PostalCode: 30309 Country: US NetRange: 64.91.128.0 - 64.91.223.255 Try using "ipconfig" on your FS PC. Go into a DOS window (at Start, enter "command" and hit return, then at the prompt enter "ipconfig" and hit return. You'll get something like this (which is from the PC I'm using to type this): This tells me the IP address, on my local network, of this PC is 192.168.0.202. Regards Pete

With 2cm of travel surely a little "nudge" as you call it shouldn't change things. you should have the lever in the middle of the 2 cm really. And in any case a "dead zone" is one which sends nothing at all to the sim, it is an area calibrated with no changes whatsoever. i.e "dead". No, of course not. The throttle values are changing continuously between them, it isn't anything on the input side which is interpreting the values as 13 and 23%. That's something in your specific aircraft model. The whole problem would be easy peasy to solve using zones on the right-hand side of the axis assignments, one well-defined zone to set each individual value which the AIR file needs to set its thrust. You could have a nice little dead zone between each 'gate' that way. Yes, "controls". But there are only "controls" available on the left hand side too! AXIS "controls" are "controls"! You can assign to ANY controls on the right -- AXIS ones, same as on the left, as well as other controls, not available on the left. Why not just look, use the drop down, and see? I think you misunderstand what "controls" means -- it includes all your axis controls as well as those usually assigned to buttons and keypresses! Plus all those added by FSUIPC for doing all sorts of fancy things. Hundreds of them! You need to specify a parameter with the AXIS controls, which will be forwarded to the Sim unmolested. Don't calibrate, no need for that then. You just program your 4 zones for the 4 throttle "gates" and assign the axis control with a fixed parameter which makes the air file set that gate. I have no idea what the parameter should be -- you could find out by determining the centre of the range of "OUT" values at present which engage that gate setting. You can use "Axis throttleN set" (N = 1 to 4 for 4 engines), which has a range of -16383 to +16383, or "ThrottleN Set", which has a range of 0 to 16383 (the negative values are for reverse thrust). BTW With all this trouble I would expect 99% of the purchasers of this aircraft to have immense difficulty. Are you the only one using it? If not, have you had a look to see if there's a Forum somewhere where users are solving things? Regards Pete

Yes, of course. It will be an honor to me. :D Thanks! Pete

If it uses FSUIPC offsets to do this (and it won't in FSX) then you should be able to read them from that offset, yes. At least I've not done anything to stop that. Pete

Actually it would be almost as quick for you to search for the word "plan" in the FSUIPC4 Offsets Status document as it is for me. I don't know all these things from memory, I have to look them up the same as everyone else. Yes, you can load a Plan via FSUIPC4. Offset 0130 is relevant, and the plan can be anywhere accessible via a UNC pathname. FSUIPC4 is merely using the facility offered by SimConnect, so you could use it directly instead. It's your choice. Regards Pete

Okay. Thanks. I just need to know if the devices with the same name also have the same GUIDs, or different ones, and if the GUIDs follow the device or stay with the USB port. If the GUIDs are the same, or stay with the port, then there's no point in me trying to use them. There's also another possibility -- that Windows generates entirely new GUIDs if you unplug them then reconnect, in which case they would be a total waste. Actually, of course, I can check that here. You only need one device to check that! ... Well, Win7 64-bit seems to retain the GUID and Joystick ID even if I swap USB sockets. But of course I only have one device. If you don't know exactly how to locate these things, let me know and I'll try to help. ... Here's help in any case: Run Regedit from the Start menu. You'll get an Explorer type screen. Negotiate down to: HKEY_CURRENT_USER (for Vista and Win7) or HKEY_LOCAL_MACHINE for XP, then System \ CurrentControlSet \ Control \ MediaProperties \ PrivateProperties \ DirectInput \ VID_xxxx&PID_xxxx \ Calibration where the VID and PID xxxx values are those you can get from DXDIAG. There you should see a numbered entry for the number of identical devices you have connected: 0, 1, 2 etc. Select each and note down the fields on the opposite window: GUIDa seies of 16 pairs of characters Joystick Id the joystick number as FSUIPC would see and use, e.g. 01 00 00 00 for 1, etc. Regards Pete

That's great -- I noticed from your other reply near here. No, not for freeware. But I'd like to point folks to your site in my documentation and in my Announcements above, if that's okay? Best Regards Pete