-
Posts
47,111 -
Joined
-
Days Won
53
Posts posted by Nick Cooper
-
-
I suppose it depends on what you are trying to achieve.
I don't think that this is the first airport that Ken Hall has developed.
-
Hello,
changing the ICAO code as you suggest would then fail to exclude the default 61B
and there would still be two active airports at the same place.
-
5 hours ago, jfwharton said:
I do have one question, however, regarding updating the navaids in P3D/FSX. Why should updating the navaids affect the field elevations? I would think that all that would change would be the navaid frequencies, headings (for ILS approaches) and stuff like that. Nothing that would affect the elevation of the airfield.
Basically because the FSX airport database and the addon navigation database do not coincide.
In all cases, the airport elevation is chosen from a fixed point, because in the real world, very few of them are perfectly flat.
In FSX and P3D they are, with a few notable exceptions, all perfectly flat, so if the chosen spot in one database is not exactly
the same as the chosen spot in another, the elevations will not coincide.
The main problem, as already explained many times in this topic, is the presence of two airport versions at the same time.
-
This and many other airports will be made P3D v5 compatible, I feel sure.
- 1
-
That aside, P3D v5 might well change things a great deal.
-
Hello,
the persistent error could be that your default airports have been modified.
If this were to be the case, then the 61B exclude would not work on KBVU and would adversely affect the airport.
You could try disabling G:\P3D v4\scenery\0202\scenery\APX17190.bgl and see if the addon then looks as it should.
-
KBVU and 61B are the same place. It was 61B and now it is KBVU, in the real world.
If a real world ICAO code is changed and then the simulator's navigation database is updated or
an addon is added with that updated ICAO code, then any exclude made for 61B will not work
and the added KBVU version will interfere.
It will do so with both the default airport and any addon.
This is what I suspect here.
If it helps, imagine someone being told to deny entry to a gathering to a person named Smith.
That person arrives, but as she is now married, she is called Jones.
Shouting out "Smith, please leave" still refers to her but she pays no attention, because she is no
longer called Smith.
-
Logically, there is an influence on this airport that other customers do not have.
We seem to have ruled out most possibilities, the most likely being something that updates the airport data
and less likely that you have a remnant of another version that is affecting both your default version, if that
is what you are showing and the addon.
Your image of the addon shows the aircraft "spawned" at a location below the addon which suggests that
either the addon's elevation is not working, highly unlikely given Jack's screen shot topic, or that your installation
contains something that is setting a different elevation.
The presence of an added elevation for KBVU is still my main suspect.
An airport named 61B could not exclude it, either in the default version or in the addon version.
It could be an AI traffic addon too.
There is no way other than what you suggest to return the installation to the root folder.
Where does the addon airport appear in your in-game scenery library?
-
Hello,
it is not the way that Orbx locks stuff, it is the way that P3D locks stuff.
If it installed into the simulator, nothing of Orbx at all is locked.
Are you using someone's mesh?
-
If you have installed this into your P3D v4 folder, can I have a look at your scenery.cfg file please?
-
Did you have a problem here before you added the new product?
-
Looking at this topic, it does not seem that there is an error in the product.
-
Is Vector AEC for 61B actually disabled, can you check?
-
If not, try verify files.
-
Something that updates the airport data.
Fs aerodata for example.
-
Hello,
it has nothing to do with that but with the client.
Are you using a navigation data update?
-
Are you using a navigation data update?
-
Hello,
you need to be using the very latest version of P3D, 4.5.13.32097, are you?
-
Do you have any added anti virus software?
-
Did you try Melanie's solution of uninstalling from Windows first?
-
-
Hello,
if your scenery starts to look like this:
First run Verify files for Global Base and for all your open LC products.
Before posting a support request, please try this fix:
Please try renaming Scenery\BASE\Scenery\lclookup.bgl to lclookup.bgl .off
and then apply this terrain.cfg file fix
Then run Verify Files for the Orbx Libraries and try again.
Please note:
1. that each of these steps must be taken in this exact order, or further problems will result.
2. that the term "Orbx Libraries" refers specifically to the Orbx Libraries product, it does not
mean Orbx products in general.
- 2
-
Thanks, I have cancelled the request to Holger.
-
Hello,
shall we ask Holger Sandmann for his advice?
How to fix Boulder City issue?
in PREPAR3D® V4.x Support Forum
Posted
Hello.
Evidently that would work.
I think Ken has already said that he does not modify default files.
That does not leave that option open to him.
The option remains open to anyone willing to go down that path for themselves.