Pete Dowson

No, there is no difference in this regard between a registered copy of FSUIPC 3 running on FS2002 and the most recent version of FSUIPC 2. It sounds like you have something else going on there. The only difference between the old versions of FSMeteo and ActiveSky and the new ones is that they used the older methods of Weather control -- but differently. Active Sky used the old FS98 methods, whilst FSmeteo used the AWI. Both are still supported identically in FSUIPC 3. In FS2004 (only) the NWI is supported in addition, but this is only used in very recent releases. Regards, Pete

Register it at SimMarket, then enable it in the Technical page. It is a user facility, and a main attractions of FSUIPC, to persuade folks to subscribe. :D Regards, Pete

Sorry, no. You need PSS to advise. There is no difference in FSUIPC, though certainly if you have not registered FSUIPC I may expect there to be problems with un-accredited add-ons like the Vulcan. Though the windscreen wiper is certainly not a function of FS and nothing FSUIPC will be involved in. I have absolutely no idea what the Vulcan can be doing, and most certainly nothing to generate 'black screen' crashes, which sounds like a graphics problem. Sorry. Pete

Same as before, if you have registered FSUIPC. Go to the Technical page, it is there, same as in previous versions and as documented. Regards, Pete

This was the original 100% aim of Esound, and in fact all it did originally, when I first wrote it for FS98 so may years ago. It worked with the Adventure sounds then, which is all you had to do ATC. I struggled desparately to get it working in FS2000 after FS has completely changed the way it handled sound, but I never found a way to do it. This is why I dropped my interest in Esound and developed in no further. I certainly wouldn't consider it for FSUIPC when Esound already has all the right code in it to handle multiple sound cards and so on. I can do this already, running Radar Contact on a second PC via WideFS. The ATC from Radar Contact is far more professional than the inbuilt FS ATC is, anyway. Whilst Esound does have facilities for EPIC support, it was not written for EPIC and does not require EPIC. The "E" in the name stands for "Extra", not "EPIC"! :) If someone can find a way of intercepting the ATC sounds, by all means I will implement this in Esound, and my interest in that program will be seriously revived, as it could meet it's original purpose again. Whilst doing this perhaps the same genius could also please tell me how to intercept the ATC displays, so I could divert those too -- to an alternative PC, or even to an application program for processing. Regards, Pete

How does VB allow you to define a full 32-bit word in hex, then? What if you used &H00008000? The value being used in the IPC interface is a 32-bit value, after all. In C/C++ the upper zeroes are rather implied by the notation, as in 0X8000. Maybe just VB &X08000 should work? That is certainly one way, though I think the way to tell the VB compiler that your original is unsigned is to add an & at the end, thus: &HC000&. At least that is what some VB programmers tell me (JD being the first -- thanks John!). Regards, Pete

No, any number of accredited programs can access FSUIPC. Most will hopefully do this automatically -- i.e. they will provide the key without you even needing to know about it. Pete

Good. I'll release Esound 2.572 next week, then, when I also release FSUIPC 3.11. (The current one is 3.10 by the way). How odd. It does here, at least from the USB version of EPIC. Are you still using the ISA EPIC card? Under Windows 98? Regards, Pete

If you read the first few sections of the FSUIPC User documentation you will see a lot of information about access keys and registration. It also lists all the facilities you get if you register your own copy of FSUIPC. As well as all that you'd never need to worry again about getting keys for other programs, as they aren't needed for a paid-up user. I don't like to sound like a salesman here, it isn't the reason for the Forum, but sometimes I really do need to point out that you are going through a lot of hassle, and even getting a lot of support from me, but all to save spending 20 Euros! :lol: Regards, Pete

I didn't mention EPICIO. I don't think that has a logging function -- but you could check with R&R about that. I mentioned logging in EPICINFO. That's all described in the EPICINFO documentation. But if you aren't using EPICINFO it isn't any use to you. Regards, Pete

He might just be away. Folks do take holidays. He was provided with keys for all of his programs back in August. For the freeware ones I could publish them, but I'd really want his permission. I don't think it would be proper without. Regards, Pete

I have no idea, I don't use it, but the facilities for capping the top speeds in FSUIPC were originally put into in way back in FS2000 days because occasionally Squawkbox would insert ridiculously high wind speeds (like hundreds or thousands of knots!). So I assume so. I think folks who prefer FSMeteo or other weather sources switch the SB weather off. Maybe it's off by default now? I don't know, you'll need to check. The idea of SB providing the weather is to keep it the same as on the Controller's PC. Regards, Pete

Still think it could be worked out from the FSUIPC IPC write logging. Regards, Pete

Not sure how the weather is related to the throttle position, and certainly nothing in either FSUIPC or ActiveSky will be touching the throttle. Where do you read "00" for throttle setting? Do you mean the throttle levers are being pulled back to idle? Or is it the Air Speed you are reading, rather than the throttle? If so, then what you are encountering is icing. Make sure that pitot heat is enabled and probably anti-ice also --- FS2004 seems to be prone to bunging up the pitot tube if you get anywhere near any cloud with serious icing levels. As for ActiveSky stopping updating the weather, that sounds like a problem with some of the earlier versions. Make sure you are using the latest versions of both FSUIPC (3.10) and ActiveSky (1.91 I think). Check also with Damian's forum, "Project: ActiveSky" here on Simflight. Regards, Pete

It should do. It always has! The main problem is in distinguishing which one is which, as they all have the same name, so as you scroll down the list nothing seems to change. I did ask Ralph if he could number them but he never managed to do that. Regards, Pete

If you already have a working Network, you simply put WideServer.DLL and INI into FS's Modules folder, install the WideClient.EXE and its INI file on any client PC, add a parameter to the Client INI to tell it the name of the Server PC, and run it. When FS is running with WideServer installed, any WideClient which links to it presents an FSUIPC interface to any suitable applications on the client PCs. So, if you do have other FSUIPC applications currently running on the FS PC, you can move them off. Typical client applications include FSMeteo, Radar Contact, Squawkbox, ActiveSky, TrafficLook, FSRealTime, NAV3, Flight Deck Companion, and of course Project Magenta. Do not confuse WideFS with WidevieW. The latter is by Luciano Napolitano and is for linking multiple installations of FS. I don't think there's an FS2004 version ready yet. Regards, Pete

Sorry, I know nothing about multiplayer. Maybe FS cannot support real weather and multiplayer at the same time because they can't get the weather to match? Sorry, I really don't know. Maybe someone else can jump in about this. Of course if you are using Squawkbox or similar and that is setting any aspect of the weather at all, then FS2004 automatically reverts to user-defined. The same applies to using FSUIPC with the option set for it to affect FS weather. Oh, and please be sure you are using the latest version of FSUIPC in any case (3.10). Regards, Pete

Oh dear. Sorry, where on Earth did I say that? Which bit is too technical? Please just get the key and enter the details. All other discussion is futile really. If it doesn't work then, that's the time to get technical. All the preceding messages have been rather off-base simply because I was under the impression you'd already tried registering it and weren't getting anywhere! :( Actually, it's now getting to the point where really I think you might even consider, instead, simply registering FSUIPC and be done with it. I think you have got your money's worth of time out of me by now! :D Regards, Pete

Well, before I saw your log I would have assumed it was because he was using the external application interface to FSUIPC. But now I believe that he just doesn't realise that I'd extended the manual program registration system so it will cope with (correctly interfaced) Gauges and DLLs as well. That wasn't part of the original plans (before version 3.00 release), but it was long before Eric's applications for the Keys. Regards, Pete

No, F16.gau. Yes. Erbut I thought you already had the key? You asked him already! I don't have all that private mail anymore, but I could have sworn you said you tried it and couldn't make it work. I thought that was the whole point of me looking at the logs! Pete

I am sending you a Beta version of FSUIPC to try. Use the syntax as you have it (CRin place of CP ...). It should work okay. Let me know. Regards, Pete

Yes, thanks. But I did actually reply in the other one. Didn't you see? And the Log file you posted there was a better one -- it shows the data required. You just need to register the program F16.gau with the Key Eric gave you. Regards, Pete

It's "FS9.CFG" and it is in the documents and settings applications data, under Microsoft and flight simulator. Similarly your saved flights and so on with be in your document folder in a new sub-folder. I recommend you check out the FAQ in the FS2004 Forum here. Why not? The Fs2004 joystick assignments are better than the FS2002 ones -- more controls are now assignable. What is worng with it? Regards, Pete

If the sound is played then it isn't likely to be Esound which is crashing -- it has long since finished its part in this and relinquished control. I really cannot spend any more time on this. I think you really do need to investigate the sound files you are using. Regards, Pete

It is the method originally designed by Adam Szofran in FS5IPC back in FS95 days. It has been kept all the way through for compatibility. It uses a memory mapped file but it isn't polled, the details are passed by a message. FSUIPC not keep track of applications, the file belongs to the application and if only read/written by FSUIPC. There don't think there were any named pipe facilities available on Windows 95 (not that it would be very efficient for a many-to-one relationship), and sockets were also primitive and needing User installation, as far as I can recollect. Memory mapped file methods of transferring data betwen processes in efficient enough. In fact it is basically the same method underlying the way some of the debugging aids work, although there they are wrapped up in high level functions like "ReadProcessMemory". You can find all the details in the FSUIPC SDK on http://www.schiratti.com/dowson. Regards, Pete