Pete Dowson

It cannot possibly make any difference. The two installations are completely separate, no overlap, no shared files, nothing connecting the two. Sorry, you'll need to explain what you mean here. "Map"? Do you mean assign? Don't the buttons appear in the Buttons & Switches tab when pressed? You can use the same FSUIPC4.INI file -- just copy your original one into your new installation. there is no difference. However, I've no idea if there are conflicts between the Saitek software and FSUIPC -- that's a matter for the Saitek support forum. I understood most users were more successful discarding the Saitek stuff. Regards Pete

Replacing the same program by the same program won't make any difference. Are you saying there is still no FSUIPC4.log file or FSUIPC4.ini file in the Modules folder? What files are there? Your DLL.XML file was most certainly wrong, and I cannot imagine there being two separate faults in your system, so I'd be more inclined to think that you didn't actually correct the DLL.XML file properly. Maybe you should post it again? Pete

Sorry, but the mouse wheel trim is only for devices recognised by Windows as mice, with mouse wheels. Sorry, I've no idea how you are relating mouse facilities to games controllers. They are different devices. You can't make a game controller look like a mouse -- not unless the controller driver allows it to emulate a mouse to Windows' satisfaction. Why on Earth do you want to use "mouse trim", which is a facility for folks with a mouse but unfortunately no game controllers. With a game controller you can assign directly to the elevator trim axes or the trim increment and decrement controls! Pete

BTW, on checking here it appears you purchased FSUIPC3 twice -- once on 8th March and again on 31st May! It's very kind of you, but I wonder why? Have you used both keys? Or was one of them for someone else? Regards Pete

This will happen if FSUIPC thinks the key is invalid. This will occur either if it is truly invalid or if the computer's date is incorrect and shows that the registration was purchased after the current date. Check the date. If this isn't the answer, close down FS and show me the FSUIPC log file from the Modules folder. Pete

FSUIPC cannot possibly have anything to do with your monitor or any 'flicker'. There's not one bit of code in FSUIPC involved with graphics or displays. Any display facilities provided for other programs in FSUIPC use standard FS facilities. So, you have something else going on. Check your video driver. Compare FS windowed mode with full screen mode. Do you have any programs displaying messages on screen in FS? That can cause flicker with bad drivers. Regards Pete

Why are you starting a fresh install more than once? What goes wrong during the Install? The log you added shows okay. I've no idea what you are talking about here. What is the "everything" which is okay? What do you mean "pc flickers"? What's this "start al programs to drop down a program list"? Which FS menu is that? Also you talk about FS9 with FSUIPC4? FSUIPC4 will not run in FS9, it is for FSX, ESP or Prepar3D. Your install log shows FSX, why do you say FS9? Please try to explain exactly what your problem is, what you actaully do to get it to happen, and say exactly which Flight simulator you are talking about. I need to make some sense out of what you are saying before I can help. Pete

Okay, I see the problem. Your DLL.XML file was already corrupted at the end so that FSUIPC4's addition was ineffective. This section: is incomplete and has mismatching bracketing. FS will stop processing the file when it gets to this. Delete those two lines and it should be okay. Regards Pete

No, if you got it working already I wouln't worry. It is possible even with the default 737 to calibrate on the ground, but difficult to get the Arm zone set properly because of the immediate deployment. Sorry, I've no idea but i don't know why there would be any. I don't use any of these sophisticated add-on aircraft bcause I have a complete hardware cockpi,t with no FS panels at all, and all systems provided by Project Magenta. Regards Pete

Do your prop pitch and mixture work with default planes? If so, then those add-ons must not be using the FS controls. Do they have any documentation telling you how to operate those controls? Can you operate them from the keyboard or by mouse? If so, enable event logging in FSUIPC (and axis logging) and see if you get the FS controls logged when you change those settings. Do A2A have a support forum at all? Regards Pete

You posted the same message twice -- I've deleted the other. Did FSX ask you to approve it being loaded the first time? If so did you say yes, to load it and to trust it? Is there an FSUIP4 log file and an INI file in the Modules folder? If there's a log please show it to me. If not, please find the DLL.XML file in this folder@ C:\Users\Bob\AppData\Roaming\Microsoft\FSX and paste it here. Pete

The only times i've ever seen that has been when there's some sort of scenery conflict -- two different ground levels competing. And also sometimes when using AES for push-back (but that seems to have gone away at present). Try the general FSX forum here or over in AVSIM. Regards Pete

You posted your support request in the FAQ sub-forum, where it won't get answered, so I've moved it to the Support Forum for you. You can't do it with the aircraft on the ground because whenever the axis passes through the "arm" point the spoilers deploy fully. Take the aircraft into the air and just pause FS whilst you set them up. Regards Pete

Super! Glad you sorted it all out. I hope you manage to continue, but please don't feel unable to come back if you experience any more complex problems! Pete

If there is no FSUIPC.LOG and no FSUIPC.INI in the FS Modules folder, then either you are looking in the wrong place, or FSUIPC has never ever been run. Therefore it cannot be saying that it is unregistered! The first things FSUIPC does when it is loaded is create a Log file. Then it reads the INI file and if there isn't one it creates one for you. If it has done neither then it is not installed, OR you are running a different install of FS9, or you are not looking in the true folder for 'modules'. Maybe you have Windows hiding the common filetypes from you? If you have, then look at the files called "FSUIPC". The one called 'configuration settings' or similar will be the INI file, and the one called. probably. 'text file' will be the LOG. They may have different descriptions because the description comes from the program used to read them. Is there a KEY file (which may be called a 'registry' file)? If so have you checked it yet as I suggested? All SimMarket provide is a link to the Schiratti site. That's what is in the slot labelled "Demo download". It points to the one on www.schiratti.com. Pete

Sorry, I don't understand these things either. It isn't an area I know much about I think 'agn' files are autogen files. I don't think those missing does any harm, but I wouldn't swear to that. CAB files are simply containers for other files. I don't know why it would want missing ones of those. Maybe there's a scenery Forum someplace (AVSIM?) which has experts on this stuff who can advise, or perhaps check in the CTD forum over in AVSIM? Generally i've not found missing files a problem for FSX. It just seems to waste a lot of its time checking for stuff that may or may not be there or which might be available to it in different formats. When I view what FS is doing with files it makes me very sad indeed as it seems to do a helluva lot of unnecessary or repeated accesses all the time -- very often reading files which cannot possibily have a bearing on your locality, stuff from thousands of miles away. Think how fast it could be if it didn't do all that stuff! :sad: Anyway, I wouldn't worry yourself about it unless you do get a CTD, then you need to check the last accesses for clues. It won't be the very last, so you'd need to look back a litte. To avoid lots of irrelevant stuff freeze the ProcMon log as soon as the CTD happens. Regards Pete

0D6C is the 32-bit parameter which you'd supply in the "parameter" field in the FSUIPC assignments, if you need one. Not all macros will need a parameter. 0D7C is in the middle of the 40 byte area starting at 0D70. Do NOT write to 0D7C, but to 0D70!!! Three errors in such a short piece!!! Where are you getting your bad information from? First: those macros do not use a parameter, so whyt write to 0D6C? There is no point. It is a waste of time. Second: Writing to 0D7C does nothing. Why are you using that value? Have you not referred to the offsets list? Please do so! Third: If the macro file name is PMDG 747.mcro the first part of the string (before the :) is correct, but, as you can surely see above, it does not contain a macro called "PMDG 747", only ones named "SEATBELTS ON" and "SEATBELTS OFF", so why are you trying to use a macro which doesn't exist? :sad: Pete

So the key is not rejected by the Installer? There is no demo version, and SimMarket do not have it. The very latest versions are always here, in the Download Links subforum, but the Schiratti webpage should be 3.999 which is okay. Please run FS, then close it down, then show me the FSUIPC.LOG file and also the FSUIPC Install Log file, both from the FS9 Modules folder. You can paste both here, into a message. Please also check that there is an FSUIPC.Key file (but do not post it here). You can look at it with a Text editor and check the details yourself. There is nothing elxe in FSUIPC's registration checks -- just the date, the name, the email and the Key -- the last three are all in that Key file, no where else at all. In fact you could have simply copied that file over from your previous PC. Pete ]

I located the BGLs affecting me by using "ProcMon", a free program from www.sysinternals.com which can be used to log access to all files, devices, etc. It produces a lot of data so you have use to the filters to narrow it down to specific file types and special actions, like "createfile" (the action used to open existing ones as well as create -- misleading name). It takes a lot of patience though. I spent a couple of days on it because I wasn't willing to avoid trips to or over Denmark! Regards Pete

Well, I suppose it could change the timings of things, but if it is associated with a specific area of the world it is nearly always going to be because of a problem with that scenery. By changing the order of things you are probably simply still getting the problem but the memory corruption is then occurring in a place which at that time isn't being used for anything critical and doesn't therefore cause a crash. Another small change at another date could cause it to matter again. If that happens I would seriously consider reinstalling the scenery, also looking ot see if there's an update for it. The last time I got such an odd problem it was actually a couple of bad BGL type files in a much lower level scenery -- one of the Ultimate Terrain layers. The only fix was to delete/rename two specific BGLs, and the onlty plake it caused the crash was Copenhagen (though i don't think I went to Oslo before fixing it), so yours might even be the same problem. Do you have UT installed? Regards Pete

What are you actually reading in PITCH[0]? Why have you defined PITCH as an array of 2 16-bit unsigned words? Offset 0842 is the vertical speed and as documented, it is one signed 16-bit word,i.e. 2 bytes long. You are correctly reading two bytes, so what is the other PITCH word for? And why "unsgined" when is distinctly tells you it is signed? I don't understand why you'd want to call the vertical speed "PITCH", -- that smacks of carelessness. And what is this "expression formula" which you want to apply, and why can't you? If you want the vertical speed in floating point feet per minute just do this: signed short VS; double verticalspeed; ... FSUIPC_Read(0x842,2,&VS, &result); ... verticalspeed = - (VS * 3.28084); }[/CODE] As always, please PLEASE take more care when looking up and checking offset use and access. Why aren't you using the tools provided, like Logging and FSInterogate to work out what you need to do? Regards Pete

I'm sorry, but there is no way FSUIPC can be involved in any of those types of CTD. And there is no relationship that I know of between those products and FSUIPC, excepting the possibility of your enabling the NGX's SDK provisions for supplying data for third party programs, which FSUIPC maps to offsets. It actually sounds exactly like a scenery problem causing memory corruptions. Folks always like to blame FSUIPC for all such things, but it really cannot be involved at all. The only small difference a new version might make, because of its different size, is a slight shift in some memory positions for some data. If you were going to reinstall anything I would suggest that the Oslo scenery be your first target. Regards Pete

That depends whether you set the "repeat" option. Your choice. Sorry, what "program listing"? Pete

The current installer is 3.999. What is the symptom of your install problem. do you get a message? No message? How can you tell? Describe what happens. Okay, found it. the key is valid. Either you are making a mistake, or you are doing something else wrong, but I need to know how you are detecting that it isn't registering. Message? Or what? Check the date on your PC. If the PC date is before your purchase of FSUIPC the key will not work. Correct the PC's date. Make sure you rightclcik on the Installer and select "run as ... administrator". Pete

Never heard of anything like that. Sounds like your HOTAS is programmed to send keystrokes and it is sending spurious signals all the time. If it is programmed in FSUIPC just rename or delete the FSUIPC INI file so nothing is preogrammed in FSUIPC. If that fixes it then you need to investigate what's gone wrong with the control. Pete