Pete Dowson

If by "hex.address" you mean access values in FSUIPC, then I'm afraid you are out of luck. When programmers make panels like those they do their own thing, within their own code, and do not usually export it in any way accessible to FSUIPC. The only definite exception I know about is Project Magenta. The 767PIC version 1.3 does allow access through a DLL I think, but I don't know if they make it available. Certainly I've never seen any official documentation for it. For others I think you can really only resort to programming mouse clicks -- something like Luciano Napolitano's "Key2Mouse" program could be used to convert keystrokes to mouse clicks. Regards, Pete

Sorry, but there is really no way possible to use different parts of an FS panel on different PCs without an installation of FS on each one. Each part of an FS panel uses so much code inside FS that it is completely dependent upon it. WideFS can only link EXTERNAL programs to FS over the LAN. If your client PC is powerful enough for FS then you can try linking multiple copies of FS together, but this involves WidevieW (by Luciano Napolitano) not WideFS. Even then, from what I've heard, the panel parts aren't actually driven correctly on clients, so you'd need to run the panel on the server and use the Client for views. All in all you'd be much better off using multiple monitors on an single PC. You can undock panel parts and simply drag them onto the other monitor. Regards, Pete

Sorry, but there is really no way possible to use different parts of an FS panel on different PCs without an installation of FS on each one. Each part of an FS panel uses so much code inside FS that it is completely dependent upon it. WideFS can only link EXTERNAL programs to FS over the LAN. If your client PC is powerful enough for FS then you can try linking multiple copies of FS together, but this involves WidevieW (by Luciano Napolitano) not WideFS. Even then, from what I've heard, the panel parts aren't actually driven correctly on clients, so you'd need to run the panel on the server and use the Client for views. All in all you'd be much better off using multiple monitors on an single PC. You can undock panel parts and simply drag them onto the other monitor. Regards, Pete

For spoilers it is easy enough to assign an axis in FS's own Options-Controls-Assignments dialogue. Scroll down the Joystick axis assignments and you will see it. FS2002 does not provide such a method for Trims and Flaps. You have to "cheat" by assigning a different axis, one that FS does recognise but which you are not otherwise using. You can do this in the FS assigments too, but then you need to determine the NUMBER of that FS axis control -- there are some suitable ones listed in the FSUIPC Advanced Users Guide, but for a complete list you can download the FS controls documents from the Schiratti site. Then, armed with the numbers so assigned, you have to edit a couple of parameters in the FSUIPC.INI file, in order to tell FSUIPC which axis controls to intercept and divert to trim and flaps. All this is actually explained in the Advanced Users Guide. It isn't part of the normal user interface as it is an unusual thing to find enough spare axes for these things except on cockpit-builders systems, and these are "advanced users", at least in my book! Pete

For spoilers it is easy enough to assign an axis in FS's own Options-Controls-Assignments dialogue. Scroll down the Joystick axis assignments and you will see it. FS2002 does not provide such a method for Trims and Flaps. You have to "cheat" by assigning a different axis, one that FS does recognise but which you are not otherwise using. You can do this in the FS assigments too, but then you need to determine the NUMBER of that FS axis control -- there are some suitable ones listed in the FSUIPC Advanced Users Guide, but for a complete list you can download the FS controls documents from the Schiratti site. Then, armed with the numbers so assigned, you have to edit a couple of parameters in the FSUIPC.INI file, in order to tell FSUIPC which axis controls to intercept and divert to trim and flaps. All this is actually explained in the Advanced Users Guide. It isn't part of the normal user interface as it is an unusual thing to find enough spare axes for these things except on cockpit-builders systems, and these are "advanced users", at least in my book! Pete

Both WideServer and WideClient automatically produce log files, called amazingly "WideServer.log" and "WideClient.log" respectively. They are in the same folder as the INI files you provided. They are mentioned in the documentation and always contain the full story. Pete

Both WideServer and WideClient automatically produce log files, called amazingly "WideServer.log" and "WideClient.log" respectively. They are in the same folder as the INI files you provided. They are mentioned in the documentation and always contain the full story. Pete

these are only the INI files. I also asked for the LOG files. It is the LOG files that tell what is going on! Pete

these are only the INI files. I also asked for the LOG files. It is the LOG files that tell what is going on! Pete

It isn't here. Look for yourself. And I see no other thread. Pete

It isn't here. Look for yourself. And I see no other thread. Pete

Ahyes, I see. Sorry, I must have forgoten to take them out of the FSUIPC.FSI file before I released it in one of the SDK updates. Those were locations I used when developing the FS2002 code in FSUIPC, in order to determine how to drive the autopilot and recognise what modes it was in. All that stuff changed between FS2000 and FS2002 and it took me quite a while, and help from FSInterrogate (as you see) to work it out. As the comment in the FSI says, they are "For Test and Diagnosis Only". With "Extras" logging on in FSUIPC you may also see those values logged occasionally too. There's now nothing useful in those flags which is not available, as controls and indicators, elsewhere in the interface. Please stick to the locations documented in the Programmers Guide. Anything else is not guaranteed is any case. Sorry about the confusion! Pete

Ahyes, I see. Sorry, I must have forgoten to take them out of the FSUIPC.FSI file before I released it in one of the SDK updates. Those were locations I used when developing the FS2002 code in FSUIPC, in order to determine how to drive the autopilot and recognise what modes it was in. All that stuff changed between FS2000 and FS2002 and it took me quite a while, and help from FSInterrogate (as you see) to work it out. As the comment in the FSI says, they are "For Test and Diagnosis Only". With "Extras" logging on in FSUIPC you may also see those values logged occasionally too. There's now nothing useful in those flags which is not available, as controls and indicators, elsewhere in the interface. Please stick to the locations documented in the Programmers Guide. Anything else is not guaranteed is any case. Sorry about the confusion! Pete

Sorry, I'm confused. I just reply to messages as I see them. What is the problem you have? I don't think I've seen seen any Logs from you yet, have I? Pete

Sorry, I'm confused. I just reply to messages as I see them. What is the problem you have? I don't think I've seen seen any Logs from you yet, have I? Pete

No, you omitted the WideServer Log, which would actually show the Server name and allow you to set "ServerName" instead of the awkward IP address. In your WideClient.ini the ServerNode is irrelevant for TCP/IP, that is only used for IPX/SPX. This is NOT the error you said in your earlier message. I don't rightly know what "connection refused" means, Windows tells me that. I suspect you have Windows XP firewall enabled on the server. Check that sort of thing. There is absolutely no difference between 5.40 and 5.50 excepting (a) the internal flag to tell WideFS what to do if no "UseTCPIP" parameter is provided is changed to assume "Yes" instead of "No", and (b) the Shutdown facility uses a different parameter on Windows 98 to Windows XP in order to correctly power off the PC. This is only relevant if you use "AllowShutdown=Yes" and would need everything working in any case. There is most definitely no difference whatsoever in the Networking side. I suspect you've changed options in XP, or possibly recently installed, updated, or re-installed it, and haven't got the settings right to allow external access. Please check these things. Regards, Pete

No, you omitted the WideServer Log, which would actually show the Server name and allow you to set "ServerName" instead of the awkward IP address. In your WideClient.ini the ServerNode is irrelevant for TCP/IP, that is only used for IPX/SPX. This is NOT the error you said in your earlier message. I don't rightly know what "connection refused" means, Windows tells me that. I suspect you have Windows XP firewall enabled on the server. Check that sort of thing. There is absolutely no difference between 5.40 and 5.50 excepting (a) the internal flag to tell WideFS what to do if no "UseTCPIP" parameter is provided is changed to assume "Yes" instead of "No", and (b) the Shutdown facility uses a different parameter on Windows 98 to Windows XP in order to correctly power off the PC. This is only relevant if you use "AllowShutdown=Yes" and would need everything working in any case. There is most definitely no difference whatsoever in the Networking side. I suspect you've changed options in XP, or possibly recently installed, updated, or re-installed it, and haven't got the settings right to allow external access. Please check these things. Regards, Pete

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

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

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

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

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

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

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

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