Hi everyone,
I use P3D V5.3 HF2, CPU i7 9700, RTX 3060TI, SSD.
Title may be a bit confusing, but I tried to find a similar problem on the web, with no success.
I want to implement photoscenery on the south part of Quebec province in Canada. Very large area. I use SBuilderX to download tiles of 100 km x 50 km, at LOD14. Each BGL file is around 900 MB, which includes 4 seasons, night and blend/water mask.
I then use QGIS to process OSM landuse shapefiles for each area. And next, I use ScenProc to produce the Autogen files. I also do this process for buildings and other features.
When checking my scenery at different airports, I noticed that at CSF7 Casselmann, there is a large forest going through the runway, the plane facing from north. I also realized that those trees are not material. I can go trough them without crashing. (I did a test on other autogen, and crash occurred...) And, when I run through these trees, they disappear when looking on each side or backward. After more verification, I know that this problem occurs elsewhere. I have to mention that the Autogen process produce around 2,500 files for each photo tile.
In ScenProc (I have the latest dev version v3.1.0.0 re87ce1b0 DEV 2022-03-20)), I tried different approach to process the forests. Polygons directly from the shapefile, ReplacePolygonByVegetationRectangles, and PolygonToPoint, at different level of precision. I tried to download the shapefile a second time, same problem.
I also went in Annotator to see if trees are created at this location, but they do not exit there.
Another annoying event is that large areas of forest (which may or may not real) appear and disappear depending on the direction of the flight...
As another test, I did a photoscenery only for the CSF7 airport with autogen trees for this local area. No problem there.
I want to mention that I do photoscenery and autogen on a regular basis. First time I do it on this scale, and that this problem occurs.
So, I suspect that the size of my photoscenery may be the cause, but I cannot confirm. Also, if I a have to reduce the size, what is the maximum that I can process.
Before I provide more information, is there anyone who have or had this problem, and how it can be solved?
Thanks in advance
Richard
I use P3D V5.3 HF2, CPU i7 9700, RTX 3060TI, SSD.
Title may be a bit confusing, but I tried to find a similar problem on the web, with no success.
I want to implement photoscenery on the south part of Quebec province in Canada. Very large area. I use SBuilderX to download tiles of 100 km x 50 km, at LOD14. Each BGL file is around 900 MB, which includes 4 seasons, night and blend/water mask.
I then use QGIS to process OSM landuse shapefiles for each area. And next, I use ScenProc to produce the Autogen files. I also do this process for buildings and other features.
When checking my scenery at different airports, I noticed that at CSF7 Casselmann, there is a large forest going through the runway, the plane facing from north. I also realized that those trees are not material. I can go trough them without crashing. (I did a test on other autogen, and crash occurred...) And, when I run through these trees, they disappear when looking on each side or backward. After more verification, I know that this problem occurs elsewhere. I have to mention that the Autogen process produce around 2,500 files for each photo tile.
In ScenProc (I have the latest dev version v3.1.0.0 re87ce1b0 DEV 2022-03-20)), I tried different approach to process the forests. Polygons directly from the shapefile, ReplacePolygonByVegetationRectangles, and PolygonToPoint, at different level of precision. I tried to download the shapefile a second time, same problem.
I also went in Annotator to see if trees are created at this location, but they do not exit there.
Another annoying event is that large areas of forest (which may or may not real) appear and disappear depending on the direction of the flight...
As another test, I did a photoscenery only for the CSF7 airport with autogen trees for this local area. No problem there.
I want to mention that I do photoscenery and autogen on a regular basis. First time I do it on this scale, and that this problem occurs.
So, I suspect that the size of my photoscenery may be the cause, but I cannot confirm. Also, if I a have to reduce the size, what is the maximum that I can process.
Before I provide more information, is there anyone who have or had this problem, and how it can be solved?
Thanks in advance
Richard