Pete Dowson

If it appears in the Add-ons menu and you can use it, then there MUST be an INI file and a LOG file and an INstall log, and the problem is that you are simply looking in the wrong place! It may be related to UAC and a default install location, as Andy suggests, but I don't think the files are "thrown out". The way Windows tries to "protect" you is by only showing you the originally installed version of the Folder, not the one actually in use -- and changes there don't affect the real copies. Try running Windows Explorer "as administrator" (a right-click option) to see if it shows you the correct folder then. When the Installer runs it creates the Modules folder with full user access, so you should always be able to see it no matter what privileges you use. However, it is just possible that, if you did not run the Installer itself "as administrator", as instructed in the provided installation instructions, the folder still doesn't have full user rights. If you have allowed FSX to install in the default Program Files folder then you will probably have problems with lots of add-on programs which need to access those folders. There are two ways around that. Either run FSX, and all add-on programs for it, "as administrator", or turn Windows UAC off. Pete

Rotary switches send "button press" and "button release" alternately, so the answer is to assign the same action to both press and release. Pete

Sorry, is there a question here? EZCAM is okay, what is the question for this Forum? BTW 4.92 is not supported The current earliest supported version is 4.921f, and there is an update to 4.921i available. See the Download Links subforum. Regards Pete

Oh, okay. Thanks for letting me know. Pete

What was "insuccessful" about the previous install? Is there an INI file generated? Is there an AddOns menu is FSX flight mode, containing FSUIPC? It would help more if you pasted here the Install log. Regards Pete

As far as I can see it is not FS version-specific. There might be some failures which aren't common between FS9 and FSX, but there will be as many as possible. It uses FSUIPC offsets which are designed for cross-version compatibility. Pete

It is "mouse look". For space bar use you should assign it in the Key press assignments. Assign key press to mouse move on and release to mouse move off. you can assign to any key or button. The mousewheel operates the zoom too. Mouse move moves the eyepoint in the cockpit, left right, forward, backward. BTW if you use EZDOK, why bother with these other facilities anyway? It does what you want too, surely? Pete

Well, it's lucky that through an oversight some of the axes assigned "direct to calibration" are let through even if calibration has not been set. That doesn't happen on all axes, and didn't used to happen on FS9. I haven't fixed it for fear of messing installations up like yours where althoguh you assigned "to calibration" you never actually went to the calibration page and enabled it. Best to delete the [Axes] line for that if you are not using it, or it could interfere. It's the one to D,25. Yes, of course. You've not read much of the supplied documentation, then? Miscellaneous page: there are mouse move, mouse look and mouse trim options. Yours is mouse look, and you can do it with the middle mouse button held down, much better than the space bar. It applies to all views as far as I know, at least in virtual cockpit mode. Regards Pete

Okay. that was quick! However, I notice you are still only using default calibrations: Elevator=-16380,-512,512,16380 Rudder=-16380,-512,512,16380 Throttle=-16380,16380 Aileron=-16380,-512,512,16380 Have you not tried doing proper calibration, following the steps in the user guide? Also you still have the spoilers and a reverser assigned "direct to calibration", but with no actual calibration set. Pete

Yes, I assumed you were using FSUIPC's axis assignment from your original message, but there are several ways of assigning everything there and different controls you can use. Hence my question. That's the INI file, with your settings. did you try logging, as I suggested? First off, your FSUIPC is out of date. Version 4.920 is no longer supported.. You need to update. Second, you have very little actually assigned in FSUIPC: the only axes you have assigned are listed in your INI file: [Axes] 0=1Z,256,D,4,0,0,0 1=1V,256,D,22,0,0,0 2=1S,256,D,25,0,0,0 These are, respectively, Throttle, Spoilers and all-engine Reverser. All are assigned "Direct to FSUIPC calibration", but these are your calibrations: Elevator=-16380,-512,512,16380 Rudder=-16380,-512,512,16380 Throttle=-16380,16380 Aileron=-16380,-512,512,16380 which include only "Throttle", making the other two assignments pretty useless. Furthermore, these calibration values are the default values set by FSUIPC ready for you to adjust to suit your particular controls. It seems you've not yet actually processed througfh the necessary and documented steps to proper calibration. If, as you say, your elevators and rudders are working then you evidently must have these assigned in FSX, not in FSUIPC. The default FSUIPC calibration values will still apply, of course, but not being true calibrations they may not be having the best results. Really you are in danger of having conflciting assignments because assignments in FSX will conflict with any similar ones in FSUIPC. You should choose one or the other. You can still calibrate in FSUIPC either way, but there is little point if you simply leave the calibration values to default. Maybe you deleted some earlier INI file and are left with some later changes, forgetting you'd deleted everything beforehand? Otherwise i cannot imagine how you've had successful use of these facilities in FSUIPC before now. Regards Pete

More information needed I'm afraid. How is it assigned -- i.e. which mode of assignment and which control? Is it calibrated in FSUIPC or not? Is this with FS9 or some older version, or FSX or P3D? What actual version of FSUIPC? If you don't know any of these things, maybe you can paste in your FSUIPC INI file from the FS Modules folder? That would fill in many of the answers. Additional, however, is whether it is the same with default aircraft as well as whatever add-ons you are using. Finally, you could, for yourself, try some of the logging facilities to see what is going on -- axis logging, for example. See the Logging tab in FSUIPC's options menu. Regards Pete

If there is no INI file produced and also no LOG file then FSUIPC has not even run, so it cannot possibly "sin". It looks exactly like you have not actually installed it at all (!), because if you had there would be an Install log and a subfolder called FSUIPC Documents with all the documentation and other add-ons (Lua mainly). Also, the documents you are listing are never installed in the Modules folder, only in the subfolder., so I'd guess that you cobbled the contents of that folder together yourself? Just delete those files and run the latest Installer for FSUIPC4. See the Download Links subforum.. Pete

The FS controls, the ones you can assign directly in FS, or also in FSUIPC. The controls that everyone uses everyday for most aircraft. The ones listed in the assignments list in FS and in the assignments dropdowns in FSUIPC. There's a list in the FSUIPC Documents subfolder too, in your FS Modules folder. Well, they wouldn't and shouldn't need to repeat the Microsoft documentation and Help for FS. But didn't you ask your question there, where there's more likely to be folks who know what you need to do? Log them using the FSUIPC assignable control for this, or the Lua plug-in called Log Lvars. The FSUIPC just lists them each time you use the assigned control, whilst the Lua plug in version logs changes so you can see which buttons and switches do what. Pete

Do you mean the distance from your aircraft, or, as I will assume, the maximum distance from the NAVAID which you can receive it? If you mean the latter then it would (should) depend on your altitude and other factors like the weather. I don't know how much that stuff is simulated in FS though. MakeRunways doesn't provide NAVAID data, except for ILS's as they are parts of the runway data. There are programs which covert BGLs into readable XML format. Maybe the range is in that data. Sorry, it isn't something I really know much about. ILS reception in general would be about 20-25 nm, but only within a certain angle from the LOC. And it would (should) vary according to terrain. VORs vary considerably depending on whether they are intended as High or Low level NAVAIDs, or just locators like Markers. I don't know offhand whether the range is set in the BGLs by a numerical value or by type. You'd need to decode some ad see, or refer to the BGL documentations. Sorry if I'm not much help here. I could do the research, but then so could you. ;-) Regards Pete

Well, it isn't that specific BGL causing the problem. THis also explains why it changed between two versions of MakeRunways. I think there is a bad BGL in your complete list somewhere, and it is causing some sort of memory corruption which then causes the crash later on. I need to get to the bottom of that, so, please, as a first step could you ZIP up the Runways.TXT file in its entirety and email that to me? It will still be a few megabytes even zipped I expect. I might then have to add yet more logging into MakeRunways to track down the culprit. However, there is a quicker and easier way, if you don't mind doing it. It is a bit tedious. You'd need to make a safe copy of your SCENERY.CFG file, and then do a test with each layer in turn disabled. Once you've nailed the layer responsible, then find it in an earlier Runways.txt and send me the airport BGL(s) listed for that layer. If you have a large number of layers (I have about 450!) then you would find it quicker to disable half at a time, identifying the half responsible, then halving that, and so on. This "binary chop" method would reduce the number of test runs for my 450 layers from 449 tests down to just 9. There is a program which helps manage scenery layers in this way -- something like SceneryConfigEditor I think. It's freeware. Thanks, Pete

Don't the regular controls work? Have you checked their documentation for alternatives? Does the panel use L:Vars? If so you can try those. Otherwise, does it support keystrokes for its functions? If the makers of the aircraft simply do not want you to use any hardware with their aircraft then they don't need to supply any way of doing it for you. But perhaps you should first ask in their support forum? Regards Pete

Your email still has not arrived, over 6 hours since you said you'd sent it. Can you check you got the email address correct, please? [EDIT] It arrived overnight. Deley very strange. Never mind. I'll test it this morning. Pete

That just means the gauges are not written in a way which allows Mouse Macros to work. The gauges have to be written using the standard Microsoft C/C++ gauge SDK. Very few new aircraft use it these days. Surely heading inc/dec control is by standard controls in any case? Pete

I have not received this yet. I have to go out now -- I'll check in the morning. BTW in case I cannot reproduce the error, can you paste here the last entry and error details from the log again, please. Pete

That information is very useful, but as Andy says, the version you are using is rather old. Maybe there is still a problem, and the crash data at the end of the log would be very useful to work out what it is, but it needs to refer to the current version (4.674). I might be able to check it here with 4.674 too, but I'd need that BGL file. . Addon Scenery\scenery\AFX_ULWK.bgl Do you think you could ZIP it up and send it to me at petedowson@btconnect.com? Thanks, Pete

Sorry, I don't know because I have no information. I need to know the version number of MakeRunways -- if not the latest you need to update, please. And there will still be a file called "Runways.txt" generated because that logs exactly what the program is doing all the time. Either show me that, or if it is quite big (and it probably will be), just extract the last few entries -- including the last heading which says what Layer it was processing, and probably which file. It is likely you have a corrupt or bad BGL scenery file, or maybe just a very unusual one which MakeRunways doesn't understand. We have to identify that file. Regards Pete

I don't know whether the L:Var name is correct (I don't have that aircraft), but if it is I can see two things wrong: As Roman says, the first example should have "ipc.writeUB" as the function called, not "ipc.writre". The second example shows a little misunderstanding of how a function is defined: function DOT_ALT_chg ("L:AB_AP_ALT_Mode",dot) You cannot provide a constant like ":AB_AP_ALT_Mode" as the name of the parameter to be filled in by the caller. That has to be the name of the variable to receive the name of the LVar. So: function DOT_ALT_chg (name, dot) Okay, you do not use 'name' in the function, but the purpose is to allow one function to handle more than one LVar, so the name then becomes useful. (Sorry, I see the documentation is a little misleading here -- it is expplained in words but the example is poor). The value of that LVar is provided in 'dot', so you don't need to ipc.readLvar in the function at all, it is supplied for you. So this should do it: function DOT_ALT_chg (name,dot) ipc.writeUB(0x66CC,dot) end event.Lvar("L:AB_AP_ALT_Mode",100,"DOT_ALT_chg") The other thing to consider is whether the value returned for the LVar is going to fit adequately in an 8-bit Byte (66CC). Do you know its values? If it is only a 0 or 1, like a switch, then it should be okay, but you need to check. Have you logged its values to see? I'm afraid I don't know SIOC and cannot comment on whether this is correct. Regards Pete

Assigned in FSX to what, exactly? It can if you assign it as a set of switches, because you then assign it to the individual panning controls. If you assign it as an axis, then probably, but not easily. I think you'd need to use aa Lua plug-in, which would receive the angle (the 0-360 value) and transform it appropriately. So 0 to 180 needs to be 180 to 0, and 180 to 359 needs to be 359 to 180. So if X <= 180 then X = 180 - X else X = 540 - X end Pete

Not sure why. I offered to do the condition for you. So I examined the data you posted ready to do it. I compared line by line to see what was going on and found only one line changed, with two buttons to change it with. I merely pointed out that it was a waste of time doing it for this. What is so upsetting about that? I offer to do the work for you, and you come over so ungrateful? So why not show me the lines needing the change? I saw no way of doing what you wanted with those two sets -- remember, you wanted to switch between two sets. All you needed to show were the ones needing changing. So I don't understand why you gave me two modifier buttons. How was I supposed to apply two modifier buttons to one changed button action? Don't you see this makes no sense? How rude and nasty you are!!!! I go out of my way to offer to do it for you, and you talk to me like that? I spent quite a while poring trough the two lists line by line to see what was going on, which is how I found only one change. I've got better things to do than waste my time with people like you, and I would certainly earn more than $40 in the total time I wasted on you in a regular job! :sad: His was one of the two alternative ways I mentioned in the first place, when you then came back and said it was simpler than that, just a button to switch betweeen two sets of actions. I offered to explain further or do it for you. You took me up on the latter then get stupidly upset when I merely point out the data you supplied wasn't related to the question you asked and explained exactly why. Good bye. I'm out of here now. Pete

But both sets are virtually identical! I can see only one assignment which is different -- 36= for button P3,0. Is that the ONLY one you want switching? If so it seems a little daft using one button to switch one other. You might as well assign both to the respective functions and be done. Er ... you only want ONE button to hold down to select the alternate, surely? When unpressed it's one set, when pressed it's the other. What are you going to do with TWO buttons to select with? Makes no sense, and is not what you said you wanted at all. Regards Pete