Pete Dowson

Not with WideFS. WideFS is a client extension of the FSUIPC interface. Any application which interfaces to FSUIPC and which doesn't need to be installed inside FS can be used on a WideFS client, but bits of FS itself, like the sound innards, can't be moved over. You could only do that sort of thing by having two complete installations of FS and linking them via either multiplayer or using Luciano Napolitano's "WidevieW". Regards Pete

Sorry, but if it doesn't work there's something wrong and going back doesn't fix it. More details are obviously needed. What is the "CS 757"? Perhaps identifying the product a little more clearly would help, as well as explaining the problem? Wouldn't you surely agree, if you thought about it? Are you sure it isn't simply a specific problem to your installation? How do you know it is at all related to any specific version of FSUIPC? What versions do you think it, whatever it is, works with, and why? Pete

It must be just a coincidence. There's really no way FSUIPC is doing anything with any part of any add-on until and unless you actually use the facility. The macros are simply lines in the INI file. They do nothing at all in themselves. The only time they are used is when you have them assigned and then actually USE them. It's just like any tool. Sitting in your toolbox a tool does nothing (well, except rust, perhaps). You have to USE it for it do do anything. Same with anything assigned in FSUIPC. No, nothing at all. It cannot. Regards Pete

There are no Bank Hold facilities or indicators internal to FS at all, so there's nothing for FSUIPC to read. If there is one in a particular cockpit it must be a facility implemented locally to the gauge. There's no way to access such things. When the "BNK" button on the Learjet panel is pressed (no matter whether it turns on or off), it sends an "AP MAX BANK INC" control to FSX with a parameter of 1. What on Earth this is doing I've no idea. There's also an AP MAX BANK DEC control, but the Learjet panel never seems to send that. And the parameter is not used in either case. FSUIPC4 does provide access to the Max Bank value -- offset 2E04, as documented. Watching that it seems to alternate between 14 and 27 degrees each time you click the Learjet 45 BNK button. Weird. I would assume that all that part is actually broken, but the fact that you appear to want to use it suggests otherwise. Can you clarify what is going on? Regards Pete

If you cannot "fire" in the "game" at all, then I'm afraid FSUIPC4 cannot make it suddenly work. You need to get in touch with the Support for the "game". Whether you use a PFC device or a Saitek jyostick or a keyboard button or anything isn't at all relevant. You already said the button is seen by FSUIPC4, so the PFC driver and FSUIPC are both working fine. If there is no way provided in the "game" to "fire" then having a button is not going to suddenly make it work. Sorry, there are no miracles, really. You use "firing opposition" and "firing button" as if they are different things. "Opposition" means something which opposes -- i.e. is against. So that makes no sense here. I realise English is not your main language. Maybe you can get a friend to translate for you? All I can do is repeat what I said. If there's a keypress or control provided by your shoot-em-up game in FSX for firing a gun, then it will be assignable to a button or key in FSUIPC. If there is not, if the "game" only provides Mouse control over the guns, then you might need to try to first create a Mouse Macro, and then assign it to your button. If the mouse button method doesn't work then there really is no way, unless you invest in something like Luciano Napolitano's "Key2Mouse" to program a key as a mouse press then assign your button to that keypress. However, back to your first statements -- if the firing facility does not work in the game in any case then FSUIPC cannot fix it. You need to contact the support for that game. Regards Pete

What is the firing button? What control or keypress are you trying to assign? Can you please try providing rather more information when asking for help? There is no way I can see what you are doing from here, and I cannot guess either. You have to tell me what you are actually doing and what the result is. Just saying that you "fail", that something "does not work" does not offer enough information to even guess what you might be doing wrong! Don't you see that? Maybe this firing button on this add-on aircraft has no way of assigning any control or keystroke? How do you do it normally, without a button? Is there any documentatin with this aircraft? Have you checked? If it operates with a mouse only, there is a chance that it might work with a mouse macro created and then assigned. Please think what you are doing and then tell me what that is. Unless you know what you want to assign a button to, you cannot very well assign it at all, can you? Regards Pete

Sorry. I don't have any Saitek gear and I'd never heard of this Switch Panel interface program before you mentioned it. I can only suggest you ask the author. It looks like he is offering help on that web-page (the www.krosa.it one). Have you asked there? I really cannot support other folks' programs, especially ones I've never heard of for hardware I haven't got! Sorry! Regards Pete

There have been a few. Maybe two or three a month coming through this Forum, so FSUIPC4 related. I've seen the same for other applications on other Forums. Which is a point: When the problems with SimConnect occur they affect all SimConnect applications, so I'm not sure why FSUIPC should be singled out -- though it is probably the most-installed SimConnect using application and has been around the longest (since the day of FSX's release, or before for Beta testers). Quite honestly I've no idea why some folks have these problems. I do get the impression (but have no proof) that attempting to uninstall and reinstall FSX is likely to create them. Some folks have also suggested that there is some interaction between .Net installers and SimConnect's installer which gets the latter messed up. I currently have five FSX installations -- two on XP32, one on Vista32 and two on Vista64, and have never been able to reproduce any of the SimConnect problems folks have reported -- not even once. So I find it very difficult to advise. I also don't really understand Vista's over-complex file and folder permissions system, nor the weird Side-by-Side library system. This last, the WinSxS system, sounds like a good idea but it seems to have been implemented in the most difficult and confusing way. The worst problem it produces is that, whilst installers seem normally to be able to install Side-by-Side libraries okay, no uninstallers seem ever to be able to uninstall them. And that where the problems, when they do occur, become worse. If you cannot uninstall something, the re-install won't work, so repairing a broken library setup doesn't work. One of my contacts in Microsoft (the SimConnect prime author) did start on making a program to check all this stuff and auto-repair it when broken, but pressure of work in other areas forced him to stop. I don't know enough about it to do it, but someone needs to. Not just for SimConnect, but for any WinSxS library setup. If you need numbers specifically for FSUIPC4 I can only suggest you do a search through this Forum. Search on words like "WinSxS". Count the number of different visitor names contributing. But you may also wish to post on other Forums (e.g. the nearby FSX Forum) for a general consensus, not specifically FSUIPC4-oriented. I've also asked folks who get these problems to report them via tell_fs@microsoft.com, so there must be a good database inside MS HQ somewhere. Doesn't your MS Tech Support contact have any contact with the place those go to? Regards Pete

No idea. The broadcasts are on port 9002. But they will be outwards from the Server to all Clients. Not sure whether or why firewalls stop outgoing messages, but maybe they do. Regards Pete

If you mean SimMarket's link, it's exactly the same link to exactly the same file. It's a direct copy of that link. Regards Pete

It isn't normally needed as usually FS users with Networks only have one Workgroup. The broadcasts needed to tell the Clients where the Server is only work within a defined workgroup. It sounds like you have two differently named ones, maybe because you never bothered to rename the default, which i think is different in XP and Vista. Regards Pete

There's one there!!! It is one of the files which Windows Explorer is hiding the extension for. It is one of those starting with "FSUIPC". What do you think they are? Can you not see them? Take a longer look!!! Please please please uncheck that horrible "hide extensions for known file types" option, which you even showed in your pictures, or else learn what filetypes Windows decides are "known" so you will also "know" them! :-( :-( :-( Pete

Evidently something went wrong with your download. You'll need to download it again, and try to get it properly. Where are you going for it? The one on the Schiratti site is fine, from here at least. If you get problems with any website you normally need to check with the website provider. I don't have a website myself, so I'm not sure what is involved. but normally things that go wrong are traceable to the user end of the chain. Regards Pete

Does this mean that my axis assignments and calibration WILL NOT be affected? Or will I need to do them again? Yes, it means they will not be affected, and no, you will not need to do anything again. As I said, re-running the installer will not change ANYTHING in your installation. it will simply rebuild the DLL.XML file.. It won't even re-install FSUIPC4 itself if you've updated the latter with a later interim version, and it will tell you so. Pete

No, I've not heard of anything like that. What does E-Jets do? I assume it's a collection of add-on aircraft? Does it try to install its own SimConnect DLL, perhaps? If so, maybe it makes a mess of the DLL.XML file which SimConnect needs to manage loadings. Try installing E-Jets THEN re-installing FSUIPC4 using the installer. Re-running the FSUIPC installer won't change anything in your installation, but it will re-build the DLL.XML file and maybe fix the problem. Either way you should report it to Wilco's own support. Regards Pete

FSUIPC.LOG. There's a DLL (FSUIPC.DLL), a LOG (FSUIPC.LOG) and an INI (FSUIPC.INI). If there's no log then FSUIPC has never been run, or you've deleted the Log. I expect you have got Windows Explorer hiding filetypes from you because Windows treats you as an idiot. Since you are not and know you are not I suggest you use the Explorer folder options to tell Windows not to be so silly. ;-) Regards Pete

Ah, sorry. But not all the paragraphs within each main section feature in the contents list -- I really wanted to keep that to one neat page. I found the relevant parts myself, just to prove to myself they were actually there still, by using search (using the word "GoFlight"). Searching usually finds things pretty quickly. If it didn't I'd have to generate an IndexUgh. ;-) Regards & Happy New Year, Pete

Which do you count as the "second bit"? Looking at the Log file? Show it to me, you don't need to understand it. Why on Earth waste your money, then? I don't understand. What is so complicated? You use facilities you want to use, don't use facilities you don't want to use. The User Guide is the place to look. It is conveniently divided into smaller sections, one on each area of use. It's also the place to browse through BEFORE paying out good money, because if you find nothing in there you want to use (or even nothing you understand) then why buy it? Regards Pete

In what way do you "fail"? Don't the buttons get seen in FSUIPC? Can you elaborate at all? To do what? Most assignable controls don't use a "parameter", and for those that do use it the setting you need may be obvious, but it depends on what you want to do. There's no single answer! Regards Pete

You need a special cable to link PC to PC directly, one with the wires crossed over. Ask in the store for an EtherNet or Cat5 crossover or PC-PC cable. That IP address looks like an external IP address, one on the World Web. Are you sure that's right? Most local PC networks use IP addresses beginning 192.168...., though I know there are less used alternatives. Maybe that router is setup incorrectly? I would recommend setting fixed IP addresses in any case on all PCs on a local network, especially when used for FS, as it stops those intermittent blips in performance when Windows goes and asks for IP address data. Regards Pete

Why not use the view Up control, instead of terribly inefficient and re-assignable keystrokes? Now that I know you are using FSX, I would ask why you don't use its splendid camera facilities instead. You can set up your own cameras to do what you like, each with their own control/selector. Ask around in the FSX forum. I'm sure someone there will show you the ropes. ;-) Regards Pete

FSUIPC3 can, like all of its predecessors, only handle joysticks through the Windows "joy" API. This provides for 32 buttons, 1 POV and 6 axes (XYZRUV). This interface is simple and efficient and was used by everyone until the invention of the over-enginerred, over-complex, and rather slow "DirectInput". Even FS, when it used DirectX for other things like the screen, still used the old joy interface until, I think, FS2002. The DirectInput interface can handle up to 64 buttons, 4 POVs (my names PQMN) and 8 Axes (XYZ Rz Rx Ry, S1, S2 which I name XYZRUVST). I changed FSUIPC's axis assignment facilities over to DirectInput during the re-write made necessary by FSX, so FSUIPC4 supports 8 axes and 4 POVs (as axes), but still uses the older "joy" API for the buttons (so, only 32) and 1 POV (as 8 buttons). However, the work involved in rewriting FSUIPC3 in this area to do the same is huge, and it simply isn't worthwhile at this stage. I have too much to do going forward. I am only applying easy changes to FSUIPC3 arising from ones first made to FSUIPC4, and that particular change is far from easy. There should be a solution for your 6 axes, though. The interface program should be supplying those axes as the same 6 supported by the "joy" interface, not 5 from that set and one from the DirectInput set. That makes no sense. It may well be as easy as a Registry change to do that -- but you will need to talk to the people who know your interface. Regards Pete

No idea how you lost your settings, but if they were in all places, including FSX and GoFlight configurations, it sounds like your FSX session crashed rather than terminated correctly. FSX in particular only saves its settings when it closes normally. FSUIPC's settings are saved in its INI file when you OK out of the options and settings dialogue. You will certainly not easily lose those. There's nothing different about a set of buttons and knobs just because you change aircraft. You have to decide what you want them to do then assign the appropriate functions, no matter what aircraft you use. At least with FSUIPC assignments you can make them aircraft-specific, so they switch over when you load different aircraft. I don't know in CHCM or GoFlight's software can do that. Regards Pete

Yes, as far as I know. GoFlight's own software is completely independent to FSUIPC. In fact I think you can mix them in any case, even on the same unit. Just running GFdisplay does nothing. It is a free program provided for programming the way the lights work. It is not intelligent. It doesn't know what you want the lights to do unless you tell it, through its parameter file. So, you programmed the "press" action for Gear Down, but forgot to program to "release" operation to tell it to do Gear Up? That's because the GoFlight software is written specifically to drive GoFlight units in the way they were designed to be used. FSUIPC is a general facility for assigning whatever you like wherever you like. Greater flexibility has a price -- you have to do more work to use it. If the GoFlight stuff does all you want, use it. Only use FSUIPC for stuff you want to do differently! Sounds like you've assigned the space bar to do something else -- you might have done that in FS, in FSUIPC, or maybe even elsewhere? You'd need to check this yourself. FSUIPC doesn't touch the keyboard unless you've asked it to. Regards Pete

What version? You forgot to mention it! :roll: If it isn't 4.40 or later, please update it. Regards Pete