Jump to content
The simFlight Network Forums

winsaudi

Members
  • Content Count

    492
  • Joined

  • Last visited

  • Days Won

    19

Posts posted by winsaudi


  1. Right, this is what has annoyed me.  I see it as lazy, unprofessional and unbecoming in a commercially sold product.  There are quite a few errors in "Real Traffic" but this one gets under my skin.

    There are multiple uses of the same aircraft registration in the edds_gaandlocaltraffic file.  That would be OK to reflect, for example, an arrival of an aircraft and its departure; however, this is not the case for many lines in the "Real Traffic" addon for EDDS. Using just one example of many, have a look at the following 6 lines:

    EDDS, EDSB, 06:15, PL2, DHHSA, 0, 1, 0, DHHSA, DELTA HOTEL HOTEL SIERRA ALPHA
    EDSB, EDDS, 06:16, CJ5, DHHSA, 0, 0, 0, DHHSA, DELTA HOTEL HOTEL SIERRA ALPHA
    EDDS, EDDM, 07:05, H25, DHHSA, 0, 0, 0, DHHSA, DELTA HOTEL HOTEL SIERRA ALPHA
    EDDS, EDZF, 08:59, BEC, DHHSA, 0, 0, 0, DHHSA, DELTA HOTEL HOTEL SIERRA ALPHA
    EDSB, EDDS, 13:47, SR2, DHHSA, 0, 0, 0, DHHSA, DELTA HOTEL HOTEL SIERRA ALPHA
    EDDM, EDDS, 15:08, DF9, DHHSA, 0, 0, 0, DHHSA, DELTA HOTEL HOTEL SIERRA ALPHA

    1. So "Real Traffic" uses of the registration D-HHSA for 6 different aircraft types!  A quick search on the web shows that D-HHSA is actually a Robinson R22 Beta II helicopter.

    2. The timings conflict, the first line has PL2 D-HHSA off chocks at Stuttgart at 0615 but then it also calls up for arrival just 1 minute later as a CJ5.

    3. It is not even dep/arr/dep/arr/dep/arr; it is dep/arr/dep/dep/arr/arr so it departs twice before arriving twice.

    I'm sure these problems will result in some aircraft 'no shows' as will the other multiple-use of aircraft registrations.  Very disappointing. Laziness? Amateurish? But not "Real Traffic".

    BTW, the first "Delta" in the callsign can be dropped just like the "November" for US registered GA.  I have modified my callsigns but have used snips from the original "Real Traffic" file above.

    @hexzed  Ben, I'm looking forward to your custom schedule!


  2. No problems VG, your information is normally first class.

    Changing the subject slightly, I am a little perplexed by the inclusion in RC EDDS of the B733_ag.  There are no AG flights in edds_schedule and in edds_airlines it links to ASL Airlines Ireland (ABR), but according to the IATA website the AG code is allocated to Aruba Airlines (ARU).  I'll add a few AG flights to the schedule and see what turns up.


  3. 6 hours ago, VenturaGuy101 said:

    RLA|A5: {AIRLINAIR} Airlinair, France
        E170: EMBRAER 170, REGIONAL JET [EDDS]

     

    VenturaGuy101,

    Your list is mainly correct but the A5 E170 is HOP (HOP! Air France) not RLA Airlinair.

    Also included in Texpack 15 (and not in your list) are: A319_he.jpg / A320_he.jpg / DH8D_he.jpg / A321_8q.jpg / B733_ag.jpg
     


  4. Gabor,

    I don't think the following flights in kmem_schedule.txt can appear either:

    EWR, MEM, ER4, C5, 4917, 21:57, 12:00, 1, C5

    EWR, MEM, ER4, C5, 4916, 16:49, 12:00, 1, C5

    MEM, EWR, ER4, C5, 4913, 12:00, 17:50, 1, C5

    MEM, EWR, ER4, C5, 4932, 12:00, 16:09, 1, C5

    This is because there is no corresponding UCA in kmem_terminal.txt

     


  5. Gabor,

    I don't think the following flights in kmem_schedule.txt can appear:

    BFM, MEM, AB6, FX,  860, 09:58, 12:00, 1, FX

    BFM, MEM, AB6, FX, 1350, 22:16, 12:00, 1, FX

    MEM, BFM, AB6, FX,  746, 12:00, 16:16, 1, FX

    MEM, BFM, AB6, FX, 1526, 12:00, 03:48, 1, FX

    This is because there is no BFM airport in kmem_airports.txt as there seems to be an error with this line:

    BMF MOBILE_AL_USA                             30.37 N  88.04 W KBFM

    I think it all should be fixed by changing that line to: 

    BFM MOBILE_AL_USA                             30.37 N  88.04 W KBFM


  6. Kev M,

    You are not wrong mate and Craig is also spot on.  IMHO far too many of the threads on this forum are because of:

    1. Installation problems; smart installers from the software developers are a must.

    2. Voice recognition/sound problems; what guidance on this matter comes with the email confirming your purchase of T3D? Nil?  I couldn't get it to work until this forum got me through the setup stages.

    3. How to get any updates; where in the purchase process does it tell the buyer to keep the original download links to get any future upgrades?

    These are 3 key areas where I think FT & ND are letting customers down; great products not so well supported.  How many people have bought T3D and have had one of these 3 problems but are unaware of this forum with its cluster of knowledgeable & helpful members?  I shudder to think.

    A bit more support/information with the original purchase would go a long way with more happy customers, fewer pleas for help, and a boost to the customer satisfaction levels with FT & ND.

    Vic/Ariel/Gabor:

    This post is a bit of tough love and meant with the best of intentions.  But what about a 'Welcome to T3D email' for new purchasers with clear advice on installations, voice recognition setups, etc?  But don't worry, I'll keep buying your products as they give me days of fun getting them to work!! 🙂 

    Wayne

     


  7. 21 minutes ago, crbascott said:

    Wayne, this is not a BMT Micro issue.

    If you look at your Pro and airport receipts, you'll notice there is not an expiration date. FeelThere has wisely chosen not to implement an expiration date. However, the same cannot be said for Nyerges Design as they've decided to implement an expiration date on their RT and RC products. A very baffling decision since RT is constantly updated which ultimately requires every customer to contact BMT Micro as some point tin time. 

    Craig,

    Many thanks for your explanation.

    Gabor,

    Can you have a look at changing the Nyerges Design process with BMT Micro?  These expiring links are annoying especially with time zone differences and weekend differences that add further delays to getting the latest versions of the addons.

    Thanks, Wayne


  8. If @AirJamaica is correct the "Current Versions Sheet" has yet to be updated as well, and what about Real Traffic? Has that been updated?

    I cannot verify that either RC KLAX or RT has been updated as I am waiting for BMT Micro to refresh my links, once again. Surely there has to be a more user friendly way than having links that constantly expire? Come on BMT Micro, think of a better way!


  9. Pdubya,

    I have a completely different understanding on this matter than your idea that contributors will make the liveries, my understanding is that those public spirit members that write custom schedules will give Nyerges Design a wish list of which aircraft/airline liveries are missing from the current RC packs and ND is asked to add these extra liveries to the relevant RC package. So format, fidelity etc still remains in the hands of Gabor at ND.

    Wayne


  10. Joe,

    Many thanks for a look at Gabor's fine work.  I hope the release of the new RC KLAX & RT is not too far in the future.  Included in your list of 'New To KLAX' (but available in other RC packs) - I see  Alaska 737-900 & Frontier A319 but in the current (old) RC KLAX airplanes_texpack03.manifest are the following lines:

    - Assets/Resources/airplanes/Textures/B739_as.jpg

    - Assets/Resources/airplanes/Textures/A319_f9.jpg

    So it seems those liveries are already available for old RC KLAX users. 

×
×
  • 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.