FSDreamTeam forum
Products Support => Las Vegas FSX/P3D => Topic started by: RALF9636 on January 19, 2018, 12:45:58 pm
-
I just installed FSDT KLAS, updated to the newest version, P3DV4.1.
I have the problem that the photoreal ground textures of Megascenery bleed through the surface as if the ground of FSDT KLAS is semi-tranparent. In the attached picture you see for example the photoreal aircraft which come from Megascenery Earth Nevada. It is not connected to FTX SCA. The problem exists no matter if SCA is activated or not (I executed all the steps top make it compatible and have no elevation issues).
I also tried with FSDT KLAS deactivated and the default airport: no bleed through problem with Megascenery.
Also I have tested for example FSDT KLAX over Megascenery California without such a problem.
I figured the file AP_KLAS2.BGL is the afcad file. I deactivated that file and the bleed through problem was gone (of course all kinds of other problems occured without an afcad file). But that showed that something seems to be wrong with this file.
Can you reproduce the problem or have any idea what causes this?
-
I too have this issue. Attempted a re-install but nothing changed.
-
The problem is not obviously KLAS scenery and it's correctly made this way (the AFCAD doesn't have a solid apron), because it comes with OUR background photoreal scenery so, you are supposed to see that one, not other sceneries in conflict.
This should normally be solved by having the airport on an higher layer in the Scenery Library. Which is where our installer place it by default (for a reason). But if you moved or installed other 3rd party sceneries *after* KLAS was installed, or used 3rd party utilities to rearrange the ordering of sceneries, you must rearrange the Scenery Library to have KLAS on top of everything that might conflict with it.
Airports should always be on top of everything else, as a general rule.
-
The problem is not obviously KLAS scenery and it's correctly made this way (the AFCAD doesn't have a solid apron), because it comes with OUR background photoreal scenery so, you are supposed to see that one, not other sceneries in conflict.
This should normally be solved by having the airport on an higher layer in the Scenery Library. Which is where our installer place it by default (for a reason). But if you moved or installed other 3rd party sceneries *after* KLAS was installed, or used 3rd party utilities to rearrange the ordering of sceneries, you must rearrange the Scenery Library to have KLAS on top of everything that might conflict with it.
Airports should always be on top of everything else, as a general rule.
I have KLAS above Megascenery in the library of course.
Somehow the lower Megascenery photoreal layer seems to take priority over the photoreal scenery that comes with KLAS even though the latter is higher in the scenery library. I did not see that with any other airport and I have a lot of airports on top of Megascenery, including other FSDT airports like KLAX.
-
Just to confirm my scenery library should look something like this?
Just to note that all the scenery you see can not be moved. Below that included other sceneries that can be moved. I uninstalled both Aerosoft Vegas City and KLAS Airport and this is how it ends up.
-
As above ^
-
Just to confirm my scenery library should look something like this?
Yes, that seems fine.
The only way a lower-priority scenery could take precedence over an higher priority scenery, would be if it's a mesh scenery with an higher resolution. However, only the mesh itself (altitude data), should be seen, maybe causing elevation issues, but not the photorealistic part, which should come from the scenery on top.
Have you tried disabling Megascenery ? At least this would confirm that's the conflicting scenery, not something else.
-
I don't use Megascenery.
The only other scenery in this region is the Aerosoft Vegas City and ORBX Global + OpenLC North America (I also only have Northern California installed and not Southern). At this point I am at a loose end.
-
The attached image shows my KLAS with Megascenery (and also AS US Cities Las Vegas) deactivated.
The photoreal aircraft are gone but I am not sure if this is how it is supposed to look because parts of the apron have a different colour and less sharpness than others, so maybe there still is something shining through.
-
I can confirm that Aerosoft's Vegas seems to the conflict. I uninstalled and as above see no more photoreal aircraft.
Should we contact Aerosoft?
-
Yes, Aerosoft's US Cities Las Vegas comes with a photoreal layer too (I deactivated that one because I use Megascenery), so that must be the one you see if you don't have Megascenery.
But that shows that it is not an Aerosoft or Megascenery specific problem because the problem occurs with both of these addons which include a photoreal coverage of the airport.
The problem is that FSDT KLAS does not completely overlay that photoreal layer as airports normally do, for example FSDT KLAX does it fine with Megascenery California.
-
The problem is that FSDT KLAS does not completely overlay that photoreal layer as airports normally do, for example FSDT KLAX does it fine with Megascenery California.
That's not the problem. As I've said in one of my previous posts, KLAS doesn't overlay a photoreal scenery, because it comes with its own photoreal scenery so, if it was made to cover up a photoreal scenery underneath, it would end up covering its own photoreal scenery too.
So, the real issue is not how the KLAS AFCAD is made (it *must* be made that way, just like any other airport that comes with a photoreal scenery in the background), but why the Aerosoft photoreal is "winning" against the KLAS photoreal, even if it's on a lower layer.
Are you sure it's not coming with a mesh too, maybe one that is of a (nominally, not real) higher resolution than FSDT KLAS mesh ? If that scenery comes with a mesh .BGL and it's a separate file just for the mesh, a possible solution might be removing just that file.
-
First let me thank you for your continuous effort to help me solve the problem.
As I said it is not connected to Aerosoft US Cities Las Vegas specifically. I have deactivated Aerosoft Las Vegas but kept activated Megascenery Earth and I still get the photoreal image with the photoreal aircraft visible. And I am quite sure Megascenery does not have its own mesh, at least all files are either named "...aerial...bgl" or "...POI...bgl", no file is called "...mesh...bgl".
And I repeated the test I already mentioned in my first post: I deactivated the file AP_KLAS2.BGL (by renaming to ...bgl.off) and the photoreal aircraft were not there anymore. What I saw was probably the photoreal image of FSDT.
So that file must somehow affect what photoreal image is shown.
Another thing I noticed which might help to track this down. The photoreal aircraft only appear close to my position. They pop up when I get closer as if a new LOD-step would be loaded at that time. So may be Megascenery has a higher maximum LOD than the FSDT photoreal image and takes priority as soon as the maximum LOD is loaded?
-
Just an FYI I have reset my PC (due to other scenery issues and a bit of a clean up) so will try both these sceneries before anything else.
-
I can confirm that for me... with just the Aerosoft Vegas City installed and FSDreamteam KLAS, the issue still persists. Until there is a true explanation I think I'm done with this scenery for now.
-
Until there is a true explanation I think I'm done with this scenery for now.
You mean the Aerosoft scenery ? Because, according to your own report:
I can confirm that Aerosoft's Vegas seems to the conflict. I uninstalled and as above see no more photoreal aircraft.
Is the one that is causing the problem to begin with. In any case, we'll try to get in touch with the scenery developers if they have any ideas about this.
-
I had this problem also, but I don't have MSE or Aerosoft Las Vegas installed, only FSDT and Orbx NorCal and FTX Global.
Was there any resolution to this issue?
Cheers, Rob.
-
I finally had some spare time to have a look at the Aerosoft Las Vegas scenery (but I believe it's the same with other similar products), and the issue is they have a photoreal terrain which is of higher resolution than our own, LOD17 ( 30 cm/px ), compared to LOD15 ( 1mt/pixel ).
If you set the Texture resolution ( not the Mesh resolution ) to be higher than 1 mt/pixel, the sim will try to load the higher resolution textures even if the scenery is on a lower priority layer. This has always been the case for meshes, but it seems to be new for photoreal terrain.
And, since the US Cities Las Vegas developers didn't removed the airplanes from their photoreal background, they will show up, because the FSDT KLAS is designed to be used *together* with the photoreal background that comes with it, so it's partially transparent.
If you set the Texture resolution to 1mt/pixel, the sim will then use the photoreal background that comes with the FSDT KLAS, as long it has a higher priority in the Scenery Library.
The only solution from our side, would be creating a new photoreal background with at least 30 cm/px resolution, but in the meantime, setting the resolution to 1 meter should work.
Also, it might be best to remove the KLAS AFCAD from the Aerosoft scenery:
\Prepar3D v4\Ecosystem\aerosoft\USCitiesX-LasVegas\Scenery\AF2_KLAS.BGL
And this file from the FSDT installation folder:
\Addon Manager\FSdreamteam\KLAS\scenery\mesh_terrain.BGL
-
We made a new photoreal background for KLAS at LOD17. It's not different than the existing one, but at least it won't be covered by other photoreal sceneries from other developers (with airplanes in...) when the texture resolution is set higher than 1mt/pixel.
As usual, it can be obtained by running the FSDT Live update.
-
Thanks Umberto, I'll give it a try.
Just to clarify my situation, I don't have AS US Cities Las Vegas installed (never had it installed at any point). PILOT's mesh, Orbx FTX Global, NorCal currently installed and FSDT KLAS.
Cheers, Rob.
-
I guess that, when you said you had this problem, of another photorealistic scenery shining through (which maybe you recognized because the airplanes, which we surely don't have in our scenery), that other scenery was made in a similar way so, just having a LOD higher than ours, allowed it to show, regardless of its priority.
I guess this is how the sim was designed to work: by assuming the scenery with the highest LOD "must" be the better one, but it's clearly not always the case, and it will cause issues for sceneries like KLAS, which were designed to work together with their own photoreal scenery and wouldn't look right with another one.
But this should be fixed now, until someone will came up with a LOD18 photoreal...