It's possible that it's something in your configuration however, let's not rule out a memory allocation bug within the geoconvert tool as some others are having crashing issues as well.
Even though our testing was a success doesn't mean that something isn't missed here.
We will look into this more when Torsten returns from his much deserved vacation 
We will look into this more when Torsten returns from his much deserved vacation
Well, I'm just getting frustrated when I do not understand the reason.
Until then, I am very pleased with approximately 50 x 50 nm.
That said - GeoConvert is amazing. I love this opportunity. Now I have also trained to create airports (tsc-file and in 3dsMax). Thank you so much IPACS. 
Well, I'm just getting frustrated when I do not understand the reason.
Until then, I am very pleased with approximately 50 x 50 nm.
That said - GeoConvert is amazing. I love this opportunity. Now I have also trained to create airports (tsc-file and in 3dsMax). Thank you so much IPACS.
If you have 3DS Max, I will be adding a detailed tutorial on creating a full airport with models creation and placement, scene alignment on top of geoconvert scenery, adding vertex weighting, decals, lighting, and layering. Just give me some time here is I've been extremely busy lately.
My setup is very similar to Hartman's, and I also have crash above 50nmx50nm. Increasing virtual memory to 32 GB does not help.
Maybe this has something to do with VAS?
I currently have ~156gb allocated to pagefile and all of it is on SSD drive. My current project (which made it from levels 9 to 10 and 12 and is now on 14) is using 141GB of that. the tifs are roughly ~140 gb of data.. makes sense i'd need that much paging space to store it for the low levels (9,10)
I am thinking about getting a 256gb ssd and dedicating it to paging for geoconvert.
Thanks for pointing this out, but somehow I remember Jeff has a similar setup as mine but he can do more than 100nmx100nm region of 30cm resolution without crash.
I have an notebook computer of the same amount of ram and pagefile (but less powerful CPU) can also do bigger regions than my desktop computer, but not as big as Jeff's. So I presume it does varies from computer to computer, but the GeoConverter itself is fragile indeed. I never crash with FSET (with ms resampler) or Ortho4XP for whatever scenery size, and I can do other things in the same computer.
Display More
I currently have ~156gb allocated to pagefile and all of it is on SSD drive. My current project (which made it from levels 9 to 10 and 12 and is now on 14) is using 141GB of that. the tifs are roughly ~140 gb of data.. makes sense i'd need that much paging space to store it for the low levels (9,10)
I am thinking about getting a 256gb ssd and dedicating it to paging for geoconvert.
So I presume it does varies from computer to computer, but the GeoConverter itself is fragile indeed.
That's what I suspect too.
My biggest wish for GeoConverter, is that we can select areas of approximately 50 x 50 nm - and that GeoConverter can create these areas so that they can be assembled without the problematic joints. Now I experience both a black line and black fields scattered along the joints. Then we do not need to make areas as big as possible in the first place.
If you have 3DS Max, I will be adding a detailed tutorial on creating a full airport with models creation and placement, scene alignment on top of geoconvert scenery, adding vertex weighting, decals, lighting, and layering. Just give me some time here is I've been extremely busy lately.
All info is welcome (as long as I have the ability to understand).
I have previously worked professionally with 3ds Max. And I have followed the examples from the Wiki.
But I am used to another technique, and therefore experience the examples from Wiki as unnecessarily complicated. Regarding "mass production" - it is much easier to create a library of items and then assemble it to completed airports.
My biggest challenge has been to understand how rigid we have to be. It took some time to find out that we need to use an "Ambient Color" map. But I still do not understand why we have to use the "Ambient Color" map. 
That's what I suspect too.
My biggest wish for GeoConverter, is that we can select areas of approximately 50 x 50 nm - and that GeoConverter can create these areas so that they can be assembled without the problematic joints. Now I experience both a black line and black fields scattered along the joints. Then we do not need to make areas as big as possible in the first place.
We added a new tutorial to the wiki that explains this in better detail HERE
Maybe this will help you better.
We added a new tutorial to the wiki that explains this in better detail HERE
Maybe this will help you better.
Great.
I have not seen this detailed explanation before. Then I will study this further.
Thanks so much.
