Pete Dowson

Okay. I have the USB Cirrus Pro and complete with radio stack etc and it all works fine with the PFCHID.DLL. It might be quicker to simply install it as I suggested. You should find it all works fine. Regards Pete

That's the Install log, not the run-time log. Is there an FSUIPC4.LOG file? Did it generate an FSUIPC4.INI file? Is there, in FSX, when ready to fly, an "AddOns" menu with FSUIPC listed in it? It certainly did not say it couldn't find FSX.CFG. What do you think this line means? It installed fine. Now we need to know if it is is running okay. Hence my questions above. Regards Pete

You are making a mistake then. You MUST enter all three parts, name, email, key, EXACTLY as shown. Use cut-and-paste to be sure. I'm constantly amazed at how many different ways folks find to spell their own names, even. Use the same spelling you submitted on purchase. Note that as you are hiding your identity behind a codename here I can't even check it for you in any case. Pete

Okay. In that case the easiest thing to do is as follows: 1. Write the values for each parameter to your own assigned user offsets. 66C0 - 66FF are available. 2. Write a small Lua plug-in which processes changes in those offsets and sends the controls for you. 3. Save the plug-in as "ipcReady.lua" so it starts when FS is ready to fly and stays running. The Lua involved would only be something like this, repeated for each offset and control: function lightdown(off, val) -- change name for each action ipc.control(65863, val) -- change control number for each action end event.offset(0x66C0, "lightdown") -- change offset and function name for each action Regards Pete

Unfortunately the only way to get that date changed is to delete the post and post a new one. I'm not going to do that I'm afraid. Not that I've found. The best that seems to be possible is what I'm actually doing: flagging the latest update in the subtitle for the Updated Modules thread. Didn't you notice that? I include the date too! Until recently I used to add the date of the last change to the actual thread title, but I was asked to use the subtitle, as I do now, because changing the title wrecks any links folks have posted to that thread. Unlike the previous Forum software, links on this one appear to use the titles rather than a thread number. It was precisely for this reason I started using the subtitles, which perhaps you've not noticed? Please look again. Currently the thread title and subtitle reads: However, it is not all that important for folks to use the latest interim update. The oldest supported version is still always the one on the Schiratti website, the main download place. Most increments provided here change odd things as requested by individuals and then made available to all. I only ask folks to try the latest here if they have a problem. This is because there is always a chance that problem has been fixed and it saves everyone time -- I would only use the latest when checking, so it's best if things match. But apart from problems and folks wanting to make use of new facilities, there is not really any need to update increments, and especially not every day or week or whenever they are posted. Regards Pete

First, I don't think the controls you mention take parameters, do they? Aren't they simple inc/dec type controls? Second, if it can send a "Quadword" (an 8 byte integer) then it's merely a matter of computation on your part to compute that from the two parts. Or do you mean a floating point 64-bit value, which of course is certainly not appropriate? Third, why not send the parameter first then the control value. The action is only triggered on the latter. Regards Pete

Not sure what that is. Is it a Cirrus console, or a full cockpit? I don't really know. Didn't it come with any instructions or software? I did produce a DLL called PFCHID.DLL which does replace the COM-port based PFC.DLL for the HID/USB devices I knew about a year or so ago. Whether that covers what you have I don't know, but you could try it. The DLL is available in the Download Links subforum. I'm surprised PFC themselves don't supply it? Or don't they know you want to use FS9? The PFCHID.DLL needs a recent version of FSUIPC installed and allows assignment of axes and their calibration in FSUIPC. It doesn't do button assignments though because all of the PFC HID equipment has pre-defined functions for the switches and buttons. Just install a current version of FSUIPC3 (version 3.98 or later -- version 3.989w is available in that subforum), register it, and also install PFCHID.DLL in the same modules folder. It has no real options (there's a INI file with some choices). The menu it adds is just to check that it is running and to give you its version number. Regards Pete

It only supports mouse operations for them? That's very poor. If it's written with XML gauges it may be that its switches and values can be accessed via name local panel variables ("L:Vars"). They can be set via FSUIPC macro assignments, and also read in Lua plug-ins. Rather than "compatible with FSUIPC", because that isn't in question, I think you mean "amenable to being used with add-on hardware". For answers to that question I'm afraid I would have to rely on others to comment, but your first port of call should be to the User Contributions sub-forum where a lot of work has been documented for some aircraft,. There's also some hints on the FAQ subforum. The reason I can't advise is that I simply do not use any add-on aircraft panels, but, instead, Project Magenta, which effectively supplants the systems you want to control. This is another avenue you might want to explore, depending on how much you want to spend. Apart from PM which is admittedly pretty expensive there are others of varying price or even free (I think). There's Sim-Avionics, Flight Deck Software, ProSim737and FsXpand that I know of. Regards Pete

There's no offset mapped to control directional landing lights. You have to use the controls, if they work on the aircraft you are using. Send them via offset 3110. Pete

So, then the same answer applies. Please check it. Also check this thread: http://forum.simflig...rror-with-4645/ Is your problem anything like that? Is there an FSUIPC4.INI and FSUIPC4.LOG file produced in the Modules folder? Can you provide any crash details at all? Is the problem still there with 4.657? Pete

No. REX is good for textures and stuff, but it doesn't beat ASE for weather, in my opinion. It installs with FSX. But if you want to run ASE from a networked PC you'd need to install SimConnect on that PC too -- it's done using an install file ("SimConnect.msi") which is on the FSX disks. Regards Pete

Sorry, but pmSounds is not one of my programs. Pete

If you are going to splash out for ASE you may not need to -- it's weather can be pretty smooth too, especially if you use its global weather mode (DWC). Regards Pete

For efficiency WideServer.DLL (the server component of WideFS) was incorporated into FSUIPC4 during trhe re-write for FSX to save having to have two separate modules both seeking the same information from SimConnect in FSX. However, all that means is that you don't have to place a separate DLL into your FSX installation. The registration and consequent enablement of WideFS was always through FSUIPC in any case. WideFS will not operate without registration. Whether you need to purchase FSUIPC is dependent on what you want -- the User Guide tells you exactly what you get if you purchase it. You don't need to purchase it to install it or use it for other programs, including WideFS, to use for their FSX access. Yes, SimMarket. They have an exclusive -- excepting Intercraft for a Japanese purchase only, and Project Magenta for bundling with a Project Magenta purchase. If you are really worried about how much I will get, please don't. I get a much better deal with an exclusive agreement than I would otherwise. Regards Pete

There should be a way, if you want the firewall up (I personally hate the b***ers), to enable FS and WideClient a way through. Since I hate them and don't use them I've never ventured into how. Sorry. Regards Pete

I'm not sure what data you are expecting to be transferred to a throttle quadrant. Normally it is the other way around, that the quadrant sends data to FS. Regards Pete

Actually the latest FSUIPC incremental update is 4.657. Version 4.651 was quite a few weeks ago. But what was your problem? The install log is for 4.60a of course. And it shows it was completely successful. What is the problem? So far you've mentioned none. Regards Pete

Er, are you saying you are running FS9 on BOTH PCs? Because FSUIPC cannot be installed without FS. As I said, the WideServer log file will be in the FS9 Modules folder, the same place you placed WideServer, and the WideClient log file will be right next to WideClient.exe and WideClient.ini. I can only help given information. So far I'm afraid I'm none the wiser. Why? What are you trying to edit there? Please try to tell me what you are doing and why. Whether it is Vista or not shouldn't be relevant -- unless you made your WideClient folder in the Program Files folder ... did you? Mide you, if you did it probably wouldn't really let you write the WideClient exe and ini files there, as you said you did. Since you, yourself, copied the Wideclient.exe and ini files into the Laptop, how come you cannot save an amended INI file? Did you write protect it or something? Really, rather than hare off into editing INI files it would be better to check basic things, like whether the Laptop can see the Server PC and vice versa (eg to copy files, etc). And whether both PCs are in the same Workgroup. You can check the latter in the Computer properties -- right click "My computer" (or maybe just "Computer" on Vista) and select properties. On Vista it should show on that screen. On XP you have to select the "Computer Name" tab. The main thing, of course, is the firewall. The default firewall in Vista, certainly, will no doubt block all access to and from any other computer. You'd either need to disable it or make exceptions for FS9.exe and WideClient.exe. The same would apply to anything wanting to exchange data between the two. I never use a firewall on a PC (I rely on the one in my router), so I'm afraid I can't advise much on that. Windows help, maybe? Regards Pete

4.657 as of an hour or so ago. In the Download Links subforum, right? So no more questions at present? Pete

Did you mean to say something in the last message you posted? Pete

Have you tried setting all those up with a default aircraft? If they work there,you are doing it correctly. There really isn't much to it and the documentation should surely be clear enough? If not, what are you stumbling on? I think most Wilco add-on aircraft, like PMDG and many others, do not use the default built-in FS systems for many things, notably autopilot, electrical subsystems, overhead, and so on. I don't know that aircraft specifically, but it should come with some documentation telling you what you can do, such as possibly assigning keystrokes to the functions. Then you can assign the keystrokes to the Goflight buttons. FSUIPC supports every possible built-in control, and then also a lot of utility ones it adds, but it cannot possibly provide specific facilities for every add-on aircraft system which does its own thing. It can usually be done, but not by simple assignment to a suitably named control. Maybe folks in the Wilco support forum will be able to give specific assistance. Regards Pete

Okay, done. 4.657 contains these additions: Regards Pete

I'm not a 'sir', just 'Pete' will do. WideFS should work "out of the box". You should have no configuring to do provided your network is set up correctly, and that's a Windows business, not one of WideFS. You've "run out of ideas"? Apart from starting FS and starting WideClient, what other 'ideas' have you tried, so far, please. There's no point in me going over things you've already tried. Obviously, the first question is: are both computers connected together in a Local Network? If not that's your first job. Have you looked at all at any of the documentation? In particular you do need to read the first few paragraphs of the section entitled Configure your Network ? This is why there's a notice there, in red,, as follows: IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! For Network help you might need to look to the Windows help -- I'm no Network expert at all. WideFS merely uses standard working Network facilities, and they need to be operational first. Finally, please, if you come back fpr more, could you state the version of FS, and the versions of FSUIPC and WideFS you have installed. These are most important. Additionally, information about why a client canniot see a Server, or vice versa, is provided in Log files -- a WideServer.Log in the FS Modules folder and a WideClient.log in the WideClient folder. If you could show me those it might help. They are ordinary text files and you can paste them inyto your messages. Regards Pete

Yes, because the newer installer looks in "All Users" too, and other users than the current one. The earlier one only fails if you don't install FSX for the current user. Why are you using the up and down section for flaps? There's a perfectly good detente setting section in the calibration tabs, for use after you calibrate. Sorry, which windows where? I still have no information from you, so I still cannot help. Regards Pete

Ooops! What a silly mistake! Sorrty -- and thanks! I'll fix that directly. Yes, using the HID programming facilities you can drive any HID device, once you figure out the protocol. No. I've never looked at the HID level stuff for GoFlight, but for other devices I have looked at I have to figure it all out by using a USB monitor program. The one from AGG Software is very good ("Advanced USB Port Monitor", http://www.aggsoft.com/ ). I think you can get a trial period. The documentation which would be useful to you, because it details the GFDev.dll interface, is the GoFlight SDK, from their website. I think that it is likely that the data formats used in that interface are directly reflecting the data in the HID reports. Regards Pete