Pete Dowson

It is called that. it is Windows which is hiding things from you! If I were you I'd turn that option off -- Explorer menu - Tools - Folder Options - View tab - uncheck "hide extensions for known file types". The FSUIPC user guide advises this action too. Regards Pete

FSUIPC always produces a log file, no matter what you do. It's right there alongside FSUIPC4.DLL and FSUIPC4.INI. If no Log and no INI files exist, then FSUIPC is not running and has never been run. Maybe you have Windows hiding filenames from you, and reporting Log files as "tet files" and INI files as "configuration settings"? Pete

If the DLL was corrupt, it would not run. It would fail its signature check and that would be the error you would get. Replacing the FSUIPC4.DLL with the FSUIPC4.DLL can do nothing. But version 4.8 is out of date in any case and not supported. The earliest supported version is 4.853. Do not use any earlier version. Please see the FAQ subforum threads about FSUIPC4 not running for information about the SimConnect bug which can stop FSUIPC4 and some other add-ons from running. If you want further help on this I would need to see the Windows event log details relating to the crash, and the FSUIPC4 log if one is produced (usually this error means FSUIPC4 is not even being loaded, so if that is the case there will be no Log file produced). Ah. In that case it does sound like your FSX installation is corrupted, or you have installed something which is not compatible. Are you faulty? ;-) I shouldn't think so! But something in your setup might be. I couldn't say about Windows 8. I know there is nothing of mine which will have any trouble with Windows 8, but there may be some hardware drivers which may not be available yet, or which appear to work but really do need some changes. All of my software uses standard user-level interfaces which have not changed. Regards Pete

Not sure what that means. FSUIPC goes into the FSX Modules folder lie many other addons Regards Pete

What's "FSELIMINATOR". Do you mean WideClient.exe? What have USB cables and ports got to do with WideFS? How on Earth does it get to be 2.4GB? How many hours does that cover? What sort of logging options are you enabling? Please do not mess with those options unluss asked. And I cannot offer any help with no information, so you need to at least extract something. What about the WideClient version number and what you are using it for? That would be a start! From the Windows crash data it seems the Cliet is having problems with DirectInput, so you certaniyl need to describe what you are doing in a lot more detail. As it is you provide nothing. I'm afraid i cannot possibly support such an old version. Please update to a supported version before asking for support. Pete

FSUIPC options (Add-Ons menu, FSUIPC), Logging tab, tick the weather logging item on the left. Press OK. The weather data is logged into a file called FSUIPC4.LOG in the Modules folder. Pete

Yes, good idea. You also need to check the DLL.XML file (in the same folder as the FSX.CFG) -- and if there is an FSUIPC4.LOG file in the Modules folder, show me that. You might also want to get a SimConnect log -- there's a FAQ subfrum thread about how to do that. Regards Pete

If you are writing a program to run externally to FSUIPC and drive your displays, then you need to download the FSUIPC SDK and read the documentation there. There are parts for programming in C/C++, ASM, VB, Delphi, C# etc. If "they" say that then there must be a driver supplied with the card and instructions for programming it. I'm afraid I can't tell you how to work with someone else's products. The link points to a page listing lots of products, most dealing with switch and encoder inputs into FS. By "FSUIPC compatible" they may simply mean that their devices emulate normal joystick devices which provide a standard interface to FS and FSUIPC. You need specific information for output to displays, not input from switches which is an entirely different and much easier proposition. If that's what "they" say, and they do mean the card for output to displays, then yes. Who are "they" BTW? You might be better off talking to other cockpit builders. Try MyCockpit: http://www.mycockpit.org/forums/ Regards Pete

Sounds like you've lost your DLL.XML file (from the same folder as FSX.CFG), or maybe something you installed overwrote it rather than updated it, or simply corrupted it. Re-run the FSUIPC4 installer That will either create a new file, or try to correct the existing one. If it still doesn't load, find the DLL.XML file, rename it to something else, then run the FSUIPC4 installer again. Regards Pete

I think you misuanderstand what FSUIPC is. It is not a hardware driver. It is an interface into FS for application programs. Any data you might need can be extracted, but it would need a driver which understands your hardware and interfaces to FSUIPC to extract it. FSUIPC does provide a plug-in facility for small drivers and so on written in Lua. If your hardware has a relatively simple Serial or USB interface which is well documented, it wouldn't be a huge job to write the code. But if you aren't a programmer you should really look for cards which come with drivers for FS already. Also, the interface into FS provided by FSUIPC is free for non-commercial use, so, unless you want to use the Lua plug-in facilities, or use its button, switch and axis facilities for assignment and calibration, you do not need to purchase a registration. Regards Pete

We were in Berlin during a steam railway tour, chartered trans organised by the Railway Touring Company, this last Spring. Visited a few Brauhauses, our favourite for beer and food being Brauhaus Mitte near Alexanderplatz. Best hefeweizen I've come across! ;-) We'll be in Stuttgart soon after New Year, then Augsburg. No other plans for Germany next year, yet. Regards Pete

You'd need to direct them through a Lua plug-in. I can't think of any way of doing that. But you can use offset 0888 to select which Engines are affected by the generic throttle, prop and mixtre controls. Offset 0888 reflects the selection you can make on the Keyboard via E+1,2,3 and/or 4. So if 0888 = 15, all engines, if 0888=10 (binary 1010), engines 2 and 4, and so on. You could use Lua plugins, or, easier, simply use Offset Byte Setbits and Offset Byte ClearBits to manipulate the selection. The more usual way of using a restricted number of axes is of course to use the mapping options, one control onto several is better. FSUIPC can handle engines 1->234, and so on, automatically according to the aircraft loaded, and you can deal with engine failure needs be having buttons or Lua plug-ins to set the "disconnect axis" flags for the engines you want to relinquish control of. regards Pete

If the Lua program which requires it is running in FSUIPC from the FS Modules folder, then DLLs it calls should be in a Modules subfolder called "DLL". If it is being run under an external copy of the Lua interpreter than it probably depends on where that looks. I couldn't say offhand. Version 5.1 has been modified to suit the FS environment before being bolted into FSUIPC. I have not seen what changes there are in 5.2 to make more work worthwhile, but unless your application is explicitly needing something only available in 5.2 I wouldn't worry. Regards Pete

But only the MCP and EFIS units use an ASCII protocol. The centre console, quadrant, MIP and other controls, including the overhead switches, use a binary protocol. The PFC driver I wrote for the 737NG, to interface to FS, is designed sepcifically to work with Project Magenta. The best way for you to proceed would be to specify to Prosim the PM offsets, so that it basically takes the place of PM. PM do publish full details of those offsets. Sorry, what do you mean by "seven options"? Support for PFC serial devices is provided via PFC.DLL and PFCFSX.DLL, and for USB devices by PFCHID.DLL. FSUIPC is needed, but it is used directly by these other modules. I am sorry, but the protocol data is proprietary to PFC and I am bound by non-discolsure agreements. I strongly suggest you either use PFC.DLL or PFCFSX.DLL as intended, or negotiate with PFC for whatever information you think you need to go it alone. Regards Pete

MakeRunways version 4.613 is uploaded. See the Download Links subforum. The XML file still includes airports without eligible runways (as some applications are merely after identiying or locating airports, relating ICAO id to position and vice versa), but now each runway entry in the XML file has two more items: <ClosedLanding> and <ClosedTakeiff> which can be TRUE or FALSE. Regards Pete

So how are you driving your indicators and gauges? There must be some software to handle them. If you aren't programming them, who is? The PMDG 737NGX read-outs are all mapped to FSUIPC offsets exactly as listed in the document supplied -- please see your FSUIPC Documents folder, in your FSX Modules folder. Pete

I would assume it must be a DLL you already have, included presumably with the PoKeys package? A google search gives the makers website (http://www.poscope.com). There are packages for download there, but I would have thought you already had what you need. Pete

Ah. Actually I'm not sure that's possible the way FS has implemented panning. You'd need to write a fairly complex program to do that. The mouse look works on the graphic which is displayed. The panning can go so many degrees each way from the graphic's centre(0.0), and the current position of the mouse is related to a specific point in that graphic, but I don't see any way to determine that in coordinate terms so that the panning can begin from there. You may have noticed that the distance moved by panning corresponds to the movement of the mouse cursor from the centre of the displayed view -- the edges are the extremes. That relationship is destroyed as soon as you move the mouse in non-mouse look mode, so even if the graphics coordinates can be determined, the proportion of movement is then not related to the relative position of the cursor on screen, so things would all go wrong. As I said, the FSUIPC implementation only exists because without it folks who disable controllers in FS have no mouse look facility. Why Microsoft decided that "mouse look" is a controller function, when the mouse isn't actually a selectable controller in its list, I don't know, but that's why there is a mouse look in FSUIPC, and why it is designed to work in the same way as it does in FS. I think you are after something different which may well be offered by more comprehensive view programs like EZCA and TrackIR, and maybe Opus, but is not really part of the role FSUIPC is filling. Sorry, Pete

The FS control "EXIT" does this, as does CTRL+C, and of course, closing the Window using the normal close button, top right. You can send any of these to FS to close it down. In fact you can simply get its Window handle and send it a "WM_CLOSE" message. That works with any program. You don't need FSUIPC for any of this. The confirmation "Are You Sure" will still occur unless you change that FS option. Pete

It's okay. I don't want those. The email from SimMarket would not point to a download location which supplied 4.30 in any case. I've searched for rogue copies lying around on the 'net, and haven't located any 4.30 version, so I think it might have been a mixup on your PC only. Maybe something else you installed also overwrote your correct version with an older one -- there are some bad add-on installers which do that. It isn't anything to do with licensing or payment, only the use of an out of date copy. Forget it now. Pete

I've looked into this. Unfortunately it isn't anything simple like a window handle change -- the different VC views are all using the same Window. But, at least for the standard views included in default aircraft, they do have different Window titles. So I can detect a change in those. I've implemented this is a version for you to test to see if you like it. All it can do is reset the view to centre when you use Mouse Look after changing views. To work from the last position in that view would mean saving the Window titles and positions for every possible such title, as it ses them, and the number of such views is not predictable. I am not really willing to go that far. I don't think the result is better in any way, and, worse, it it is different to the way the built-in FSX mouse look works -- the latter works the way FSUIPC does now, before this change. Since the whole reason for me implementing mouse look in FSUIPC was to duplicate the FSX facility, which is made inoperative when you disable controllers (which folks often do when assigning everything in FSUIPC), I really want the facility to be identical as far as possible. Anyway, try the changed version. If you like that better I can make it an INI -file selected option in a proper release in due course. But the default action needs to replicate the FSX implementation. Download FSUIPC4859e test, try it and let me know. Pete

I don't know. It depends how FS behaves. Did you try the FS mouse look to check? I did ask you about this. Of course, FS has the advantage in any case because it knows when you change views, whereas this isn't realy identifiable in FSUIPC. I don't know how it could be done, but that doesn't mean it's impossible. I expect I could do it by having an extra control which you program to another key or button to "reset mouse look". Then you'd need to press that each time you changed views. It would need to reset the cursor to the centre of the new view. There might be a more complex way to determine a change of view -- I'd need to investigate. If the currently focussed Window handle changes then maybe that always indicates a view change and I could automatically re-centre. But then it would re-centre when you returned also. Would that be right? I can see that it could become a real mess, but I'll take a look when I have a moment. Originally, when I first implemented Mouse Look in FSUIPC, it re-centred each and every time you released the mouse button and pressed it again. That was MUCH MUCH more annoying, I can tell you, and everyone complained! Odd that no one before you has complained that it doesn't re-centre. No, the presense of the cursor isn't relevant. FS changes it to a cross in mouse look mode. Pete

I assume you mean "ShowText", which was not actually by me, but by Rob van der Wiele. It is available in the "Other useful programs" thread in the Download Links subforum. Regards Pete

Yes, but the link on the Schiratti page to the SimFlight purchase page does NOT download anything. All the download links both here and on the Schiratti page most certainly have not supplied version 4.30 for over 4 years. That's why I need to know where you actually downloaded it, NOT where you purchased it! They are two separate actions! The link on the purchase page is actually out of date, as I just discovered, but it does point to 4.80, not 4.30. I will ensure that gets fixed too, but at least 4.80 is less than one year old! ;-) You don't need to "rebuy", and the only purchase place is the SimMarket FSUIPC4 page. Regards Pete

Right click on the DLL and select "Properties - Digital Signature" then select the signature (SimFlight not simMarket), and click "Details". It should say "This digital signature is OK". If it doesn't then you have some corruption in the registry, or the Windows DLLs dealing with signatures, encryption or trust, Maybe you have the cryptograhy service of Windows disabled -- look in the Services tab of the Task Manager -- I think it's the one called CryptSvc. There are two threads in the FAQ subforum dealing with signature checks. Look at both. Regards Pete