Jump to content

The new Vector 1.51 has error exception windows...


Recommended Posts

25 minutes ago, Nick Cooper said:

There hasn't been a 1.50 update has there?

Lots of requests to modify the text file to 1.45 though.

To shermank, the duplicate files error message, though you had uninstalled?

Hi Nick, and all.....I realized the error message I got was not the one posted earlier. Mine occurred during the DL from FTXC...

 

 

YBiWtdX.jpg

 

I am currently downloading 1.5 through OrbxDirect and into FTXC....and will see how things go...using the extraction tool you posted earlier

 

Link to comment
Share on other sites

8 hours ago, PNW User said:

OK...here's the deal....you CAN NOT update to v1.51 from an already installed Vector product. You will get a broken AEC function.

 

You need to uninstall your current Vector v.x, and install a full, clean Vector v1.51

 

I just saw this topic.

 

2 hours ago, I tried to update Vector to v1.51 from an already installed Vector product using FTX C v3.

I had an error first. Then I cleared the temp in FTX C v3, and updated again: after 27 mins it was done.

I ran AEC twice without problems.

 

Am I just lucky?

Should I uninstall completely (what is the best way?), then reinstall using my downloaded zip (that I got just in case)?

Link to comment
Share on other sites

Hello,

This may be a temporary fix to avoid the need to re-install.

The error seems to be happening when the auto configuration is run.

For now, after you have installed the update and before you run the

auto configuration, please go to your ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery

folder and delete these files.

 

APT_BISF.inactive 

APT_BIAR.inactive

APT_BINF.inactive

APT_BIRK.inactive

ABP_BISF.inactive

ABP_BIAR.inactive

ABP_BINF.inactive

ABP_BIRK.inactive

 

I am locking the topic, because we have acknowledged the probable error and offered a temporary

fix.

There is no value in any more posts of "me too" but of course if any different errors are experienced,

please create a new topic.

I can assure you that we are working as hard as possible to fix this which did not occur after pre-release

testing.

Apologies for the inconvenience caused. 

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...