Pete Dowson

ALL versions 4.xxx incorporate the "WideServer" module, as it was built in when FSUIPC4 was written. Your 4.3 includes it. I don't understand why you think anything has changed. You cannot use WideServer unless you pay for the key and register it. Yes, of course. You did not buy a key for "4.3", you bought a key for "FSUIPC4". If you don't keep up to date you don't get support, in fact. I can only support the current version. Please do browse through the Announcements in this Forum too from time to time. they are there to help and inform. Regards Pete

Okay, Sorry, then, I don't know what else to advise. Have you cross-checked with the default airliners? Might it have been wind shear or a sudden change in pressure or temperature? Regards Pete

Don't you control the throttle on approach? And full flaps will slow you down -- you don't normally set landing flaps till you pass the outer marker (or 4-5nm). you'll be capturing the ILS a lot further out than that, surely? Gear down between 10 and 5nm out, unless you need it earlier to help reduce speed. Check also that your spoilers/speed brakes aren't deployed. They should be armed not up. Regards Pete

Those positions sound like the ones which would be shown if the unit was "off" or disconnected. Check the USB power management -- go the the windows Device Manager (part of Settings -System, or My computer (right-click) Manage) and make sure you haven't got Windows set to turn off power to any of the USB ports. This is done by removing a checkmark in the Power Management tab of the properties of the USB Root Hub entries (right click for properties). Actually it's a good idea, and very realistic, to do such control checks in any case. Regards Pete

Your default flight has them set so. FSUIPC does not set any values till you move the levers -- it also ignores the first few values to avoid setting spurious values. Just save a flight with the engines idling (or more more realism, with them off). Why not simply waggle the throttle levers up and back a little? Regards Pete

Interestingly, all FSUIPC does when you change offsets 07FC and 0800 from zero to non-zero is send FS the controls KEY_AP_APR_HOLD_ON and KEY_AP_LOC_HOLD_ON, respectively, which is exactly what the mouse or keystroke would do. Enable the event logging as well as your offset value tracking and see what is going on. You do know you can send FS controls via offset 3110, don't you? Oh, please always, ALWAYS, give versions numbers when you ask a question. Regards Pete

Yes. In fact you are expected to, because I cannot support old versions. There are only two current versions of FSUIPC -- FSUIPC3 and FSUIPC4. When you purchase the registration you get lifetime support and upgrades for that main version (that's FSUIPC's lifetime, not yours! ;-) ). Yes, it retains all your settings and registration. After installing 4.50 you may want to replace the DLL itself by the latest interim update, supplied in the "Updates" Announcement at the top of this forum. Browse through the list of changes there to see if any affect you. Interim updates usually just contain a revised DLL which you just copy directly into the FSX modules folder. Regards Pete

As I said,: "It's your Plane"the letters I Y and P are the initials of those three words. I used the abbreviation after mentioning it for brevity. Sorry if it confused you. It is not only a speech recognition program, but a lot moresee http://www.itsyourplane.com . I think you can download a free trial, see how you get on. Regards Pete

Great. Well done! ;-0 Pete

Are these mouse macro's, generated in FSUIPC? If so, just give them the same macro name and FSUIPC will merge them. Otherwise you'll need to edit the macro file and manually merge two entries into one. The format is provided in the Advanced User's manual. Ask again if it isn't clear. Regards Pete

Where are you looking for this "module" tab? some folks seem to think it will appear in the opening dialogue, whereas, of course, it only ever appears in the menu bar at the top of the normal flight mode screen, when you are ready to fly. If FSUIPC.DLL is in the FS2004 modules folder it is literally impossible for it not to be loaded -- at least not without FS complaining that there's a module there it doesn't like. This is because ALL of FS2004's modules are in its Modules folders -- it either loads or complains about every DLL there. First, tell me how many files with the first name "FSUIPC" you see there, in the Modules folder. If FSUIPC has ever run there will be three -- the DLL, the INI and a LOG. If you have Windows Explorer set to hide known filetypes from you then you'll not see the "INI" or "LOG" parts -- it'll just say they are something like configuration settings and Notepad files, respectively. No, no difference on Windows XP. There is a problem with Windows Vista when you install FS2004 in the Program Files folder, because that is protected and you start having to get extra privileges to get to the "real" Modules folder. But there's no such protection on XP. The last time this happened it turned out, after a lot of to-and-fro'ing, that the user THOUGHT he had only one installation of FS2004, but in fact had two, and was loading a different copy to the one in whose modules folder he'd copied FSUIPC.DLL. I think this is the only possible explanation assuming the other checks I mentioned prove okay. Regards Pete

What has this got to do with this thread, on Voice buddy? WideFs works fine on Windows 7 -- I am using it in a system with mixed Viata, Win7 and XP PCs. You have a set up problem on your Network. If you can't resolve it, post your WideClient and WideServer LOG files -- but please start a thread for this new subject. Pete

That is so weird. Apart from the use of the Network there's nothing in WideServer which is any different from what's in FSUIPC. Ut is simply examining FS variables and copying data. Maybe it is related to relative priorities and adding WideServer's activities to an already heavily-loaded PC is clobbering the recognition, itself a very CPU-intense operation. Try setting Voice Buddy to run at a higher priority. Alternatively if you are using a 2-core processor you could try assigning FSX to one core and voice buddy to the other. I think you can do that in Windows Task manager -- right-click on them in the Process list and set the "Processor Affinity" separately. (I don't know if you can set them to do this automatically). Oh, you may need to put "sapisvr.exe" to the same processor as Voice Buddy too, though i'm not sure. i'm only going by what i read in the "It's your Plane" docs. (IYP is what I changed to instead of Voice buddy, which I gave up on as being too unreliable in a noisy cockpit). Regards Pete

Wonder of wonders, my FS2004 PC booted up okay today! I've checked 2EF8 and, whilst I do not know enough to tell whether the figures are correct, the value given most certainly varies as one would expect when changing the payloads. Why do you think it isn't working? (I am using FSUIPC 3.911, in case there's a difference). Comparing the sorts of values I'm getting there with those in FSX I can see what your problem might be -- it's a bug in the FSX version. I am presenting it as a percentage whereas it should be a fraction -- i.e. not 16.2345 but 0.162345 -- in FS2004 and before it was always the fractional value, you multiply by 100 for a percentage. I'll fix FSUIPC4 -- look out for Version 4.517 soon! Regards Pete

It doesn't? That's the first time that has been reported. It always has worked, through FS2000, FS2002 and FS2004. Can you give me more details? I'll try to check it here if I can get my FS2004 PC up and running. Had hardware difficulties with it recently. Are such values available in FS? Only if you tell me where they are to be found. I'd rather find out why 2EF8 has suddenly stopped working after all these years! Regards Pete

Hmmm, I used AS6.5 all the time till I changed to FSX, now with ASA. The pressure and temperature when using Active Sky are both certainly under its control -- but possibly some of the downloaded data has inconsistencies on occasion. Often this is either due to the timing of reports from different stations being very different in a fast changing weather situation, or simply some weather stations being omitted (unavailable) at the time. I know HiFi simulation have been doing a lot of work on getting such anomalies sorted out -- `maybe there are options in AS6.5 which will do a better job if set differently? It would be worth checking its documentation or going to their support forum. Also consider upgrading to ASA if the looks to have better capabilities. Regards Pete

No, sorry. We never did find out any way to influence that directly -- not that it ever was reported as a real problem, mind. I suppose if it was then we'd have found a way. Why, are you getting problems with temperature? Using which weather source? Regards Pete

Is Voice Buddy using a TCP/IP Port, perhaps? If they are both trying to use the same Port, only one will win. WideServer uses ports 8002 and 9002 by default, but you can change these in the INI file (FSUIPC4.INI for the Server, WideClient.INI for the clients. You couid check the Voice Buddy documentation, to see what it might be doing in this area. Apart from the Network access there's really nothing else WideFS could be doing on the Server PC. Regards Pete

I've used Voice Buddy in the past alongside WideFS with no problems. I cannot imagine where there could possibly be any conflict as there in nothing in common between them -- voice Buddy isn't using a Network connection, for instance, and WideFS has nothing whatsoever to do with either sound or voice recognition. How do you think they may possibly be related or conflicting? Regards Pete

So when are they going to do something? I can help them. They only have to ask! Pete

What makes no sense is that Captain Sim apparently don't know anything about it and no one except your good self has come forward with such a conclusion. There's really nothing i can do without any further information, unless someone wants to buy me a copy of the aircraft to test with. I am certainly not going to do so myself as it sets a bad precedent. Before long I'd have to be buying every product made for FS and trying to test them here. It isn't my job -- I think the makers of the aircraft should really be a little more responsible to their customers. Regards Pete

Okay. The main problem is that either your FSUIPC or your WideFS key is invalid. Was one or the other a time-limited one for evaluation? Project Magenta customers are often afforded that luxury, one which I don't subscribe to. Otherwise, there are only two possibilities: either one or both of the keys are invalid by reason of being generated by an illegal pirate key generator, or the date on your FS PC is incorrect, making it look as if one or both keys were issued later than today's date (according to Windows). This latter can happen if the little battery maintaining your PC's CMOS memory settings has expired. There's a further problem in that the name of your server PC. "fs" is not being resolved on your client PC: 3074 Trying TCP/IP host "fs" port 80 ... 3074 Error on client gethostbyname() [Error=11001] Host not found What concerns me here is that mention of Port 80. Why have you set WideFS to use port 80? The default is port 8002 -- port 80 is normally reserved for regular internet or email activities as far as I'm aware. The default of 8002 was chosen deliberately well away from any default ports. The fact that WideClient is searching for a specific server by name is a little odd too. By default, as supplied, WideFS should be self-configuring. You only need to mess about with servername parameters and the like if you are using mixed systems (win98/NT/2000 with XP/Vista) or you have your PCs in different workgroups (unusual and not recommended). [LATER] I just noticed! The WideServer log shows the date as "01/01/02". That's your first and main problem, I think! I'll need to start logging the PC's system date in the FSUIPC log I think. There have been several cases like this -- usually folks with a new PC which they've not bothered to set up correctly yet! Regards Pete

Well, I really cannot imagine what it is which you and Soldano have set in FSUIPC which causes any problems. By default, with no assignments, no calibrations, no settings, FSUIPC does nothing -- the same as if you had not registered it. It really then cannot possibly interfere. There is really bound to be some setting or assignment which is causing an incompatibility, but with no information to go on there is nothing I can do to help. Re-reading the earlier reports here it looks as if Soldano is saying that the aircraft actually USES FSUIPC for something -- if so then how do you fly it without? There is almost nothing in this thread which makes any sense. Maybe someone, someday, perhaps, will actually come here with something more definite. Regards Pete

I really do always need VERSION NUMBERS. The term "last version" is meaningless. I've had folks saying they're using the "latest" version and it turned out to be a year old, but was the "latest version they'd seen". It isn't hard to find the version numbers -- they are displayed in the options, in the logs, in the documentation and even in the File Properties Version tab! Unchanged, and with no other changes, software doesn't suddenly stop working or change its behaviour. You need to try to think what you changed then. Something you changed did it -- or else a hardware fault has developed. Show me the WideClient, WideServer and FSUIPC Log files. Make sure everything is closed down first, though. Regards Pete

Probably because they are such completely different aircraft with different systems and different control panels? And does the Sikorsky even have a GPS? I'm not sure FSUIPC variables are anything to do with it. You should find out how to control the aircraft systems using normal keyboard or button assignments. Very very rarely are aircraft built which use additional FSUIPC variables -- they are nearly all made so that an ordinary user (non-cockpit builder) can fly them using keyboard, joystick, and maybe mouse. If you want me to locate specific facilities inside FS which correspond to the buttons and switches on the FS panel which do work, you need to say (a) what they are and (b) what key or control operates them. If they are only usable with the mouse then you may be able to use the Mouse Macro facilities in FSUIPC to operate themI cannot tell you, you have to try. Regards Pete