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

HELP!! Crash on SPLITGRID

iangbusa

iangbusa

Messages
223
Country
us-ohio
I don't know if anyone has come across this before. Hopefully I'm not repeating someone else's problem.

I seem to have something in the shapefile data (all polygons) that causes SPLITGRID to crash scenProc - no log file when run in batch and only a dialog to say it's stopped working. It's happened to me in a couple of instances. At first I thought it was running out of memory with large data and many features but I broke down each area gradually and all worked until I reached a particular level. There;s something in the few features there that SPLITGRID doesn't like.

Arno - I have the data zipfile available and could PM to you if you're interested. I'm completely bewildered.

ian
 
iangbusa said:
I don't know if anyone has come across this before. Hopefully I'm not repeating someone else's problem.

I seem to have something in the shapefile data (all polygons) that causes SPLITGRID to crash scenProc - no log file when run in batch and only a dialog to say it's stopped working. It's happened to me in a couple of instances. At first I thought it was running out of memory with large data and many features but I broke down each area gradually and all worked until I reached a particular level. There;s something in the few features there that SPLITGRID doesn't like.

Arno - I have the data zipfile available and could PM to you if you're interested. I'm completely bewildered.

ian
Click to expand...
All

This one is really baffling me. I've attached the shapefile info and my spc file. Can anyone let me know if they get the same problem? This is happening in multiple specific areas and it must be something in the input data but I have no clue what.

Really could do with some help!!

Thanks

ian
 

Attachments

Thanks! I'll give that a go. The scenery won't be as realistic if I do, unfortunately. It's strange though because I know it works very well on very large files with lots of polygons each containing several holes. Really weird.
 
MyPC8MyBrain said:
try unchecking - process holes (in the option menu)
Click to expand...
Chris,
Oh dear. Tried IMPORT with DONTPROCESSHOLES and get the same crash problem. Then I noticed you said uncheck in options. I just don't see that option when I open scenProc. Wonder what I'm missing. I'm running r2740 DEV 3/24/2014.
Thanks for the advice - keep it coming! I'm totally stumped by this one.
ian
 
my mistake Ian; i guess Arno moved this switch from setting to syntax switch

short of blaming the data files; id wait for Arno's advice
 
No worries, Chris. Meanwhile I've drilled further down into just one area that shows the same behavior - now a very small file with just a couple of polygon features. I still cannot see what is wrong or different in this file. I've attached a zip here just in case anyone would like to give it a try in scenProc and see if they get the same crash.

It's driving me mad! Argh! Has to be something simple I'm doing wrong but just can't see it.
 

Attachments

i believe the issue is your polygon is concave instead of convex

ConvexVsConcave.jpg
 
Just look at this below! A concave poly... and it's the one that blows up scenProc.

Now, I wonder what I can do about all these concave polys I have???

upload_2014-4-12_11-15-35.png
<===== Doesn't work

but I have many that seem to work - like the one below just north of the bad one. Puzzling.

upload_2014-4-12_11-17-2.png



I'm missing something somewhere!
 
its about the direction your drawing your poly;
you need to go clock wise to have a convex
if you go the other direction; your drawing a concave
thats why some shapes complete and some don't; you didn't draw these did you?
 
MyPC8MyBrain said:
its about the direction your drawing your poly;
you need to go clock wise to have a convex
if you go the other direction; your drawing a concave
thats why some shapes complete and some don't; you didn't draw these did you?
Click to expand...
No - they're from a geodatabase. Not from OSM. Not my own work but I paid for it! I suppose I now have to work out (program) something to go through all my shapefiles and check whiich way the polys are drawn! :yikes:
 
One thing I notice though, in addition to the hole, is that the "bad one" appears to be the only one in this sample area with two concave "bays". I'll check on that also.

Arno! I hope you're listening to all this! It's probably the kind of thing you can spot in a flash. And, Chris, many thanks for your patience and advice again.
 
YVW,
Arno is on vacation;
i understand the urgency but the man deserves a rest
our community will help as much as possible until his safe return
 
You must log in or register to reply here.
Back
Top