-
Posts
47,093 -
Joined
-
Days Won
53
Posts posted by Nick Cooper
-
-
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.
-
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?
-
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.
-
Anything's worth a try.
-
Hello Dave,
I have split this from where you added it.
However, I cannot replicate the problem.
-
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.
-
2
-
-
Thank you but this topic is for software that does work.
I have edited your topic to reflect this.
-
Hello,
at the moment, no, not least because for now, the P3D method is broken.
-
1
-
-
Hello,
Thanks for reporting this.
Hopefully it will join the long list of similar reports that are not yet fixed.
-
No, it is a wish for your good luck.
-
Clearly this area is more than important to you.
It perhaps begs the question why you did not purchase PNW instead.
Nevertheless, it is only a flight simulator.
Removing Vector will impact the whole of the rest of your flight simulator
for the sake of one river estuary.
You can apply for a refund using the ticket system.
Good luck with that.
-
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.
Here is how it is portrayed by Vector.
and here is how it is portrayed in PNW
-
Hello,
I have been advised that what I am seeing is PNW, for which I apologise.
I should have realised this.
Vector has not been fixed in this respect.
-
I will pass this on internally for attention.
I am still stuck with my own fresh installation having the update but let's wait for a comment.
-
Hello,
as far as I am aware, I have the same files as the customers and I admit to being mystified
as to why you should not be seeing the correction.
Ideally, we need someone else who is also a customer to check the area for you and see what they see.
If they have the same problem, I can refer it back to the developers but on the face of it, it has been fixed
but you don't seem to have the fixed files.
-
I am so sorry that you found my post unhelpful.
As I have the products correctly installed and there is no trace of the error here,
I am unable to replicate what you see or offer you any further advice.
If you have installed everything correctly, you will need advice from someone else
who has recently downloaded and installed Vector in case somehow you have
downloaded a version without the updates.
I cannot help you with that.
Sorry.
You could try deleting ORBX\User documents\Versions\FTX_GLOBAL_VECTOR_PACK.txt.
If you then open FTX Central, Vector will show as not installed.
If you click on install product, FTX Central will check all the files and update them as
necessary.
It must be worth a try.
-
Please see my screen shots which have nothing but FTX products.
Thanks.
-
Hello,
This is Vector version 1.52 here.
-
Hello Don,
you have an open topic showing you that the airport itself is not broken.
Please don't request the time of a developer for something that is most likely a problem
on your PC.
You will see that I have answered the topic and it is awaiting your attention.
Thanks.
-
Hello.
This topic is not intended as a substitute for support requests and is not designed for everyone.
It is not intended as anything other than a simple guide to a means to fix a common occurrence.
If you are prepared to follow the guide below, please do.
If you see an error such as this in an FTX airport but do not wish to fix it yourself, please
simply make a report in the appropriate support forum.
-------------------------------------------------------------------------------------------------------------------------------
Sometimes, airport taxiways will appear to have missing sections in P3D.
There is a fix for this, it involves the use of the freeware Airport Design Editor.,
opened for P3Dv4.
First, select this choice and navigate to the airport bgl file.
select Taxi Links
a window will open with a list of them all
click on Select all
once you have selected them all, click on Edit and adjust the Draw Detail and Draw Surface settings
to "Yes".
Click on Done.
then click on Compile and in this window, make sure that the Compile File Name is identical to the
name of the file that you are editing.
Compile the file and copy it over the existing file, that you did of course back up first.
If you find this helpful, you are welcome.
If you find it offensive that a suggestion should be made that errors can be fixed by the customer,
please remember that there is no obligation at all to do this and support for such errors is freely available.
If you do wish to learn this simple technique, it can be applied to any airport that displays the error and can
be opened in ADE, whether payware or freeware and by any developer.
-
6
-
2
-
-
Hello,
you will see that I have marked this as noted and pinned it.
Hopefully it will be added to the list of things to be fixed.
-
Hello,
it looks as if Vector has misread the numerous gullies as rivers.
-
1
-
-
Thanks.
The omission is Vector's, so I have moved your topic to the Vector support forum.
-
Hello Greg,
The troubleshooter is for products that require migration.
Both EU Germany North and Open LC South America are
new and do not require migration.
ORBX VECTOR stutters in EGSQ
in Orbx Global Vector Support
Posted
No problem, I am assuming that it must have worked for you too.![:) :)](//content.invisioncic.com/t324365/emoticons/default_smile.png)
I am only the messenger here, I asked for a fix and Holger Sandmann identified the problem
and provided the fix.
All credit is due to him.