macwino

Peter, I'm a bit confused by your questions, so let me state in further detail exactly what's going on. The easiest situation to explain is that of a crash on landing. If I press Alt at the time of the crash, and then go to Flights>Reset Flight, the scenery and traffic reload and the sim restarts about 5 seconds or less before the crash. It's a very short time because it's not enough to avoid the crash. If you do a Reset Flight command during normal flight any change in the flight location isn't really noticeable. There's no saved flight file other than the usual files saved every 60 seconds; nothing named like what you are looking for. No time right now to run a test and check out the time stamps, etc. that you requested, but when I have a chance later tonight (I'm in California), I'll try a crash and report back. Thanks for the help. Robert

Peter, the cfg file is in the correct location - the main fs9 folder where most all of the fs files and folders are stored, including the fs9.exe file. If you can't come up with a solution, then there must be some conflict with another program I'm running, but I've not a clue what it might be. Robert

I am running v1.5 of AutoSave. It is acting strangely following a reinstall of FS 2004. I am using the default generated autosave.cfg file with no changes at all. Nonetheless, AutoSave is acting as though I had added the command AlsoSave=My Restart to the cfg. In other words, when I execute the Restart Flight command under the Flights menu - with AutoSave installed in the Modules folder - the reloaded flight commences a few seconds before where I was in the flight, instead of on the runway where I started the flight. If I remove AutoSave from the Modules folder, then the Restart Flight command works as it should, and returns me to the runway where I started the flight. I've tried regenerating the autosave.cfg but this doesn't help. The same inexplicable behaviour continues. So it sesms that the AlsoSave=My Restart code is embedded in my version of AutoSave even though no such line has been added to the cfg. Peter, can you help me out with this anomaly? Thanks, Robert PS: Attached is a copy of my autosave.cfg file.

Quote: Well, in general it is usually better to provide the ServerName rather than the IPaddress, as you are less likely to change that. What version of WideFS are you using? Are both Server and Client running WinXP? With the current version of WideFS and XP all round you should never need to specify server name, IP address, ort anything. ---------------- I'm running v6.5.1 of WideFS. Your advice about using the server name instead of the IP address is well taken. I just didn't know my server name right off the bat and I did know the IP address. I've since changed the entry to the Server Name. I know this should have worked automatically as I'm running XP on both machines, but for some reason it apparently connected automatically at first, but sometime during the past 2 weeks it stopped connecting and needed the Server Name entry to reconnect.

Hi Peter, I wish I'd posted 3 hours earlier. Your analysis pointed me in the direction to fix the problem. Thanks so much. First, you're right - I was very confused - but you straightened me out. Yes, I'm using GPSOut for the moving map, not WideFS; however, I've been launching WideFS for years whenever I used the moving map because I thought I had to. Dumb! Second, I found that WideClient wasn't receiving any info from the FS9 machine; it was indeed disconnected. But I suppose it was connecting a few weeks ago when I had this working. So something messed up the connection. In any event, I read the manual and added the line you suggested to the WideClient.ini referencing the IP address of the FS9 machine. Once I did that, all was working fine. Finally, I have valid registrations for both FSUIPC and WideFS. The email address used by my simFlight Network forum registration is a real old one and is not the one I used when I registered the programs. I'll email you the registration info shortly just to confirm this, and I'll try and change my email address with the forums so all is up to date. Thanks again for all the help, and especially for explaining to me just what was going on here. Robert

I am having a problem running Google Earth with MyFsGoogleEarth over my registered copy of WideFS. I am using the very latest versions of FSUIPC and WideFS. I am posting here because I am getting the following error message from MyFsGoogleEarth when I try and track a plane in Google Earth: [initFs2] Error opening FSUIPC connection: 14 This error message is accompanied by a Google Earth error message that "Fetch of the NetworkLink failed." Do you have any idea what the FSUIPC error means and how I might eliminate the error? I use WideFS for a moving map program with a null modem cable connection and it works just fine. But this Google Earth connection is an ethernet connection and doesn't seem to be working. What's most frustrating is that I had this working a few weeks ago. Then, I did a defrag of my hard drive on the main FS9 machine, and this appears to have changed the IP address for my FS9 machine - or that's my best guess as to what caused the change. I made the necessary corrections in Google Earth's settings for the new IP address, but I now get this error referring to FSUIPC. My WideFS ini file makes no reference to IP addresses since I understand this to no longer be necessary. So I'm at a loss as to what the problem might be. Thanks, Robert

Pete, thanks for the info. I'll give it a try and look forward to the update. In case you were wondering what kind of keyboard I use, it's an Apple keyboard. I use it for cosmetic reasons because it matches the Apple widescreen cinema display that I use for fs9.

I'd like to be able to program the F14 and F15 keys to buttons on my CH Products yoke. I presently use them to turn my Track IR off and on, and to center it. But when I try and enter these keys in the button page they do not register. Is there any way to program these keys to yoke buttons? A clarification: On a standard PC keyboard these keys are denoted Scroll Lock and Pause Break. Within the Track IR controls I am able to assign these keys to perform Track IR actions. I'd like to be able to use FSUIPC to assign these keys to buttons on my yoke. Thanks, Macwino