Pete Dowson

Sorry, did I say "memory"? I meant things which could possibly rebuild stuff in memory and so cause it to free or defragment some. Things like "reload scenery" and/or "reload aircraft", both commands available for key or button assignment. I think they are called "Refresh scenery" and "Reload User Aircraft". Other things which might help are "Reload panels", and possibly FSUIPC's added "Traffic density toggle" -- use the latter twice to toggle between no AI traffic and your normal levels (this won't work with UT2 added traffic though -- it has it's own shortcuts for that). Regards Pete

Assigning keystrokes to buttons in FSUIPC merely allows the buttons to cause Keyboard messages to be sent to Flight Sim. Whether they are picked up by an add-on will then depend on how that add-on detects keypresses. It might be that it hooks into the FS Windows procedure earlier than FSUIPC. Or it might be that is obtains keypresses more directly, from Windows for example. I really couldn't say. You can enable Keys logging in FSUIPC's logging tab and check that your FSUIPC assignment is sending the cirrect things. It might well be worethwhile asking over in the support forum for that particular add-on. There is also a thread in the User Contributions subforum here which I think provides commands for the Flight1 Mustang. http://forum.simflight.com/topic/63155-flight1-mustang-commands-upd-15th-mar-2010 Regards Pete

Switches and encoders have to connect through Windows as a joystick type device. FSUIPC isn't a hardware driver, it is a software interface which runs inside FS. If your switches are visible to FS then they can be assigned in FSUIPC -- just go to the Buttons tab in FSUIPC options, press the button or operate the switch, and assign to whatever action you wish, including macros. Be sure to disble that device or at least de-assign the switch itself in FS otherwise it will likely have a dual action. If you switches and encoders aren't connected to your PC yet you need to get some sort of interface board. I use Leo Bodnar's BU0836 boards which can connect 8 axes (potentiometers) and up to 32 buttons/switches and a POV. Regards Pete

Sounds like IYP is having a problem with the Internet connection. I doubt this is anything to do with any of my programs. Have you tried IYP support? Robert is quite responsive. It is always best to try support for the program you are having trouble with. If you suspect any WideFS problems, check the logs. There's a WideServer log in the FS Modules folder and a Wideclient log in the Wideclient folder. That's what they are for, to tell you what is going on. Pete

With FS running and connected to that client, just go to the FSUIPC Button assignments tab, then press each of the button screen buttons in turn and assign to whatever it is you need it to do. Regards Pete

Yes, but your code extract is not setting or using the others. Additionally i don't know if "5" refers to the 5th or 6th element (in C/C++ 5 would be the 6th as C/C++ counts from 0. Lua counts from 1. I've no idea about C#). The other problem is that the Lua format for the arrays, whose pointer is being passed, is not going to be acceptable to those Pokeys functions unless the person who made the Lua pokeys library you are using has dealt with this sort of difference. All numbers in Lua are 64-bit floating point. I don't know what C# would use for its BOOL and UINT types, but most likely 32 bit integers -- most certainly not 64-bit floating point values. But whoever wrote the Lua library for pokeys would have surely known that. Well, I suppose the Pokeys folks wouldn't know about Lua in any case. You really need help, or at least good documentation, for the Pokeys Lua interface library I assume you must be using. You need to contact the author of that rather than of Pokeys itself. Regards Pete

No. Well, probably the equivalent in Lua is channel = {} duty = {} ms = pokeys:GetPWMFrequency() / 1000 period = ms * 20 channel[5] = true duty[5] = ms * 1.5 pokeys:SetPWMoutputs(channel, period, duty) [/CODE] but it makes no sense. You have two 6-entry arrays (channel and duty), but only set number 5 in each. And I don't know the external pokeys library, so I've no idea about those two calls. Is there a support forum for the pokeys driver you are using? Regards Pete

You really do need to update. The crash is almost certainly because the SimConnectP3D.DLL installed with FSUIPC4 now is for 1.3 only. Remove it from the Modules folder and it should be okay using the ESP SimConnect you still have installed. if it isn't you need to send the Windows error log to Lockheed Martin. However, they will no doubt tell you that 1.2 is no longer supported. Next time i make a new Installer update I shall need to check for the older version and delete my interfacing Simconnect DLL automatically. but I honestly didn't think it would happen. with an ongoing development like P3D. Regards Pete

I assume you mean that when you select FSUIPC from the Add ONs menu the FSUIPC settings dialogue does not appear? (The FS screen always goes black in any case -- that is an FSX function). This problem is ALWAYS a video Driver fault. Possibly you are using the default Windows 7 drivers for your video card instead of downloading and installing the latest for your specific card? The default driver is no good. The only other alternative is to switch FSX to Windowed mode, which will give no such problem (ALT + Enter toggles between full screen and Windowed mode). Please note that you MUST update your old FSUIPC installation if you want furthere support. The current version is 4.827. Pete

There's really no point in providing an unreadable image. You need to go to the Windows logs and provide the information on the crash If you don't know where to look, press your Windows Start button, type "Event viewer" into the search edit box and press return. When the viewer appears select "Windows Logs" then "Application". Scroll down looking for a red ! marking an error, and the one referring to the Prepar3D process. -- you can see all the details in the pane below when you select it. If you double clcik it you'll get a window with a "copy" button so you can copy the text ready to paste into a message. From the Log, the main problem appears to be that your P3D installation is corrupted: That error can only possibly occur if the installation is bad. You could try renaming the file "SimConnectP3D.dll" or moving it out of the Prepar3D Modules folder. This will force FSUIPC to use the ESP version of SimConnect which you also have installed according to the Install log.. And this shows that you are NOT using version 1.3 of P3D, or at least that it isn't installed correctly. You have 1.2. The version number for version 1.3 is 1.3.3708.0. I strongly suggest you update to version 1.3. Regards Pete

There is no user manual included in the ZIP file. The document included there is the Installation and Registration guide. And that lists the documents you get and where they are installed -- i.e. in the FSUIPC Documents folder in your FS Modules folder. Please do read that Installation guide first, that's why it is packed in the ZIP right next to the Installer! What do you mean by "the float"? I have no idea where you are looking or what your questions are. Names like "rudder trim left" and so on are the names of the FS controls as defined by FS. FSUIPC doesn't invent these. Most should be obvious (like "left" means to the left, "right" means to the right -- what else? -- "set" means directly set by parameter). But I cannot define the meaning of every one of the hundreds of FS controls -- they vary a bit in any case according to which version of FS you are using. FSUIPC just gets the list from FS and exposes it for you to assign to! I certainy think you must be looking in the wrong place. Please go back and check the Installation guide so you know where to look and for what! That is why it is there! Normally trim is contnually adjustable and you adjust in left or right to centre it. If you want a quick centre action just Set it with a parameter of 0. 0 = centre. Follow the numbered steps clearly given in the User Guide chapter on calibration. I am not going to reproduce here large sections of a large manual. It sounds like you haven't read the Installation Guide and so not know where the bulk of your FSUIPC installed deocuments are! :sad: Pete

It isn't FSUIPC resetting anything -- it isn't even aware of such a switch -- so it must be FS defragging memory or even releasing some stuff it now finds out it doesn't need any more. Similar effect to saving the flight I suppose. Regards Pete

There have been no other reports of any crashes with FSUIPC in P3D. As always with any problems I need to see logs. You'll find the Install log and the FSUIPC4 log in the P3D Modules folder. I also need to know the version of P3D (is it 1.3?) and a fuller description of the crash -- i.e. what leads to it, what actually happens and what, if any, information you can glean about it. Ideally the module name and offset address. These will be in the Windows application logs if Windows detected the crash. You can paste logs and other data in a reply here. Regards Pete

Version 4.81 is not compatible with FSX RTM or SP1. You should update to the currently supported version of FSUIPC. Please see all the usual websites. You must have downloaded 4.81 some time ago. Current is 4.827. You can get it also from the Download Links subforum here. You should in any case either install the FSX updates or Acceleration. they fix a lot of bgs. Regards Pete

Looks like you don't see the Wideclient "screen" at all. The INI file shows the position as being somewhere a long way left and above any likely screen you have: Try deleting that line and when you get the WideClient screen coming up, size and position it as you need and close WideClient so it saves the correct data. Alternatively, if you wish, change to Visible=Max Regards Pete

That's the Simconnect menu facility. It is fixed in that format, and can only be answered by pressing the numbers. It isn't any good for keeping data updated for folks to read -- it's a choice system, nothing else. I could offer a straight-through interface for that, but it seems so rigid compared to the needs of the programs I was supporting that it didn't seem worthwhile. Additionally it wouldn't be backwards-compatible for FS9 and before without a lot of work. Is that all you want to use the Window for, an immediate choice and that's it? I did implement the "ask" function for that. Pete

Not at present. The facility is really almost a directinterface to an FS function I found, and only offers the facilities it provides. I don't know if any of the other Lua facilities allow you to get such info -- i.e. the basic Lua libraries? Probably unlikely. Ideally i'd rather use a system like the one in the ext library, where all sizes and positions are in terms of percentages of the screen size, with a screen number too for multiple screens. Maybe I can do that for the Lua Display options, though I think I'd rather look for a way of implementing something more flexible, with multiple window possibilities perhaps. I didn't implement the wnd library in FSUIPC, only in Wideclient, because as it stands it would only be any use for folks using FS in Windowed mode. If I could find a way of having separately created FS child windows working in full screen mode then that library would be far better for your purposes. Unfortunately every way I tried to do such a thing either simply didn't work or created flashing windows. It's to do with DirectX which is presumably where I'd need to delve deeper. I know some add-ons manage good windows on top of FS in full screen mode, so it is possible. The ext library might be made to work with FS child windows if i made it search those as well as top level windows, which is all it does at present. Maybe that would be an easier way. I'll check when i get back later in May. Regards Pete

Okay. I'll consider this, but with Lua it will be named by the most recent Lua program to name it -- the opposite of the FS window created by the 3380/32FA method where the first one sticks and no one later can change it. I'll probably add it as an optional parameter to the ipc.setdisplay function, making the position and size optional too. Maybe read the name with the ipc.getdisplay function too, so nice cooperative programs can save and restore it. I'll look at this when I get beck from holiday, 15th May or later. Too busy this week. Regards Pete

I don't understand much Spanish, but the auto-translater converts this to: To which the answer is: Both FSUIPC and WideFS registration is performed in the Installer. Just run the FSUIPC Installer program and enter one or both keys when it prompts you to do so. The Installation and Registration instructions are included in the document inside the ZIP file. Sorry, only English though. Regards Pete

Duplicated equest? See other answer. Pete

FSUIPC itself, whilst it does add a lot of extra commands, doesn't provide view commands. You need to assign to the appropriate FS command. All of the possible FS commands are listed in the FSUIPC assignment drop downs. I'm not sure off-hand which one the "S" key normally used -- probably either "View mode" or "View type". When I need to find out which command to use I enable "Event" logging in FSUIPC's logging tab, press the key or click the mouse, and then look in the FSUIPC log file where it will be listed with both number and name. There's a complete list of all FS controls installed in your FSUIPC Documents folder, within the FS Modules folder. Regards Pete

For the ipc display library, why not use "ipc.linedisplay" instead? That gives you a complete line-oriented display capability. It's the one used in the examples supplied, like hidDemo and GFDdisplay lua programs. I use it for logging stuff too in many of my programs for my cockpit. That title is related to the offset 3380 text window. The Lua window has a fixed title. There's only one such Window in any case, shared by all Lua programs. That's wht the ipc.setdisplay function is for! Pete

Yes, please see the FSUIPC offsets list. Use offset 3380 (for the text) and 32FA (for the control). Multilined text is done by including new line or return codes in the text ("\n" or "\r" in strings, same as the byte values 10 and 13). This is what Radar Contact uses. You are limited to 127 character maximum, with a zero terminator. The Lua display facilities are actually a lot more user-friendly, but it's your choice. On a WideFS client you can use the Lua wnd library, and even control its size and position with the ext library. Regards Pete

Sarcasm isn't welcome here, especially when it is completely off the point. i know nothing about Saitek drivers nor any Saitek equipment. If you want support for Saitek you must go to Saitek support. I support FSUIPC and WideFS, not any hardware, and especially not hardware from a company which doesn't pay its invoiced license fees! Please don't come back here again. You aren't welcome. Don't bother to purchase FSUIPC. Pete

The tiller is meant for a separate axis, not the same axis as the rudder pedals. I'm really not sure what sort of result you could expect from having them both on the same axis. But if you don't want them conflicting you'll need to assign both "direct to FSUIPC calibration", and then calibrate both. Obviously it would be pointless doing this is you calibrate them both the same way. I guess you'd calibrate the tiller with a steeper slope (-ve number) and the rudder with a slightly flattened one, so that the tiller is more responsive. That's only my guess though. i've never tried using the same axis for both. Pete