Pete Dowson

No, I dn't think it's available there, is it? There are new data areas for AI as mentioned in the recent release notices (see the History document). It'll all be covered in the next SDK version, which I hope to release over the weekend. Yes, you have to. Regards, Pete

My module is actually called FSUIPC.DLL, and you need to make sure you are using the latest version which is currently 3.129. The error about a flight file is nothing to do with FSUIPC. It sounds like your default flight file is corrupt or missing. Check that in your FS9.CFG file. The Elite driver for FS2002 doesn't work with FSUIPC 3 because of an error in their code -- they do not check the version correctly. You have to get a new driver from Elite. Also, it probably won't work until and unless you Register FSUIPC in any case, as Elite have never bothered to approach me for any access rights. Regards, Pete

Thank you very much! And the best to you, and all visitors, from me too. Let me echo your colourful words (thanks too for all that work!): MERRY CHRISTMAS & HAPPY NEW YEAR! Best regards, Pete

You have two throttle levers, right? You want independent controls for Engine 1 and Engine 2, with a reverse section on each? First you need to assign each throttle separately to Engine 1 and Engine 2 in FS's assignments. This is not what you have done so far, by the sound of it. It also is nothing to do with FSUIPC, yet. All this should be covered in FS's Help, but here goes ... Get both throttles working in FS as it stands, first. The FS assignments are accessed by Options-Controls-Assignments. Select the "Joystick Axes" tab, find the "Engine 1 Throttle Axis" entry and select it, click "change assignment", and waggle the throttle 1 lever so it gets recognised. Confirm that you want to change it. Now do the same with the "Engine 2 Throttle Axis". This should give you full forward throttle range on both engines. Make sure the "sensitivity" is at maximum or near so for both axes or you will get lopsided control (sensitivity is also in Options-Controls). When that's working okay, go to the FSUIPC options, Joystick pages, and locate page 3, giving calibration of separate throttles. Calibrate both throttles 1 and 2 following the directions in the FSUIPC user guide. Make sure you have a zone around your "idle" detente to give a reliable output of 0 when the throttles are at that position. The minimum position should give an output of -4096 for full reverse (though that may vary according to aircraft) and the maximum position and output of 16384 for full forward thrust. If you want to use two throttles on 3 and 4 engined aircraft, just check the "Map 1->12, 2->3" and "Map 1->12, 2->34" options on the throttles calibration page in FSUIPC. "Okay" out of the FSUIPC oiptions and you should be set. Regards, Pete

There's nothing official. If you can write Gauges, then they are pretty much the same except those have a .GAU filetype and are loaded through PANEL.CFG references. If you search this Forum I'm sure you'll find a thread that has more details in, even a reference to somewhere helpful. Sorry, I can't remember the thread subject line, but it was a result of a similar query. You really need to think it through first. Remember that if it is something that will be running whilst FS is running, once you are 'inside' the same process as FS it is your responsibility to ensure harmony, to run smoothly without unduly impinging upon performance, and so on. You can no longer rely on Windows to operate the multiprogramming as you can when you are a separate process. If your program is some utility that is in fact inactive except when called upon, then maybe the performance element isn't so important, but you are still using FS's virtual memory space too, so need to consider that. Another thing to consider, if your program uses the FSUIPC interface, is whether it would be useful run on a client PC via WideFS. One of the best known and well used Module-programmed add-in is FSNavigator, and it is a great shame that it isn't actually a separate program so it can be run on a separate PC -- even I would use it then! :wink: Regards, Pete

Clouds you mean? Have you got the FSUIPC option enabled to add a cirrus layer? I think it defaults on. What's "FSConnect->Write"? I don't recognise that. Is it something from my SDK? No, but there is an option in FSUIPC for that. Perhaps a casual read of the FSUIPC User Guide may be in order? :wink: Regards, Pete

Oh, good. That was quick. Wha'd I say? :) Regards, Pete

The answers would be easier if I could see what WideFS was saying. Check the WideServer LOG and the WideClient LOG. Those are files produced to tell you what is going on. If there's no connection at all the most likely problem is that you have not told the Client the name of the Server (if using TCP/IP) or the ServerNode (if using IPX/SPX). If you are trying to use IPX/SPX then you may get problems in any case with a mixed network of XP and 98SE systems. At least I could never sort mine out , it didn't work properly till I changed to TCP/IP only. Regards, Pete

Hmmm. It's interesting that the system generates the traffic even if it can't produce an image for it! Very strange. Regards, Pete

Ah, yes. ZoneAlarm can stop things and doesn't always tell you it is doing it. Glad for found out what it was! Regards, Pete

FSUIPC isn't "polling" keys so it cannot implement a shorter interval to do it in. Keyboard events are dealt with by the Windows keyboard system which generates Windows messages like WM_KEYDOWN, WM_KEYUP and WM_CHAR. These are processed by FS directly, unless intercepted by FSUIPC when set as Hot Keys or programmed in the Keys page. But even if FSUIPC is converting keystrokes to FS controls (which isn't applicable here in any case) it cannot do this "faster" than the keystrokes are arriving! So, sorry, there's no way at all to do it with that cockpit. The 767PIC programmers did produce a direct programming DLL for use with their gauges, licensed to folks such as Aerosoft (for their MCP). I don't know if they'd be willing to let you have that, or sell it to you, but that is the only way you'd get to beat its crazy continuous control sending. It would mean you programming your own interface, as Aerosoft did. You might consider moving on to PMDG cockpits. I understand they will be producing an SDK for those who want to interface equipment to them, though I have no details nor timescale yet. And, again, it probably won't be free. Regards, Pete

As long as the field IS listed, it might work with nothing in it. Try this key for it: MDSZ I7L9 RHLL If that doesn't work there are other steps I can take. Please let me know. Regards. Pete

Sorry, I've never heard of that. Does it use the Network? Check the WideFS documentation. It does explain why that can happen -- here, I'll reproduce the appropriate paragraph for you: "Note that the number of current connections is shown in the title bar of Flight Simulator. This may fluctuate if responses to clients aren't currently being sent. This is because the client assumes that a lack of response for many tries means a disconnected link, so opens a new one. The server detects disused links after a while, and closes them, but there's an overlapping period whilst more connections may actually be open than there are clients." So, something is stopping responses from the Server. Check the WideServer and WideClient Log files, that's where any useful information will be found. It is most definitely something up with the network though. If this "VoiceBuddy" does something with the network or your protocols then it may well be responsible. Regards, Pete

Well I've now got 2/3rds of the information I need. I don't need "File version" but "Product Name", from the Version information. Regards, Pete

Is is Freeware? If so, supply the details I need and I can make a key. If you look at the list of Freeware keys above you'll see what I need: 1. Exact program name (as in "name.exe") 2. The 'Product Name' field from its "Properties" (right click, select Properties, then Version) 3. The 'Company Name' filed from its Properties. Regards, Pete

Yes, it was. See your email. Pete

"Ref" is short for "Reference" and is the unique number for that aircraft inside FS. It's presented by FSUIPC for reference by programs accessing the data. Only by this reference can changes in the list be determined, as the slots available get re-used as aircraft come into and go out of range. Really? I've never seen that. you can scroll through all the visible traffic in a separate window in FS using CTRL+W. That's because TrafficLook knows nothing about flight plans. TrafficBoard does that, though. Regards, Pete

Sorry, you'll have to address that to PMDG. There's no graphic's programming at all in FSUIPC. It sounds like there's a problem loading the background bitmap, which should be easy enough to resolve, but I am no panel expert. It certainly works fine here. Regards, Pete

Version 3.06 of FSUIPC is out of date and not supported. The current version is 3.129. I'm sorry, but I've never heard of ACRAD. Does it use FSUIPC at all? If so it will need a key to access any unregistered version 3.xxx FSUIPC. No one has contacted me at all about this. Maybe all the other users have registered their copy of FSUIPC? Regards, Pete

It isn't a "great" program, it was written merely to test the facilities in FSUIPC, and as an example of the data it provide. It is provided as a useful utility, perhaps, but it is not intended as a developing application. I only enhanced it recently to add tests for the new data FSUIPC provides. As to your requests: 1. The data shown is whatever is opted for in FSUIPC. The default is airline+flight number for airliners, and tail number for GA. If you are not seeing flight numbers you have the option wrong in FSUIPC. Note that Flight Numbers are not assigned until clearance is obtained. Those aircraft 'sleeping' at gates do not yet have valid flight numbers -- the one which FS provides me for those is the default one from the AIRCRAFT.CFG file, so they all look the same! 2. What for? There are other programs that do that. TrafficLook is not meant to be a timetable viewer, it is a test program for the facilities in FSUIPC. I think you will find TrafficBoard more what you seem to be looking for. 3. If you want a text version of it use the Printing facilities and print to a file. Regards, Pete

Nothing more since last time I wrote. no. Sorry. Regards, Pete

CD? No, it isn't worth it. Just go to http://www.schiratti.com/dowsonand download it. It isn't very big. All my software is there. FSUIPC is also available from AVSIM, but the Schiratti page, as referred to everywhere, is complete with all my stuff. Not sure where you think you are "not getting a straight answer", it seems pretty clear to me where you get the programs. Where have you been looking? Just check the announcements at the top of the page, or any of my documents for the past few years. They all point to the Schiratti page. Regards, Pete

Not at all, don't worry about it. Of course I would rather you were a paid-up user of FSUIPC 3 :wink: , but it isn't too busy here at the moment, so feel free. Jagged lines which are supposed to be straight come about because the pixels needed to perform a perfectly straight line at that angle don't exist. You'll find that when the horizon is perfectly level it looks fine, and it will look fine at certain other angles too. The higher the resolution the less exagerrated the effect becomes and less critical angles occur. The same improvement can be obtained by moving yourself a lot further away from the screen, of course, until the eye no longer discerns the lack of straightness in the edges. Anti-aliassing is a way of using pixels of differing intensities along the line to fool the eye into thinking it looks straight. It gets a lot more complicated than that, and there are many different methods of doing it which have different effects and different impacts on performance. I tend to be quite happy on an 18" screen at 1280x1024 without AA, but I suspect at 21" I would find it more annoying. But even in the old cruder graphics of yester year never would I have found it bad enough to warrant aborting a flight as you say you do! I'm not understanding this again, I'm afraid. How are you setting the weather? Do you have a save flight + WX file which illustrates the lack of FSUIPC's visibility limits taking effect? All I am seeing is the results of FS setting unlimited visibility. If you never want to see the horizon then the imposition of limits in FSUIPC should work. If you'd like to send a saved FLT + WX to me, along with your FSUIPC.INI file, I can try it here (I do have an FS2002 installation still, somewhere here ). Zip them and send them to petedowson@btconnect.com. Of course I will be using FSUIPC 3.129 or later, but the visibility control for FS2002 won't have changed. You can use global weather without forsaking "real world" weather settings by using an outside weather control program such as FSMeteo or ActiveSky. These programs improved the weather implementations in FS2000 and FS2002 immensely in my opinion. Only with FS2004 has Microsoft's own weather download facilities caught up. This is only my opinion of course. Well I've looked, and these don't look bad at all to me, I'm afraid, but then I've never been upset by lack of anti-aliassing. I know some folks won't ever fly without it, but I prefer the higher performance I get without. To me it just isn't worth the lost of any frames per second just to smooth a few edges now and then. Good job we all have different tastes, though, else the world wouldn't be so interesting, eh? :) Regards, Pete

Sorry, they're all supposed to be self-explanatory. Which ones are a puzzle? TrafficLook is only showing the data FSUIPC is providing, it isn't examning any traffic files as such. I did TRY to find the ETD and ETA -- and in fact I got close, but the code is very convoluted and it would have involved going through two additional FS modules in assembly code to work out how to decipher what I could find. It took many hours of hacking just to get the airport and runway data. I think what you want may be better served by TrafficBoard, which uses both FSUIPC data on traffic and decoded traffic schedules. There's a separate Forum near here about that. Regards, Pete

Okay. Was the previous version of FSUIPC, the one which you had successfully registered, 3.00 or 3.01 or similar? Only in the first few days of FSUIPC 3's release were there any difficulties with accented characters. I thought we'd replaced all the invalid keys long ago. Is this your first FSUIPC upgrade since the end of August? Anyway, I will check therm and take appropriate action when I see them. But I do need the original email. Thanks, Pete