Pete Dowson

To get you started, check out the example Lua plug-in called "record to csv". That isn't making GPS type records, but a comma-separated-values file containing lots of relevant information. That format is readable directly into Excel or other spreadsheets for easy analysis. Regards Pete

Cancel what dialogue? That makes no sense, sorry. If there's an outstanding dialogue awaiting a reply nothing else runs. dialogues are "modal" which means they stop everything whilst active. But "uninstalling" consists only of deleting the DLL, and all reinstalling it does it put the exact same DLL back! It cannot possibly make any difference whatsoever! It sounds more like you made some real mess of some of your settings, and when you "uninstalled" you deleted the 'bad' settings by mistake. You most obviously have something else completely going on, then, because FSUIPC isn't even loaded until FS is properly loaded, and does nothing at all until you are ready to fly. I think you are ascribing your troubles completely incorrectly. BTW, you don't even mention the version of FSUIPC you are using. This is always needed, or you waste time posting here. The oldest currently supported version is 3.99, so if yours is older I advise you to update. Pete

Uninstalling and reinstalling things rarely truly helps, unless you start with Windows itself, reformatting the hard disk. Quite often, especially wiyth FSX, reinstalling it makes things much worse because parts of it don't uninstall properly and then won't reinstall. This particularly applies to SimConnect, which is the part which loads and runs those things you want to see in the Add Ons menu. It might not yet be quite that bad, however. If re-running the FSUIPC4 installer (NOT uninstalling anything) brings FSUIPC back to the Add-Ons menu, then the other missing things are probably missing because of a corrupted DLL.XML or EXE.XML file. Even if re-running the installer does not work, it still might be due to a badly corrupted DLL.XML file. Some installers are prone to make a mess of that file, which is probably why yuo are experiencing the problems after installing each add-on. Best thing hen is to find the DLL.XML and the EXE.XML files (you might not have the latter). They are in the same folder as your FSX.CFG file. If you don't know where to look for that, show me your FSUIPC4 log and I'll point it out. When you've found the fil(s) you have two choices: 1. Either delete them both, then reinstall each add-on, ONE AT A TIME, testing after each. If, after any of those installs, the Add-Ons menu disappears or loses an entry, you've just found the bad installer and can start again, omitting that, and report to the relevant support. 2. OR you can paste the files into a message here (they are trext files) and I'll se if there's some simple corruption which you can fix by hand. Regards Pete

Sorry, this is not at all related to any of my software. FSUIPC is an interface for FS, it isn't any sort of video or hardware driver. I've never heard of "imo", but surely there must be some sort of driver for your touchscreen, so you probably need to see what facilities that has. Pete

I will add the mouse wheel zoom. Maybe soon. It is only omitted because I did not know about it. [LATER] Okay. It is now added. Please download version 4.713. Regards Pete

Sorry, he didn't say anything like that. And you surely must be wrong. Just updating the version of FSUIPC changes nothing of itself. The original FSX mouse look must be the same as it always was as nothing is touching it. Only enabling FSUIPC Mouse look will change things. But you would only do that if you had already disabled FSX mouse look completely by disabling controllers. That's the whole point (the ONLY point) of adding the FSUIPC facility in the first place! Pete

Does the FSX mouse look do a zoom with the mousewheel? I didn't know that! Masybe when I have another bit of free time I'll look to see if I can add that. The problem is that i've never used any of these mouse facilities before. A mouse is an unwanted invader in my cockpit, just as a keyboard would be! ;-) The mouse wheel trim is a different facility. Yes, if you've enabled it, it will work in mouse look mode too, at present, because I didn't know the mouse wheel was used differently in that mode! Pete

There most certainly IS a problem. your flap axis value for flaps 0, as you can see, is 12288. That's almost maximum! YOU STILL HAVE NOT EVEN SET THE "REV" OPTION, AS INSTRUCTED!!!! THAT IS PROBABLY WHY YOU ARE GETTING THE VALUES IN THE WRONG ORDER!!! Can you not see the Rev option, still unselected??? Yes, of course, because you tried to set that flaps value to a LOWER setting 5771 -- see "IN") than the 0 flaps value already set (12288). The settings must increase. You cannot have the detentes in any old order, they must increase with the axis input. Then in your second picture you are trying ot set -188, an even lower value!!! Please do read the screen values. They tell you what is going on. It really isn't at all complicated, it's just mapping IN numbers to OUT values needed by FS. You'll need to start again. cancel the detentes, set REV and calibrate, THEN set the detentes. how many times do I have to tell you the exact same thing? :-( Pete

Right ... I've gone back and tested that to exhaustion in the default Cessna 172SP. It doesn't operate with the mouse at all in the virtual cockpit, only in the reproduction of that switch on the full panel (shift+1). This is true here regardless of FSUIPC's mouse look option, and even with FSUIPC not even loaded. The FS controls for that switch are pretty obviously named, so I'm surprised you never found them: FUEL_SELECTOR_LEFT FUEL_SELECTOR_ALL FUEL_SELECTOR_RIGHT I think the lack of mouse operation on the switch in VC mode is an FSX bug. Regards Pete

Please re-read the part of the User Guide headed: After a few paragraphs you will reach this: The "IP address" should strike you as being relevant since that was what you knew you had to set, no? :rolleyes: No. All that stuff is far too complex for my aging feeble brain. Sorry.;-) Pete

What would be the purpose of such a thing? It would be far easier to implement it as a simple Lua plug-in. It would only need to be a few lines in Lua, reading the relevant offsets, formatting the line and writing to a file, based on a 1 second timer event. I always tend towards solving simple requests in simple ways, and the Lua plug-ins facility was exactly intended for such purposes. Regards Pete

That's extremely odd, considering the mouse look function only does anything at all when enabled with the mouse look toggle control! I'll check it here. Do you mean the fuel tank selector (left/right/off on the Cessna, for instance? Or do you mean the start levers (idle/cutoff) on jets which enable the fuel for starting? You can always determine what FS control is being used by enab;ing Event logging in FSUIPC then operating the control and looking in the log. [LATER] I'm afraid you'll need to explain your problem in more detail as I have tried every switch to do with fuel or fuel tanks in several FSX default aircraft and i cannot find any that are in any way affected by the setting of the "mouse look" checkbox in FSUIPC. As I said, there's really no way I can see it having an effect as it does nothing unless mouse look is toggled on (with the mouse pointer changed to the cross-hairs). I'd need to be able to reproduce the problem, and I cannot at present. Regards Pete

You need to select the direction (REV) before calibrating, else the calibration will be oriented for the wrong direction. If everything is symmetric it doesn't matter so much, but it rarely is. Pete

Yes, sorry. The heading is degrees TRUE. I forgot to compensate for magnetic deviation. The difference where I tested it is quite small so i didn't notice. This line in the Lua needs to be changed: heading = math.floor(((ipc.readUD(0x0580) * 360) / (65536 * 65536)) + 0.5) Change it to heading = math.floor(((((ipc.readUD(0x0580)/65536) - ipc.readSW(0x02A0)) * 360) / 65536) + 0.5) I'll have to amend the sample in the Lua download too. Regards Pete

The onlt parts of the INI file which are re-read during a session are the Keys, Buttons and Axes assignments -- you do it via the Reload button on each of those tabs. Like most other programs all normal INI file parameters are only read at start up. (INI stands for "Initial"). You have the flaps lever reversed. Zero flaps is with the lever full forward, but for throttles that is max thrust. Minimum flaps (0) needs a minimum value sent to FS, not a maximum value like max thrust on a throttle. Assuming you don't want the axis running the opposite way to real aircraft flap levers, flap axes have to be reversed BEFORE calibration. There's a REV button for this. The same would apply to spoilers / speedbrake, as the "off" or "down" position is also full forward. You might also find toe brakes on pedals need reversing because, for some reason, manufacturers seem to usually make them sending there max value with feet off. Always get the direction working correctly, then calibrate. Assign detentes last of all. I did actually advise you to calibrate first -- if you had done you would have surely noticed that you needed to reverse the axis? Using the detente facilities provided and documented (there's a two page section in the User Guide on that very subject. Didn't you look?). But do this AFTER you have calibrated with the direction set correctly!! Pete

Since I wasn't even aware of the FS "flaps detents set" control and have no idea what it does, I can't really help with that. I thought you were happy exploring it on your own. And you can see that you have three ranges set, two of which cover the entire pssible input range from 5594 to 16384, only, oddly, leaving are shorter range from -2198 to 5594 in between!! As adviced before, if you want to use a flaps axis I would strongly advise using the flaps axis control -- either one, FLAPS SET or AXIS FLAPS SET would do, though generally the latter is probably best as it is the one FS would assign if you used FS instead. just get it working first, calibrate it like any other axis. Do not bother with any detente settings until it is correctly calibrated, and able to actually select all flap positions. Only then enable detentes in the calibration section as calibrate them one at a time. Though bear in mind what I said before. Detentes are well and good if you only ever fly aircraft with exactly that number of detentes. They won't match positions otherwise. I have them in my 737NG cockpit, but I never fly any other plane in it -- only the 737NG for which it was designed. They are two different matters. You only show a portion of the INI file, not enough for me to check, but did you change the UseProfiles parameter in the [General] section? It won't work anywhere else. And check there aren't two such lines, one overriding the other. Pete

No, because it will create more problems for me to answer for those using some add-on aircraft which need the normal FS controls. If i say this way is better than that way then those folks will get problems through following that advice. There is no single solution suiting all. Sorry, but that is not the way it is. All I can do is supply a toolkit which you apply as best you can to suit your specific needs. And there is no way I can know them in advance because I am not the owner of every single add-on out there nor would I have the time and expertise to deal with them all. Pete

Yes, but if Axis Mixture Set does nothing, then either your FS installation is broken, or you have a conflicting assignment elsewhere, or you have calibration set with bad values. There are no other options. It is NOT a function of FSUIPC, but a function of FS. FSUIPC merely sends it on. It is exactly the same as assigning it in FS. Regards Pete

I must apologise. That's a new control to me! I've never noticed it before now. It must have been added in one of the FSX updates and i never noticed -- it isn't in any of my lists. But consequently, I'm sorry, but i have no idea what that FS control does. If you want to experiment with it and see what it does, that's fine, but I think it might not do what you think it might do. Maybe the parameters are merely detente numbers rather than angles? Axis Mixture Set is the same generic axis which FS would assign by default, and affects all selected engines. The 1, 2, 3 and 4 versions are for those specific engines. There is no way Axis mixture Set would not work (it would wreck almost everyone's FS installations if it did not), unless you have for some reason deselected the only engines you have (using the E + 1 2 3 4 keypresses or similar), or you have calibration set incorrectly on that generic axis. Regards Pete

"New FSUIPC tool"? Which 'tool' is that? FSUIPC itself will never do anything it isn't told to, so it can't possibly shut everything down on its own. So what tool are you using with it? Why not simply stop using that 'new tool' if it doesn't do what you want it to? It sounds like you've saved a default flight with everything shutr down, so naturally FS loads it back that way next time. Just find the flight in your documents \ Flight Simulator files folder and rename it or delete it, to force FS to load its normal default flight. Or select an aircraft which is equipped correctly for switching everything on and starting engines (like most default aircraft), start everything and save a new default flight. Pete

Thanks! Got it. Strange that a direct file search for tcas.zip didn't find it for me. Actually, that is probably the best place to put the link to the Avsim file, too. It would be better for questions and any updates or new files too. Would that be okay? I think I should change the Lua document to point folks to the resources available in that Subforum, rather than have them expect the Lua Zip to keep growing and needing more downloads. I'll do that soon -- there's a new "display" library to add (available only in the WideClient implementation), as discussed in this Forum thread: Thank you & Best Regards Pete

Sorry, I don't know them. you may need to check them individually or ask the authors. You really need to at least browse the Lua documents supplied with FSUIPC -- not necessarily the Library reference, which is for those programming Lua, but the intro. You can assign buttons or keys to any Lua program installed in Modules, or run things automatically in several ways. You've lost me there. The controls sent when range entered part of the axis assignments has no "flap detente set" option at all. There is no FS control by that name either. The flaps detentes are part of calibration, not part of assignment. You need to assign to the flaps axis, as with any other axis, then go to calibration and calibrate like any other axis, then, and only then, optionally, calibrate detentes. But bear in mind that if you calibrate specific detentes they are only any good for the current aircraft. Detente positions for each aircraft differ. Unless you are sticking to one aircraft type there is not point in detentes. Regards Pete

There are a few Forums which won't accept you unless you use your proper name -- UK2000, for instance. Hmmm. I see. Of course one never says how many others are living with you and not going on holiday! ;-) Pete

As an FSUIPC plug-in? If so, that's great! Since I originally published the Lua documents, the User Contributions subforum here has blossomed, and there are some excellent Lua implementations there too. Do you think your work should be included in the ZIP package I supply for Lua, or would it be better if you posted on User Contributions? I've had a search through Avism's file library and cannot find your "tcas.zip" at present. Can you supply a link, please? Oh, and if you do decide to post in the subforum, a link to Avsim will be fine. You shouldn't violate any Avsim file library conditions. Thanks & Regards Pete

No idea. I assume it is only on a Russian or at least Cyrillic language version of Windows. Is that whay you have? Not English? According to your Install log, it is English, and it installed okay, so there is no worry about folders. I think you are getting mixed up with completely different problems, nothing whatsoever to do with your signature failure. Why not follow the suggestions I made? Or am I wasting my time here? Regards Pete