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

Point placement accuracy

Hi Darren,

I also checked the heading now. A while ago you reported an offset by PM if I remember correctly.

What I did is place XML object and autogen objects using the same point features. The only issue I had is that for the XML objects I needed to apply a -90 offset. But after that the two objects aligned perfectly.

So I don't think there is a small heading offset anymore in the autogen library objects.
 
Hi

I think that is a different issue Arno.

The workflow to reproduce it is to place some objects in sim as xml ( I'd used instant scenery for that to place lot's of Electricity Pylon objects on exactly the right spot, as I only have line data for the utilities which doesn't tell us where the pylons are within the line). I then decompiled the resulting BGL to give me the *.XML. Then I used ModelX's "xml placement to shp converter" tool to give me a shape file with the Pylons as points with heading attributes. I used that shape file in sceneproc and found the headings were wrong. The objective was to increase the performance of the pylon objects by converting them to AGN. ...I've not re-tested this method with the latest version yet.

I've just run the latest version '2753' but unfortunately it crashed as soon as it got to CREATEAGNLIBOBJ steps. I was using my full script (nearly 4000 lines) So I'll cut it down to just the steps needed to test the railway gantry object and I'll try it again.

EDIT

Have re-tested now with a much simplified script and I'm afraid Scenproc 2753 is crashing the moment it gets to a CREATEAGNLIBOBJ step :(
 
Last edited:
Hi Darren,

Can you show me how your CREATEAGNLIBOBJ step looks?

And do you get any error with the crash?

Regarding the heading. How big was the offset you saw?
 
Hi

The simplified test looked like...
Code: 
IMPORTOGR|O:\Volume-6_Area-1\COMPILE\SourceData\AGN\Autogenesis-Shp-Files\vol-6-1-TRAIN-GANTRY.shp|*|*|NOREPROJ
SPLITGRID|AGN
CREATEAGNLIBOBJ|FTYPE=POINT;train=TRAIN-GANTRY|{cd163f82-46a9-b4ca-bbc7-eab04d745148}|hdg|0|2;28
EXPORTAGN|FSX|T:\Texture

I just received a standard windows error "scenproc has stopped working...windows is checking for a solution"
Reverting to the previous version it runs OK. ( but with the offset still present in the results of course)

The heading offset when converting xml placed objects - shape - agn looked around 30 degrees or thereabouts, but I don't think it was consistently the same else I would have added a heading offset in the script. I really need to retry it to give you better information.
 

Attachments

Last edited:
I'll try to reproduce the crash.
 
Hi,

I see where the crash comes from. I made some changes to the way the heading attribute is stored by scenProc. Before it could either be a vector or a heading value. I dropped the vector notation to make the code easier. But it seems your file still had that notation. I assumed most people would use PLACEPOINTSALONGLINE in the same script.

I'll add support for the vector notation back to not break backwards compatibility.
 
Hi,

I have restored the old way now. So please have another look tomorrow. It shouldn't crash anymore.
 
You must log in or register to reply here.
Back
Top