• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

AeroFly FS 2 support in scenProc

I think that's no matter. When flying over forest, i saw areas from filters 1 and 3, perhaps 2, with problems.
For indication, i downloaded saturday the last devlopment code, and used it with my script having the old function
Code: 
PlacePointsInPolygon|NATURE="Forêt fermée de conifères"|0.0001;0.0001|1.0;1.0|INHERITPARENTATTR
and the problem was here; with version 2 it worked nice.
I changed to PolygonToPoint, but the problem is still here.
I noticed the v3 is very fast; the rendering of a 1°*1° was 3 days with v2, now it's 15 minutes.... my PC is an I5 4Ghz 24Go ram.
 
Hi,

OK, thanks for the feedback. Let me see if I can reproduce something. Both the PlacePointsInPolygon and PolygonToPoint step use almost the same code, so that they behave the same is logical.

The performance of v3 is indeed a lot better, I have improved the internal code a lot.
 
Hi,

I ran quite some tests here, but I have not been able to reproduce the issue. All my trees are nice and random.

So if you would have a test case that reproduces the issue that might help.
 
Hi Arno,
I created a subset of my datas (my shepfile is 3*3° and 1.5 Go).
Here come the shapefile i use (VEG_TEST2_REP.rar), my script (Template_test.rar), my batch command line
Code: 
"F:\Aerofly SF2\scenproc\scenProc.exe" "F:\Aerofly SF2\scenproc\Template_test.spc" /run /log "D:\Geo\0.log" 3;3.25;44;44.25
and the resulting toc file (Veg__N4400_E00300_N4403_E00303.rar).

The area of my previous screen pictures is N44.005 E3.020 (decimal degree) where you can see the change of the tree location distribution, inside the same shape polygon (ID ZONEVEGE0000000293430983, NATURE Forêt fermée de feuillus)

Thanks
 

Attachments

Hi,

I ran your script here on the sample data, but I don't see areas where the trees are not random. What I did is save the point features to a file, so that I can view them in QGIS with the polygons. See the image below.

One other suggestion, in the SplitGrid step you use a filter NATURE="*" to indicate that vegetation should not be split. I don't think that is what you want, as it will result in trees ending up in different tiles than expected. That filter is meant to prevent building polygons from being split into two buildings on the edges of tiles. But in general vegetation is better split.

1582981269100.png
 
Hi Arno,
I tried removing the NATURE filter in the split grid and some parts were corrected, others not...
And yes, i had forgotten the export points to shapefile option, very usefull for displaying source and result in QGIS !
Then i saw there was a new revision (i used the last saturday one) :D ! I installed it and all is nice now (with or without splitgrid filter) for the tree randomness location.
Probably some collateral effect of correction of found bugs...
Again, thank you very very much for your support
 
Glad to hear it also works for you now :)
 
You must log in or register to reply here.
Back
Top