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. Once the app has opened the sound resource it doesn't change it. You can load up FS then when it is ready, change the default sound device and load up Radar Contact, or whatever. I've done this sort of thing before now, but these days just use another PC, it's easier! Pete
  2. I've never heard of it referred to as FS2003. It was originally FS2004, then FS9, the "Century of Flight" seems to have stuck now, but I wouldn't swear that it'll stil be that on release. So, "FSCOF" Not exactly. The weather in FS9 will be more advanced. There was almost no change from FS2000 to FS2002 so the AWI, designed for FS2000, was sufficient. I aim to retain the AWI but not enhance it. I will add completely new facilities to take full advantage of the developments in the weather. But I may not have time to do that in the first released version. Regards, Pete
  3. I've never heard of it referred to as FS2003. It was originally FS2004, then FS9, the "Century of Flight" seems to have stuck now, but I wouldn't swear that it'll stil be that on release. So, "FSCOF" Not exactly. The weather in FS9 will be more advanced. There was almost no change from FS2000 to FS2002 so the AWI, designed for FS2000, was sufficient. I aim to retain the AWI but not enhance it. I will add completely new facilities to take full advantage of the developments in the weather. But I may not have time to do that in the first released version. Regards, Pete
  4. Odd, there are a lot of folks happily using WidevieW. Perhaps your Network is not fast, or your client PCs aren't the same specification as your main one? Best really to have the instrumentation on the main PC and only views on the others. Okay, then use WideFS instead. No idea, sorry. You need someone who uses WidevieW to tell you, maybe Luciano himself can offer suggestions. Use WideFS. That's what it is for. That is what Project Magenta uses. Pete
  5. Odd, there are a lot of folks happily using WidevieW. Perhaps your Network is not fast, or your client PCs aren't the same specification as your main one? Best really to have the instrumentation on the main PC and only views on the others. Okay, then use WideFS instead. No idea, sorry. You need someone who uses WidevieW to tell you, maybe Luciano himself can offer suggestions. Use WideFS. That's what it is for. That is what Project Magenta uses. Pete
  6. It's a big job. Ask Enrico how many man hours went into Project Magenta. I take it you are an experienced programmer and can deal with the graphics as well as the real-time animation? Surely you are not asking for a complete tuition in this -- you need some reference books I think. Have you looked at the existing free gauges such as FreeFD (I think there's a link to this on the http://www.schiratti.com/dowson page). Pete
  7. It's a big job. Ask Enrico how many man hours went into Project Magenta. I take it you are an experienced programmer and can deal with the graphics as well as the real-time animation? Surely you are not asking for a complete tuition in this -- you need some reference books I think. Have you looked at the existing free gauges such as FreeFD (I think there's a link to this on the http://www.schiratti.com/dowson page). Pete
  8. If I were you, now, I'd hold off. The weather facilities in FS9 are going to be substantially improved and I am looking at an easier way of taking advantage of it rather than extending the AWI. Admittedly, the new facilities will not be backward compatible to FS2002 or FS2000 as the AWI is (or to FS98 as the method you are now using is), but even so ... That is certainly how it is intended to be used. Every time you call the Process routine Windows has to do a process switch, allocate memory, send the message, free memory, and process switch again. You not only slow down your program, but also FS. It's even worse if your program is run on a Networked PC under WideFS, as not only all that has to happen, but WideClient also has to send a Network block over for each call. The Read and Write calls merely add data to a block in your memory, forming it all up ready to send. Takes no time at all. It's the same as this message -- how efficient would it be if I put each sentence in a difference response to you, or worse, each word? Regards, Pete
  9. If I were you, now, I'd hold off. The weather facilities in FS9 are going to be substantially improved and I am looking at an easier way of taking advantage of it rather than extending the AWI. Admittedly, the new facilities will not be backward compatible to FS2002 or FS2000 as the AWI is (or to FS98 as the method you are now using is), but even so ... That is certainly how it is intended to be used. Every time you call the Process routine Windows has to do a process switch, allocate memory, send the message, free memory, and process switch again. You not only slow down your program, but also FS. It's even worse if your program is run on a Networked PC under WideFS, as not only all that has to happen, but WideClient also has to send a Network block over for each call. The Read and Write calls merely add data to a block in your memory, forming it all up ready to send. Takes no time at all. It's the same as this message -- how efficient would it be if I put each sentence in a difference response to you, or worse, each word? Regards, Pete
  10. Not just the "flight sim" folder, but the Modules folder inside that -- the same place that you put FSUIPC into (which is also needed in any case). You can put the Client stuff where you like. I normally plonk it into the same folder as the Application I want to load. so, for instance, if it is FSMeteo and I have all the FSMeteo stuff in a folder "C:\FSMeteo", then I put WideClient in there, then edit the INI file to make WideClient load and close FSMeteo. THEN I drag a shortcut to WideClient.exe onto the desktop, name it "FSMeteo" and change its Icon to the FSMeteo Icon. that way, it looks like I'm starting FSMeteo, but in fact it runs Wideclient which in turn starts FSMeteo. With the parameters in the INI file you can even make FSMeteo load only when FS and the Server are ready. No! The "FS utility" is the program you are wanting to run on the Client PC. FSUIPC is an FS module, not a separate program, and can only be loaded and run by FS. Pete
  11. Not just the "flight sim" folder, but the Modules folder inside that -- the same place that you put FSUIPC into (which is also needed in any case). You can put the Client stuff where you like. I normally plonk it into the same folder as the Application I want to load. so, for instance, if it is FSMeteo and I have all the FSMeteo stuff in a folder "C:\FSMeteo", then I put WideClient in there, then edit the INI file to make WideClient load and close FSMeteo. THEN I drag a shortcut to WideClient.exe onto the desktop, name it "FSMeteo" and change its Icon to the FSMeteo Icon. that way, it looks like I'm starting FSMeteo, but in fact it runs Wideclient which in turn starts FSMeteo. With the parameters in the INI file you can even make FSMeteo load only when FS and the Server are ready. No! The "FS utility" is the program you are wanting to run on the Client PC. FSUIPC is an FS module, not a separate program, and can only be loaded and run by FS. Pete
  12. You can now try the http://www.schiratti.com/dowson page -- Enrico has kindly provided an alternative method for donations via PayPal on his website. this just became operable today. Maybe you might find it simpler? Regards, Pete
  13. You can now try the http://www.schiratti.com/dowson page -- Enrico has kindly provided an alternative method for donations via PayPal on his website. this just became operable today. Maybe you might find it simpler? Regards, Pete
  14. I'd love to find a way to do that. In FS98 I was able to separate off the ADVenture sounds (Adventures then being used for ATC), which is why I wrote ESOUND.DLL, but I could never figure out how to do than in FS2000 or FS2002. I supsect things are even more complex with the FS2002 ATC itself. This is one of the reasons why I use Radar Contact Version 3, running on a separate PC via WideFS. Regards, Pete
  15. I'd love to find a way to do that. In FS98 I was able to separate off the ADVenture sounds (Adventures then being used for ATC), which is why I wrote ESOUND.DLL, but I could never figure out how to do than in FS2000 or FS2002. I supsect things are even more complex with the FS2002 ATC itself. This is one of the reasons why I use Radar Contact Version 3, running on a separate PC via WideFS. Regards, Pete
  16. No. They are highly supported by base code and DLLs in FS itself. Really they are a "template" for the gauge, whether it is written in C or XML -- obviously more so in XML which is an interpreted template in any case. Pete
  17. No. They are highly supported by base code and DLLs in FS itself. Really they are a "template" for the gauge, whether it is written in C or XML -- obviously more so in XML which is an interpreted template in any case. Pete
  18. Yes, it is odd the way it worked in FS98. It was the folks who had got FS98 weather programs working who told me these things. I've never used them myself. I think MS intended to add more types but didn't. Ah, I didn't notice that. Forget what I said then, except it is a good idea to clear the storm layer since it may have been set from before. Sorry, I don't know VB -- I suspect it would get quite complicated in VB. It is defined in terms of C of course. Maybe someone else could help (thought the only two persons I know who have used the AWI are Marc Philibert, in FSMeteo, and Luciano Napolitano, in WidevieW). Pete
  19. Yes, it is odd the way it worked in FS98. It was the folks who had got FS98 weather programs working who told me these things. I've never used them myself. I think MS intended to add more types but didn't. Ah, I didn't notice that. Forget what I said then, except it is a good idea to clear the storm layer since it may have been set from before. Sorry, I don't know VB -- I suspect it would get quite complicated in VB. It is defined in terms of C of course. Maybe someone else could help (thought the only two persons I know who have used the AWI are Marc Philibert, in FSMeteo, and Luciano Napolitano, in WidevieW). Pete
  20. The data you are setting is not entirely valid. Going from the LOG (I do not know or use VB): First setting: 583869 WRITE0 0EA4, 2 bytes: 64 0D 583869 WRITE0 0EA2, 2 bytes: 9D 12 583869 WRITE0 0EA6, 2 bytes: FF FF 583869 WRITE0 0EA8, 2 bytes: 39 05 583869 WRITE0 0EFE, 2 bytes: 04 00 583869 WRITE0 0F1E, 2 bytes: 49 09 583869 FS98 Cloud2: type=4, from 7798ft to 10764ft (+/- 1965ft), cover 8, turb 0, ice 0 You are setting Upper Cloud first. That won't work. The first cloud is Thunderstorm or Lower cloud. You can't have a second or third layer before you have a first layer. Don't ask me why, it is the way FS98 worked, and the interface you are using (unlike the Advanced Weather Interface) is based on FS98 practice. Worse, you are trying to set cloud type 4. which is not defined. You see the list in the SDK document? 583869 WRITE0 0F1C, 2 bytes: 40 0B Writing to 0F1C is the same as writing to 0E9A -- as clearly documented. You should really be only writing to 0F1C upwards in any case. The 0E9A area is for reading. But FSUIPC enforces this rule in any case. Writing to both as you are only wastes time. 584069 WRITE0 0EA4, 2 bytes: F4 05 584069 WRITE0 0EA2, 2 bytes: 6E 15 584069 WRITE0 0EA6, 2 bytes: FF 9F 584069 WRITE0 0EA8, 2 bytes: E8 0B 584069 WRITE0 0EFE, 2 bytes: 07 00 584340 FS98 Cloud1: type=7, from 5000ft to 17998ft (+/- 10000ft), cover 5, turb 0, ice 0 Again, there's no type 7, and you cannot have a variation in cloud base of 10000 feet when the cloudbase is only 5000 feet in the first place. Variations are usually small, like 50-300 feet. Possibly, apart from the invalid cloud type FS doesn't like such a big variation. From the FSInterrogate pictures you attached, I also noticed that the Storm layer coverage is set to 1 but with no cloud altitudes set nor a type. This seems to be left over from a previous setting (?), but you should take care to clear the storm data before setting the lower cloud. So the order is: 1. clear storm layer (or, of course, set it if required) 2. set lower layer (taking care to ensure VALID numbers) 3. if more than one layer, set upper layer (with VALID numbers) and you do all this in the 0F1C- area (same applies to all the other weather data). This is the FS98 way, so you are limited to two cloud layers, plus the optional stom lowest layer. FS2000 ad FS2002 can have many more layers, but to use them you'd have to switch to the AWI. Regards, Pete
  21. The data you are setting is not entirely valid. Going from the LOG (I do not know or use VB): First setting: 583869 WRITE0 0EA4, 2 bytes: 64 0D 583869 WRITE0 0EA2, 2 bytes: 9D 12 583869 WRITE0 0EA6, 2 bytes: FF FF 583869 WRITE0 0EA8, 2 bytes: 39 05 583869 WRITE0 0EFE, 2 bytes: 04 00 583869 WRITE0 0F1E, 2 bytes: 49 09 583869 FS98 Cloud2: type=4, from 7798ft to 10764ft (+/- 1965ft), cover 8, turb 0, ice 0 You are setting Upper Cloud first. That won't work. The first cloud is Thunderstorm or Lower cloud. You can't have a second or third layer before you have a first layer. Don't ask me why, it is the way FS98 worked, and the interface you are using (unlike the Advanced Weather Interface) is based on FS98 practice. Worse, you are trying to set cloud type 4. which is not defined. You see the list in the SDK document? 583869 WRITE0 0F1C, 2 bytes: 40 0B Writing to 0F1C is the same as writing to 0E9A -- as clearly documented. You should really be only writing to 0F1C upwards in any case. The 0E9A area is for reading. But FSUIPC enforces this rule in any case. Writing to both as you are only wastes time. 584069 WRITE0 0EA4, 2 bytes: F4 05 584069 WRITE0 0EA2, 2 bytes: 6E 15 584069 WRITE0 0EA6, 2 bytes: FF 9F 584069 WRITE0 0EA8, 2 bytes: E8 0B 584069 WRITE0 0EFE, 2 bytes: 07 00 584340 FS98 Cloud1: type=7, from 5000ft to 17998ft (+/- 10000ft), cover 5, turb 0, ice 0 Again, there's no type 7, and you cannot have a variation in cloud base of 10000 feet when the cloudbase is only 5000 feet in the first place. Variations are usually small, like 50-300 feet. Possibly, apart from the invalid cloud type FS doesn't like such a big variation. From the FSInterrogate pictures you attached, I also noticed that the Storm layer coverage is set to 1 but with no cloud altitudes set nor a type. This seems to be left over from a previous setting (?), but you should take care to clear the storm data before setting the lower cloud. So the order is: 1. clear storm layer (or, of course, set it if required) 2. set lower layer (taking care to ensure VALID numbers) 3. if more than one layer, set upper layer (with VALID numbers) and you do all this in the 0F1C- area (same applies to all the other weather data). This is the FS98 way, so you are limited to two cloud layers, plus the optional stom lowest layer. FS2000 ad FS2002 can have many more layers, but to use them you'd have to switch to the AWI. Regards, Pete
  22. It sounds plausible, but if so it seems to be rather a serious error in the design of that part of PM. What does Enrico say? He will surely know that there are folks with individual throttle controls. Please keep me posted. Pete
  23. It sounds plausible, but if so it seems to be rather a serious error in the design of that part of PM. What does Enrico say? He will surely know that there are folks with individual throttle controls. Please keep me posted. Pete
  24. Yes, of course you do! The Server is the one "serving" the clients. No client knows about any other clients! Furthermore, the shutdown facility is done merely by setting an offset in FSUIPC which is read by all clients. If FS isn't running, then neither can FSUIPC or WideServer, so there is nothing going on between any of them! This is why the shutdonw facility in WideServer is delayed by a number of seconds, to ensure all Clients read the message. Pete
  25. Yes, of course you do! The Server is the one "serving" the clients. No client knows about any other clients! Furthermore, the shutdown facility is done merely by setting an offset in FSUIPC which is read by all clients. If FS isn't running, then neither can FSUIPC or WideServer, so there is nothing going on between any of them! This is why the shutdonw facility in WideServer is delayed by a number of seconds, to ensure all Clients read the message. 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.