You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems in Blender there is a problem loading files over a certain size.
After hammer the server for hours I've tracked it down to a limit of 4440 for box size.
After that it loads nothing fast.
Import finished in 0.8906 sec.
2018-04-19 05:58:42.522 DEBUG: updateTarget:Rawmodel-49920
Import finished in 45.0781 sec.
2018-04-19 06:01:09.787 DEBUG: updateTarget:Rawmodel-49922
Really I think Maybe what would be better for me is a grayscale image map. Is there a way to just load an hgt file or something?
Anyway Blender is free to download and try and verify this problem?
Maybe allow export into an alternative format. I imagine you maybe turn it into an OBJ first anyway?
I thought it might be the 'New' Scale factor causing the issue but it's probable the file size.
I guess I could try to report the bug to Blender as well. Just looking for some feedback here first.
It's somehow file size in general, I've had to lower other sections down to 4200 box size, etc.
The STLs sizes are; for 4440 209MB and for 4200 187MB. As to number of verts and faces I would have thought they be the same but Blender can't read something that it can in the same region after lowering the size.
Takes a couple days to put four pieces together... never perfect. Simply too much data where a HGT to PNG for the Height with an actually texture too would be nicer for me in Blender.
The suggestion that this brings to mind now is to include a decimate algorithm on your end.
If you could perform that "Decimate" functionality that you can see demonstrated in Blender's modifiers was an option online when generating it would handle larger data without completely loosing data as decimate intelligently removes more when flatter rates of change across the surface are detected. Maybe that requires an Obj or DXF format instead, so I realize maybe this is not likely here but just letting you know my experience and thoughts. Thanks for listening.
The text was updated successfully, but these errors were encountered:
Nothing will open the downloaded stl files, I have 5 apps that open .stl files and none will open the ones generated at http://jthatch.com/Terrain2STL/ I tried to write to ask for help but your contact email is [email protected] which doesn't look real.
It seems in Blender there is a problem loading files over a certain size.
After hammer the server for hours I've tracked it down to a limit of 4440 for box size.
After that it loads nothing fast.
Really I think Maybe what would be better for me is a grayscale image map. Is there a way to just load an hgt file or something?
Anyway Blender is free to download and try and verify this problem?
Maybe allow export into an alternative format. I imagine you maybe turn it into an OBJ first anyway?
I thought it might be the 'New' Scale factor causing the issue but it's probable the file size.
I guess I could try to report the bug to Blender as well. Just looking for some feedback here first.
It's somehow file size in general, I've had to lower other sections down to 4200 box size, etc.
The STLs sizes are; for 4440 209MB and for 4200 187MB. As to number of verts and faces I would have thought they be the same but Blender can't read something that it can in the same region after lowering the size.
Takes a couple days to put four pieces together... never perfect. Simply too much data where a HGT to PNG for the Height with an actually texture too would be nicer for me in Blender.
The suggestion that this brings to mind now is to include a decimate algorithm on your end.
If you could perform that "Decimate" functionality that you can see demonstrated in Blender's modifiers was an option online when generating it would handle larger data without completely loosing data as decimate intelligently removes more when flatter rates of change across the surface are detected. Maybe that requires an Obj or DXF format instead, so I realize maybe this is not likely here but just letting you know my experience and thoughts. Thanks for listening.
The text was updated successfully, but these errors were encountered: