Pete Dowson

Ah, so cutting down on video objects reduces or erliminates it? In that case it may well be a video memory thrashing problem. How much video memory have you got? Regards Pete

It can't be a "big deal" if the Installer said everything was okay, because that means it worked. However, it does seem odd. Certainly there's nothing like that on XP. In my Vista Home Premium I can't find anything either. Let me check I'm looking in the same place. Computer - Properties - Manage - Event Viewer - Windows Logs - Applications. Right? I have no Install FSUIPC4 errors listed there. I do have SimConnect RTM, Beta4 and SP1 installed, but not Beta3 on that PC, so if it is logging an error because that one is missing it isn't logging it here. Or if it is, it isn't where I'm looking. Strange. Maybe it's related to some security settings someplace which we have set differently. Regards Pete

No, not possible except in one circumstance -- a bad key for FSUIPC which looks okay and is accepted, but which is actually made by a pirate key generator. If, when you register FSUIPC again, you get a repeat of the problems, Zip up the FSUIPC.KEY file and send it to me (petedowson@btconnect.com) and I can check that. Regards Pete

I don't think you really need to, and I wasn't assuming you did know. However, it is fairly self-explanatory -- a system for having different versions of a Library (as in "DLL") simlutaneously installed and available for use by whosoever wants to use them. This allows folks like the MS FS Team to change SimConnect, or whatever, completely, should they need to, without destroying compatibility with programs written to the older interface. Yes, I assumed you were, and that's why I was trying to explain that if the system is logging this it will only be for information, as it will also be reurning it to FSUIPC's Installer. ErI didn't think you were. How could it refer to my Installer if you were? Sorry, we seem to be talking at 100% cross-purposes. Fine, then. There is no error at all then. So what's the beef here? Does the Install log list the Versions of SimConnect it finds? That's the result of the loop, and that loop is the only time the Beta3 version would be checked for. I can do so next time I power up the vista PC. Is it something you are concerned about? I'm certainly not sure why it would flag it as an error if the program is catching errors, as it is. Maybe it's a Vista bug. Regards Pete

Hmm. I've not heard of any problem like that. I, like many others, have AutoSave enabled all of the time. Since it's a change-of-view problem I'm wondering if it might be video driver related, and all that AutoSave is doing is altering the timing slightly. How often is autosave saving files? Try less often, see if it crashes less easily, more often, see if it crashes more easily. AutoSave is doing nothing more than calling a SimConnect routine to save the flight every so often. Between those intervals it is completely dormant. Please do make sure you are sending the reports to Microsoft when requested, then try different video settings -- eg Windowed / Full Screen, less or more video options -- reduced mipmapping, filtering, etc. Some combination may be critical. Also look for different video drivers. If you are using Vista I have heard that some of the Vista video drivers aren't too stable yet. Regards Pete

What am I supposed to be looking for? What is the problem you need solving please? Only this is wrong: All this shows is that the FSUIPC key in the FSUIPC4.KEY file is not a valid Key for FSUIPC4 with that user name and address. Not having FSUIPC4 registered won't stop applications working, it will only stop you using the extra user facilities. Regards Pete

But under Vista uninstallers are completely unable to uninstall Side-by-Side instrallations. According to Microsoft, once installed they stay installed (unless you get them out manually as you say). They say it doesn't matter becasue new versions don't have to overwrite old ones, they just sit side-by-side. the problem then is if the re-install tries to install the same (broken) one again -- does it succeed? Judging by what happens on XP, no it doesn't. Version 1.04 of what? 4.072 of FSUIPC? It has nothing to do with any system Log. Sorry, you've lost me now. Were there ever any errors shown in the FSUIPC4 install log? It is at installation time that it checks the installed Simconnect versions, and then again on being loaded -- but I think you said it never got loaded. That "10.0.61234.0" version of Simconnect mentioned in your earlier message is for SP1 Beta3, the first Beta release needing a change in FSUIPC. FSUIPC4.10 can work with the RTM version of SimConnect, or SP1Beta3, SP1Beta4, as well as SP1 RTM. All this is logged. If the system records an error when the Installer or the DLL itself goes through its Manifest Probe loop to find the versions available, that'll just be for information -- the error is returned and the program thereby knows that version isn't installed. Regards Pete

Isn't IVAP a SimConnect client now? They aren't user alternatives. If a program is written to use FSUIPC exclusively, then it will run on WideFS. If it is written to use SimConnect, then it uses SimConnect, and WideFS does not come into it. SimConnect has its own Networking system. No, of course not. It uses SimConnect 100%. How can it be incompatible if it is completely dependent upon it? It sounds like you've added a SimConnect.XML file on the FSX PC which enables the remote SimConnect but excludes the local one. The XML file needs two sections -- a so-called "global" section (confusingly meaning "remote") and the same default "local" section shown in the SDK. If you re-run the FSUIPC4 installer, and the only problem is that you've got a "global" section and no "local" section, it will fix that for you automatically. I have no idea what IVAP does, sorry. Doesn't it come with any documentation or installation guide? Regards Pete

No, none. Everyone has confirmed what I see. When you right-click on the Icon for FSX, there surely must be a "Run as administrator" option? I've now got two Vista installations (one Home Premium, the other Ultimate) and they both provide this option for all programs, not just FSX. I've no idea how to hide ityou must surely have some super-protective settings enabled somewhere, or possibly you are logged on as an ordinary user, not the Administrator? If so, see if there's a "Run as ...." which allows you to specify the Admin username and password prior to running FSX. If you let FSX install in its default place, deep within "Program Files", then you are prevented from changing anything at all in its folders -- it is all part of Vista's super protective system to stop you messing things up. The only way to edit stuff in any Program Files folder is to change access permisions. Please don't ask me how to do that -- it took me several days following other folks' advice and I can't explain it. I eventually managed to make my FSUIPC Installer automatically change access permissions to the modules folder, so I can write the LOG, INI and KEY files there. That was by a lot of "magic" code which I'd find difficult to explain too! I like the *look* of Vista, but pretty much everything else about it does tend to annoy me. Maybe I'll get used to it, one day, but meanwhile I am sticking to XP for development and "real" flying. Regards Pete

You don't need a registered FSUIPC for WideFS, you need WideFS to be registered. However, if they both say "connected" I assume that is what you mean? No idea what is meant by a "missing DLL". Is this for FSC or something you've read to do with WideFS? Sorry, I've no idea what this means. Where are you trying to "open ther client"? The only part always needed is WideClient.EXE. Run that. It sounds like you are running it in any case if it says "connected", otherwise it couldn't say anything! ;-) If you want any help with muy programs, I need these things please: Version numbers: Wideclient and FSUIP4 version numbers. Log files: Wideclient.Log for the client, WideServer.Log from the FSX Modules folder, and FSUIPC4.Log also from the Server. From the rest of your message it seems you have Windows hiding the filetypes like "INI", "TXT" and "LOG". The Log files are text files so if you double-click on them you can read them. Do that then copy them here. Or else change your explorer options so you can see files by their names. Regards Pete

Ah! I didn't know that. So, is the only way to "repair" a broken SimConnect on Vista to uninstall and re-install everything? I think the problem on Vista with that is that uninstalls NEVER remove Side-by-Side installations, so when the re-install occurs it will probably be unable to fix the broken SimConnect! I think I need some more expert advice so I can change my "FSX Help" text properly. Regards Pete

One minor point there: the string should always be zero terminated, so for an "h" on its own you needed 2 characters, 'h' and a zero byte. You were just lucky that the next byte (in 3381) happened to be zero already. The length in the Write to 3380 is still only 1, so only 1 byte is written to 3380. you need the entire string length including the zero at the end. Not surprising when you look at your code. you are writing a charracter to 3380, then overwriting it with the next, etc, til the last. So, the only one left in 3380 is the last. Isn't that obvious? I don't know why you'd want to write only one byte (character) at a time -- it is very inefficient -- but if you do you'd need to increment the offset (3380) each time too, otherwise, isn't it obvious that you are simply writing to the same location (3380) all the time? Why not simply write the whole string at once? FSUIPC_Write($3380, Length(field), @field[a], dwResult); And don't forget to make sure there's a zero byte ending the string and included in the length. Regards Pete

Do you have the documentation from the SDK? There it states: As it implies, the positions and names can't be changed, only the loadings, and then such changes don't have the desired effect -- in FS2004. The facility should work better in FSX as it is officially supported now via SimConnect. FS most certainly doesn't automatically reload anything. There is a "reload user aircraft" control you can assign, however. Have you tried that? Regards Pete

Sorry about thatI'll add something to the ReadMe. Meanwhile here's the details of each of the CSV files: RUNWAYS.CSV (ORIGINAL RUNWAYS FILE -- for FStarRC): ICAO, Rwy*, Latitude*, Longitude*, Altitude*, Heading Mag, Length*, ILSfreq* R4.CSV (RUNWAYS FILE for RCV4): ICAO, Rwy*, Latitude*, Longitude*, Altitude*, Heading Mag, Length*, ILSfreq*, Width*, MagVar, CentreLatitude, CentreLongitude, ThresholdOffset* R5.CSV (RUNWAYS FILE for RCV5): ICAO, Rwy*, Latitude*, Longitude*, Altitude*, Heading Mag, Length*, ILSfreqFlags*, Width*, MagVar, CentreLatitude, CentreLongitude, ThresholdOffset*,Status* G5.CSV (GATES for RCV5): ICAO, GateLetter, GateNumber, Latitude, Longitude, Radius*, HeadingTrue, GateType*, AirlineCodeList ... T5.CSV (TAXIWAYS for RCV5): ICAO,TaxiwayName,Minimum Width*,PointList ... where PointList is a sequence of: Latitude,Longitude,TaxiType*,Width* * Rwy is nnn for runway number, then 0, 1=L, 2=R, 3=C, 4=W (water) * Latitude is of threshold or AFCAD's "runway start" * Longitude is of threshold or AFCAD's "runway start" * Altitude in feet * Length in feet * ILSFreq as nnnnn for nnn.nn, or just 0 when no ILS * ILSFreqFlags is ILSFreq then optional B (backcourse), D (DME) G (Glideslope) equipped * ThresholdOffset in feet * Status: ,CT for Closed for Takeoff and/or ,CL for Closed for Landing * Radius in metres * TaxiType is 0 = unknown 1 = Normal 2 = Hold short 3 = unknown 4 = ILS hold short * GateType is: 0 = none 1 = Ramp GA 2 = Ramp GA Small 3 = Ramp GA Medium 4 = Ramp GA Large 5 = Ramp Cargo 6 = Ramp Military Cargo 7 = Ramp Military Combat 8 = Gate Small 9 = Gate Medium 10 = Gate Large 11 = Dock GA Regards Pete

I don't know a thing about designing aircraft for FS, but I assume it's all part of the graphic design, in the MDL file? Maybe you need to download the aircraft design SDK from the Mcrosoft websites? Regards Pete

No one had ever asked for tis data from FSUIPC before in all its 7 year history, and I've no idea how to find it in FS's innards. The same really goes for most of FS's aircraft design data (whether from the AIRCRAFT.CFG file, or its AIR or MDL files). The main reason for supplying fuel tank capacity and fuel indications is so that external gauges and fuel displays can be made. Unless you are trying to replace the actual flight simulation activities of FS I'm not sure why it should be able to supply any aircraft design values in any case. Surely, in that case, you'd need much more data anyway. Can you explain? Regards Pete

I don't understand the code at all (not my area), but in C/C++ "long" is certainly not usable for receiving a "double" as, even if it doesn't get "converted", a double is 64 bits long and a long is only 32 bits. In C/C++ you'd read 8 bytes from the quoted offsets directly into a double. Regards Pete

Apologies! It was at the end of the line when it was first added and the ReadMe updated, but of course there are other things added after. I'll amend the ReadMe! Pete

Good! No, it won't just by copying in the Modules folder. You have to run the Installer to get the correct parameters into SimConnect's files in your "Documents and Settings". FSX is not like FS2004 -- it won't load DLLs just because they are there! This is why I had to build an Installer for the first time. Sorry, I don't know what that means. But never mind. I'm glad it is all okay now. Go fly! Enjoy! Regards Pete

No! By coincidence, Registry update files (which used to be ".reg" files) came to be called .key files some time around when XP came out I think. But the FSUIPC.KEY file is NOT a registry update. It is simply a text file containing your Key infomation. Do not double click it! If you want to view it, right-click on it and open it with Notepad. Pete

FSUIPC will install in any folder you correctly install FSX into. It doesn't care what the folder is. The problem you had was that the Registry did NOT point correctly to the FSX folder where it should have done. This would cause you problems later. I also said that if you re-installed FSUIPC using the later version of FSUIPC it would offer to fix the registry for you. In order to get the registry pointing to the wrong place, you must have actually moved FSX using Explorer. I always install FS into nice easy folders to remember, like C:\FSX or more usually on a different disk altogether, like E:\FSX. On one system I have FS2002, FS9 and FSX all installed like that. I only let FS install itself in the default places for testing installers. ;-) After you load FSX with FSUIPC installed, there will be an FSUIPC4.LOG file produced in the FSX Modules folder. There always is, you can't stop it if FSUIPC is running. Just close FSX, find the two files, FSUIPC4.LOG and FSUIPC4.KEY in the FSX Modules folder, ZIP them together and send them as I said. Regards Pete

There's nothing I know that'll do that, assuming FSUIPC4 is installed correctly, and you are running as an Administrator. Please ZIP up the FSUIPC4.LOG and FSUIPC4.KEY files and send to petedowson@btconnect.com, and I'll check them here. I'm away from tomorrow for a week, so please do it as soon as possible and I'll get straight onto it. Why are you reinstalling? If FSUIPC4 is installed and it is running well enough for you to get to the Add-Ons/FSUIPC menu, there won't be that much wrong, especially not enough to justify a re-install. But let me see the files first. Regards Pete

By "go to FSUIPC" do you mean go to the Add-Ons menu, and click on FSUIPC? That takes you to FSUIPC options. Only one of the options there is to register FSUIPC. It never asks you to do anything explicitly. Many folks don't register because they have no need of the extra facilities. If it is registered it will say it is registered, if it is not, it will say it is not registered. The rest is up to you. If you mean it is saying you are not registered, and you are clicking on the Register FSUIPC button, then the fact that is shows your name and email means there is an FSUIPC4.KEY file in the FSX Modules folder containing those details. Also, in that file, there will be the Key you registered with before. It sounds like you re-installed Windows, or rolled back to a previous restore point (before you registered). Is that right? You would need to re-register then, certainly, but you can cut-and-apaste the key from the FSUIPC4.KEY file -- it is only a Text file, open it with Notepad or any text editor. Regards Pete

FSUIPC never asks you to register, either. It never asks anything. If something is asking you to register, it most certainly isn't FSUIPC! Please describe exactly this window or whatever which is asking you such a thing. Obviously if it is another program altogether the FSUIPC Key you have will not work! Regards Pete

With the same sort of error? Were you using this AOL software before, and autothumbnail worked? The fact that autothumbnail stopped working in SP1 may simply mean it isn't compatible with some changes between the original version of FSX and SP1. There have been a lot of changes, and compatibility is only guaranteed for those programs which played exactly by the rules. FSUIPC4 had to be changed to work properly because of some intricate arrangements, unpublished links. What connection to the Internet? Nothing to do with FSUIPC or SimConnect makes any connection to the Internet, so that is irrelevant. The connection which is being blocked, or slowed too much (more than 3 seconds I'm told) is between one part of FSX (SimConnect) and another part (FSX.EXE and its constituent modules in the FSX folder). Okay, if you think that rather than a problem with AOL, please report it with all the relevant details, to Microsoft Tech Support, and also send it all to tell_fs@microsoft.com. Regards Pete