Pete Dowson

Okay, let's stop there a moment. According to my records that is certainly the correct access key for flight tracker, provided it has the following properties: Program name "FlightTracker.exe" Product Name (in Version Info) "FS Flight Tracker" Company (in Version Info) "K. D. Lovell" So, assuming those things are true, it would have worked if you entered the details correctly. So, please explain what you entered and where, exactly. Then I can see where you went wrong and help you get it right. Right? Regards, Pete

Sorry, I'm afraid I don't understand your shorthand at all. What does "clic cwr screen fsuipc!" mean, exactly? And what "appears"? If you can explain in a few, possibly longer, words, maybe I can help. Regards, Pete

Sorry, I've no idea. Try the FS2004 Forum, there's usually someone there who's seen each sort of crash you can get. Regards, Pete

No, FSUIPC offers no such options. It's a real pain in FS2004 to get anything to stay on top of FS -- it was easy enough in FS2002 and before, but MS changed to some different DirectX techniques in FS2004. Even if you get it on top in Windowed mode, doing so in Full Screen mode is still a big problem -- you get flashing. For FSUIPC's own dialogue I intercept FS98MAIN's Paint messages and validate the paint area to prevent flashing. This is okay providing you don't want your stuff displayed in normal flight or slew modes. Otherwise, sorry, it's a matter of trial and error to find something that works. Maybe others have an idea. You may have to delve into DirectX methods (ugh). Regards, Pete

Okay, good. Maybe FDC thinks it's a single engined aircraft or something? Anyway, glad you got it sorted. Well, I wouldn't worry about the latter, but generally the first thing to do when you have an aircraft problem is fly the nearest equivalent default aircraft to copmare it. If the default is okay then your suspicion should fall onto something in the add-on aircraft installation, maybe a gauge, a setting, or a CFG file parameter. If the default suffers in the same way, then you start looking at possible other add-on influences, as, in this case, FDC. Regards, Pete

Can you say what has been changed to achieve this, or have you never used FStarRC before? The runways database is binary. It contains a sorted table of all runways in all airports, but, alas, it is still based on FS2002. I have on my list to rewrite my scanning program for FS2004, but, though I think I now have the new AFD formats, it is not a trivial job and I haven't yet had time to do it. I know it works well with version 9.xxx because there have been folks using this for a while now. I only just updated my FliteMap before Christmas, and am now running 9.04 (Build 7523). FStarRC works fine with it, still. Regards, Pete

There's no support at all for displays and indicators in FSUIPC, sorry. BUT I have completed a separate program, which complements FSUIPC's facilities for GF modules, and allows full control of all the displays and indicators. This is "GFDisplay". I finished it and tested it all well before Christmas, but I have not had time to do any documentation for it yet -- and it needs it, I'm afraid. I'll complete a set of examples (involving both FSUIPC button programming and GFdisplay parameters), and do the documentation, then I'll put an announcement up here asking for Beta testers. But it won't be for a couple of weeks at least -- probably end January (I hope). Regards, Pete

No, not without detailed information -- that would probably be in the Client log files. Something is blocking. The symptom of increasing numbers of connections is described in the WideFS documentation. There are also a couple of threads here which include suggestions which have worked. But things have moved on a bit -- you may want to check the announcement at the top of this Forum, which also includes a test version for folks with problems to try. I'm also still working on improvments so keep an eye out. :wink: Regards, Pete

I don't think there's any other way you'll get pre-made detentes to match FS's. You'll have to do it the other way. Build the thing then make the detentes where you get the stablest results for each position. Calibrate your axis in FS or FSUIPC. FSUIPC is a little more precise and has a jitter filter, but you want best calibration in FS first. But the notch positions will be FS's choice, not yours. Regards, Pete

I'm sorry, but I don't really know how you use that particular aircraft's FMC. If it accepts keystrokes directly, then FSUIPC can be used to convert button presses to keystrokes, though the gauge may need to be put into the mode where it accepts these. Some gauges only operate with mouse clicks, at least for button pressing (the selection keys either side of an FMC, for instance, as well as some of the function ones below). If this is the case with your chosen aircraft then I think you will need to look at Luciano Napolitano's Key2Mouse program. Regards, Pete

I have managed to implement a multiple position calibration system for the PFC throttle quadrant axes, in my PFC.DLL, but it can only work with a fixed number of known detentes, of course. I don't plan to do the same in FSUIPC. I assume you are selecting the specific aircraft you are going to fly, before making this flap system with its fixed detentes? I think the best way is to implement it with a numberof trimpots, one for each detente interval, each large enough to be able to cope with the normal range (i.e. 50k or 100k max). Then instead of a main potentiometer for the lever axis use a multiposition switch or some electrical contact system, so that the current passes through a different trim pot depending on the postion selected. Then, by adjusting the trimpots one by one from one end or the other, you should be able to calibrate it, after a number of cycles through, to suit the values needed by FS. You could use fixed resistors instead of trim pots, but you will then need to use a potentiometer initially, to find the resistance values needed to select each of FS's detentes, and an ohmeter to measure same. This would also be a good way, possibly mixed with some trimpots for fine tuning. Just ideas. Regards, Pete

No, FSUIPC 3.xxx works on all versions of FS from FS98 onwards,, up to and including FS2004. It must be an old version of FDC, then, because some version of FDC has most certainly been accredited, and has a built in access key for FSUIPC 3. Maybe it was updated for FS2004? FSUIPC 3.44 works on FS98, FS2000, FS2002 and FS2004. It will also provide some features on CFS1 and CFS2, but not CFS3. Regards, Pete

If you calibrate the separate throttles in FSUIPC, the AXIS_THROTTLEn_SET controls are changed to THROTTLEn_SET controls so you can use the reverse range. The single AXIS_THROTTLE_SET control is left alone. Your 2 but only for individual throttles. FSUIPC does not support reverse on the single throttle -- you have to map it to the multiple ones. I think this dates from FS2000 where even the single THROTTLE_SET did not give reverse. The separate Reverser axis provided by FS operates using the THROTTLEn_SET controls too. BTW I'm not sure whether all those events will be trapped by the Panels trap facility, because on FS2002 and FS2004 I am calling the Event routine in SIM1 for some of these things. It depends where it is hooked. Regards, Pete

Thanks Rob! I didn't know all that stuff. Very useful. Nice to learn something every day! Regards, Pete

Yes, it was issued to the author on 9th August 2003, and as far as I know it was incorporated into the program for automatic access, and so needs no manual entry. It must have worked because that was almost 17 months and there's been no queries since then. Maybe you have an out of date version? Regards, Pete

Aha, that makes 3! I hope so. They've not arrived yet, and I have some chores to do, but I will check them later tonight. Thank you! [LATER] AhI see you attached them instead of emailing. Okay, they were short enough. Thanks. Pete

There's no known problems with 3.3 and FDC. The only problem I know of was with Windows 2000 only (not XP), and was certainly fixed in an FSUIPC version long ago. I suggest you contact FDC support. Regards, Pete

The formula I use in TrafficLook is very approximate, being normal plane trigonometry. That'd be reasonably close for near waypoints, but progressively worse as distance increases due to the curvature of the Earth. Also, I think my formula would be pretty bad anywhere near the poles (> 60 degrees N or S). // Everything in double floats, angles in degrees, result is True not Mag double Wrk = cos(PI * (fabs(MyLat+WayLat))/360.0)*(WayLon-MyLon); double Bearing = (MyLat == WayLat) ? 90.0 : (180.0 * atan(fabs(Wrk/(WayLat-MyLat))) / PI); if (MyLat >= WayLat) { if (MyLon >= WayLon) Bearing = 180.0 + Bearing; else Bearing = 180.0 - Bearing; } else if (MyLon > WayLon) Bearing = 360.0 - Bearing; If you want accurate bearings for longer distances or for anywhere in the world, you need spherical trig. Then I'm rather lost. You can find formulae on the 'net but you need to search. Regards, Pete

I don't know how you've got your clients set up to respond to Shut Down requests, but if they aren't so configured you can now make the logs include a performance summary by configuring a Hot Key in WideServer to send a shutdown request. Then only things configured to shut down will. But, honestly, I don't want logs unless there is something BETTER or WORSE, or anything suspicious. Else I'll be overwhelmed and not get anything done! :) Regards, Pete

Strange. No one has mentioned anything to me about any such reports. I have no idea what would prevent the electrics being operative in their cockpit -- I would expect them to know about that. If they thought it was FSUIPC you'd expect them to contact me about it. I have a contact inside PMDG and I am copying him both of your messages and asking what is meant. I see there is also this: I don't know Paul at all, but have you contacted him, as it evidently didn't fix your problem? Are you using the same PMDG aircraft on FS2002 and FS2004? I didn't think that was possible! Are you using FSUIPC 3.44 on both FS2002 and FS2004? I'm pretty sure that the FS2004 versions of the PMDG aircraft are a good deal more advanced than the FS2002 versions. Well, I haven't, sorry. But before you go back to PMDG, some clarifications. Are you running FSUIPC as a registered user? If so, see if the PMDG works when you remove your FSUIPC.KEY file from the Modules folder. If it does, then your FSUIPC access key is not correct. Zip up the KEY file and send it to me at petedowson@btconnect.com and I will check it thoroughly here. Regards, Pete

I'm just putting it all together now. Details will be in the announcement and in the ZIP read me. Hopefully, the details I need you to colllect will be in the log. If not, I have a really bad problem. The thing is, though, because I will be trapping the errors things may look okay. Or they may not. You will have to check the logs on the Clients at intervals, or when anything is supsicious. Regards, Pete

Yes, thank you! My deductions were correct in respect of the list of "routes" in IPXROUTES. I shall go ahead with the changes to WideServer so that they will be listed in cases like your Server too. Thanks again. I will be releasing an interim Beta (6.442), for both WideServer and WideClient, later today. I'll put them as an attachment to an Announcement, above, if you would like to try them. Full details will be included. Regards, Pete

It sounds like you need to go through the correct procedure to get things going. This isn't an FSUIPC matter. Check the overhead panel. You need at least the batteries on to start with. Also, in case you have the avionics switch in FS off by default, go to a default FS aircraft which shows an avionics switch, and make sure the avionics are on BEFORE loading the 737NG. It may be loading with FS is a situation where the PMDG doesn't have an operable switch. These are only suggestions. With a complex fuly simulated cockpit like the PMDG series you do really need to study the manual. Also try asking others. I believe there is a PMDG forum? Sorry I cannot be more specific. Whilst I do have the PMDG 737NG series, I don't actually use their panels, but Project Magenta instead. Believe me, with pmSystems providing the overhead, it can be just as complicated to get things going until you know what you are doing! :wink: Regards, Pete

Ah! Do you know, I've only just found that! :oops: I could have sworn the first one was the one I replied to first. Strange. :? Unfortunately the logs aren't helpful, except that I note that you are still using TCP/IP. I have switched over completely to IPX/SPX now, on an all WinXP setup. Have you tried IPX/SPX? I could't tell whether the crashed WideCliet had actually done much before crashing. It would have been more useful to see the WideServer LOG after FS had been closed, as the performance information is at the end. So it "crashed to desktop" with no message, nothing? Weird. I've not had anything like this before with WideClient, so it must be something in the very recent changes. I am putting together another interim test version (6.442, both Server and Client) which will log more performance data, and which also changes some of the defalut parameters again as a result of feedback. I am adding error trapping to WideClient so hopefully I will get a chance to see some details of this crash. This time, in case I forget anyone, I will be putting up the replacement modules as attachments to an Announcement here. It will be later today, so please look out for it. I'll include details of tests needed and results to be returned. Thanks, Pete

Okay. I'll look to see if I can change over the "fix control accelerations" option to work from that PANELS call instead then, though it won't be as easy as doing it from a Gauge. FSUIPC is running all the time, but the panels stuff normally has to be mde and unmade each time a Panel is loaded/unloaded. However, I'll delve into it and see where to place a more permanent hook. Thanks! Pete