• 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.

Yet another feature request

I have added the UNLOADXMLOBJECTS step now. So give it another try tomorrow.
 
Thank you Arno, i tested 4/7 build
unless im doing something wrong (most likely)
im getting no data in my files now with exportbgl (flat400k)
its as if the new unload is performed before the files is saved
 
What's your script?
 
Code: 
IMPORTOGR|D:\OSMDATA\test.shp|*|*|NOREPROJ
#1
PLACEPOINTSALONGLINE|FTYPE=LINE;type=residential|SINGLE|400;400|5;5|200|type|light|hdg
CREATEXMLLIBOBJ|FTYPE=POINT|{7e032006-450c-41a9-b1d6-3a5b56ddbd32}|hdg|0|10|NOAUTOGENSUPPRESSION
EXPORTBGL|FSX|test_A1|D:\OSMDATA
#
#Unload 1
UNLOADFEATURES|FTYPE=LINE;type=residential
UNLOADXMLOBJECTS
 
That looks ok, does the event log report point features are made and xml objects created and exported?
 
yes it does
if i keep my eye on the export dir
i see the xml is built with data initially; once its submitted to resample
it disappear and i get flat files
 
If there is a bglcomp error it should be in the event log as well.
 
Chris, I think you're trying to achieve the same thing as me, lol you're both all over it :D

(now if only I can sort out my other non scenproc related issue of resample.exe crashing when running multiple instances - random crash)...
 
its running now
it performed several steps with the flat files output
i saved the log; bglcomp is nowhere to be found

Code: 
11:34 PM   SceneryProcessor   Information   scenProc finished processing
11:34 PM   SceneryProcessor   Information    0.61 seconds for IMPORTOGR
11:34 PM   SceneryProcessor   Information    0.59 seconds for PLACEPOINTSALONGLINE
11:34 PM   SceneryProcessor   Information    0.92 seconds for EXPORTSHP
11:34 PM   SceneryProcessor   Information    0.66 seconds for UNLOADFEATURES
11:34 PM   SceneryProcessor   Information    0.05 seconds for UNLOADXMLOBJECTS
11:34 PM   SceneryProcessor   Information    124.67 seconds for CREATEXMLLIBOBJ
11:34 PM   SceneryProcessor   Information    18.71 seconds for EXPORTBGL
11:34 PM   SceneryProcessor   Information    146.21 seconds total
 
Last edited:
Dean, thats because you're running too much RAM
32GB is enough; you can send the other 32Gb to Arno to upgrade SDO server :p

joking aside; i work around it by copying resample.exe several time
and running multiple jobs with a different resample executable for each
resample1.exe ---> Job 1
resample2.exe ---> Job 2
resample3.exe ---> Job 3
resample4.exe ---> Job 4
...
 
Last edited:
MyPC8MyBrain said:
its running now
it performed several steps with the flat files output
i saved the log; bglcomp is nowhere to be found
Click to expand...
Check your options to see if it's set right there.
 
hmm... something in particular we are looking for?
it look pretty straight forward to me

if i remove unloadxml step; we are back to the previous result of compounded data


Untitled.jpg
 
Humm, weird. A step never influences a step before it. Let me check later if I can reproduce it.
 
Sorry, forgot to check if i can reproduce your issue. I guess it didn't solve itself yet?

I just dig out an old batch script for some data I have laying around and it seems to run much slower than before and use more memory as well. So I guess I start to see the point of these UNLOAD steps as well now :)
 
But I will also check why loading takes so much longer. I thought one of the smaller files was only a few minutes and now after 30 minutes it still hadn't finished. So I might have made certain things a bit slower :)
 
strange; i experienced exactly the opposite
in fact the first version i run only with few features
it happened so fast; i had to verify i had files there :D

later my combined script went in a fashionable time frame
(slightly faster as everything was fired off one scp script, no batching or reloading in between)
its possible we run different features thats act differently; i mainly run place points along...

unless your referring to initial load time when called via batch script with bunch of attributes
i have noticed this in the past few builds; but attributed this to my file system being little messes up

FYI: i have some very optimized scripts with designated files;
that will run for hours and consume every available bit of RAM (16GB)
those files contain only the necessary data and not one bit more; and still...
 
Last edited:
MyPC8MyBrain said:
Dean, thats because you're running too much RAM
32GB is enough; you can send the other 32Gb to Arno to upgrade SDO server :p

joking aside; i work around it by copying resample.exe several time
and running multiple jobs with a different resample executable for each
resample1.exe ---> Job 1
resample2.exe ---> Job 2
resample3.exe ---> Job 3
resample4.exe ---> Job 4
...
Click to expand...

Ha ha ha. Actually not at all related to Scenproc or RAM ;) , it was on my own program running resample.exe and completely separate from Scenproc and I figured out how to get around it.
 
You must log in or register to reply here.
Back
Top