Pete Dowson

There's no "registered" versus "unregistered" version. When you register the software is just the same, you merely unlock the user facilities. It copies the IN values into each idle field alternately when you press the "Set" button above those fields. It has no choice, that's all it can do -- copy current value. But YOU have to push the button when the values are okay! If you push them when the INput value is -16384, then you'll get -16384. FSUIPC will not invent mystical unused numbers to go in there. They have to be values supplied by your lever at the positions you set. Evidently your levers are designed to provide a full range only from the detente to full max. The part of your levers before the detente are obviously not providing a different value. Didn't I read others saying that the reverse on those throttles are by a button being pressed by pulling the levers back? I suspect you cannot use them the way you hope, unless you are prepared to have the idle further forward, and the reverse operating back to that detente. There's a CH-hangar website which contains lots of assistance for CH users. There's also a sticky thread here called "FSUIPC Guide for CH Users" -- have you looked? I think you need to learn a little more about your CH TQ so you can decide what to do with it. Regards Pete

At least one of the SimConnect DLLs appear to be missing from their proper places in the Windows WinSxS system. Either that or the permissions set on those folders prevents the WinSxS system operating. I'm curious still -- you didn't answer my question "Did it work before you registered?". Why did you specifically mention the fact that you'd just registered? Was that related to the problem at all. Also, the fact the you are posting in a thread related to deleting folders in Vista 64 leads me to think that you may have messed up the SimConnect installation altogether. Why, for instance, did you post the link to where it shows you how to change permissions and delete files? I assume you've tried deleting the SimConnect folders themselves and repairing FSX bas plus the SP! and SP2/Accel updates? All I can suggest at present is that you try the very latest FSUIPC4 update, from the Updates announcement above. That's a bit more flexible how it links to SimConnect (because it has to link to ESP's version too). But apart from that it looks like a re-install of Vista may be necessary. Regards Pete

The only part of WideFS which goes on the client PC is the oddly named WIDECLIENT.EXE. It shouldn't really be that confusing when it is named like that? The part of WideFS which stays where it is, on the Server, is WideServer.DLL -- that's included inside FSUIPC4 for FSX, but inserted into the FS Modules folder for FS9 or before. You seem to have got the Server running, so all you need to do is put the WideClient.exe program on your client PC, and run it. The Client is provided along with all the WideFS documentation in the downloadable file called "WideFS.zip". The names of the files surely suggest that they might contain what you need? It should have been easy enough to get that far from the first few sections of the WideFS User Guide, surely? If you can't read English perhaps you can get help with translation? Regards ete

Sorry, I've never heard of "Windev" nor "W-language". How are you trying to use FSUIPC_Read and FSUIPC_Write if you cannot use FSUIPC_Open? They are all part of the same library. Yes, the code for FSUIPC_Open uses the filemapping calls. The sources for the whole interface are provided in several languages in the SDK -- C, VB, Delphi at least. If you understand these calls, check the source. I can't do more that what is shown in the relevant source files! Regards Pete

Why are you adding this to a thread entitled "Delete system folders in Vista 64"? Did it work before you registered? If you remove the FSUIPC4.KEY file from the FSX Modules folder, does it work? What does the FSUIPC4.LOG file show? That's the first place to look. If it isn't producing a log file, then it isn't even being loaded by SimConnect. The Installer also produces a log and that will contain useful information too. The first place to look, surely, in in your own folders, for logs and the like. Why make it harder first? Pete

Don't you think you should be doing some debugging? I can immediately see two things wrong just with a casual glance: 1. You are reading a two-byte (16bit) value into a single byte variable. That alone is going to corrupt something. 2. You are comparing that (one byte!) value, which would, if it were possible in one byte, be in units of 100 x statute miles, as documented, with a floating point double (0.3) -- it will of course NEVER be less than 0 as it is unsigned! You also seem to be using a Key, IKB3BI67TCHE, which I don't think is a valid application key and which certainly hasn't been issued to a "test.dll" as far as my records show. You shouldn't really be writing to offset 8001 on every cycle. If you want to do one-off things like that, do it after the Open2() call, just the once. However, with any reasonably recent version of FSUIPC you do not need to write any key anywhere. Why not try using your debugger? Also make use of FSUIPC's logging facilities -- you can log your IPC reads and writes. Pete

Okaythanks! I'll add the link to the Help announcement. Regards Pete

First off, never use FSUIPC_Open() when inside the FS process -- the shared memory area will be shared by all such callers and they'd corrupt each other. Only use FSUIPC_Open2(), and supply the memory area for the exchanges your self. Apart from that, I'm sorry, but I've no idea why you aren't getting the information. I'd need to know more, like: 1. Version of FSUIPC4 (always needed)? If not the very latest (4.435), try that first). 2. Log results? Go to the Logging tab in FSUIPC options -- enable IPC Read logging, get your problem, close FSX, show me the FSUIPC4.LOG file. Regards Pete

Okayfixed in version 4.435, in the Updates announcement now. Thanks for finding this so quickly after 4.433 was released. I wish all the feedback on interim versions was so fast and complete! ;-) Regards Pete

Thanks! I've managed to reproduce the problem and I think I know what it is -- it only occurs when changing the user aircraft before the flight has finished loading to the point you are ready to fly. It looks like the user aircraft ID changes but by the time SimConnect tells me I've already requested data using the original ID. If you only change aircraft in the Aircraft menu, after the flight has loaded, it's okay! So that's a much quicker "work around" than the one you suggested. Normally I never even see the opening screen which you are using. I load all my aircraft and flights and so on using the normal in-flight menus. This is why I never saw this one. Thanks -- I'll get it fixed tomorrow. Look out for another update. Regards Pete

You OPEN the link to connect to FSUIPC. You do as many READs and WRITEs as you want for one cycle, with one PROCESS call to process them, per cycle. When your program finishes you do a CLOSE. That is the sequence. There is no more to it. Your program does not need to know where FSUIPC.DLL is -- it is running inside the FS process. The Open call connects to it using shared memory. You never call anything in FSUIPC.DLL directly. It sounds as if you haven't even downloaded and looked at the FSUIPC SDK, which contains all you need -- including example programs and LIBraries to link to, if you use C/C++. Please go get the SDK if you want to interface to fSUIPC. Regards Pete

Okay. It might be worth trying the latest version, 3.871, from the Updates, as I suggested. There's been quite a lot of work done since last November. However, I suspect that area is mainly one I attended to in the FSX version, FSUIPC4. Are you testing this in FS2004, or an earlier version of FS? It may make a difference! Right -- that's always been how it worked, since FS98 at least. But in my latest copy of the Offsets list, Have you checked 0896 at all? Oh, no, don't worry. I see it gives the same as 0898. I think that is what misled those who told me about these values, since FS98 days. Checking in the FSUIPC4 Offsets, I see this fact was already discovered for FSX, because the RPM Scaler offset includes this comment (in red): (On turboprops this will give the shaft RPM, since there is currently no Gear Reduction Ratio available to fix values on such aircraft. I will fix this when I can) I also remember putting the request in to the FS team for the Ratio to be provided, via SimConnect. I didn't realise the same problem applied to FS9 and before too -- I will have to add the same comment to the documentation. Oh, that's easy enough. You read the AIR file pathname. The CFG file is in the same folder, so just strip of the filename part and append 'aircraft.cfg'. Hmmm. I wonder where the panel gauges get the value from -- or probably they don't need the real value, just the percentage of maximum, which is what the values provided really are? The graphics would be designed with the scaling in mind ... Regards Pete

FSUIPC_Open, as described near wherever you found FSUIPC_Read and FSUIPC_Process. When your program finishes, use FSUIPC_Close. Pete

I'm sure they will apply the current conversion rate from Euros to Dollars when you purchase it. They do convert to GB pounds when I buy things, and they have thousands of US customers, for sure. That's a question for Project Magenta. From SimMarket or from Project Magenta, if they have your details and do bundle it -- though I would have thought in the latter case it would have been part of your original purchase whenever. Pete

Seems odd. I'm sure there are plenty of apps using FSUIPC and getting the correct RPM for their instrumentation without having to use such means. Perhaps it is limited to just that one aircraft? What is "the latest version", then? PLEASE give version numbers! They are not so hard to find, after all. Why the reluctance? Folks have said "latest version" and they meant the latest they've seen -- once that was a year old one! Do you really mean you've gone to the Updates announcement as I asked and downloaded the one from yesterday? And which version of FS? FSX, ESP, FS9, FS2002, FS2000 or what? I can check things for you, but you need to answer my questions, please! Pete

You are attaching this message to one almost 3 years old! What happened in between? Lots of things have changed since then! Please state version number of FSUIPC, and if not the very latest (see Updates Announcement), try that first. Also, state version of FS as well, please. FSUIPC3 works with anything since FS98 except FSX/ESP and CFS3. Pete

Yes, please could you post the fragment of FSUIPC4 log file which you get up till the crash? Just paste it into a message, please. Also, if you have time, could you enable SimConnect logging (see the FSX Help announcement above for instructions) and obtain a SimConnect log leading to the crash? That will probably be quite large, so ZIP it up and email to me at petedowson@btconnect.com. Please include your FSUIPC4.INI file, from the FSX Modules folder too, in case it is some configuration dependent thing -- I'd need to set mine up like yours. Thanks. I'm not sure I understand. Do you mean that effectively you get the same flight, the default flight, loaded twice instead of once? Can you not successfully load aircraft whilst in flight mode, direct from the Aircraft menu? So far I've not managed to create any crash here, no matter what the default flight aircraft is, and I've tried selecting both the PMDG 747X and the Level D 767. But I am using the Aircraft menu to select aircraft, as I normally do, rather than ending a flight. Perhaps I should try that instead? Otherwise if you could give the exact actual sequence you use which guarantees the crash, I'll try exactly that ... Thanks. That should prove very useful. I'll work on this tomorrow (Monday) as I'm tied up this evening. Regards Pete

Yes. some of the [General] parameters won't apply, but they won't do any harm. Certainly, because FSUIPC4 uses DirectInput for Axis Assignment, the axis identities may change. X and Y are always okay, but the others are often assigned slightly differently. But I wouldn't recommend ditching and re-programming. The differences should be quickly determined, if indeed you get any. Actual joystick numbers for USB devices only usually get changed when you unplug them and re-pug them in differently, OR when you change the version of Windows (eg XP to Vista). That sort of thing would affect FSUIP3 and FSUIPC4 alike. To get around that both FSUIPC3 and FSUIPC4 have new facilities in the updated versions these last two months or so to identify joysticks be an assign letter (A-Z) and assign the letters to numbers via the joystick name known to Windows. Details of all that are in the CHANGES documentation in the Updates announcement. Regards Pete

Sounds like a timing problem in SimConnect as none of those FSX-designed add-ons use FSUIPC -- but they are all SimConnect users. There's no interaction with FSUIPC. What updates have you installed into FSX -- SP1 and SP2 or Acceleration? There were quite a few bugs in the original SimConnect, and really I wouldn't trust anything before SP2 for serious use. When you say "every time I loaded any Wilco Aircraft 737, Airbus, Level D 767, and PMDG 744 and MD11 as soon as the program started", can you explain please? what is the DEFAULT aircraft being loaded before you change to one of those others? Are you loading FSX to the selection screen, or does it go direct into flight mode and then you change aircraft? Can you provide any details about the crash at all, please? Like module name reported, and address -- from the details offered by Windows. Regards Pete

4.433. The "AllowSuppressForPFCQuad" parameter will be added to the currently active [JoyStickCalibration ...] section only -- FSUIPC doesn't read inactive sections till they are activated by loading the associated aircraft. If there isn't such a parameter, then as usual you can add one yourself. The warnings will only appear if you have the PFC driver running AND that "suppress possible interference ..." option is set -- if it isn't then there is no need for the warning. The warning is a little extra text next to the affected axes in the appropriate Calibration tab pages -- Throttles and Reversers only (reversers using the FS throttle axes too of course). The reason the suppression is ONLY for throttles is that it is only variations in those which cause autopilot problems for FS -- e.g. the A/T disconnecting. Regards Pete

The name and address (email or street, it doesn't matter) with which you purchased the key identifies you as the owner of they key. There cannot be two different owners, one for WideFS and one for FSUIPC in use at the same time. It does point out in the user guide that you need to use the same details. Active Sky Advanced does not use FSUIPC at all for FSX connection, so any problem you have with that is completely unrelated. You need to deal with HiFi Simulation on that -- probably it needs at least FSX SP1 installed and you haven't updated your installation? Yes. you need to get one of your keys changed to match the name/address for the other. Go to SimMarket and raise a problem ticket and explain to them your mistake and what you wish to do about it. Sorry, ASA is a HiFi Simulation product and it is their job to support it. I do really have enough to do supporting my own programs! I'm sure you understand? Regards Pete

Okay, version 4.433, now available, has these facilities -- the warnings in the Calibrations sections for all throttles and reversers (because that is all it affects), and an extra JoystickCalibration parameter "AllowSuppressForPFCquad" parameter, which can individually override the suppression, even if it is enabled in the PFC driver, for all or specific aircraft. The default is "Yes", so it acts as it did before this version. The same changes apply to 3.871 for FS9 and before. Regards Pete

Aha! An external application -- an .EXE. Sorry, I misread it as you wanting to make a DLL. There's only one version -- the difference in operation is based on their registration unlocking extra USER facilities -- that is facilities for the user to set and change in the FSUIPC options. The facilities offered by FSUIPC to applications, those that you will be using, are not dependent upon user registration -- they work with or without the user paying for FSUIPC. For freeware applications you may also package FSUIPC with your program, though i'd really rather folks downloaded it for themselves so they get the current version. Regards Pete

Duh! I'm getting senile as well as old! :-( The option IS still available, in the PFC driver!!! I don't need really to add anything to FSUIPC -- but I'll carry on now I've started as it makes it possible for FSUIPC to automatically suppress the non-PFC throttle quadrant when switching aircraft. I'll also add a warning "but using PFC" against the throttle, prop and mixture axes in the Calibration tab when the axes are being suppressed. Please, delete those extra logging entries, then run FSX. Go to the PFC options, not the FSUIPC ones, and right there, on the Main tab, UNSELECT the option "Suppress possible interference from Game Port throttle assignments". I'll need to re-word that on the next PFC update, as obviously Game Port isn't the right term these days -- USB wasn't around when I did the first PFC versions. The obtions is not selected by default, and this is why I couldn't repro your problem. I clean forgot about that option and never looked once at the PFC driver! ;-) Please confirm this is the correct diagnosis, at long last! Regards Pete

I've heard of FSSound.dll, but i've never used it and don't know what it does or where it is from. I've never heard of SOARRec.dll I'm afraid, so I've no idea. Since I don't know what they do or where they are from I'm afraid I cannot comment on whether you "also" need FSUIPC. Regards Pete