Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. That's fine. I run the Glass Cockpit on one Client and the MCP and FMS on another. Where are you running the MCP? That is needed, as it is the MCP which includes all the processing for the PM commands. If the MCP isn't running then none of those PM controls will work as far as I know. If you are not using an MCP I think your only recourse is to use the KeySend facilities in FSUIPC, and program the KeySends to send keystrokes to the ND in the Client. Really Project Magenta support is the better place to sort this out, as it is a PM matter. All I do is provide the tools to program the commands it uses. What it then does is up to Enrico Schiratti. Pete
  2. Sounds very much like you've not installed FSUIPC. Pretty much all of my modules need FSUIPC when used in FS2002. Sorry it isn't documented -- this dependency wasn't actually discovered till long after release, because most people use FSUIPC in any case. Regards, Pete
  3. Sounds very much like you've not installed FSUIPC. Pretty much all of my modules need FSUIPC when used in FS2002. Sorry it isn't documented -- this dependency wasn't actually discovered till long after release, because most people use FSUIPC in any case. Regards, Pete
  4. Yes. Use the Keys page in FSUIPC options. All of the available Project Magenta controls are listed in the drop-down, for assignment to joystick buttons as you like. Pete
  5. Yes. Use the Keys page in FSUIPC options. All of the available Project Magenta controls are listed in the drop-down, for assignment to joystick buttons as you like. Pete
  6. No. FSLook is even more limited than FSInterrogate. It isn't looking at offsets, it is reading FS Gauge TOKEN variables, those with names documented for regular FS gauge use in MS PAnels SDKs. If panel programmers choose to do their own thing, then only they can tell you how to get their variables. They are not "public" FS values, they are private to their panel modules. There are no such things as "offsets" (in the FSUIPC sense) for them. The "offsets" in FSUIPC are positions in FSUIPC's mapping of FS variables. It has no way of getting into private panel coding. Regards, Pete
  7. No. FSLook is even more limited than FSInterrogate. It isn't looking at offsets, it is reading FS Gauge TOKEN variables, those with names documented for regular FS gauge use in MS PAnels SDKs. If panel programmers choose to do their own thing, then only they can tell you how to get their variables. They are not "public" FS values, they are private to their panel modules. There are no such things as "offsets" (in the FSUIPC sense) for them. The "offsets" in FSUIPC are positions in FSUIPC's mapping of FS variables. It has no way of getting into private panel coding. Regards, Pete
  8. I don't know -- I suppose it must be in the registry. I just used to reselect the default in the Control Panel multimedia or sound applet (not sure which, probably mm). Regards, Pete
  9. I don't know -- I suppose it must be in the registry. I just used to reselect the default in the Control Panel multimedia or sound applet (not sure which, probably mm). Regards, Pete
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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
×
×
  • 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.