Pete Dowson

something is very seriously wrong on your system if FSUIPC managed to locate and load a Lua program without the "lua" filetype. It sounds like you have Windows hiding filetypes from you or something. FSUIPC searches for All *.Lua files, it will not see any others as Lua. Yres, as I said. You could add other RunLua lines to it if you wanted more Lua programs automatically running in future. The exact syntax was exactly as I told you, and i also told you that you could add similar lines! It seems you did not really read my reply! I repeat the relevant part here: ... have an ipcReady.lua file which runs any others you wish, via one statement for each like: ipc.runlua("GFpower.lua") It's not exactly "programming" to make a file with one line in it copied from a message as I showed! :-( Pete

The latitude and longitude of the aircraft is certainly available in a couple of places in FSUIPC offsets. You'd need to consult documentation for Phidgets to find out how to drive their displays though. Sorry, I know nothing about them. Regards Pete

Damian and I are working on it. Not long now ... Regards Pete

Not recently.There were no suitable files last time I looked, but I'll try again. [LATER] Still as it was several years ago -- the only shared Boeing files are for a 737-200 and a 747-100/20 with RB engines. There's a "basic" model B737-700. Maybe I'll try that, but I fear it might be worse than the one I have already. Regards Pete

If the frame rate problem is completely dependent upon the size of the window then it must be something to do with the way the video screen or desktop is configured. If I were you I'd post on the general FSX Forums, both here in SimFlight and over in AVSIM. It certainly isn't anything to do with FSUIPC. In fact I've no idea why you would even mention FSUIPC in the same message -- how is setting a 2 x 2 window in any way related to FSUIPC settings? Regards Pete

As documented in the Lua documentation (see the FSUIPC documents folder inside your FS Modules folder), the Lua files automatically loaded are ipcInit.lua, which is run right at the beginning of FS, before anything is loaded, and ipcReady.lua which is run when FS is ready to fly. Use the latter. You can either rename your file to ipcReady.lua, or, probably better for future expansion, have an ipcReady.lua file which runs any others you wish, via one statement for each like: ipc.runlua("GFpower.lua") Pete

Dammit. It's this new Forum software. It has separate links and viewable text, and I keep forgetting to edit both! Grrr. Please try again! I managed, eventually, to get the winds and temperatures included -- I somehow had a ridiculous flight start time and date for the flight. I suspect it was because I started with one of my large library of plans. I can see I'll be re-planning my routes each time from now on! ;-) I always find it's optimised altitudes way out for my B737 or B738. I'm going to have to work through the aircraft files for them to see what's wrong -- they were supplied to me by one Stamatis Vellis (who I don't think is flying sims these days) a long time ago. I don't suppose you have any good advanced model B737 or 738 Jepp aircraft files? Regards Pete

Okay, done. Version 2.11 if FStarRC works fine with FliteStar 9.521 build 15211. Tested here under Win7 okay. Download it from the Downloads subforum. Hey, I like the new free internet weather facilities in this update to Flitestar, but do you know how to get the Wind data automatically inserted into the Report and used in the fuel and time and best altitude computations? Regards Pete

If you assign both via FSUIPC as "direct to FSUIPC calibration", and calibrate in FSUIPC, then FSUIPC will prevent any contention in any case. It will arbitrate between the two, acting on the one providing the largest deflection from 'centre' (or 'idle' for throttles). This way, whichever one is actually being used is the one which is in control. Regards Pete

This is because Windows is assigning the different ID's after you rearranged the USB connections. It is precisely to get over these sorts of problems that I introduced the "joy letters" facility in the first place, but you are not making use of it. If you adopted letters for the different devices, as advised, then FSUIPC would be able to keep track of such changes, automatically. What is wrong is that your device 2 doesn't exist now and has become device 3 instead. You have already noted this! Therefore in every place where joystick 2 is mentioned, in [Axes ...] and [buttons ...] sections you will have to change the joystick number from 2 to 3. Otherwise you need to find the combination of USB plugs and sockets to reproduce the original configuration, and use the joystick Lettering facilities in FSUIPC to avoid such problems in future. Regards Pete

I use both Its Your Plane and Radar Contact on a WideFS client. I find both much more responsive that way, and you have the additional benefit of a separate sound system for them -- e.g. for a headset and/or overhead speakers. I don't know about FS2Crew though. Perhaps their documentation, or support forum, might tell you? Regards Pete

FSUIPC does not interfere by itself with any of those systems -- it does nothing at all unless asked to. Maybe one of your add-ons is using FSUIPC to change them? Or, for the spoiler, maybe you have assigned an axis to it and not calibrated the ARM position correctly? Regards Pete

Thanks! Pete

Sounds like there must have been a fault (like a sequence number omitted) in the SCENERY.CFG file. Regards Pete

Since I've never heard of "hls, dls or cigi packets" I've no idea, but you can easily find out by reviewing the information in the FSUIPC SDK, for the FSUIPC interface, or the FSX SDK, for the SimConnect interface. FSUIPC also supports the Lua scripting language so you could evaluate things quite easily before plunging into C, C++ VB or other heavier code. Regards Pete

Selecting the FS "axis throttle" control, or the "direct to FSUIPC calibration" option? It makes a difference. The right-hand side is completrely irrelevant to your needs. If the throttle is not responsive in FS the reason depends on how you assigned it, which you don't say: However, the most likely reason is that you have not calibrated it! Your throttle is evidently very jittery and thererfore being seen each time. If you read the user guide you would find that to get around this you can use the "ignore" button, so FSUIPC will temporarily ignore the annoying jittery axis whilst you do the others. Please do read more! I cannot help further now till Monday as I am away till then. Regards Pete

You only show half the story. There's a WideServer log too, in the FS Modules folder, which might give more information. The "WideClient0" log is merely the one before the "wideClient.log", from the previous WideClient session. However, the client log does show that although the Server is discovered it doesn't appear to accept any data from the client. This is most likely due to firewall settings, either on the Client or on the Server. But the WideServer log might show differently. Regards Pete

If you are assigning to FS controls and the aircraft doesn't support those controls, then obviously nothing will happen. I'm pretty sure most things on the PMDG aircraft are either susceptible to the FSUIPC Mouse Macro facilities or the L:Var system. Check out the User contributions sub-forum on this -- I just looked and this thread is relevant and even provides the plug-in to allow you to assign butons or keypresses to all sorts of things in that aircraft. PMDG 747X commands (upd 9th April) Regards Pete

Er ... all that seems a total waste of energy when FS already has a keyboard shortcut assigned to that control. Check its list in Settings-Controls-Buttons/Keys. It's assigned to Shift+R by default. If you wanted to use H instead you could have changed it there. It certainly would have if you'd used a default aircraft. Most PMDG and other sophisticated aircraft add-ons don't use the FS-implemented autopilot and autothrottle, but their own. You'd need to find out how to assign in that aircraft, not in FS or FSUIPC. FS controls are directed to FS, that's why they are called FS controls. Deleting FS's assignments of keypresses to FS controls and then assigning them in FSUIPC to FS controls doesn't really make much sense. If all you want to do is assign keypresses to FS controls you can use FS, either defaults or reassign. Apart from which there's no conflict with keypresses -- those assigned in FSUIPC will take precedence over the same keys in FS. It is only with joystick buttons, axes and switches you need to take such care, because Windows allows multiple users to read the same devices. Regards Pete

Shame. Having their own format is all well and good, but they should support a common one as well. My update to FliteMap arrived today, but I'm out now till next week so I'll look at it when I return. But at present I'm sorry but I'm not considering adding any new formats. Regards Pete

Great! Thanks for getting back on this! As far as I recall FS9 didn't have any sound selection options, though you could try assigning a different device to voice in the windows control panel Sound applet. Regards Pete

Where do you get 127 form? You just quoted the documentation saying 256. I would advise you not to get anywhere near that number. Each running Lua plug-in occupies at least one thread, up to 5 threads for those using the COM, Sockets or VRI stuff. Pete

WARNING: The "CM2" in many of those lines refers to the macro File number (2) in the list in the [MacroFiles] section of the INI, so that will have to be checked , or edited, to make sure it refers to the Macro file you list. Regards Pete

You'll need to ask the makers of those add-on aircraft how to operate the door seal, then, because FS doesn't simulate it and FSUIPC is an interface into FS variables and controls. Add-ons do their own thing. Regards Pete

It might take a while. I don't know what I've done, but in trying to repro the problem I've got my dev system in a state where neither FSX nor ESP (separate installations on the same PC) will go into full screen mode without crashing! Must be something to do with drivers I guess as there's been nothing added or changed in my ESP install. They are both fine in the normal Windowed mode which I have to use for development (with loads of other Windows to keep tabs on). I'm pretty busy with other stuff for FSUIPC at present, so I can't really start messing with my sdev system to sort this out. I'll try and get to it when I'm on top of these other developments but it may be a couple of weeks or more. If you've not heard about it by the end of November, remind me in case it's got lost under a mound of other stuff! Regards Pete