Pete Dowson

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! Socket numbers don't matter providing they don't clash. The defaults shouldn't clash in any case. More important is your operating system and WideFS settings. You have to change both WideClient and WideServer INI files to tell it to use SPX, and you will probably need to provide the Server Node information. This is explained in the WideFS document. I've never had much success with mixing WinNT/2K/XP systems with Win95/98/Me systems when using IPX/SPX, though if WidevieW is happy that shouldn't be the problem. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! No, you only run the program on the machine in which you want it to run. I don't know FsGarmin530 but if it needs two parts running -- one on the Server and the other on the Client, then they will undoubtedly have different names. Maybe you need a different module which running remotely? I think this was the case with other programs from the same stable, like FlightMax. It certainly seems that the module is trying to find the actual physical file FSUIPC.DLL rather than simply trusting the interface. Alternatively maybe it's a question of parameters in its own INI or CFG file? Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! I cannot make that happen here -- but enable graduation, with the lower altitide set to 0 so it joins the surface layer. Maybe what you are really seeing is the added FS thin cloud layer at the top of the visibility layer, but as I say I can't see that here. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! Neither of those take any parameter. Just program it on the press. But very few of the PM facilities work unless you have the PM MCP running. It is the MCP which reads these and controls things. I think Enrico is considering changing this. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! You can send the keystrokes themselves (Shift P, then 1 or 2) or the control then the Keystroke -- controls can be send by offset 3110, keystrokes by 3200. Or program buttons in FSUIPC's Buttons page, or you can try offset 31F4 for me. This is an area I've not been able to test yet. Others have also found this. I think Teamspeak is using so direct keyboard access, or maybe the Async state, which I cannot influence. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! The altitude there is NOT floating poiint, but fixed point. The integer in metres is 32-bits (4 bytes) at 0574, the fraction is in 0570. Best to read it into an array of two integers. Read metres in the 2nd and the fraction (UNsigned) in 1/(65536*65536) ths in the first. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! Thanks! Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! Thanks! I'll add the details to the GPSout readme! Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! FSUIPC can only expose those things which exist and which I've either found for myself or which others have found and told me about. FSUIPC does not actively simulate any systems -- that is up to FS. The things you mention seem to either be derived from other things (e.g. warnings derived from monitoring existing values), or possibly refer to systems not actually simulated in FS at present in any case. If you think these things exist (for instance, check the Panels SDK from MS and see if you can make a Gauge with them) then I should be able to find them and expose them. but I need that confirmation and help to find them. I cannot spend many thousands of hours looking for things which I don't fully understand and which may not even exist. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! If FS freezes then certainly FSUIPC will too, so your program will not be able to connect. No t if FS is freezing. Sounds like a problem with video or sound drivers or similar. It *could* be your program writing something bad to FS, but if so you need to contact the author. I'm afraid i don't know "OSP" -- in fact I've never heard of it. Sorry. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! It will only work if, by sheer liuck, the byte after this is zero. No one will guarantee that, and it may depend on many other things. The correct length for a 1 byte value is 1. Declare it as a byte or character or whatever the language calls something which is 8 bits long. The length in bytes is provided in the table in the Programmer's Guide. It is in the second column, called "size". That it the number of bytes. That is exacly what it is for, so you know how big the value is! Refer to the table I provide! That is EXACTLY it!! You can read that 1 byte into an Integer, but since 1 byte is shorter than an Integer (the latter is usually 32 bits -- or 4 bytes), there may be rubbish in the other bytes still. All you need to do is set the Integer to zero (0), then read the one byte into it. Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! "double" floats are the standard floating point format on Intel processors and are, as far as I know, universally supported. They are most certainly not 64-bit integers which are hardly supported by anything. You should be able to just read the 8 bytes directly into a standard floating point varaible, whatever they are called in Visual Basic! In the reply you got from Mike this seems to provide the answer: "Use a Currency variable for Floating 64". Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! Maybe. but in FS95, 98, 2000 and (as far as I know) 2002 I am fairly sure the supported range was 200.0 to 1699.9 (in increments of 0.1). I submitted a bug report to MS for this years ago. Maybe FS2004 has partly corrected this error ... ... however, evidently not quite! FSUIPC doesn't actually perform any checking on the values at all. What actually happens when you try to write 1700 + ? All FSUIPC is doing is using the FS controls: ADF_HIGHRANGE_SET and ADF_LOWRANGE_SET Maybe you can experiment with these in the FSUIPC Keys or Buttons pages? For ADF2 those don't exist, so FSUIPC uses: ADF2_COMPLETE_SET Maybe the equivalent ADF1 version of this works better? Please try things out and let me know. If the newer control works better I can make the change (for FS2004 only) in the next version of FSUIPC. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! Are you sure you don't have more than one copy of AdvDisplay installed, maybe a renamed one? Deactivate Advdisplay (in the Modules menu -- so that the tick next to its entry isn't shown). Is that different? When not activated AdvDisplay does absolutely nothing -- no Windows, no message interception, nothing. It also won't dock itself automatically in any case, you have to do that. Reactivate it and right click on its window (which will now be titled) for the options. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! It sounds like your throttle control isn't reducing the thrust value to zero then. Re-calibrate making sure that the throttle has a good "null zone" at idle so that you always achieve zero. Reversers will not engage otherwise. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! I don't know how to get that or even if it is possible. All the GPS stuff I found is in the area mapped to offsets 6000 ff. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! It sounds, then, that they are doing something like testing the "async" state of they key, to see if it is still pressed, rather than simply waiting for the KEY_UP message. I'm afraid I don't know how to deal with that. I think it has to be down at a deeper level in Windows, to "fool" the Keyboard driver. Ugh! Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! I'm not sure what you mean by "STRG" but WideClient does have a facility to send keypresses to FS -- please check the WideFS.DOC. You have to enable it in the WideClient.ini file. Wideclient will only send keypresses that it receives as a normal Windows program, so you would have to have the window visible and with keyboard focus. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! This is NOT "squawkbox" attempting to connect and failing, but some other DLL or GAUge which you have installed, which is trying to access FSUIPC using the EXTERNAL program interface. This is very bad of it. I'm afraid there is no solution other than either finding it and removing it, or registering FSUIPC as a User. I'm afraid there is no easy way to identify it either, as it looks to FSUIPC like FS itself, because of the wrong behaviour. Even if you register FSUIPC, to allow this one to work, it can cause conflicts with other modules or gauges -- the warnings to programmers about this have existed for 3 or more years, so this is likely to be something quite old. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! Well, it shouldn't be such a proglem really -- it sounds like you should calibrate the 4 throttles again, taking care to get the end positions set more carefully to give similar values when they are at similar positions. Also, you will notice in real aircraft, especially BAe 146's, that the four throttles levers are often not truly aligned -- you adjusct them using the instruments or the auto-throttle facilities. However, that said, in the current PFC.DLL there is a control for Throttle Sync which you can assign to a spare button, of you have one. There are also options to equalise Throttles 1 and 2 when close, but at present this does not work for 4 engines. If you really find it a problem I can consider adding that, though it really should not be necessary. Regards, Pete

Oh dear, that's odd. :( I'm trying to catch up with emails and things at present, but I'll take a look at that on Monday, latest. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! If you register your copy of FSUIPC you can program the button events generated by your EPIC program in FSUIPC's buttons page. There you can convert them to keystrokes. There are actually ATC 0 to 9 FS controls too which you could try assigning more directly, but I don't know if those work. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! FSUIPC-interfacing programs need WideFS to work across a Network. FSUIPC itself contains no Network code. Regards, Pete

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now! No, sorry. I don't even use Squawkbox. You need to talk to the author, Jose Oliveira. I think he is working on a version for FS2004 -- the MP protocol is different. Regards, Pete

Go to http://www.simmarket.com. Enter your account and read your key. At least I have been told it is that easy. I don't have any such details here. Regards, Pete