Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    37,984
  • Joined

  • Last visited

  • Days Won

    158

Everything posted by Pete Dowson

  1. Ah! Norton. Yes. Somehow I equated "NAV" with NAVigational Aid (as in Ted Wright's "NAV3" program for FS, and so though it was using FSUIPC in an odd way! I think NAV is a well know causer of stuttering and pausing problems in FS, and not just with specific panels. It has generally been recommended to disable active virus checkers when running almost any real-time sim type programs, FS especially, for many years. I find it best to have it enabled only for Email checking, and activate it occasionally to check specific files or folders. FS certainly runs MUCH smoother if you deactivate ALL unnecessary background tasks. I know many folks run "EndItAll" (a freeware program) to accomplish this. Alternatively use CTRL-ALT-DEL to look at the Task List. Generally, before running FS, all you should have listed is Explorer and the tray application -- that's on Win98 anyway. I think on XP you will find far too many odd-looking applications! Pete
  2. With WidevieW, really, the "client" PCs need to be just as capable as the main FS PC -- they need a full installation of Fs just like the main PC. Oh. I suppose if you don't need to see the scenery on those PCs then they can be a bit slower, etc/ I'm not sure how WidevieW works these days. If it puts the slaves into "slew" mode then this may explain such a problem -- I don't think many of the instruments work in slew mode. On the other hand it may simply be that you are using the version of WidevieW which is really intended for multiple outside views. I remember, back when it started, there was a fully configurable version which could be set to provide all of the instrument values too. This was not "WidevieW Light", but the full thing. I don't know if it was ever updated to FS2002. Did you check the appropriate support site (Luciano Napolitano is the author, sorry, I don't know the website). You can't use normal FS panels on any PC that isn't running FS. the panel gauges are only DL's which use many routines inside FS to produce their graphics and motions. For external panels, under WideFS, there are products like Project Magenta (payware) and FreeFD (freeware). There are probably others. See the links on the Schiratti/dowson page. Pete
  3. With WidevieW, really, the "client" PCs need to be just as capable as the main FS PC -- they need a full installation of Fs just like the main PC. Oh. I suppose if you don't need to see the scenery on those PCs then they can be a bit slower, etc/ I'm not sure how WidevieW works these days. If it puts the slaves into "slew" mode then this may explain such a problem -- I don't think many of the instruments work in slew mode. On the other hand it may simply be that you are using the version of WidevieW which is really intended for multiple outside views. I remember, back when it started, there was a fully configurable version which could be set to provide all of the instrument values too. This was not "WidevieW Light", but the full thing. I don't know if it was ever updated to FS2002. Did you check the appropriate support site (Luciano Napolitano is the author, sorry, I don't know the website). You can't use normal FS panels on any PC that isn't running FS. the panel gauges are only DL's which use many routines inside FS to produce their graphics and motions. For external panels, under WideFS, there are products like Project Magenta (payware) and FreeFD (freeware). There are probably others. See the links on the Schiratti/dowson page. Pete
  4. Ah, glad you solved it. What's NAV2003? Maybe I'll take a look, see what it's doing, when (IF! ) I ever get an idle moment. Pete
  5. Ah, glad you solved it. What's NAV2003? Maybe I'll take a look, see what it's doing, when (IF! ) I ever get an idle moment. Pete
  6. I have no data whatsoever about anything in offsets 0818 and 081C. How do you know they are "assorted AP flags 1"? If you have some information which I can add to the Programmers Guide, please let me have it! Regards, Pete
  7. I have no data whatsoever about anything in offsets 0818 and 081C. How do you know they are "assorted AP flags 1"? If you have some information which I can add to the Programmers Guide, please let me have it! Regards, Pete
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.