Pete Dowson

But what exactly are you telling SpeechBuddy to send, and where to? It sounds like it sends keypresses locally, which won't help. The "input" it gets is via keypresses on the FS PC, intercepted by FSUIPC. To get keypresses on the FS PC you need to use some special FSUIPC-added controls as I pointed out. Those are detailed in the FSUIPC Advanced users Guide. Pete

NONE! That file is FSX.CFG. Don't touch that! The file you want to DELETE, or RENAME or SHOW ME, is still DLL.XML. I nver asked you to actually Edit any files. It is the DLL.XML file which we have been talking about all along!!! It is in the same folder as the FSX.CFG file, but you don't need or want to touch that! :-( This is getting rather exasperating. Sorry if I'm beginning to seem impatient. Pete

I'm not at all surprised. There's nothing going wrong in the FSX Modules folder. Replacing files with the same files again doesn't change anything in any case. I told you EXACTLY where it is! You aren't reading my rpelies properly! Look: So it is in C:\Documents and Settings\Dennis\Application Data\Microsoft\FSX. If you are using Win7 or Vista, that's the same as C:Users\Dennis\AppData\Microsoft\FSX Where were you looking before? Why not look in the folders that the Installer log tells you? I don't think that will help. It doesn't change the DLL.XML or EXE.XML files. And it often creates SimConnect problems which may then need a Windows re-install. Regards Pete

Looks like your FSX installation is corrupted. Have you been uninstalling or reinstalling FSX at all? That often seems to mess SimConnect up because it gets half-uninstalled and then won't reinstall correctly. You don't provide many details, so I'm not sure how to advise you on your next step. Installing FSX SP1 and SP2, or FSX Acceleration, might fix it. You could also try using my more recent Installer, for FSUIPC 4.638, which you'll find in the Download Links subforum. That does try a few different things extra. Failing that the next step depends on what version of Windows you are using. With vista or Win7 it is very difficult to fix manually (I've got the same problem on one PC which I simply cannot fix unless I reinstall Windows, and I'm not doing that). Regards Pete

Oh, right ... Interesting. My memory's seems to failing me more and more in these days of decrepitude, and it was probably quite a while back. If you can make it action joystick button presses, then WideClient will send them to FSUIPC and you can program them there for RC's keypresses. Alternatively, if you can send any FS control number then maybe you can send the FS control numbers -- those added numbers listed in the Advanced User's guide. If you can, and you can send the parameter to go with it, you can send encoded keypresses that way. Regards Pete

You missed the point. Apart from the few user options, one of which I pointed out to you, FSUIPC's only real purpose, stemming right from its origins back in FS895 and FS98 days, is its provision of an interface for all sorts of programs, add-ons and add-ins, into FS. It really doesn't actually do anything by itself. It's a tool. When it is running other things can do things through it. Good question. It didn't really happen in FS9. I'm not sure why it happens occasionally in FSX with the same mechanism, but I'm prwetty certain it has to do with the asynchronous SimConnect interface -- the fact that the reading of the clock and the writing of the correction are both executed by messaging and queuing between three parts -- FSUIPC, SimConnect's DLL interface, and the routines in FS itself. When FS is pretty busy I think it may be possible for such lower priority needs to get delayed slightly. Given the above explanation, unless you want ot try unloading FSX a bit or upgrading your processor or overclocking it more, I suspect the only solution is to turn it off. I have it enabled, not to correct the minutes (which would be risky), only the seconds, and i don't have any scenery reloads being caused by it, but then I am using an i7-980X overclocked to 4.65GHz and with almost nothing else running on that PC, and no complex aircraft add-on and no panel. I'm glad they mean that to you. Sorry, but you'll have to remain incredulous. I've really never used the FS map facility and do not know what you are showing me there. From everything you said it soundded most definitely like a hardware fault. Especially since you have a LED on the yoke flashing, which sounds very suspicious indeed. Have you bothered to actualy see if you get tohse symproms without FSUIPC being involved, like with FS assignments. Why are you assigning in FSUIPC in any case? And why do you like FSUIPC is you think it is responsible for all these ills? Regards Pete

So SpeechBuddy is an FSUIPC client? Really? They've never contacted me. I'm not sure where the FS control numbers come into it. Written via offset 3110? Pete

GoFlight, VRi? No, not really. Pete

You must be in the wrong folder then. Which may also explain why your earlier post showed a good DLL.XML file which didn't work! Look, from the latest Instal attempt: You evidently are NOT finding the copy of DLL.XML which FSX is actually using! Maybe you also installed FSX for "all users" or some user other than "Dennis"? Pete

You just need to enable the facility in "auto" mode (a simple INI file edit), if you don't mind your devices being called A, B, C ... If you want recognisable letters, like T for Throttle Quadrant, Y for yoke, R for Rudder or P for Pedals, etc, you'd need to edit a couple more lines or so. It isn't hard either way. The chapter about all this actually precedes those about assignments deliberately to encourage folks to read it first! ;-) Regards Pete

Okay, but in this case you didn't delete or rename the DLL.XML first, as shown by this: What happens if you do rename the DLL.XML and run the Instaler, THEN FSX, as I suggested? Pete

Why do you think FSUIPC has anything to do with it? So, either something is using FSUIPC to reset the flight, or you are mistaking a reload of scenery and textures as a flight reload. The latter will be caused by a time correction exceeding one minute. For FSUIPC to do that you must have enabled the option in FSUIPC options to synchronise the time, and also have a time distortion making it go more than a minute out from your system time even though FSUIPC would be correcting it every 50 odd seconds if it can. A reload of scenery and textures is NOT a reload of a flight, which would move your aircraft back to some previously saved position. None of those are relevant really, or at least I can't make head nor tail of them so they tell me nothing really. Sorry. Just turn the time sync off. If that doesn't fix it you need to look for other causes. Sorry, but I can't tell you openly what I think of Saitek products. Yours are obviously misbehaving. I'd get them fixed under warranty if I were you. Regards Pete

The RC menu display window on FS is not dependent on a WideFS connection in any case, once it has been created. RC does not put a time limit on that display, but there are hot keys you can use to hide or show it. FSUIPC4 cannot stop FS's own messages, or those sent by other programs via SimConnect, only those sent to it through FSUIPC. Sorry, I can't help with the former -- and the latter is probably normal depending on what messages you are talking about. For RC's menu you'd be best off asking in the RC forum. Of course. Pete

UT2 is an EXE so is loaded via the EXE.XML file, not the DLL.XML file. so this still points to a DLL.XML file error. Rename it. or delete it. Run the 4.638 installer again. Show me the DLL.XML file again. Show me the Install log. does the Installer say it succeeded? Don't you see the log in the text window behind? It is really not possible for the installer not to create a log if it manages to find and (if needed) create the Modules folder. You are not looking in the right place or for the right thing. It's a text file in the FSX Modules folder. If you've EVER succeeded in installing FSUIPC4 then there is absolutely bound to be an Install log -- else you've never actually used or installed FSUIPC4 successfully. Regards Pete

Er, so it isn't as discussed earlier, it IS writing the INI and it IS reading it back. We were going a bit down the wrong path, weren't we? You said this: but neither of those things could have been anywhere near correct, could they? And you never mentioned anything about devices, only effectively all your settings -- i.e .the whole INI -- that includes all the many options in FSUIPC too! Windows has a nasty habit of re-numbering USB devices whenever you reconnect them even slightly differently, or even if you reconnect them AFTER it has booted (because by then it has done some assignments). This is why I went to all the trouble of adding the "joyLetter" facilities to FSUIPC, so you can make FSUIPC automatically deal with such changes. You should investigate those facilities and maybe implement them. Nothing to do with anything you've described before, where FSUIPC was supposedly completely ignoring your INI file and not updating it even. There is absolutely no way any FSUIPC INI thing will change stuff DURING a flight, unless you go into FSUIPC options and tell it to reload stuff. FSUIPC is not constantly reading the INI file (in fact you said it never read it -- that's how this thread started and is entitled). If you unplugged devices and plugged them in again, it is quite unpredictable what might happen to them in that session. No idea, sorry. You could keep experimenting by plugging the devices in different ports. But one thing is for sure, please look up and use the Joy Letters facilities when you have it sorted. Regards Pete

That looks okay -- and the fact that option 1 didn't work definitely means there's something else wrong. Using a pristine DLL.XML with only FSUIPC4 listed should have definitely got FSUIPC4 loaded okay. You said in your first message but does that mean there was an "AddOns" entry in the menu bar, or not? If there was, what was in it? Is there an FSUIPC4.LOG file being made in the FSX Modules folder each time you run FSX? If so, please show it to me. Either way please show me the Install log from your re-install attempt via option 1, using the 4.638 installer. If there's no Log being made each time then SimConnect isn't loading FSUIPC, but that's normally because of the DLL.XML file being wrong, so I don't know what's going on now without more info. Regards Pete

It certainly sounds like your DLL.XML is corrupted. There are some pretty poor installers around which don't understand how to amend that file correctly. Try re-running the 4.60 installer (it won't harm your 4.648). That may be able to repair it if it isn't too broken. Otherwise you need to find it, and then you've got two options: 1. delete it and re-run the FSUIPC installer, but use the one from FSUIPC 4.638 also available in the Download Links sub-forum. Again that won't harm your 4.648 installation. However, deleting the DLL.XML will probably stop other things from running which you may still want, so make a copy first, OR 2. Paste the whole DLL.XML file into a message here so I can advise you on fixing it by hand. If you are not sure how to find the file, it is in the same folder as your FSX.CFG file, and the path to that is logged in the FSUIPC4 Install log file. Check there, or show it to me so I can tell you. Regards Pete

In that case it is somehow protected. didn't you check? FSUIPC always re-writes the INI file even if you make no changes, so the timestamp on it at least would change. Why? I don't really need those. Please re-run the Installer, then install 3.989u (from the Download Links subforum), so we are on the same page, and then if it is still a problem show me the Install log. That should be a little more relevant. Pete

I do that with Its Your Plane, which isn't free, but you might have missed your opportunity to get the same maker's "SuperATC" which would do the same. That was free till the end of 2010. Incidentally, in general it is best to change the RC assignments to Ctrl+Shift+0 to 9, as 0-9 are used for many other things. IYP and SuperATC assume the CS0-9 settings by default, I think. So how is SpeechBuddy talking to FSX on the other PC? Sorry, I've no idea. Doesn't it have any documentation to tell you how to program it to send keystrokes? Bear in mind that RC gets its keypresses from FSUIPC, on the FSX PC, not on the Client PC. So you'd presumably need to run SpeechBuddy on PC1 not PC2. That's why I was wondering how you got SpeechBuddy to control FSX from PC2. In the end I can only really help with programs I write, and maybe use. I don't know anything about SpeechBuddy I'm afraid. Regards Pete

If it didn't recognise it existing it would create a new default one. Is that what you are seeing, a new default FSUIPC INI file? If you mean it cannot write to it then something has changed permissions on either the file or the Modules folder. Is a fresh Log being produced each time you run FS? If not, maybe the folder is not writeable. If it is maybe it is only the file. Check its properties. The Modules folder is made fully read/writeable by FSUIPC's Installer, so you could try rerunning that to see if it helps. Why? That's really not needed as far as FSUIPC is concerned, and may mean you have to also run everything else "as administrator" so they can talk to each other. Try not doing it. Regards Pete

Please check the documentation, which is extensive. FSInterrogate is a dobnated freeware program from Mr. Liljendal, it isn't mine. But it is pretty easy to use. I hope you are not using FSInterrogate instead of the offset documentation to work out what offsets do what! Please do not! Refer to the full list of offsets provided. The data in FSInterrogate is sparse, incomplete and out of date. It is difficult to keep it updated. The proper reference is the documentation supplied for FSUIPC in the SDK. There are two lists -- one for FSUIPC3 ("FSUIPC for Programmers") and the other the updated list for FSUIPC4. ("FSUIPC4 Offsets Status"). Regard Pete

Yes, using the [Programs] section of the INI file, as described in the Advanced User's guide in the Chapter entitled "Programs: facilities to load and run additional programs". There are contents lists at the beginning of both the FSUIPC User Guide and the Advanced Users guide. Failing that you could always try search. Regards Pete

Calibration is described step by step in the FSUIPC User Guide. It isn't worth re-printing it all here. It is easier for you to read it yourself, surely? On your later message: To find out what things are, please refer to the documentation. That is what it is for. there are even pictures there! And the tools are built into FSUIPC. The only way to become familiar with something is to start using it. The User Guide is there to help, so please use it. Pete

I don't know. The first step is to save the Inastall Log file (the text displayed behind your error message, with a File/Save menu) then paste that into a message here. It sounds like your Registry is pointing to the wrong place for FSX. I also always need to know the VERSION NUMBER of the FSUIPC you are trying to install. If it is not at least 4.60, please update first before returning. Pete

You need to calibrate the throttle so you have more control. Otherwise you will need to use the toe brakes to keep your speed down -- general not a good idea because they can overheat. After calibrating correctly, following the steps given in the FSUIPC user guide, try also one of the "slopes". One with a flatter initial area for the throttle will give more control at low speeds. If the throttle lever is not giving you enough control at low speeds you really do need a different one if you cannot calibrate it to give you adequate control. I'm not understanding what it is you think you can do in a DLL? And what has 'ai' got to do with this? If you want to reduce the power of the caravan's engines you can probably do it in its Aircraft.CFG file. But maybe it cannot fly properly then? If it is a properly made aircraft for FSX it should contain the right values, or at least a good approximation. Regards Pete