Pete Dowson

Hmm. The term "latest version" is meaningless. Every version has a version number. I've had folks quiting "latest version" for a version six months or more out of date -- it's the 'latest' one they have seen! :roll: This really isn't likely to be an FSUIPC problem. Either something which uses FSUIPC is faulty and crashing, or, if this is at initial load, it is either a faulty FS installation or there is a hardware problem or some incompatibility with something else you have installed. The probable reason there's a difference between FSUIPC installed or not is either some add-on using ut, or, if you have none, the slightly different arrangement of FS memory when it is present. Regards, Pete

Okay. So, if that provides enough information to at least make a start on an IPC interface compatible with the one for FS. You'll need to go through each offset in the Programmer's Guide, in the FSUIPC SDK, to see if you can provide a compatible value in X-Plane. Naturally, all the "memory" is provided by the interface module, not X-Plane. Even in FS, although the memory area mapped was, in FS98 and before, part of FS proper, since then less and less is, and even the little that is currently mapped into FS memory isn't where it says it is! BTW you may want to contact the Project Magenta folks. They did make a start into dealing with X-Plane. This was last year. But I think, at that time, they found that the facilities for getting at data and exercising control in X-Plane were insufficient to support full cockpit simulation, so it was not pursued. Things may have changed with recent X-Plane releases. Regards, Pete

Not that I know of. Is there an SDK for X-plane? If you can get inside X-plane in the same way as you can with FS, and if it has compatible information and control methods, then I don't see why someone couldn't do this. There is no problem reproducing the interface, that is not restricted, it is freely published, so if someone wants to produce an X-Plane version of it they are at complete liberty to do so. But it is going to need knowledge of X-Plane internals, not FS. Regards, Pete

Ah, so he doesn't want a reverse prop pitch range on the Prop axis? As documented, FSUIPC defaults to selecting the Mixture axis as reverser. So if he has used FS Assignments to define his Mixture axis as a Spoiler Axis, he can now easily use FS assignments to assign his Prop Axis as the Mixture Axis. Then in FSUIPC simply calibrate the reverser. That is exactly what the Reverser axis facility in FSUIPC is designed to do. He may need to check the "reverse the reverser axis" option if it works back to front, that's all. As documented, it is clearly possible to assign any axis as the reverser axis. The Advanced User's guide even gives a list of the axis numbers for this. But as he is not using a Mixture axis it is far easier to use the default FSUIPC assignment of the mixture axis. My problem is that I don't understand why he doesn't understand. This facility has been included in FSUIPC now for three years and it seems to be generally well understood. Regards, Pete

What is it you are doing, or don't understand? I cannot explain it better here than in the documentation, and there's no point in me reproducing the docs here, so you need to be more specific. Regards, Pete

The separate prop axes work for the 4 separate prop axis controls. EITHER you need to reassign your prop axis to Prop 1 (assuming you only ever want to fly singles), or just use the facility in FSUIPC (in the main single prop axis page) to map the single axis to the 4 separate ones. ("Map to 4 props"). Crack? Isn't that a drug? The problems in all this are due to FS's design of the controls, not FSUIPC. There are no reverse parts on the main default controls, only on the separate ones for each engine. You can do all you want in FS assignments -- try FS's help instead of FSUIPC. If you want to use FSUIPC instead, that's fine, but you do need to look at the user guide, where I do try to explain it. I don't see how I can explain it better here are many years of it being embellished in the user guide. Regards, Pete

Sorry, I have no idea. This is really a question for the FSMetar author I think. Is it connecting to FS okay? Check the FSUIPC Log file (in the FS Modules folder). By the way, please always state version numbers when asking questions. Saying "latest FSUIPC" is rather meaningless I'm afraid. That should mean 3.30, but I've had folks refer to their 6 month old copy as "latest" simply because they had not actually seen a later one at the time. Regards, Pete

Okay, I'll see to that for the next update. Actually, that code is really redundant. It is in the C version so most folks have copied it. All it does is ensure that a Write error is logged in FSUIPC -- the data it tries to write (to a read-only location) was intended to give the library and language versions, for better diagnosis of errors from logs sent to me. But unfortunately I never enforced either the version number nor language ID system I had devised, so it is worthless. I see the line VersionGet = FSUIPC_Get(t_FSUIPC_Lib_Version, FSUIPC_Lib_Version) a little later. That is wrong -- it seems to be reading something which it should have (or could have) actually written. It is a nonsense line -- I'd remove that AND the redundant block above if I were you. I'll do that here. Please use FSUIPC's IPC read/write logging to check it -- you can see then exactly what it is trying to do and maybe why it is failing. Not to me, I'm afraid. I've no idea what it is doing. Please chack things from the FSUIPC end to see if you can figure it out. Use the logging. That is VERY inefficient. Do all the Reads/Writes you need, then one Process call. Each process call can pass a huge stack of read/write requests in one transaction. All the read/write calls do is build up the request in your own memory -- in other words all that is completely defined in the code you have. The ONLY connection to FSUIPC is the "SendMessageTimeout" in the Process call. Do only one of those per cycle. I suspect most of the trouble with VB.NET is that is is "managed" code (isn't it?), so you've probably got little control over what really happens. I've asked Bob if he can look at all this, but I don't know when he'll be able to respond. Regards, Pete

No need to be sorry. I'm not a cockpit builder myself, that is the reason I don't know the actual suppliers you may need. My equipment is a mixture of ready-built stuff, mostly from PFC (http://www.flypfc.com), but also GoFlight, and Aerosoft (Oz). For software I use Project Magenta (http://www.projectmagenta.com). I just did a quick search and came up with these sites which may be of use to you: http://www.aircraftsimulators.com/ http://www.simkits.com/ http://www.therealcockpit.com/ http://www.737ng.net/ http://www.cpflight.com/ http://www.commandfliteware.com/ http://www.hagstromelectronics.com/ http://www.flightdecksolutions.com/ http://www.simhardware.co.nz/ There are probably loads of others. Pete

Check the cockpit forum. I don't supply or support hardware. A search on the internet should find quite a few suppliers too. Regards, Pete

Well, you can do the Throttle and Spoiler assignments in FS, you don't need FSUIPC. The reverser can be done easily enough in FSUIPC. Er, that is only true if you are assigning the throttle as Throttle 1. Assign it as Throttle only -- the generic all-engine throttle supported in FS does not include a reverse part of the range. There is no reverse axis in FS as such. The one in FS cannot provide forward thrust, and will only engage reverse when the main throttle(s) are at idle. Regards, Pete

I'll try to contact him and see if he will come here. Pete

Hi Claudio, The operation was fine, and the eye sees well --- EXCEPT that the eyedrops (a steroid to speed recovery), which were different to the ones they gave me for the other eye, have caused an adverse reaction. Seems I am allergic to those. For three days the newly operated eye has been streaming continuously with tears and is puffy. Today I got a revised prescription and things are starting to improve. I am catching up with emails etc once per day but else resting my eyes. Hopefully things will improve over the coming days. Thanks & Best Regards, Pete

Er ...there's some misunderstanding here. ".Net" is not a language, it is a suite of language compilers and development aids sold by Microsoft. I myself use Microsoft .Net 2003, but I only use the C and ASM parts of it. There are also C++, C#, VB, Java and maybe other parts I don't have or hanen't looked at! Ah, you mean VB.Net! Thank you. [Duh! Only now do I see you said "VB.Net" in the subject -- problem is the subject isn't repeated in each message of the thread. Sorry] I am assured that it was working and tested before submission. I will ask around, but perhaps if you know what is wrong you could tell me? Or at least point me in the right direction. To start with, which file inside the ZIP contains the errors? Regards, Pete

Most add-on panels don't use any control numbers whatsoever, they are just sensitive to mouse clicks in certain gauge zones. Really, that's all the Microsoft gauges SDK allows the programmers to do. They can process keypresses and FS-type controls as well, but it is extra programming which many don't do. Only if they process FS controls -- all the ones that are allocated are already listed in FSUIPC (and in the FS Controls documents I publish). I suppose they might add their own extra ones, but I've not heard of anyone doing this. Regards, Pete

[quote="Oleg Today i lost my data files FS2004 (FSUIPC reg. key too) I pay to Simmarket for the FSUIPC please write me Peter !!!! my e-mail You need to re-register, but using the same original details. If you cannot find your Key (you should have kept a safe copy) you will be able to get it by going to your account at SimMarket. Regards, Pete

You just need to go into FSUIPC options and re-enter the exact same registration details as before -- your original email, not your new one. Best refer to the FSUIPC.KEY file (which is plain text) if you have lost your original email. Regards, Pete

Great! Hmmm... I seem to have 6 processes called SVCHOST running. No idea what they do. Yes. Thank you. Maybe I will try closing my similar processes down and see what happens! Regards, Pete

TrafficLook only reports what FSUIPC gives it. The range is controlled by FSUIPC -- look in the Technical options. If your FSUIPC is not user registered then you will have to change those parameters in the INI file -- they are listed in the Advanced User's Guide. 40nm is default because that's the normal TCAS range in real aircraft. AI's maximum range is about 80 nm. Regards, Pete

Please use the logging tools provided in FSUIPC to help you resolve such problems. You can log all IPC reads and writes and see exactly what you are doing. Which ZIP and which file, please? Regards, Pete

Don't bother saving the LOG file, that is recreated every time. If you are reformatting your disk and/or reinstalling Windows, which seems likely, you will need to re-enter the registration data even if you do keep the KEY file -- in this case the KEY file does give you a handy source for cutting and pasting the correct data. It is a plain text file. Regards, Pete

Yes, but only in FS2004, not before. You need the FSUIPC SDK, see the New Weather Interface documentation. To set the whole world in this way would take a long time, as each station is set with an exchange of data -- i.e. you send the data, FSUIPC sets it whilst you wait for confirmation, and so on. If you just want to create weather to load up once and for all you might be better looking to create a .WX file directly and loading it by loading a flight. Regards, Pete

I'm sorry, but I don't understand what you mean by "variables" in this context. Are you talking about values in FSUIPC offsets? If so, there are already FSUIPC controls which you can assign to buttons or keys and which manipulate values in any addressable offsets. Regards, Pete

Well, FSUIPC and WideServer close when FS closes, they have no choice. They most certainly don't carry on normally. WideClient provides data from its memory, as it always does. When WideServer packs up, that memory will no longer be updated. At present the only way to determine if FS is 'alive' and you are still 'connected' is to check one of the various "active" counters -- 337E probably being the most suitable. There's also the timer in 3374. If they don't change over a reasonable time (maybe allow a few seconds in case of severe Network hiccoughs or local problems), then assume FS has gone down or the link has been severed. Note that those values may also stall if the connection from Wideclient to WideServer is blocked or lost. You cannot differentiate this from FS closing or crashing. As far as FS closing is concerned, by the time FSUIPC knows FS is closing it only has time to tidy up, releasing resources. WideServer similarly. I don't know if it would be able to send out messages to the WideClients saying it was closing -- I could certainly investigate that if it is important. But nothing will cope with FS crashing, obviously. Regards, Pete

I'm afraid that none of the additional facilities are at all applicable to FS98. They are almost all concerned with manipulating data inside FS, and this started when FSUIPC was first designed -- for FS2000. I thought this was clear from the paragraphs in the User Guide (see section "Introduction: what is FSUIPC?"): The documentaion about all the user options in those other pages, the ones you don't see, is also entitled: with both FS98 and CFS1 deliberately omitted. This is because none of those facilities are applicable in those cases. What, in particular, were you hoping to get by installing and registering FSUIPC in FS98? I do hope you haven't spent your money inadvisedly. Regards, Pete