Pete Dowson

It looks like when it installed it didn't update the Registry correctly, because it should show up in one of those places in the Registry: Of course, if you are using a recent Microsoft operating system, like XP, Vista or 7, it is quite possible that the CFS1 installer, being quite ancient now, failed to get correct access rights or just didn't update the registry the way it should (and used to on Windows 95 and 98).. You could try manually copying the FSUIPC.DLL (and KEY if registered) into the CFS1 Modules folder. However, you may need to run Explorer "as administrator" to do so (depending on your Windows version), and you may need to run CFS1 "as administrator" too unless you change permissions on the CFS1 Modules folder. Really it would all be a lot easier if you'd installed CFS into a folder of its own outside of the dreaded "Program Files" folders which tend to be all protected these days. I've always installed all versions of FS into their own folders, like "C:|FS9", C:\CFS1" etc. If you are only using FSUIPC to assign and calibrate your controls, you might get away with doing all that in FS9 then simply copying the FSUIPC.DLL, FSUIPC.KEY and FSUIPC.INI files over from your FS9 Modules folder to the CFS1 one. Regards Pete

Hmmm. something very odd is going on then, because with no add-ons or aircraft gauges using FSUIPC, and no settings by you because it is unregistered, it is doing absolutely nothing. I can only surmise that the little extra memory it is using is sufficient to cause some memory management problems in FS. Maybe you have a failing memory chip? Well, of course it wouldn't if you are unregistered, because it would just make another identical default. Since you appear to have no use for FSUIPC, why are you installing it? Regards Pete

Which version of CFS was that? FSUIPC1,2 and 3 used to work with CFS1 and CFS2, but CFS3 was not really any relation to Flight Sim at all -- totally different code and no way for any internal add-ons to be installed even if they could be written. If you mean "Combat Flight Simulator 3: Battle for Europe " then, no, it is not compatible. It you do really mean "Combat Flight Simulator World War II Europe Series" then I'm fairly sure that's CFS1, so it should still work, though there's really no way I can help a lot if it doesn't. The FSUIPC3 installer should recognise CFS1 and CFS2 if they are installed correctly. The functioning of FSUIPC in those is a much reduced subset of its full facilities, though. Regards Pete

I don't know anything in FSUIPC which could cause stutters on its own. Is it a registered copy? Do you have assignments in it? Maybe something you are asking FSUIPC to do is causing some problem with a joystick driver or similar? You say "every 5-10 seconds", which sounds very odd. This sort of period is usually associated with Networking, where the PC is checking at such intervals for other computer connections. But unless you are also using WideFS there's no Networking in FSUIPC. Try renaming the FSUIPC.INI file so it uses default settings. If that helps then it'll be a matter of going through the settings in a process of elimination. Incidentally, I think you are more likely to get smooth fluid operation in more circumstances by setting a more normal frame rate limit, such as 30 (half your monitor refresh rate). 60 sounds a bit too much to maintain constantly on high settings even for FS9 on a recent PC. Regards Pete

Yes. You should have told your users that they need to make sure they are using a recent version of FSUIPC. The use of external DLLs by Lua plug-ins was not working at all until quite recently. Please see thread in which the problems and solutions was discussed with the author of the Saitek dll you are using. Current interim versions 4.714 and 3.997c will work okay. Please also see these two entries in the list of notes about changes: *. The Lua facilities for loading and running external modules have been improved and should now allow C DLL modules as well as Lua modules to run okay, if they are designed to run on the standard Lua interpreter. These fixes do need more extensive testing, but it seems the main cause of problems, the alignment of members of structures, was the culprit: All FS structures are single-byte aligned (i.e. no alignment), so FSUIPC had to be so arranged to interface to it correctly, whereas the default C alignment to by member size, up to 64-bit or 8 bytes max. FSUIPC now arranges for the Lua structures to be so aligned so that they match the assumption in the external modules. *. DLLs which are used by Lua plug-ins can be placed in a sub-folder in the Modules folder called DLL. Previously they had to be placed in the main FS folder, or in windows or Windows System folders. Regards Pete

You can try raising a problem ticket with SimMarket, but it looks a bit odd -- you purchased WideFS7 in the name "byron James" way back in May. it's the middle of July now. A bit strange finding you did it wrong after so long. Regards Pete

It sounds like you are using a different name for each. you can use a different email address for each, but not a different name which must be exactly the same for both. I can only see an FSUIPC4 registration for a "Ronald James", if you are the one in New Brunswick. And that's also the only one with that email address. I can't find that email address used for FSUIPC3 or WideFS6, nor any Ronald James. Maybe you are using a different name and a different email address? That won't work. There has to be some commonality of identity. [LATER] Found a 'Byron' at a similar address. Looks like he owns FSUIPC3, WideFS6 and WideFS7, but not FSUIPC4. Different email, slightly different address too. That's two users, not one. Regards Pete

Yes, I can add offsets for those. they are only omitted because they are new to FSX and no one asked before. You do realise that they are read-only, not control values? At least that is so if the SimConnect documentation is correct (sometimes it isn't). Can you tell me how to do this? The information on how to link up the mode was supplied by someone else. I don't use SquawkBox at all, so I am not in a positions to decode the SimConnect client data SB4 uses. Perhaps you can decode it and let me know. Also, whether they are just read or written too. I'll implement an interface once i know how. The current SDK contains a version of the FSUIPC4 Offsets Status document which is up to date for 4.70. Any changes/additions since then will be listed in the Notes in the Download Links subforum. Sorry, I don't understand the question? Do you mean the identity of the current airport? If so the only way i know is to look up the Lat/Lon in a database. Regards Pete

That's why it is pointed out in the Installation guide. I put the FSUIPC Documents in there because it is close to FSUIPC. I don't like installations which spread themselves all over the place. Everything to do with FSUIPC is there, and no where else. Pete

All of the user documentation plus lots of other useful stuff is installed for you in the folder called "FSUIPC Documents", inside the FS modules folder. It does tell you this quite clearly in the Installation and Registration Guide. It lists the files you get and where they are! Why not try looking at it now you've found it? Pete

The "Generic USB Hub" devices only have Power, no Power Management. It's the "USB Root Hub" devices which have the PM tab as well as 'Power'. They are usually to be found at the end of the list in device Manager, under "Universal serial Bus controllers". Maybe you are simply not scrolling far enough down? Regards Pete

Hmmm. That's odd, because if you are opening the port through the FSUIPC com library, FSUIPC knows about it and should be closing it for you when it terminates the thread. I'll double-check that. On the "terminate" call, I'll see what the Lua expert has to say before deciding what to do. I can't do anything till next week, in any case. Regards Pete

I will certainly add code to call something, if present, before terminating the thread. How about an "event.terminate" function, so you can declare to me what function to call when i want to throw the program off? I'd still need to ruthlessly terminate the thread if the Lua program doesn't voluntarily perform an exit -- how many miliiseconds should be allowed do you think? If this is not in accord with the "common Lua engine" action, could you kindly explain what that should do? As far as I'm aware I've left nothing out of the Lua code in my program. Maybe there's some in that code which needs me to call it, but I need a clue please. You seem to assume I know a lot about Lua, which I don't -- certainly not as much as your good self. What do you mean, for instance, by "__gc functions"? Regards Pete

Did you look again for the Windows power management options on the USB hubs? They are sure to be there. The axis assignments have an oddity or three. Look at this annotated list from your INI file: CH PRO PEDALS USB 0=0X,256,D,7,0,0,0 Left brake 1=0Y,256,D,8,0,0,0 Right brake 2=0Z,256,D,3,0,0,0 Rudder CH THROTTLE QUADRANT 3=1X,256,D,9,0,0,0 Throttle1 4=1Y,256,D,10,0,0,0 Throttle2 5=1Z,256,D,17,0,0,0 PropPitch1 6=1R,256,D,14,0,0,0 Mixture2 7=1U,256,D,13,0,0,0 Mixture1 8=1V,256,D,18,0,0,0 PropPitch2 CH FLIGHT SIM YOKE USB 9=2X,256,D,1,0,0,0 Aileron 10=2Y,256,D,2,0,0,0 Elevator 11=2Z,256,D,4,0,0,0 Throttle 12=2R,256,D,5,0,0,0 PropPitch 13=2U,256,D,6,0,0,0 Mixture 14=2V,256,D,18,0,0,0 PropPitch2 So, you have two assignments to PropPitch2. I expect one will be interfering with the other, especially if there's any jitter. This may give you symptoms which appear like unresponsiveness. You also have generic assignments to prop pitch and mixture which affect proppitch1 and proppitch2 and mixture1 and mixture2 as well. If I were you I'd delete lines 12, 13 and 14 in the [Axes] section. It's okay to have multiple assignments if you know what you are doing and are sure one isn't dominating the input over the other for some reason (like jitter or because it is left parked in a more extreme position -- FSUIPC arbitrates and allows the larger deflection from "normal" (off, idle, whatever) to win. But normally, if you want multiple controls assigned for different aircraft, you should have them assigned specifically to those aircraft types -- for instance, by using the Profiles facility in FSUIPC. Regards Pete

Doesn't sound like it. If merely opening FSUIPC options ad exiting again wakes the axis up, it's a connection or power thing. There's a re-scan in FSUIPC. Pete

It isn't "USB drivers - properties" but Device Manager - Universal Serial Bus controllers - USB Root Hub - Properties.. there will probably be several "USB Root Hubs". So you don't really have to unassign it, close FSUIPC, then reopen FSUIPC, and reassign it any more? What could have changed to make it so much easier? I suspect it was always like that because unassigning and reassigning really does nothing. It is the re-scanning when you go into the options which might wake things up. It certainly sounds like a faulty USB connection or one which is asleep, but it is odd if that's the only axis that does that. Maybe it's a fault in the device instead. What other assignments do you have on the same device? If you assign a different function to that same axis does it still happen? Do all the other assignments work okay? Note that all that is happening when you open up the FSUIPC options is a re-scan of connected devices, which is also done when you first load FS and FSUIPC starts. Also, it's a long shot, but perhaps you should paste your FSUIPC.INI file here please so I can see if you have anything odd going on in that. Regards Pete

I'm afraid I don't know the "vas advanced autopilot" at all so I cannot really comment. Have you looked through the User Contributions subforum to see if any one has already done something? Maybe you can do it by direct assignment -- no point in jumping to a Lua solution if it is as easy as assigning things, though of course that wouldn't deal with the MCP displays. Maybe "vas" has a Forum where you could also seek assistance? Regards Pete

It's not only in the User Guide, but it has a complete section of its own which is clearly listed in the contents, on the second page of the document, as: User profiles for all control settings Seems you need to find a better search mechanism? Regards Pete

First off, could you please find the "Caps Lock" on your keyboard and turn it off. All capitals is difficult to read and comes across as shouting. Second, although you've entitled this thread "COPYING OF PROFILES", it seems you are not actually using the Profiles feature in FSUIPC at all, but the aircraft specific one instead. It would have been easier for you to use Profiles, in fact. There's a complete section on Profiles in the User Guide. You can do such a thing easily enough, just by editing the INI file appropriately, but It is much better to use short names for the aircraft instead, via the "ShortAircraftNameOk=Substring" facility. Please check out the Appendix in the Advanced User's guide entitled About the Aircraft Specific option and ‘ShortAircraftNameOK’ Regards Pete

Hmm. There's is really no difference between something being assigned or re-assigned, so even if you needed to go into the options to force a re-scan (which FSUIPC does automatically each time the options are entered), I really can't see that un-assigning, exiting, re-entering and re-assigning is doing more than simply going into the options and exiting again. Did you try the simpler things first? Anyway, the main question here is: are you using FSUIPC version 3.99 or later? If not please update and try again. Depending which versin you are using, there was a time-out applied to slow reacting joystick axes (i.e. those whose driver timed out when it was polled) which was changed to only apply during assignment. No version older than 3.99 is currently supported in any case. There's a version 3.997c in the Download Links subforum. It's also a good idea to turn off USB power management on all of the USB connections you are using, because that can put them to sleep. (This is done in the windows device manager). Regards Pete

Yes, please do. Meanwhile here's a direct link to the 3.99 install file. There's also a later DLL (only) in the Download Links subforum. FSUIPC 3.99 Regards Pete

Sorry, but I can't really support any operating system earlier than XP. There are too many new facilities used. Even with XP some things don't work before SP1. You can stick to the old version of the Client -- it will still work with the newer Servers, but it won't support any of the newer facilities or improvements, and I cannot help a lot if you get any problems. Regards Pete

It's been fine here all that time, as it is now. Just click on the shortcut in the documentation, or on the simMarket sales pages, or here: http://www.schiratti.com/dowson.html Of course, as always, even though the main Project Magenta site moved a long time ago to www.projectmagenta.com. I don't know what is wrong your end, but if the "Peter Dowson" page on www.schiratti.com was broken there'd certainly be a lot of fuss being made, because there are links to it all over the place. If you still can't connect please do check with your ISP about what's going on. Maybe they are blocking it for some reason? Doesn't Google search come up with that page at the very top if you Google "Peter Dowson"? Regards Pete

Ian gave you the answer -- thanks Ian -- and also deleted details you should never post openly. Please note that 3.98 is now superseded and unsupported. Please install 3.99 or later. I've moved the thread to the correct place now! ;-) Best Regards Pete

Provided your name is the same (exactly) for both FSUIPC and WideFS, in the one installation, different email addresses don't matter. This requirement was relaxed about 18 months - 2 years ago. Regards Pete