Jump to content

Nick Cooper

Administrators
  • Posts

    47,108
  • Joined

  • Days Won

    53

Posts posted by Nick Cooper

  1. To pilot_17

    There is no intransigence, only inaction from  the Vector developers.

    It helps no one to constantly repeat the same complaint, just as it helps

    no one to constantly point out the same error.

    The topic has been comprehensively answered, even though the answer is not satisfactory.

     

    To Gestacon:

    welcome to the forums.

    If you have identified a new area that you believe to be defective, please start a new topic in the 

    Vector forum, ideally providing the exact coordinates and a screen shot if possible.

    Thanks.

     

     

  2. Hello,

     

    a great many answers to support requests depend on knowing a few basic facts.

     

    It would be very useful to us if you, the customers, would consider adding to or editing

    your signatures to include the specifications of your PC, the Operating System

    that you use and your flight simulator(s).

     

    Just these basics would be ideal:

     

    PC: CPU, RAM, Graphics card, Windows version, FSX version, P3D version

     

    There is now no requirement to include a transaction number in your signature, one in the order number box

    in your profile is enough.

     

    Many thanks.

    • Upvote 3
  3. Hello,

    Thanks to Holger Sandmann here is a "hotfix".

     

    This will solve the stutters at Clacton but will also remove the Vector surf effects.

     

    Either: Move your special effects slider to zero

     

    or: Please go to ORBX\Scripts\unified\regions and back up terrain_global_v.cfg.

    Then copy the attached version into its place.

    Run FTX Central and wait for it to Activate Orbx scenery.

    terrain_global_v.cfg

  4. Ryan.

     

    Please don't lecture me.

    I have spent years in this forum attempting to provide the missing support.

     

    I have explained who is responsible for this fix and reported it yet again.

     

    Everyone has to pay for Vector and I do not need to be reminded that

    in the case of Vector, I am also a paying customer with reservations about

    the level of support that it is given.

     

    You should clearly understand that:

     

    1.This problem appears to have been raised well over three years ago.

    The developers were made aware of it at the same time.

    Since then, there have been numerous reports of the same problem.

     

    2.The developers are a separate company, Pilot's.

     

    3. It is that company that was and possibly is responsible for that product's support.

    Orbx staff do not have the source files.

     

    4. Numerous company requests for this and other anomalies to be fixed have been submitted.

     

    I would agree that it is not satisfactory that after all this time, this error should still be present.

    Nevertheless, everything that can be done to expedite this and other reported matters has been done and

    we must apparently wait for Pilot's to take some action.

     

    On a slightly lighter note, I see that the fact that your Clacton runway apparently spans a small lake with

    no visible means of support does not concern you?

     

  5. Hello,

    as has been mentioned, this is not a new issue.

    I have no idea why the developers of Vector, Pilot's, have not addressed this in the past,

    I see topics from over three years ago and passed to the developers but the issue appears to remain.

    I understand that they are at some point going to produce a Vector 1.60 but no sign yet and no indication

    as to whether this will be addressed in any case.

     

  6. Hello Carl,

    I believe that we are waiting for Vector version 1.60.

    The fix to the Vector control panel is supposed to be part of that.

    You will remember that we released Vector for P3D v4 without the fixed version

    and no one has seen a trace of an alleged update yet.

    At least we are not all still waiting for Vector for P3D v4 but what is happening

    about the outstanding matters, I have no idea.

    In this case, I am a paying customer also and I don't think you will find anyone

    who feels that it has received the support it deserves from the developers.

    • Like 2
  7. Hello.

     

    1. Done

     

    2. None at all, as you must now be aware, I thought it had been fixed and I have no idea why it has not.

     

    3. It does not fix the issue, it simply disables that part of Vector and leaves the default coastline.

     

    4. As you see in my screen shots.

     

    5. You can try, I would consider it unlikely that a global product, always advertised as being improved, is likely

    to be refunded for a few square km of land that is not strictly accurate.

     

    Here is a reminder that the error is this:

    Whatever data that is used has read the area as land when it appears to be mudflats,

     

    here is Doug's Google Earth image.

     

    CYVR.png

     

    Here is how it is portrayed by Vector.

     

    CYVRw-Vector.jpg

     

    and here is how it is portrayed in PNW

     

    Untitled.jpg

×
×
  • Create New...