Pete Dowson

Ahyour example of toggling the afterburner (an FS control?) was a bit misleading, then, wasn't it! Sorry, there's no built-in facility for that. EPIC programmers can do that, from the EPIC of course. You can do that from an application program written to interface to FSUIPC (see the FSUIPC SDK). The only module I have written which acts on FS events is Esound, but that only triggers sounds not keystrokes or button presses. It was a huge amount of work getting that as far as I did and it really wasn't worth the effort. Any generalised way of doing the sort of thing you want amounts to nearly as big a job as writing a full blown Basic-like interpreter or compiler -- most different "events" in FS would need a specification of offset or token name, size, units, etc. You'd need to be able to compare, equate and so on, and presumably make compound conditions and sets of these which vary. See Esound's documentation for the sort of thing. It really is a big job to do as a generality. If you have specific needs then you will find Visual Basic (for example) probably easier to learn and more powerful in the long run. The FSUIPC SDK contains stuff to help with the interfacing to FSUIPC. Aren't the GoFlight units programmable? Check with Doyle. Seems like a bit of an omission if they aren't. Regards, Pete

Ahyour example of toggling the afterburner (an FS control?) was a bit misleading, then, wasn't it! Sorry, there's no built-in facility for that. EPIC programmers can do that, from the EPIC of course. You can do that from an application program written to interface to FSUIPC (see the FSUIPC SDK). The only module I have written which acts on FS events is Esound, but that only triggers sounds not keystrokes or button presses. It was a huge amount of work getting that as far as I did and it really wasn't worth the effort. Any generalised way of doing the sort of thing you want amounts to nearly as big a job as writing a full blown Basic-like interpreter or compiler -- most different "events" in FS would need a specification of offset or token name, size, units, etc. You'd need to be able to compare, equate and so on, and presumably make compound conditions and sets of these which vary. See Esound's documentation for the sort of thing. It really is a big job to do as a generality. If you have specific needs then you will find Visual Basic (for example) probably easier to learn and more powerful in the long run. The FSUIPC SDK contains stuff to help with the interfacing to FSUIPC. Aren't the GoFlight units programmable? Check with Doyle. Seems like a bit of an omission if they aren't. Regards, Pete

Confirm you are using the latest version, WideFS 5.50, please. You need to show me your INI files (both WideClient and WideServer.ini files) and the Log files produced by both, too. The information needed is in these files. The format of the parameter you need is "ServerName=..." or "ServerIPAddr=..." -- if you are typing "IPAddr= ..." as you say then it is wrong. Please read the documentation more clearly. The IP address you use in FS for Multiplayer will *not* be the IPAddress of your FS PC in any case. You should be assigning a fixed IPAddress on you LAN for each PC, in the TCP/IP properties in Windows Networks. Please note that *everything* I know about Networks is embodied in the WideFS documentation. If you have any problem not already covered there, you need help with your Network and you need someone who knows more than I. In particular, if your PCs are connected using a Router as a Hub or Switch, it is possible that there are firewalls or other blockages being set there which you have to sort out. A router is for connection to the Internet, it is otherwise not required for a Local Network. I think some routers provide hub-type facilities too, so you need to check what it is doing. BTW, have you tried Magenta support? I think they may know much more about Networks than I. Pete

Confirm you are using the latest version, WideFS 5.50, please. You need to show me your INI files (both WideClient and WideServer.ini files) and the Log files produced by both, too. The information needed is in these files. The format of the parameter you need is "ServerName=..." or "ServerIPAddr=..." -- if you are typing "IPAddr= ..." as you say then it is wrong. Please read the documentation more clearly. The IP address you use in FS for Multiplayer will *not* be the IPAddress of your FS PC in any case. You should be assigning a fixed IPAddress on you LAN for each PC, in the TCP/IP properties in Windows Networks. Please note that *everything* I know about Networks is embodied in the WideFS documentation. If you have any problem not already covered there, you need help with your Network and you need someone who knows more than I. In particular, if your PCs are connected using a Router as a Hub or Switch, it is possible that there are firewalls or other blockages being set there which you have to sort out. A router is for connection to the Internet, it is otherwise not required for a Local Network. I think some routers provide hub-type facilities too, so you need to check what it is doing. BTW, have you tried Magenta support? I think they may know much more about Networks than I. Pete

That doesn't mean that it's a problem in my module. All that is probably happening is that values used by 767PIC depend upon or are changed when FSUIPC is present -- FSUIPC supplies many of the otherwise unobtainable engine values that many aircraft use. No one else that I know of has this problem, and I know the 767PIC is in full time use by many people with FSUIPC. At least one person I know rarely flies anything else and has always used FSUIPC. Not that I know of, no. If they have I'm sure someone will chime in here. Sorry, but I really can do nothing about this. The PIC 767 programmers have always been downright uncooperative with everything I've tried to achieve, even though I tried to fix some of their programmed problems in FSUIPC because they didn't, and added support for their panel in PFC.DLL without their help. I long ago stopped using it, it was too much pain. I hope other 767PIC users can help you. Possibly you need an update, or something has got corrupted. Have you tried re-installing it from scratch just in case? Regards, Pete

That doesn't mean that it's a problem in my module. All that is probably happening is that values used by 767PIC depend upon or are changed when FSUIPC is present -- FSUIPC supplies many of the otherwise unobtainable engine values that many aircraft use. No one else that I know of has this problem, and I know the 767PIC is in full time use by many people with FSUIPC. At least one person I know rarely flies anything else and has always used FSUIPC. Not that I know of, no. If they have I'm sure someone will chime in here. Sorry, but I really can do nothing about this. The PIC 767 programmers have always been downright uncooperative with everything I've tried to achieve, even though I tried to fix some of their programmed problems in FSUIPC because they didn't, and added support for their panel in PFC.DLL without their help. I long ago stopped using it, it was too much pain. I hope other 767PIC users can help you. Possibly you need an update, or something has got corrupted. Have you tried re-installing it from scratch just in case? Regards, Pete

I don't really understand I'm afraid. "Toggle AfterBurner1" is an "action" by whom? You, the user, presumably? How do you do it? By pressing a button or or key, again presumably? So it's the same as programming a button or key in FSUIPC's buttons or keys page, is it not? If so, then you can use KeySend. Or am I completely misunderstanding you? Pete

I don't really understand I'm afraid. "Toggle AfterBurner1" is an "action" by whom? You, the user, presumably? How do you do it? By pressing a button or or key, again presumably? So it's the same as programming a button or key in FSUIPC's buttons or keys page, is it not? If so, then you can use KeySend. Or am I completely misunderstanding you? Pete

Yes. It looks like I will most definitely need to go "payware". As from 1st May I have no other income, at least not till I arrange a pension. The voluntary donations were fine for the first two weeks, but all through April they've been a mere trickle. I've had good contributions from many of the more famous shareware makers, have no fear. Commercial setups with boxed products are more difficult, they need contracts, agreements, purchase orders, invoices. I will have to come to an agreement with each one individually (a real pain for someone who only wants to get on and program ). You wouldn't expect box shifting companies to make "voluntary" contributions, they've no mechanism for that, no way of budgeting for it except in advance, no accounting mechanism. And the royalties that the authors get are really relative peanuts -- it's normally the retailer that makes the money. Thanks! :D See above. The bigger the company the more difficult to do anything with. How do you think they get so big? Of course they know, and they are very friendly and (when they get time, which isn't so often, unfortunately) very helpful. But they are just a small team of programmers and designers in a huge company, and have no control over anything to do with money! Thanks very much, it is appreciated. I am pressing on. But I can see no alternative but to go commercial, probably with effect from the FS9 versions. I have a record of all contributions made under the voluntary scheme (with so few it is relatively easy to keep a small database ), so credit can be allowed on request when the time comes. Regards, Pete

Yes. It looks like I will most definitely need to go "payware". As from 1st May I have no other income, at least not till I arrange a pension. The voluntary donations were fine for the first two weeks, but all through April they've been a mere trickle. I've had good contributions from many of the more famous shareware makers, have no fear. Commercial setups with boxed products are more difficult, they need contracts, agreements, purchase orders, invoices. I will have to come to an agreement with each one individually (a real pain for someone who only wants to get on and program ). You wouldn't expect box shifting companies to make "voluntary" contributions, they've no mechanism for that, no way of budgeting for it except in advance, no accounting mechanism. And the royalties that the authors get are really relative peanuts -- it's normally the retailer that makes the money. Thanks! :D See above. The bigger the company the more difficult to do anything with. How do you think they get so big? Of course they know, and they are very friendly and (when they get time, which isn't so often, unfortunately) very helpful. But they are just a small team of programmers and designers in a huge company, and have no control over anything to do with money! Thanks very much, it is appreciated. I am pressing on. But I can see no alternative but to go commercial, probably with effect from the FS9 versions. I have a record of all contributions made under the voluntary scheme (with so few it is relatively easy to keep a small database ), so credit can be allowed on request when the time comes. Regards, Pete

Being naturally curious, I had a quick look this morning to see why FStarRC didn't work on XP. I found and fixed the problem. It was relatively trivial after all. Please look out for FStarRC version 1.83, being released as I type this. Should be on the Schiratti site withon hours, with luck! Regards, Pete

Being naturally curious, I had a quick look this morning to see why FStarRC didn't work on XP. I found and fixed the problem. It was relatively trivial after all. Please look out for FStarRC version 1.83, being released as I type this. Should be on the Schiratti site withon hours, with luck! Regards, Pete

Ah .. I owe you, and Herve, an apology. I was getting mixed up. As I stated in the documentation, in the History part describing the change to 1.82, I got it working on Windows 2000, and said there that I hoped it would be fine in WinXP (XP being basically Windows NT 5.1 whereas 2000 was NT 5.0, right? How much difference could there be?). Well, since doing that and testing it on Windows 2000, I updated that PC to Windows XP. And guess what? FStarRC 1.82 doesn't work on XP. :-( Sorry. I'll try and look for a solution to this when I can, but it's going to have to wait a few months. I simply must concentrate on getting my stuff sorted out for FS9. Please remind me again in September or so. Apologies for getting your hopes up. If you can dual boot with Win98 then I'd suggest doing that. I actually have this PC with both WinXP Pro and Win2000 Pro on it, and another PC with just Win98. Regards, Pete

Ah .. I owe you, and Herve, an apology. I was getting mixed up. As I stated in the documentation, in the History part describing the change to 1.82, I got it working on Windows 2000, and said there that I hoped it would be fine in WinXP (XP being basically Windows NT 5.1 whereas 2000 was NT 5.0, right? How much difference could there be?). Well, since doing that and testing it on Windows 2000, I updated that PC to Windows XP. And guess what? FStarRC 1.82 doesn't work on XP. :-( Sorry. I'll try and look for a solution to this when I can, but it's going to have to wait a few months. I simply must concentrate on getting my stuff sorted out for FS9. Please remind me again in September or so. Apologies for getting your hopes up. If you can dual boot with Win98 then I'd suggest doing that. I actually have this PC with both WinXP Pro and Win2000 Pro on it, and another PC with just Win98. Regards, Pete

Yes, it works fine through WideFS. There's no setting up to do. I just click on a WideClient shortcut, and the Wideclient.ini is set to load FSMeteo (and, as it happens, Radar Contact 3 and TrafficBoard as well -- I run all through on one of my networked PCs). Of course you need an Internet connection on that PC for FSMeteo to download the weather. In fact that's the main reason I don't like running FSMeteo on the main FS PC -- I'd rather keep that one free of such encumbrances. Pete

Yes, it works fine through WideFS. There's no setting up to do. I just click on a WideClient shortcut, and the Wideclient.ini is set to load FSMeteo (and, as it happens, Radar Contact 3 and TrafficBoard as well -- I run all through on one of my networked PCs). Of course you need an Internet connection on that PC for FSMeteo to download the weather. In fact that's the main reason I don't like running FSMeteo on the main FS PC -- I'd rather keep that one free of such encumbrances. Pete

Sorry, not really. I guess I'd have to take some time at it and think it through. I'm really deep into other things at present. It doesn't look too hard to test as a theory anyway, without committing yourself? Let me know what you find. Regards, Pete

Sorry, not really. I guess I'd have to take some time at it and think it through. I'm really deep into other things at present. It doesn't look too hard to test as a theory anyway, without committing yourself? Let me know what you find. Regards, Pete

It's not on any list yet, and I'm not making one yet. Too busy trying to sort things out for FS9. Please ask me again around Christmas time and it'll go on the list for next year. Pete

It's not on any list yet, and I'm not making one yet. Too busy trying to sort things out for FS9. Please ask me again around Christmas time and it'll go on the list for next year. Pete

There's nothing I've changed thenyou need to work out what you've changed. Maybe a rogue sound file? A problem with the sound driver? To get more information -- a DrWatson -- please follow the directions in the FSUIPC User Guide (under the heading "If FS crashes ..."). If you are using Win98SE this will give a helpful file. Unfortunately if you are using XP it is pretty useless. Hmmmso something else you changed has done the trick. You need to cast your mind back to what happened between it working and it not working. I'm sorry, I do not develop nor support Esound any more. If I can help I will, but you need to work out what the problem is I'm afraid. The clue will be what happened to make it change. (Maybe Esound itself got corrupted? Did you reinstall from the original Zip or download it again to check?). Pete

There's nothing I've changed thenyou need to work out what you've changed. Maybe a rogue sound file? A problem with the sound driver? To get more information -- a DrWatson -- please follow the directions in the FSUIPC User Guide (under the heading "If FS crashes ..."). If you are using Win98SE this will give a helpful file. Unfortunately if you are using XP it is pretty useless. Hmmmso something else you changed has done the trick. You need to cast your mind back to what happened between it working and it not working. I'm sorry, I do not develop nor support Esound any more. If I can help I will, but you need to work out what the problem is I'm afraid. The clue will be what happened to make it change. (Maybe Esound itself got corrupted? Did you reinstall from the original Zip or download it again to check?). Pete

I use FliteMap by Jeppesen, linked to FS by my GPSout on a serial cable. This is a realy professional solution, but it is expensive. There's a program called Nav3 by Ted Wright which I used to use. Maybe it is Nav4 or something later by now. Nav3 dates back to FS98 at least. There are programs like FlightMax, which had a "FlightMax Remote" part which would work on WideFS, but I understand that the website is now closed. Maybe a search for FSutilities would get results? If you are dead set on FS Navigator, the best solution is to add a second monitor to your main FS PC and move its screen there. Most modern video cards support two monitors (two VGA or a DVI and a VGA), or you could get a cheap PCI card for the second monitor. There are quite a few folks who've adoped this solution. Pete

I use FliteMap by Jeppesen, linked to FS by my GPSout on a serial cable. This is a realy professional solution, but it is expensive. There's a program called Nav3 by Ted Wright which I used to use. Maybe it is Nav4 or something later by now. Nav3 dates back to FS98 at least. There are programs like FlightMax, which had a "FlightMax Remote" part which would work on WideFS, but I understand that the website is now closed. Maybe a search for FSutilities would get results? If you are dead set on FS Navigator, the best solution is to add a second monitor to your main FS PC and move its screen there. Most modern video cards support two monitors (two VGA or a DVI and a VGA), or you could get a cheap PCI card for the second monitor. There are quite a few folks who've adoped this solution. Pete

Yes, it shows that FStarRC is not able to hook into the printing routines on your system. Are you using Win2000 or NT? I don't think it will work on those. I only just narrowly managed to make it work on XP -- but maybe you have to be the Administrator. The techniques it uses are probably not allowed otherwise. They are the same techniques used for debugging programs and hacking into others, so I think an ordinary XP user might be prevented from doing this. No don't bother. It is not getting anywhere close to even looking at that. If it cannot hook the routines it can do nothing. Of course, because it is not able to hook into it. The only reason I would have wanted to look at the output was if the format of the printing had changed between the version of FliteStar I am using and the one you have. As I said, the method is very sensitive in this regard. If you can get it working by running on Win98/Me or by using XP as administrator, let me know how please. I've never actually logged into XP as anything but me, so I'm not aware of what's involved. Maybe I need to adjust the FStarRC documentation. Pete