Pete Dowson

Sounds like you have a thoroughly corrupted copy of TrafficLook there! The "File" menu dropdown is fixed, defined in the resources, not programmed, and lists: Print ... Ground Traffic Only Airborne Traffic Only Refresh AutoRefresh Exit The COM1 column is still there, as it was before, and the "State" column did not even exist before the current version, it was added for FS2004 and released in version 1.41 dated June 2003 ready for the FS2004 release -- this is still the current version, so it has never been changed! If you've used it before and seen the "State" column then it must be the same version -- so how come it's changed on your system? Corrupted file perhaps? The printing has always worked fine. It is a standard printing routine which I use in all my programs and hasn't been changed in many years. I just tried it here and it is okay. Please download the ZIP again and replace your EXE. It sounds like it has been messed up somehow. I have just re-checked the version in the ZIP to be sure. Regards, Pete

1. FSUIPC doesn't know any names, only numbers. 2. You don't say which FS you are using, but if it is FS2004, you don't need to provide FSUIPc with the number in the INI file, as FS2004 provides direct axis assignment for the flaps. Just assign it in the FS assignments dialogue. Regards, Pete

You wouldn't want to change the time in FS more than once, it causes reloads of scenery, stuff like that, so you'd set that just the once (Zulu and Local) and then use your time value to time the injection of the other data. You don't say how often it supplies the data, but if it is less than, say, 10 times per second, you'd probably need to interpolate between values to get smoother operation. Of the other information, you can set Pitch Roll Yaw (Heading) and Altitude, but not airspeed, turn rate, G's or AofA -- all those are "effects" of simulation, not "causes", if you see what I mean. The most important thing that appears to be missing in your data is position -- Latitude and Longitude! How will you determine that? Regards, Pete

I assume you are talking about FSUIPC's Keys page? You don't say. If so, then there's no reason. Ctrl + 1 (whether on the main keyboard or on the the keypad) is equally programmable. There's no distinctions in FSUIPC, and the combination of Shift, Ctrl, or Tab with any of the main keys works fine here. Perhaps CTRL+1 was stolen as a HotKey -- either in FS's HotKey page, or by WideServer, or by, for example Radar Contact, or some other external program? Hotkeys take priority. Pete

If you use FSUIPC's visibility smoothing, the visibility shouldn't change immediately. But I can't do much about clouds -- you should be able to see them in the distance and approach them, though. I've never had them suddenly appear or disappear, at least not the 3D ones. Pete

Nor I, I'm afraid. You'd need to look at a specific aircraft, see what's being done. Sorry. The aircraft I'm more familiar with have either fuel selector switches OR a crossfeed switch. I have no idea what happens when you have both. Regards, Pete

I've not heard of any solution to this yet. One user was trying to get the TeamSpeak folks to advise. With Roger Wilco I used a pair of Registered Messages which RW provided for PTT on/off, but I don't think there's any equivalent at all in TeamSpeak. I think it may need a program change to allow external program access. See what you can find out from the authors or support. Regards, Pete

Customer Services via http://www.simmarket.com. Only SimMarket have the details, I am not in the loop. You need to quote the same name and email as originally used. Best to print out the email with the details as soon as you get it next time. Regards, Pete

That does sound promising, yes. Please let me know. If it needs any other NMEA messages I can even add them to GPSout if you know what they are. Regards, Pete

Yes, but it is pretty much the exact opposite of what GPSout is about. GPSout is effectively "pretending" that FS is just a big GPS, and is producing the same output on the serial port that a real GPS would on its serial port. So in effect you are connecting two GPS's together. Normally you'd be connecting a GPS (FS in this case) to a PC or similar in order to follow or record the route on a map or something. What it sounds like you really want is some module that outputs something which looks to the GPS like the signals it gets normally from the satellites. I'm not sure if that is possible. If it will accept standard NMEA as input, rather than output, then it may do what you want. The Garmin I have doesn't. Regards, Pete

Hi Bob, I'm working on version 1.72 of PFC.DLL and I have list of possible enhancements, but I want to get some defaults sorted. Perhaps you can help by saying what you see in your problematic throttle inputs. These are the proposed facilities: 1. Small jitter smothing with adjustable timescales. Currently the smoothing operates on ANY value of change in quadrant inputs which causes a reversal of direction within 150 mSecs. i.e. current (smooth) value is x read value y at time t1, ok, new value = y read value z at time t2 .... if t2-t1 > 150 mSecs, ok, new value = z if z >= y >= x ok, new value = z if z <= y <= x ok, new value = z else, its a change in direction: discard value z, keep value y This works for short-term jitters and spikes caused by power supplies and many other physical factors, but it won't fix "slow" changes by 3 units due to pot position being just on a border. So I'm proposing to add another check, similar to the above, but where the difference between y and z is less than 5 PFC units. For this the time difference will be larger, and adjustable. I was thinking of a default time of more like 500 mSecs, but what are you observing as the jitter period? 2. Throttle + Prop + Mixture sync assignable control A special control internal to the PFC driver to copy engine 1 values or all of these to the other engines. Assignable in the Yoke and Avionics button assignments. I'll check what the FS Prop Sync control does, and maybe trap that for the same use. 3. Throttle + Prop + Sync connection toggle control I'm less happy about this. If I did it it would be an assignable toggle to disconnect / reconnect the inputs for these three controls on all engines. Would this really be necessary if the other things above were done? If I did it, should it automatically re-connect on a large change in any one of the axes? If so, how large? Half full range (eg 50 PFC units), or what? I'd rather not do this if it isn't warranted. I can envisage folks complaining that their throttle quadrant doesn't work! I'd appreciate your views on these things, as soon as you can please, as I need to get 1.72 out this week -- 1.70/1.71 don't work properly on Windows 98 (I'm having to make the restart/sync facilities conditional on Win2000/XP). Regards, Pete

While I have your attention, I sent you an email and it was rejected as follows: =========================== This report relates to your message: Subject: Registration of FSUIPC, Message-ID: <015f01c39a24$704b7780$df00a8c0@newleft>, To: of Mon, 27 Oct 2003 11:47:52 +0000 Your message was not delivered to: rickalty@aol.com for the following reason: Diagnostic was Unable to transfer, Message timed out Information Message timed out =========================== Is you ISP unwell? Regards, Pete

You closed down the client after only 2.6 seconds? It can take longer than that before they connection is confirmed! Here's a typical start of a WideClient Log, using TCP/IP: ********* WideClient.DLL Log [version 6.101] Class=FS98MAIN ********* Date (dmy): 28/10/03, Time 00:17:59.171: Client name is NEWLEFT 2484 Attempting to connect now 2578 Trying TCP/IP host "OFFCENTRE" ... 2578Okay, IP Address = 192.168.0.170 9750 Connection made okay! Try deleting the IPAddress parameter from your WideClient.ini file. See if it can find your Server by name rather than address. You only need to give one in any case, and the name is less error-prone. And you don't need to tell the server its own name and address. those parameters don't belong in there at all, though they won't do any harm. And where's the rest of the Server's Log? There will be much more than this! If FS is closed down there will be a summary of WideServer's performance, just like when you closed down WideClient. Are the times correct on both PCs? Was the Client actually started 12 minutes after the Server? Please delete the IP address parameters, and also let it run for a few minutes, then tell me what is wrong! Regards, Pete

If you are talking about a user key for FSUIPC, it will work if you enter exactly the same name, email and key as you did originally. Every character must be the same, the same as notified to you originally. If it is not working it is because you are making an error. If you are talking about the FSUIPC.KEY file, then it won't work like that if you had to reinstall Windows or reverse the registry to some point before you registered. In that case you will have to register again -- just cut and paste the details from the KEY file. It is effectively the same as installing on a new PC. Regards, Pete

What does? Sorry, you started a new thread with only "Thanks" as the title, so it is a puzzle. Best to post in threads to keep continuity. :wink: Pete

Two things I've now discovered: 1) Setting "SyncInit=No" won't help, sorry. The facility was originally designed defaulted off, and the parameter checked is SyncInit=Yes. Ooops! :oops: 2) I cannot make the restart sequence work at all on Windows 98. I've narrowed it down to the SetCommState API call. If seems to always crash the process when used for the second time on the same port, even with exactly the same data. It works completely on Windows XP. :cry: For now I will test for Windows 98/Me and switch these new facilities off if those operating systems are detected. Look out for PFC version 1.72 later this week. Apologies for the hassle. Regards, Pete

AFCAD2 already contains the key so you don't need to edit it, but Lee made a small mistake. Here's a quote from Lee: Regards, Pete

[quote name="Luca Zappala I know the Crossfeed toggle one does work' date=' but I don't know what it is used for. Could you enlight me? [/quote] I think it may vary according to aircraft implementation, but if you look at the fuel selector switches on those cockpits with them showing, you'll see that crossfeed left-to-right will feed both engines from left tank, and vice versa. Usually left tank feeds left engine, right tank feeds right engine. I assume you'd use crossfeed to correct an imbalance, or to keep balance when one engine is out. Regards, Pete

Okay, Got it. Thanks. I don't understand this. If you cannot post new topics, how did you start this topic? I've not seen anyone with so restricted an access. Please write to the SimFlight forum folks and see what the problem is. I am writing separately about the FS2004 problem, with more questions. It is a puzzle. Regards, Pete

These "settings" are the input values which are of no interest at all to me, they are very specific to your hardware! What I need to know is what values FS wants to set "flight" and "ground" idle. From what you've said before I'm assuming GROUND idle should be the "real" idle, i.e 0, as you said you can taxi at flight idle. If Flight Idle were 0 then you'd get no thrust, and I assume ground idle would have to be negative -- hence your "engine problems"? If you have calibrated it so that Flight Idle gives you zero (the "centre" in FSUIPC), then I am now thinking that you have calibrated it wrong, and this is the problem. You surely need to calibrate so that the GROUND idle gives the zero!? I can easily use a simple joystick, calibrated for flaps through FSUIPC, to reliably select all 9 positions on the default 737. The flaps calibration facility does not, at present, provide any notches, however. All that is happening is that the increment is used to make the output value jump from one FS-notch to the next. You have to mark off your "detentes" to suit FS, not the other way round -- calibrate in FSUIPC to suit existing notches. I will certainly provide that method in the module I have planned -- I have already done something similar for the PFC quadrant with notched flaps. Regards, Pete

I've reproduced this now, under Win98SE. It is related to the automatic restart, so for now please set SyncInit=No, and AutoRestartTime=0 as I suggested. I am trying to track down the reason for the problem, but so far it looks like the sort of thread and comms restart I am attempting is not possible on Win98. It works fine, 100%, on Windows XP. I may just have to make it automatically omit those facilities on Win98. Regards, Pete

Ah, that is an entirely different matter. Obviously if FSUIPC is not running then no programs which access it will find it, and similarly it cannot produce a LOG file! What does FS say when you attempt to load it with FSUIPC installed? I've not heard of any similar problem with FSUIPC installed before. What errors? How are these reported? What has this to do with FSUIPC? These are all standard main parts of FS. If you did delete FSUI.DLL, which is part of FS and nothing to do with FSUIPC, then you will get many errors!! But nothing like that will stop FS loading. If FS isn't loading, what is happening instead? Do you mean you click on FS's icon and NOTHING happens, or what? I'm afraid I simply cannot picture what you are saying. Regards, Pete

[quote name="roger.wielgus Of course. It is just too bad ( for me) that this value does not match the setting on the quad. When I pull the lever back to flight Idle' date=' the generated values of my pots are simply to close to the ground Idle and the engines do not like that. [/quote] But I still don't understand, and you aren't telling me :cry: What ARE the values? Use FSUIPC's Logging -- monitor the throttle values (right-hand page, offsets 088C (Engine 1) and 0924 (Engine 2), as signed 16-bit values (S16). If the values are too close to be differentiated on your throttle lever then maybe it is some poor design on the part of the FS panel maker, and I don't understand that either. What is meant by "the engines don't like that"? What sort of complaints do they make? Well, one day, possibly, if you can explain it a bit more, please. I keep asking for specifics but don't get them. :o Regards, Pete

No, sorry. I've got no access at all to do with any scenery, whether dynamic or static. Maybe someone in Lago knows how to do those things, but I always thought scenery of all types had to be pre-compiled into a BGL and indexed by FS during the loading sequence. In FS2004 you can't even add new scenery and get it to appear as you used to, you have to close FS down and restart it. Regards, Pete

I don't know the program at all, so I have no idea if it is compatible with FS2004. I would, however, assume the author knows what he is talking about. He has not contacted me for an access key or any other details. If it is freeware then it is entitled to free access to FSUIPC, otherwise you would need to purchase a user key for FSUIPC. Regards, Pete