Pete Dowson

No, you are not. If you've got the axes assigned in FS, all FSUIPC calibration is really doing is calibrating the Axis control values, internally in the Sim. In other words it is adjusting the final numbers -- the ones FS would be using if you didn't calibrate in FSUIPC -- before they are sent to the simulation engine. I suspect (though I don't know as I've never had a force feedback setup) is that what you cannot do is use FS axis assignments, telling FS you have no joysticks, and letting FSUIPC do everything. If you do that you probably won't get force feedback as FSUIPC has no force feedback code in it and you would be telling FS you have no joysticks. Well, with FSUIPC's precise calibration facilities, along with its slopes to adjust response, you can just as easily make a mess as you can with any other tool. You need to know what you actually want to achieve. Regards Pete

That actually means it was new then in FS2000 and CFS2 days, so it didn't apply to FS98 or CFS1. At the time FSUIPC was designed to continue compatibility over for programs from FS98, so those things not supported in FS98 were so marked. There's all the information there. If you look in the columns to the right, in that main Programmer's Guide you will see it is marked as "OK" for FS2002 and FS2004 And it is also clear in the FSUIPC4 Offsets Status document via the Read/Write columns. Pete

I don't personally know of any external GPS emulating program I'm afraid. There may well be one such though -- you'd need to do a search (Google), see what you can find. There are several products, at least one of which is freeware, which provide other external instrumentation, that more directly thought of as aeronautical. I'm am pretty sure you can do it -- you go into Windowed mode, undock and drag the Window, then change back to full screen. However, whether this works is very much dependent on the video drivers and the multiscreen mode they are in, and whether you are talking about FS9 or before or FSX. I think with FSX there are greater difficulties, especially in getting it to remember these things. Windowed mode is generally more flexible in this regard though, and with a maximised main screen is only usually different from full screen mode in having a title bar, which would be quite slim in a high resolution. Most folks find the frame rates comparable between the two modes, and some say the quality of the graphics is noticeably better in Windowed mode too. Regards Pete

With one PC sporting two screens, why not just undock the normal GPS gauge and drag it to the other screen? Regards Pete

You don't need to use the option via an offset, you just do what that option does, but directly -- that is, maintain the battery voltage forcibly. The offset for that is 2834, a double float value giving the voltage. Just watch that and when it drops write the full-charge value back. If you aren't writing a program to interface to FSUIPC, then you might find this easier to do using a Lua plug-in which tests the value of a switch/button and whilst it is set, loops reading/writing 2834. You'd need a "sleep" call in it for some milliseconds so you only do this at about frame rate. That offset is one of those to stop users changing options during competitive flying. Thankser, Bank Holiday? Hmm. All the same to me .. that's one of the problems with working at home, such things make no difference! Regards Pete

If I could find a way of doing it, I would add itbut I couldn't. If you've any ideas I'll look at them. It was on my list of requests for SimConnect, when MS had planned regular updates, butwell, you know how that has turned out! Regards Pete

Yes, for a hang when the registration dialogue is actually displayed, awaiting input, the Actigate module seems to be the most common cause. The only other one I know of is a specific Kensington mouse driver. I've even obtained the Actigate module and tried reproducing the problem here to see what Actigate is doing, but I've never been able to reproduce it -- neither has the Actigate author. As I said, it is quite a rare occurrence. Regards Pete

These offsets, 0D0C, 0280, 0281 and 028C all work identically in all versions of FS from FS98 through FS2000, FS2002, FS2004, FSX and ESP. I don't know where you get the idea that FSUIPC does not provide cross-platform compatibility as that is its whole raison d'etre! If you want individual light switch operation, use offset ODOC and set/cler or toggle individual bits appropriately. Pete

Can you please explain this in a little more detail? Like EXACTLY when does it "freeze"? And do you really mean a freeze (hang), or do you mean a crash to desktop, because despite the title of the thread, that's what this one is about. And are you in full screen or windowed mode? If you've not tried the other, do so please. No, not at present. There's no installer written for FSUIPC3, which is what it would need. And really it never has been needed -- there's a specific and rare video driver problem which causes a known sort of freeze/hang, and there's a work-around for that. And there's a specific problem with one or two other add-in modules, "actigate.dll" being the most usual. This thread is actually about a crash which is unique to my knowledge and so must be due to something else on the specific system. The problem in that case is identifying what that might be. The user also mentioned that every time he starts up FS2004 it rebuilds scenery database etc. And when in an aircraft clicking TAB to enter the FS menu, he sees links called "MODULES" ! These are surely signs that something is seriously wrong. Are you really getting all these exact symptoms and a crash not a freeeze? Regards Pete

Touch screens are excellent for things like the CDU of the FMS -- a much cheaper alternative to a real CDU keypad + screen. They can also be used to operate all of the buttons and keys on an overhead. I use two nice 7" touch screens simply as arrays of buttons for use in my cockpit, so I don't need mouse nor keyboard in there. I'm sure that if you have no use for it you'll find plenty of folks who have. Try the cockpit builder's forum, near here. Regards Pete

If the message window/bar is being suppressed by FSUIPC, simply unsuppress it -- uncheck the option on the main About tab in FSUIPC options. I did point these options out to you as well. There's no option in FS itself to suppress them altogether, only to control scrolling. Pete

The only options controlling suppression or redirection of such messages, assuming SB4 is directing them through FSUIPC (is it?), are on the very front TAB (the About one, showing the version numbers and Registration stuff. These options apply whether or not FSUIPC is registered. They are explained quite early on in the FSUIPC User Guide, which you will find within the issued FSUIPC ZIP file. Whether messages scroll or are static is normally determined by the application -- FSUIPC has no influence over that. However, there are options in FS itself which may well affect this. Check the FS menus if you are getting the messages in the FS message window but they are static, not scrolling. Regards Pete

What sort of flashing? The whole screen goes black, or white, or reversesor what? Or do you really just mean the clouds flickering as you almost half implied? FSUIPC contains nothing dealing with either the screen or graphics. What applications of add-ons are you using which need FSUIPC? Maybe, without FSUIPC installed, some other add-on which needs it isn't running or acting differently? If it is the clouds, that flicker as they change can occur when a program (or FS itself) changes the clouds slightly, and is related to the ring of "fake" clouds drawn all around the aircraft when it is supposed to be cloudy but you have the density slider set low. Try putting both cloud quality and density right up in the FS Settings Weather menu. Oh, did you have no FSUIPC installed before? Why did you install it? What are you using it for? Regards Pete

You cannot move FS panels to another PC. They can only exist within FS. You can, using FSUIPC and WideFS alone (no additional software), use a touch screen as a "button bar" to operate anything in FS which you can assign via FSUIPC's buttons. No graphics shown, just a configurable button matrix. If you want true panel-looking displays then you have to investigate the separate instrumentation available -- mostly payware, but i think there are some freeware solutions too. Try here: http://www.flightdecksoft.com/software/index.php For payware solutions there's Project Magenta: http://www.projectmagenta.com/ and Flight Deck software: http://www.flightdecksoftware.com/ Regards Pete

Strange -- Profiles are much smoother and easier to use as it never has to involve any INI file editing, once you have your few needed profiles set up. It is also more efficient for FSUIPC. What problems are Profiles causing for you? The whole point was to make things simpler, more automatic, and trouble-free. But if you insist, and you've not been editing any of the section names, not created any profile names which aren't simply substrings of the related aircraft names, then simply setting UseProfiles to No will revert it. The "Profiles" sections will be ignored, or you can simply delete them. If you have used Profile names not related to aircraft names, you'll have to change them back to something which can be recognised in the aircraft names. I don't understand you, though. Just in case you are as confused as you sound, here's a "diagram" of Profiles versus the old Aircraft specific method: AIRCRAFT-SPECIFIC: Aircraft Name ---> find settings sections matching Aircraft Name, or longest part of it (if ShortAircraftNameOk=Yes or Substring) PROFILES Aircraft Name ---> Find [Profile.] section listing Aircraft Name, or longest part of it (if ShortAircraftNameOk=Yes or Substring) profname ---> use to find settings sections. Settings included in a Profile are: Buttons, Keys, Axis assignments and Calibrations. All of the aircraft sharing a Profile are listed in that [Profile ...] section. The settings never need duplicating, unlike with Aircraft specific. The INI file stays shorter as do the internal tables. Better, FSUIPC presents a dropdown list of existing profiles for you to assign newly loaded aircraft to, getting aircraft-specific operation in a couple of mouse clicks instead of having to make many individual assignments and calibrations. Pete

No. Sorry, it could be any of many things something you've added, some setting not compatible with your video card, anything. I suggest you backup your FSX.CFG file and load FSX so that it boots with a default set of parameters. If that doesn't fix it you'll need to start eliminating add-ons. What does the FSUIPC4 log you included relate to? It obviously isn't one where FSX crashed on loading. I do notice a couple of things though: Is there any reason you only updated FSX to SP1 level? The SP2 update fixes quite a number of additional FSX bugs and makes Simconnect add-ons more efficient. These log entries show something is truly bogging down FSX, too: Your overall average frame rate is only 6.5 --- surely not flyable? I think you need to seriously turn down some of your settings! Worse, something is really clobbering SimConnect. Updating to FSX SP2 would help, but having SimConnect cut out and need reconnecting is really indicative of something wrong. Oddly, this didn't start happening until 9026 seconds (over 2 1/2 hours) into your session, so I'm suspecting it is either a case of memory filling up and things clogging because of disk access, or something related to the aircraft you loaded not so long before (2 hrs 6 mins into the session).: Nothing in the log shows why your FSX might crash during loading, though. Regards Pete

That's really a question for the FS2crew folks, or at least someone who has and knows the program. I've no idea. Obviously, if they have keystrokes assignable to those functions and they work when FS has the focus, you can simply assign those keystrokes to your buttons. If they are only selectable by mouse you'd probably need Luciano Napolitano's "Key2Mouse" payware program. Regards Pete

You mean "profiles" i.e. "settings", not the FSUIPC Profiles, I assume? In order to achieve what? You can carry on as you used to. Okay. If you let FSUIPC do the conversion to Profiles for you, then your profile names will be your old "substring" aircraft names. If that suits you you can leave it like that and assign new aircraft to one of those without worrying about the name, or (better, usually) change the Profile names to more appropriate generic terms for the aircraft type. It is up to you. If you change the names you need to just edit them in each of the [xxx.name] sections in the INI -- a max of 4 places for each. (i.e [Profiles.], [Keys. you don't "need" to. It's up to you. I assumed you set "UseProfiles=Yes" for a reason, though. No, not each variant if you want to edit the relevant entry in the [Profiles.] section -- the one to which you added one of the variants -- to be a common substring -- that facility still works, and you have it enabled. However, it doesn't matter. You really don't need to load them all now, just assign each time you want to fly a new one. Regards Pete

Sorry, I find your wording a little confusing there"never the problem before with FDC"that's one statement, right? "but with ACARS when I log on to it" needs something adding to make sense. Under Vista, if you run one program "as administrator" and another not, then they cannot share data in memory. Vista prevents it. If you had FDC working before, and FDC uses FSUIPC (which I believe it does), then either you were using WinXP, not Vista, then, or you were running both either "as administrator" or not. They simply must be at the same privilege level or it cannot work. Sorry, what shows what where? I don't understand why you said this, nor how it is relevant. Well, advice about FDC needs to come from someone who knows it, not I. But if you want it to talk to FS via FSUIPC you must either NOT run FSX "as administrator", or run everything which wants to talk to it "as administrator" too -- I'm sure I already said this. Regards Pete

The log shows everything is fine. FSUIPC4 is running quite happily. Nothing wrong. I think you are using Vista, right? And you have installed FSX in its default place, in Program Files. All of the Program files folders are protected under Vista, and I'm wondering if those programs, FDC and ACARS need to be able to access them and cannot? I know FDC uses FSUIPC, but does this ACARS application? Are you by any chance running FSX "as administrator" and not the other programs? Or perhaps vice versa? If so, then the problem will be that Vista does not allow programs running with different privilege levels to exchange data in memory, which is the way the FSUIPC works. You have to run everything the same way. Regards Pete

I still don't understand why, having found the problem, you have not simply corrected your original INI file and restored it as FSUIPC.INI in the Modules folder. You continue to make a lot more work by instead trying to adapt a default INI which you only did in order to find the problem! Please do consider doing things the EASY way, that is fix your original INI. Regards Pete

Dowson, actually, but Pete will do. The answer would be in the FSUIPC Log. That's the Installer log, which isn't relevant now you don't have an FSX loading problem. I'd need to see the FSUIPC4.LOG -- I did ask for both. Please show me the FSUIPC log -- make sure you close FSX first, please. Regards Pete

Okay, that's good. I don't understand. If you found the problem and fixed it, as you say, why isn't the rest okay? Just correct the error in the original INI file copy and use that. I notice these in the [General] section: ShortAircraftNameOk=No UseProfiles=No so you are not making good use of the facilities in FSUIPC? Not using shorter names, not using Profiles? Have you, by any chance, made a file with default [General] settings, not used the settings you had originally? since you have this: [Profile.Concorde] 1=Concorde BANC HiVC NoCabin 2=Concorde BANC LowVC Cabin I suspect you aren't using a corrected original INI, as you should, but the default INI without everything pasted back in. Regards Pete

FSUIPC does nothing you don't ask it to. So you have things programmed incorrectly somewhere. That confirms even more that you have something assigned wrong. I suspect you are missing something in your checking. Don't remove FSUIPC.DLL, only the FSUIPC.INI file (rename it FSUIPC.TXT, say), so when you reload FS everything reverts to default settings. This will prove that it isn't FSUIPC as such, but your settings. Then you can add settings back from your saved version (FSUIPC.TXT) by cut and paste. Do it a little at a time till you find the cause. You can do this without having to reload FS -- keep both files open for editing and use the FSUIPC Buttons and Axes and Calibrations tab "reload" buttons to get them re-read each time. Alternatively, leave the INI be and enable Button and Events logging. See the problems and check the logs to see which buttons or axes produce (or don't produce) the desired control events. If you don't understand the log, show it to me. What is a "complete re-install"? There's only the FSUIPC.DLL, which won't change, and the INI file, for which see above. Regards Pete Craig

There's nothing in FSUIPC4 which can do that. Can you provide more information on this "fatal error"? It means nothing on its own. There should be more data available in the error report. Have you yet tried loading FSX with FSUIPC4.DLL temporarily removed from the FSX Modules folder -- if not, do so. What happens then? Also, show me the FSUIPC4.LOG and the Install Log files from the FSX Modules folder. They are both ordinary text files you can find in the FSX Modules folder -- paste them into a message here. How can everything be loaded and ready to go if FSX has crashed with a fatal error? You aren't making sense here I'm afraid. It really is very unlikely to be anything to do with a change in FSUIPC version as there aren't any recent ones relating to anything in FSX, only user options and minor fixes in the user facilities, none of which would be relevant whilst FSX is loading. I suspect you must have changed something else at the same time. Regards Pete