Nick Cooper
-
Posts
47,111 -
Joined
-
Days Won
53
Posts posted by Nick Cooper
-
-
Hello Carlos,
do you still have a copy of the picture?
It must have been some time ago.
-
Hello,
nothing is happening to the "roof textures" at all.
What we are all seeing is the default P3D v5 buildings superimposed over the Orbx product buildings.
-
1
-
-
Hello,
I think you are just removing the P3D v5 default buildings, that's all.
-
1
-
-
Hello,
I have no idea, I am afraid, apologies.
-
Hello,
I wonder why you are asking the question here, when the problem seems to be that of "PP".
I also think that it is unlikely that an X plane 11 developer will be routinely visiting the
General Discussion - NO SUPPORT REQUESTS HERE PLEASE forum.
-
11 hours ago, Cannow said:
I think you are seeing stock airport
Hello,
it looks like the KSAN product is not working in the same way as it does in P3D v4.
I will draw this to the attention of the developer.
-
2
-
1
-
-
- Popular Post
Hello,
one can read many complaints that there is no improvement, it is worse, it doesn't work etc etc.
The simple answer is indeed to read the instructions for installing the new version and then follow all of them.
Please read through all of the following text before starting the process.
Regardless of where Orbx products or addon aircraft are installed, the P3D installer will leave them alone because it can only
uninstall files that it installed in the first place.
1. using the Windows control panel, uninstall the P3D v5 client and when asked if you want to deactivate P3D v5, answer No.
2. Then uninstall the content and then the scenery and finally the top P3D v5 entry in the Windows control panel.**
3. You will now be left with a P3D v5 root folder that contains only files that you have added. If you added none, it will be empty.
EDIT 12th June 2021: Please Note: In most cases, the uninstallation of the client will completely remove the ShadersHLSL folder.
If your P3D v5 root folder still contains a ShadersHLSL folder after the P3D Client has been uninstalled, the ShadersHLSL folder should be manually deleted, as it must contain amendments added by the user or third party software that will cause problems with P3D v5.2.
4. Run Setup_Prepar3D.exe in your decompressed download from your P3D account as an administrator.
Make sure that the target directory is the one you are left with after the uninstallation.
Unless you installed to the default location, you will need to make a change.
Wait until the process is complete. You will not be asked to activate P3D again.
If you had everything installed inside the P3D folder,
Global Base must be uninstalled and installed again.
You must run Verify files for all open LC products.
You must run verify files for the Orbx Libraries.
For good measure, also run Sync Simulator.
To find Sync Simulator, Click Settings -> Help -> Sync Simulator.
If you had everything installed outside the P3D folder, then this is the advice from Ben.
QuoteIf you have installed your Orbx products into a library (i.e., outside the simulator), when you uninstall v5 your Orbx products will still remain installed, but just not linked to your simulator.
Then, once you've installed v5, open Orbx Central. Click Settings -> Help -> Sync Simulator. That will edit your Prepar3D add-ons.cfg, re-adding the Orbx library path and automatically linking your Orbx scenery again.
Once you have completed these steps, you must at least rename or delete your
C:\Users\your user account name\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg file
and let P3D build a new one.
You might need to delete the P3D v5 shaders at C:\Users\your user account name\AppData\Local\Lockheed Martin\Prepar3D v5\Shaders.
You can delete the entire Shaders folder.
Ideally, you should run the P3D\Delete Generated Files batch file but it will leave every setting back at default.
If you have spent time on controls settings, for example, you will lose them all. It's up to you.
If you do decide to run the batch file, be sure to run P3D at least once after that and before you run Settings -> Help -> Sync Simulator.
Based on my own experience, doing all of this and nothing else will leave you with all the features of the Hotfix or update working as promised and your Orbx products intact.
EDIT 10th June 2021: Now that P3D v5.2 has been released, it has become clear that unless the user installs at least both the updated Client and the updated Content, anomalies will occur, not least in the operation of the simulator.
For this reason a full reinstallation of all three parts is recommended.
Notes:
** 1. Following a customer question, these are the four entries referred to in line 2.
UPDATE 14th June 2021It would appear that LM may have made changes that break this installation process.
You should not experience this if you downloaded the full installer before this date.
If you experience missing default textures after reinstallation, run Repair for the Client module.
-
23
-
3
-
14
-
Hello,
in the case of FSX Steam Edition, this problem will typically occur when the customer runs the Steam Verify files function.
This overwrites numerous Orbx files.
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.
-
- Popular Post
Hello,
it seems that this is a fairly common problem.
The reason is usually that the Orbx version of the lclookup.bgl file has been replaced with another one, usually the default version.
The second reason is also because the Orbx edits to the terrain.cfg file have been replaced, once again usually by the default version.
Both these files are crucial to the correct display of Orbx Global base and all the open LC products.
It is important to be aware that if the Delete Generated Files batch file in the P3D root folder has been run, the terrain.cfg file will have
been restored to its default state. Similarly, if an update to the P3D version or even a re-installation of the existing version has been
carried out, the lclookup.bgl file will also have been returned to its default state.
These are not the only causes of this problem, but they are the main ones.
If your scenery starts to look like this:
First run Verify files for Global Base and for all your open LC products and
the Orbx Libraries to rule out the possibility of missing files.
If this does not work:
1a. If your Orbx Libraries are installed into the P3D folder
Please try renaming Scenery\BASE\Scenery\lclookup.bgl to lclookup.bgl .off
Run Verify files for the Orbx Libraries which will replace the lclookup.bgl file.
1b. If your Orbx Libraries are installed into an Orbx Central Library, please do not rename
Scenery\BASE\Scenery\lclookup.bgl to lclookup.bgl .off
2. Rename C:\ProgramData\Lockheed Martin\Prepar3D v5\terrain.cfg to terrain.cfg.off
3. Run P3D v5 once to create a new terrain.cfg file and close it.
4. Then run Settings\Help\Sync Simulator in Orbx Central which will write back the Orbx entries.
5. Then try P3D 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.
-
9
-
2
-
10
-
Thanks, did you see a green notification before you left the Insertion Point page, that it had made the changes?
-
Thanks for these comments.
I have asked the developers to come to the topic and comment.
-
1
-
-
Hello,
it reads as if you have not set the Orbx Central Insertion Point.
It should be Airports and Regions just below the lowest of your other developers' add-ons
and open LV just below Regions and Airports.
-
-
Hello Patrick,
can you be specific please?
-
KBVU.
61B is no longer there.
-
1
-
-
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.
-
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?
Poll: An OpenLC solution for Asia
in General Discussion
Posted
I think it may already be back.