Pete Dowson

Yes, it is supported in the current GFDisplay release (1.24) -- it would also need the support in GFDev.dll -- maybe yours isn't up to date? I think the one in the Updates & Goodies announcement in this Forum copes with the MCP Pro. Regards Pete

What is all this about "on-line"? There is nothing at all in any of my programs which need you to have an Internet connection. All of my programs will work just as well on free-standing PCs which have never even seen the Internet, let alone being connected at the time. Therefore I must assume you are getting mixed up with something else which wants you to be on-line for some sort of verification. You NEVER have to be "on-line", and the Globalsign "fix" is just a one-off exercise needed for old Windows operating systems which didn't have GlobalSign included in their list of known signature suppliers. Once the fix has been run once it is never needed again, the details are stored into Windows permanently. And once you have Registered FSUIPC you never have to re-register unless you have reinstalled Windows, or deleted your FSUIPC.KEY file. It sounds to me as if you are mixing up completely different things, most of which are nothing to do with FSUIPC. Regards Pete

Yes. Just don't delete your FSUIPC.INI file -- all your settings are in there. No, but the 3.93 install is by installer. The interim updates in this Forum are simply the DLL files themselves. You have to manually place them into the FS Modules folder. If you are using Vista or Win7 and you have FS installed into its default place in "Program Files", you should run Windows Explorer "as administrator" (a right-click option), otherwise you may only be seeing the Aliassed folder, not the real one. Regards Pete

It means the Lua program has not compiled due to an error. If it doesn't compile it doesn't run. The Lua program concerned is Sync 2 Throttle.lua and the line is the first line, number 1 (the "1" after :). The error is "unexpected symbol near 'ï'". It sounds like you have either corrupted the file, or not selected it all and saved it as a whole, or have added your own non-lua characters to it. Regards Pete

The offsets are the same. It should work okay, but you may need a tighter loop -- FS9 might be overriding the values more often. Try lowering the Sleep value in the line: ipc.sleep(500) You should be okay with values as low as 20 or 50. Experiment. Pete

I don't think having sound off stops the sim addressing the sound card. I've had problems before, with sound drivers, and they didn't lessen with the sound "off". Yes, but these symptoms are certainly indicative of intermittent hangs or dropouts somewhere, and a sound card/serial port conflict seems the most likely. Or at least a serial port conflict somewhere. I will still be worth your while, I think, to investigate the possibility of changing IRQs, or at least checking them. Of course. It's in the documentation, in the section about INI file parameters towards to end. But I'm really not sure that's a good solution. Regards Pete

When you purchase FSUIPC3 you get all updates to FSUIPC3 free forever. FSUIPC4 is separate (for FSX and ESP). There are a number of Announcements at the top of this Forum which tell you all sorts of things, including what versions of what are supported. It is also where lots of interim updates are posted, and other useful things. I cannot support old versions in any case. Later versions contain lots of fixes to older versions, as well as lots of new facilities. The History document which will be installed will tell you all about both. As I said, a version -- 3.93 or later (3.947 is available in the Announcements, but you should install 3.93 first in any case).Pete

Me too, unless it is just pure loading on the PC and it can't do so many things at the same time -- which seems rather unlikely. There's no relationship between FS simulating engines running and any exchanges going on along serial ports. However, one possibility springs to mind, if it is related to the sound. Are you using on-board sound, or a sound card? Are the sound device and the on-board serial port using the same IRQ (interrupt)? If so, that may well be the problem -- they are interfering with each other. If your stuff is 7 years old, is it possible you are still using Windows 98 or Me? Those older operating systems were very poor at sharing IRQs well. Even early versions of XP weren't so good. Check in the BIOS settings, which is where you may also be able to assign IRQs differently. If both devices are on-board you might be out of luck, but if the sound is on a sound card, maybe plugging it into a different PCI (or ISA?) slot would work. Regards Pete

If you want FSUIPC support you need to update to a supported version -- 3.93 or later. However, for anything to do with cloud graphics and glitches thereto you'll need to talk to the support forks for yuour weather program. Pete

That's almost certainly going to be because of a bad WX file, saved in your Flight Simulator X Files folder. The weather data saved with flights is in a binary form, and when corrupted it can mess SimConnect's weather reporting up. FSUIPC is reading weather from SimConnect regularly in order to populate the weather offsets. Unless there's any good reason to keep the weather saved with your flights, try deleting all of the .WX files. Or at least moving them out for a test. Regards Pete

Provided it is in some folder where it is found by the system, yes. Really the GoFlight software installer should also install it, as FSUIPC tries to find it using the pointer to the GFConfig installation, but I'm wondering if they don't do that any more? Regards Pete

There is no way any program of mine tries to install any Microsoft files at all, let alone any from Combat FS. It also does not care whether the FS2004.exe folder is read only or not. I think you must be misinterpreting something quite seriously, or running something else entirely. FSUIPC's installer creates a log file showing what it has done and recording any problems. Please check that, or show it to me if you don't understand something. Regards Pete

Thanks! I will be putting your excellent examples into the Lua package soon, when I do the next user updates. Best Regards Pete

What message? You need to keep in thread for any sense of continuity! If you mean registration, please read the Installation and registration document which you will find in the ZIP you download. The guidance documents are provided for goosd reasons. Pete

FSUIPC4 is not the same product as FSUIPC3 (it was a complete re-write and a lot of work), and your FSUIPC3 keys are not valid for it. SimMarket have separate sales booths for each. Please follow the links in the documentation and on the download site. Pete

There's no difference in FSUIPC whether on XP 32, 64 or Vista 32, 64 or Win7 32, 64. I doubt that the Goflight module, GFDev.dll is any different on Win7 64 compared to XP 64, either, so in all likelihood it is just that you don't have GFDev.dll installed in its usual place, or with the Registry entry for GFConfig pointing to the folder with it in. THat all should be sorted out when you install the GoFlight software -- maybe you didn't do that on the XP 64 system? Try putting GFDev.dll into the Windows folder, where is should be found without registry pointers. If you cannot find your copy there's one downloadable from the Updates & Goodies Announcement above. Regards Pete

Oh dear. On FS9 FSUIPC and GPSOut are completely separate things. You need those parameters in the GPSout.INI file. Please do read the little text document which comes in the GPSout ZIP! And actually, if you look back I already told you this, viz: Regards Pete

No. I don't really do "tutorials" as I am a lousy teacher. And in any case, FSUIPC is really a bag of tools for doing almost anything you want, to there's no such thing as a general way of "getting the most out of it" -- it absolutely depends, every time, on what you want to do. By all means, when you know you want to do something specific and you are not sure (even after referring to the documents) how to do it, come and ask. I can handle specific questions, but I cannot teach. I've no idea about any "IO cards" as I don't have any. I only use ready-made devices. If you buy IO cards for building your own kit you really do want good documentation and assistance from the folks who make the cards, and possibly also from those who use them -- i.e. other cockpit builders. Take a look at the assorted Forums over in MyCockpits (http://www.mycockpit.org/forums ). SimSamurai (http://simsamurai.net/ ) has nearly finished a "Quick Start Guide" to getting FSUIPC going well with CH devices, which would also mostly apply to other ready-made joysticks and the like. But the home-building world is something else again. Regards Pete

Not with that ";" in front -- that will stop the parameter being read. That's a "mouse macro" for calling mouse processing code inside a specific panel module (Gauge). It is nothing to do with FSUIPC offset data. You cannot write mouse macros, you must generate them for specific panel switches using the facilities as documented! You need to formulate the question more precisely. ;-) Do you simply want to write a value to an FSUIPC offset as a result of a Button push or Key press? If so, go to the relevant FSUIPC options tab (Buttons or Keys), press your button or key, then scroll down the FS controls lists till you come to the range of "Offset" controls. You'll find there are such added FSUIPC control to write Byte, Word, Dword, Float32 and Float64 values, and also facilities to set or clear bits (OR and AND effectively), and both normal and cyclic increments and decrements. There are even examples in the documentation. Regards Pete

I'm sorry, I've never heard of that. It sounds like something you've installed has some protection built in and is specifically guarding against being hacked into (one of the potential uses of a "debugger"). I'm afraid you've just need to try removing or stopping anything you've added, one at a time, till you find out what is doing it. Also check what processes are running, using the Windows task manager. Maybe you have an infected system? Do a virus scan too. Regards Pete

Well it really cannot be anything to do with AutoSave being there. There are three ways you can get this happening. One is by having a another copy of FSUIPC.DLL, renamed, but still in the modules folder. Another is by having a copy in the main FS folder. Finally, and more usual, is a copy actually still running in an FS9 process which hasn't actually terminated, because it has hung after closing its windows. Check for the latter by using the Task Manager (ctrl+alt+del). Select the Processes tab and look for FS9.EXE. If it is there, delete it using the button below. If you have this happening then something you've installed is causing FS9 to hang on termination. It could be a video driver bug, or some other FS add-on. Which proves it isn't related to AutoSave. Regards Pete

Good. All's well that ends well! ;-) Pete

Version 4.020 of FSUIPc is over 3 years old, and it doesn't understand your updated FSX! Please download at least 4.53 and install that. Please also review the Announcements in this forum which give you all the information you need, and will save you lots of time! Pete

That's not going to give you an immediate solution, even if I decide it looks like a worthwhile avenue to go down. Sorry, I don't understand that part. Maybe i will whenm I've looked into it? Have you tried my suggestions, like with a small delay? Have you tried even with the shift codes corrected? I'm reasonably sure you should achieve success. Regards Pete

Thanks. Downloaded now. I'll take a look a little later. Bit busy right now. Best Regards Pete