Pete Dowson

It certainly sounds as if at least one of the aircraft intended to go into the selection menu is courrupted in some way. The fact that other things being present or not can make a difference is quite understandable when you consider that the problem may cause memory corruption anywhere. In that sese it is the same as scenery errors causing corruption and G3D crashes. Quite often those are NTDLL crashes instead. All you can do is proceed to eliminate each of the aircraft in turn. Do it by halves -- move half the aircraft folders out, test, then do the same for the half which then contains the error, and so on. Even with 256 aircraft (say), that only takes 8 tests. Pete

That's a corrupted function address in an object definition. There's no way of trapping and bypassing that -- it means something has trampled over essential data. I would suspect faulty scenery, aircraft or texture files. No way does it look like a genuine FSX bug. Regards Pete

I've not forgotten you. Things caught up with me, but I'm aiming to make new releases on Sunday, or Monday latest. Pete

I just found your support query posted incorrectly in the User Contributions forum! Please only use the Support Forum for support -- I've moved it here for you. Why are you using 'G' when there are perfectly good Gear Up and Gear Down controls? If you want the switch to do something both when it goes on 9"pressed" and when it goes off ("released" you have to program both the press and release actions -- obviously? Pete

Not knowing VB.Net at all, I don't really know what those do. That method merely sends the raw WM_KEYDOWN or WM_KEYUP commands with appropriate parameters supplied by you. It's the most basic and probably most complicated way -- but standard Windows. Maybe in VB.Net you never actually come against the actual Windows messages? I don't know how much you are insulated from all that. Easiest way by far is to use the built-in FSUIPC control to press and release a key -- see the Advanced User's manual. It's number 1070 in the list of Additional "FS" Controls. you can send any of those except the offset controls) by number, using offset 3110 with the parameter already placed in 3114. Pete

There are lots of examples you can look at, both in the package installed with FSUIPC and in the User Contributions sub-forum. Pete

Yes.. The WideClient support for Lua plug-ins includes most, but not all of the features in the FSUIPC implementation, plus some additional features. The documentation explicitly says which does and does not apply. Sorry, I don't know what you are talking about. What is "Interface IT"? Pete

FSUIPC4? FSX? You never mentioned this! Saitek devices do not use FSUIPC on FSX, only on FS9! I suspect your problems lie elsewhere -- maybe you've not installed the Saitek drivers? I think your finding that the devices worked before you installed FSUIPC to have been misleading you. Remember I said "if the Saitek devices work when you are unregistered in FSUIPC (i.e. if you temporarily remove the FSUIPC.KEY file) ...". did you test that idea at all? If you want me to check your FSUIPC installation, please show me the FSUIPC4 Log file -- paste it in a message here. Make sure you close FS first. Pete

You don't mention how these are programmed, so it is difficult to advise. Are you writing a program, as it sounds like by your mentioning of "0B58". Or is this all by assignments in FSUIPC? If it's the latter than you can make the operation of one switch conditional on another by adding the conditions in the assignment lines in the FSUIPC INI file. The advanced user's guide tells you all about conditions. You'll need a program to do that. It would be a short Lua plug in. You could sort the whole thing out with a little plug-in. Regards Pete

I just looked at one of my PFD.INI files. I have these settings: StartElecOff=On StartElecAvionics=Off / Switches off the displays until / either a key is pressed or the / offset 0X510 is cleared / It can also check the Avionics / Flag within FS and enable the instruments / one after the other[/CODE] I don't know how they default. Regards Pete

I think whether the PFD/ND/EICAS displays come up dark initially is set by a parameter. I've always had mine so set because when I switch on the cockpit I like it to come on "cold and dark" even before I've finished getting FSX running. I'm afraid I don't recall exactly what parameter this is. Check the PFD INI files. Regards Pete

If WideClient is waiting for FS to start, as you say, then PM's PFD has nothing to display. The black screen is emulating the aircraft screen before it is powered up. All my cockpit screens are black before I switch the battery on, and for that FS must be running and the clients connected. Pete

ALWAYS test on a default aircraft. Many add-on aircraft implement their own subsystems with their own values. FSUIPC's offsets listed are only FS's. The is very old and I cannot support it. you must use 3.999z if you want support. Pete

Saitek use FSUIPC3 on FS9 and before without any license or permission, so I'm rather loathe to support anything to do with them. They simply refused to pay the agreed license fee. However, if the Saitek devices work when you are unregistered in FSUIPC (i.e. if you temporarily remove the FSUIPC.KEY file), but don't when you are registered, then FSUIPC thinks your FSUIPC key is wrong -- illegal or pirated. It might do this, though, if it is simply that your PC has a date set which is before your registration purchase date. Also, it may simply be that you are using an old version of FSUIPC. if you purchased your registration this year you mst use 3.999z or later. I cannot support any older versions in any case. Pete

If you want a single Lua program with lots of alternative actions then that program has to work out what to do, so you'd need to use the parameter (ipcPARAM) with different values for each action and test this (if .... then .... else .... etc). There are examples of such in the User Contributions section. But really, when a large file has to be reloaded and compiled for each button press you'd find it easier and more efficient to keep it simple, one or two (eg on and off as above) actions in each little file. Pete

You still have not stated what aircraft you are using nor the version of FS nor version of FSUIPC! How do you expect any help? Use logging or FSInterrogate to wrok out what you are doing wrong! Pete

You are making a mistake then. All three parts, name, email and key, must be exactly as stated. Cut and paste to avoid errors. Pete

If you cannot program it directly in FSUIPC then I don't see how Linda can help. You need some way of operating the switch in the aircraft -- a keypress, a control, a mouse macro or a local panel variable (L:var). If none of those can be used then it can't be done. If any of them can work, then you can do it simply without delving deep into the complex workings of inner Linda. function Lights_Approach_On () Lvar = "L:OHD_EXT_LIGHTS_L_APPR_SW" ipc.writeLvar(Lvar, 1) end function Lights_Approach_Off () Lvar = "L:OHD_EXT_LIGHTS_L_APPR_SW" ipc.writeLvar(Lvar, 0) end[/CODE] So, if those are correct for your aircraft, then it uses L:Vars. All you need to do is have one little single-line Lua file: [CODE] ipc.writeLvar("L:OHD_EXT_LIGHTS_L_APPR_SW", ipcPARAM) [/CODE] Save that in the Modules folder as, say, "D8ApprLeft.lua", and assign the switch 109 press to "Lua D8ApprLeft" with parameter 1 and the release to the same with parameter 0. Pete

Is the aircraft a default FS aircraft? Are you reading them correctly? I think they are 64-bit (double) floating point values. You don't even say which version of FS you are talking about, nor the version number of FSUIPC. Pete

If you have a text-based Lua script (not a compiled one) which operates switches in one way and you want to change it, then, yes, of course you can change t, but you'd probably need to learn a lot about the script, unless it is very simple, beforehand so you knew what to change and where. As far as I recall, there are a number of scripts used by Linda and it gets quite complicated. I'd certainly advise getting help from the authors. But without understanding those lines, I don't see how you can do that. Sorry, nor do I! Look at your example: -- ## System functions ## function InitVars () -- uncomment to disable display -- AutopilotDisplayBlocked () end [/CODE] That part does nothing at all. It is just comments. [CODE] -- ## Exterior Lights ############### function Light_LandingAll_On () Lights_Approach_On () Lights_Flare_On () end function Light_LandingAll_Off () Lights_Approach_Off () Lights_Flare_Off () [/CODE] And that part shows two functions which just call other functions. There is no code here reading buttons or switches and no code here talking to FSUIPC. Evidently all the parts relevant to what you want to do are elsewhere. Why would you want life to be so complicated in any case? Why not just assign your button 109 to the landing lights directly in FSUIPC? This must surely be straight forward, expecially if you already have the macros to do that. Why do in in Linda? Regards Pete

You are using an old unsupported version of FSUIPC. Please update. No, they appear to be all there BUT in one direction your switch seems to be break-before-make, and in the other direction is it make-before-break, so that, in the latter case, if you have "release" of the Right selection to indicate 'Off', you'll also get it when turning back from Off to Right. There are two possible ways aroud this as far as I can see: 1. When you want "Right" from "Off", turn to Left first then back to right. 2. Make the Off assignment conditional on the Right button being released. The latter method involvs a little editing in the FSUIPC INI file. Check the section "Compound button conditions" n the Advanced User's Guide. If you don't understand it, get back to me with your current INI file button section. Regards Pete

That's designed to stop the cancellation effect of intervening controls, something that was certainly necessary on some add-on aircraft which seem to be sending controls very frequently, internally. Well, you've really tried everything that's likely to work. There's only one remaining possibility, and that is writing to the FSUIPC4 offset for the door control -- but since that merely sends the TOGGLE_AIRCRAFT_EXIT control with the parameter, I suspect that won't work either. If you did want to try it you'd need to assign to Offset byte togglebits (or setbits or clearbits) with offset x3367 and values 1, 2, 4 or 8 for doors 1-4 (those values can be added for multiple doors). Have you tried Majestic's support? I've noticed AVSIM have a dedicated forum too now. Regards Pete

Sorry, I don't really understand what notes this is referring to. I'm not a Linda user and know almost nothing about it I'm afraid. If you tell me what you need to do in FSUIPC I can point you to it. Pete

Sorry -- I don't even know vbs so you are way ahead of me. I'd only be able to try to find out by googling. Pete

Sorry, I do not support Saitek devices. Regards Pete