Jump to content
The simFlight Network Forums

johnhinson

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About johnhinson

  • Rank
    Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://
  1. Thanks very much for the answers. This explains the circumstances I have encountered. There could be a case for it, but it isn't for me to ask. I will go back to the developer with the information you have kindly given me. Once again, thanks. John
  2. OK, no problem. Just two follow-up questions, then, if you don't mind: Does FSUIPC supply the callsign information for an AI aircraft based on the aircraft.cfg and nothing else? Does FSUIPC give an indication to other software whether the identity of the aircraft is a tail number or callsign (other than the obvious that you and I can see the difference with our eyes!)? I'm guessing perhaps that the only way would be the presence of a flight number? Thanks again for your time, John
  3. Thanks very much for your reply. Basically, the AI flightplan specifies that the aircraft should fly under its tail number and not use the callsign shown in the aircraft.cfg. FS2004 reads that and identifies the aircraft under its tail number in its ATC system. I was therefore thinking that TrafficLook would show the tail number, but it doesn't. I know this sounds trivial, but I'm trying to approach the issue in a systematic manner one step at a time. Many thanks, John
  4. I think you misunderstood my comment as your responses don't really seem to relate. No insult was intended. I don't think it was unreasonable for me to expect the file on the main site to be current, but you and others have kindly explained why it wasn't. John
  5. I have a question about the output in TrafficLook.exe. Here is a screenshot from my system: It is entry 04 that I am curious about - shown as AIRCOMPANY KH (Actually AIRCOMPANY KHORS) This is the aircraft.cfg entry: [fltsim.3] title=AIA MD82 Khors Aircompany sim=aiamd80v5acofadv model=SD texture=khors atc_airline=AIRCOMPANY KHORS atc_parking_codes=KHO atc_parking_types=GATE ui_manufacturer=AI ui_type=McDonnell Douglas MD-82 ui_variation=Khors Aircompany description=AIA Douglas MD8x series and this is the Flight Plan for one of four aircraft wetleased to ATA Airlines: AC#28303,UR-CDN,1%,WEEK,IFR,1/05:05,@1/05:35,170,R,0000,OITL,1/07:05,@1/07:35,160,R,0000,OITT,2/03:00,@2/04:00,310,R,0000,OIII,2/06:00,@2/07:10,320,R,0000,OITT,2/09:30,@2/11:25,330,R,0000,OIMM,2/11:45,@2/13:55,330,R,0000,OITT,3/03:00,@3/04:00,310,R,0000,OIII,3/06:00,@3/07:10,320,R,0000,OITT,3/09:30,@3/11:25,330,R,0000,OIMM,3/11:45,@3/13:55,330,R,0000,OITT,4/03:00,@4/04:00,310,R,0000,OIII,4/06:00,@4/07:10,320,R,0000,OITT,4/09:30,@4/11:25,330,R,0000,OIMM,4/11:45,@4/13:55,330,R,0000,OITT,5/09:30,@5/11:25,330,R,0000,OIMM,5/11:45,@5/13:55,330,R,0000,OITT,6/05:05,@6/05:35,170,R,0000,OITR,6/07:05,@6/07:35,160,R,0000,OITT,6/14:30,@6/15:30,310,R,0000,OIII,6/17:30,@6/18:40,320,R,0000,OITT,0/05:05,@0/05:35,170,R,0000,OITR,0/07:05,@0/07:35,160,R,0000,OITT,0/14:30,@0/15:30,310,R,0000,OIII,0/17:30,@0/18:40,320,R,0000,OITT Note that the flightplans have been designed (not by me!) to make the aircraft fly under its tail number by using the letter R instead of F. Flight Simulator 2004's ATC system describes the aircraft as UR-CDN, but TrafficLook shows it under its callsign. Is this how it is intended to work? My reason for asking is that I think a third-party programme I use is getting similar information from FSUIPC and becoming confused. Notes: 1. The abbreviation to thirteen characters is not an issue, I have tested this with a smaller callsign. 2. I know that I could force it to show the tail number by removing the aircraft.cfg atc_airline= entry but this would then affect the airline's own flights. Kindest regards, John
  6. Thank you. Not for me to question, I suppose, but I wonder why the up-to-date version isn't available on the main web page for the software at http://www.schiratti.com/dowson.html. Being just a general user of the software, I got directed here as it said it was the only means to make contact with the author but I certainly didn't expect to have to spend ages going through a forum I have never visited before to find that what was shown to be the current version on the site actually wasn't! It seems a very complicated way to expect customers to deal with an issue they have identified. But all now sorted, hopefully. Best wishes, John
  7. Sorry to be a pain, but the version currently available (3.98a) seems to still give this problem. John
  8. Thank you. I will re-download from your web page. The version I am using was only downloaded a few days ago. John
  9. Hello, I haven't used this forum before but wish to make a suggestion for a future FSUIPC update. I hope this isn't the wrong place to post it. I use a registered (and current) version of FSUIPC and have manually made an entry in the ini file (for Radar Contact use) as follows: WhiteMessages=Yes However, any time that I change something in FSUIPC settings (such as adding a Hot Key), this changes to: WhiteMessages=No Is it possible for this entry to be made to remain as entered? Thanks, John
  10. Thanks, Peter, I think this answers a lot of questions, actually. My suspicions are that it is RKG_speed.gau which is one of a set of freeware add-ons that show True Air Speed amongst a lot of other things, like fuel calculation. I used this in a panel I released publicly a while back - many users reported system crashes but I couldn't recreate these. It is only now that I have a temporary FS installation for testing (I haven't entered my FSUIPC registration) whilst my proper machine is kaput that I have discovered how planes with this gauge are causing system crashes. There was mention of a update many years back but I suspect it has now fallen into history. A shame, given how useful these gauge it are. Once again, many thanks, John
  11. How can I tell from this which gauge needs accrediting, please? 1988953 Client Application: "fs9" (Id=3524) 1988953 K:\Flight Simulator 9\fs9.exe 1988953 Product="Microsoft Flight Simulator 2004 - A Century of Flight" 1988953 Company="Microsoft Corporation" 1989063 Illegal read attempt: offset 02B8, size 4 [P3524] 1989063Program or module not accredited for use with this unregistered FSUIPC 1991844 ### IPC Message processed in 2781mSecs ### 1992063 Advanced Weather Interface Enabled John Hinson
  12. Werhay, thanks! And I guess I owe an apology for taking your time. I never thought to look, given the info given to me by the developers. John
  13. Thanks, and sorry - not been through this process before. Yjis should be better: ********* FSUIPC, Version 3.400 by Pete Dowson ********* User Name="" User Addr="" FSUIPC not user registered WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=0000B027[0000B027] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=0 32969 System time = 23:33:12 32969 K:\FS2004\ 32969 System time = 23:33:12, FS2004 time = 12:00:00 (00:00Z) 106094 C:\Documents and Settings\John\My Documents\Flight Simulator Files\northolt.flt 106485 AIRCRAFT\Douglas DC-3 4tank MS\dc3.air 106985 Aircraft="DC-3 Iran National Airlines" 118063 Client Application: "AFCAD" (Id=2984) 118063 J:\AFCAD221\AFCAD.exe 118079 Product=" AFCAD" 118079 Company=" " 118079 Key is provided 147125 AIRCRAFT\Bristol Britannia\britannia.air 147641 Aircraft="Bristol Britannia Aeronaves de Mexico" 159282 C:\Documents and Settings\John\My Documents\Flight Simulator Files\UI generated flight.flt 160094 Clear All Weather requested: external weather discarded 208422 Advanced Weather Interface Enabled 222094 Module identified = "F16.GAU" 222094 Illegal read attempt: offset F000, size 2 222094Program or module not accredited for use with this unregistered FSUIPC 227391 ### IPC Message processed in 5297mSecs ### 253141 System time = 23:36:53, FS2004 time = 23:35:01 (23:35Z) 253141 *** FSUIPC log file being closed Memory managed: 4 Allocs, 95 Freed ********* FSUIPC Log file closed **** Best wishes John
  14. Thanks for your speedy reply, Peter. I ran the log for a short spell, and then opened the gauge. This is the main part of the log: ********* FSUIPC, Version 3.400 by Pete Dowson ********* User Name="John Hinson" User Addr="[removed]" FSUIPC Key is provided WIDEFS not user registered, or expired [Continuation log requested by user] Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=4000B627[4000B627] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=0000001F LogExtras=1 506687 System time = 18:02:04, FS2004 time = 17:56:25 (17:56Z) 506687 *VIS* SM: Min=0.00, MaxRny=0.00, MaxOvc=0.00, MaxCld=0.00, MaxClr=0.00, Upper=60.00, FT: LwrAlt=6000, UppAlt=25000 506891 Traffic File #36 = "scenery\world\scenery\traffic-europe-k" 507453 GetRealAddr(22000304)=6106E144 (orig 3304) 507453 READ0 3304, 4 bytes: 00 00 00 34 507453 GetRealAddr(22000308)=6106E148 (orig 3308) 507453 READ0 3308, 4 bytes: 07 00 DE FA 507453 WRITE0 (failed, read-only!) 330A, 2 bytes: 4C 04 507453 GetRealAddr(2200B880)=610796C0 (orig F080) 507453 READ0 F080, 40 bytes: F9 FF FF FF D0 1F 50 42 A8 9C 4E B9 7F F9 F9 44 507453 EE 97 17 01 60 FF 45 55 52 4F 50 41 20 39 37 30 507453 38 00 00 00 00 8C 62 20 507453 GetRealAddr(2200B8A8)=610796E8 (orig F0A8) 507453 READ0 F0A8, 40 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 507453 GetRealAddr(2200B8D0)=61079710 (orig F0D0) 507453 READ0 F0D0, 40 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 507453 GetRealAddr(2200B8F8)=61079738 (orig F0F8) 507453 READ0 F0F8, 40 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 507453 GetRealAddr(2200B920)=61079760 (orig F120) 507453 READ0 F120, 40 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 507453 GetRealAddr(2200B948)=61079788 (orig F148) 507453 READ0 F148, 40 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 507453 GetRealAddr(2200B970)=610797B0 (orig F170) 507453 READ0 F170, 40 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 507453 GetRealAddr(2200B998)=610797D8 (orig F198) 507453 READ0 F198, 40 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 507453 00 00 00 00 00 00 00 00 ... then much more of the same (or similar) No doubt it means more to you than it does to me! John
  15. Hello Peter, I've almost completed an 18 month project for a free-ware add-on panel. One of the many special features of this panel is an AI radar window - it displays the locations of nearby AI aircraft and their identity/speed/height etc. As you will imagine, it requires FSUIPC to interface. This is a third-party freeware gauge available at Flightsim.com, filename rdrwdw.zip. Over a year ago I contacted the authors concerning the use of the gauge, to which they agreed willingly. However, they said thay didn't plan to approach you for accreditation as a new version would be along shortly. Here we are now and there is no sign of a newer version and email to the authors does not seem to get through any more. Several of my beta testers have tried, as well as myself, over the last month or so. So, here I am, on bended knee, asking if there is any possibility of free accreditation of this gauge so that users of my panel will not suffer a disabled feature. Kindest regards, John Hinson http://sftt.co.uk/britannia
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.