topic Re: Export hanging on "Finalizing Export" in ArcGIS CityEngine Questions

Export hanging on "Finalizing Export"

RobHoward — Tue, 30 Apr 2013 16:12:26 GMT

When I try to export a scene, the exporter sometimes infinitely hangs on "finalizing export."

This is a problem with a new building I've developed. It's meant to be very fully featured in terms of randomized
facade elements, attached models, texture variations etc.

The rule file has gotten very large. If I reduce it down in size by eliminating some of the facade elements and variations,
the export works. As I reintroduce things, eventually I'll reach a point in which the export starts hanging on "finalized
export" and it fails (I have to kill the CE process to get out of the program).

This suggests there is some kind of limit to how complex a rule can be if it is going to export successfully. Is this the
case? And if so, is there a way to test or know what that limit is?

Thanks.

Re: Export hanging on "Finalizing Export"

ScottFujikawa — Wed, 01 May 2013 18:03:29 GMT

Hi,

Are you using the 64 bit or 32 bit version? The 64 bit version better utilizes memory so you can push up larger scale projects.
Take a look at this thread which may offer you some solutions:
http://forums.arcgis.com/threads/56490-Freeing-up-system-memory

Cheers,
Scott

Re: Export hanging on "Finalizing Export"

RobHoward — Mon, 06 May 2013 19:10:40 GMT

We're using the 64 bit version.

I tried increasing the Java memory as per that thread, although I think (from reading other threads) that java memory doesn't affect
model exporting?

At any rate, when I alter the CityEngine.ini file line (-Xmx4096M) it doesn't have any effect. The memory indicator in the lower
right doesn't seem to show any difference either, it is just under 2000 like it normally is. Is there some step involved in getting
CE to recognize the higher Java memory threshold I've set?

Re: Export hanging on "Finalizing Export"

MatthiasBuehler1 — Tue, 07 May 2013 07:19:06 GMT

Hey Rob,

Are you also exporting a terrain ? Check the export granularity concerning terrain exporting. Default is 'export all visible terrains' in CE 2012.

Note that in the misc tab, the default is 'simplify terrain'. this triggers an edge-collapse algorithm to process the terrain and create less polygons. this is expensive to calculate, especially of course if you have high-polycount terrain ( check also the UV-subdivisions in the terrain layer. Turning off that simplify should speed up the terrain export.

Ok ?

Matt

Re: Export hanging on "Finalizing Export"

RobHoward — Tue, 07 May 2013 15:12:02 GMT

Hello,

We've been turning terrain layers off, both in our python script and when I used the GUI to export, so I don't think it can be that.

Quickly, to kind of "reset" the thread's main question: is there some kind of limit to how complex a CGA created building model can be? Such as too many shapes broken up into component splits or something?

My memory, both Java and system, always shows well into the "green" (Java is usually at 1900 MB, and system is usually at 6547 MB).

Re: Export hanging on "Finalizing Export"

MatthiasBuehler1 — Wed, 08 May 2013 11:32:20 GMT

Hi,

In by far most cases, complexity is no problem.

If so, you get errors in the CGA problems view. E.g. with too many recursions.

Check also the docs on the Grammar Core's 'max derivation depth' and ~width settings.

How many polygons do you create per building ? Can you export single buildings successfully ?

Let me know ..

m.

Re: Export hanging on "Finalizing Export"

RobHoward — Wed, 08 May 2013 15:35:33 GMT

I did try making those numbers larger in the grammar core, to no effect, but I do think, after trying to find an answer for you on how many polys these models are, that I might have found the problem? Here's an export log of one of these buildings (note the errors regarding the UVs):

EXPORT LOG / CityEngine 2012.1.09130547
---------------------------------------------------

export started at: Wed May 08 11:30:59 2013
export completed at: Wed May 08 11:31:02 2013
export duration: 3.1 seconds

EXPORT SETTINGS
    format:                Autodesk® FBX® 2013
    location:              C:\hh\sol\CityEngine\City\models\test
    base name:             City_zone_E2_N1
    export content:        0 (0 = models only, 1 = fallback to shape, 2 = shapes only)
    file granularity:      0 (0 = single file (or split by file budget), 1 = file per initial shape)
    file size budget:      0
    mesh granularity:      0 (0 = as generated, 1 = mesh per material, 2 = use instances of inserted assets)
    vertex precision:      0.00100
    normal precision:      0.00100
    texcoord precision:    0.00010
    merge vertices:        1
    merge normals:         1
    merge texcoords:       1
    triangulate:           1
    reproject texcoords:   0
    vertex indexing:       0 (0 = allow shared vertices, 1 = force separate vertices)
    normals type:          0 (0 = use vertex normals, 1 = use face normals (flat))
    normals indexing:      0 (0 = allow shared normals, 1 = force separate normals)
    write texcoords:       1 (0 = no texcoords, 1 = first layer, 2 = all layers)
    write materials:       1
    collect textures:      1
    file type:             1 (0 = ascii, 1 = binary)
    embed textures:        0
    write master file:     0
    master group name:     CityEngineSceneRoot
    write cam data:        1
    batch behavior:        0 (0 = normal, 1 = skip existing files, 2 = dry run)

INPUT STATS
    number of initial shapes      = 1
    number of generated shapes    = 5515
    number of generated meshes    = 5515
    number of generated materials = 5515

OUTPUT STATS
    written files: 1
    written materials: 6
    written meshes (total polygons): 5515 (64340)

INPUT REPORT
    collected/generated initial shapes:
            0: OK    : Shape                                    OID: 65d808c7-94fb-11b4-9f79-002564ace543:4
               ERROR: Mesh::normalizeUV() : can not normalize, delta u is too small (0.000000)
               ERROR: Rule 'Default$CityBuilding.WallTextureB;' : tileUV failed (normalize)
               WARNING: Split: leaf 2 has size 0.000005, too small, ignored
               ERROR: Mesh::normalizeUV() : can not normalize, delta v is too small (0.000000)

OUTPUT REPORT
    written files & status:
            0: OK:                        C:\hh\sol\CityEngine\City\models\test\City_zone_E2_N1_0.fbx

---------------

I'm thinking the shape errors are what is causing the problem? Which basically seem to be that some of the UVs are too small? Also to answer another one of your questions, I can get single buildings to export, it fails though when I try to export in groups (usually when I try to export something larger than a single city block).

Re: Export hanging on "Finalizing Export"

MatthiasBuehler1 — Mon, 13 May 2013 12:06:38 GMT

Hi,

Would it be possible that you send me a PM with your mail address and you then send me a stripped-down CE project archive ( zip ), on which I can reproduce the issue ?

If it's a bug, I'll have to reproduce it here anyway.

Let me know if this is possible.

Matt

Re: Export hanging on "Finalizing Export"

KareenBröker — Fri, 20 Dec 2013 10:48:29 GMT

Hi Matt!

Did you ever find a solution for this?

I think I am having the same trouble with exporting my shapes to Collada 1.4.1...
Maybe there is something wrong with the shapes I am trying to export or maybe I am not using the right export settings?

Best regards,
Kareen

Re: Export hanging on "Finalizing Export"

MatthiasBuehler1 — Fri, 03 Jan 2014 10:36:43 GMT

Hi Kareen,

Well, we tested the exports a lot, but there may have been some rare cases that slipped. 😞 No software's perfect.. 🙂

But I always need very precise details to be able to help. As written in the post above, if there's a 'hint of a bug', I need to be able to reproduce it on my machine here.

So please track the issue down very precisely, otherwise it's hard for me to help ..

Matt

Re: Export hanging on "Finalizing Export"

KareenBröker — Wed, 08 Jan 2014 21:01:39 GMT

Hello Matt,
Thank you for your reply. Unfortunately there is no error message. The export is just hanging on «Shape/Model Export: Finalizing export�?�». Do you have any suggestions where I could find out more? Maybe there is a log file or something?

While I am running the export, I can not get to the Inspector, Log, Problems, and Console on the right. I have tried to cancel the export operation, but that does not seem to work. So I have to use the Windows Task Manager to shut down the program�?�

I assume that there is something wrong with my dataset. I have managed to export parts of it. And some parts export fine.
Is there a function in City Engine that checks the dataset for errors?

I do have some messages in the Log, Problems, and Console tabs to the right before the export.

In the Log it says:
�??eclipse.buildId=unknown
java.version=1.6.0_32
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=no_NO
Command-line arguments: -os win32 -ws win32 -arch x86_64 -data @noDefault
Warning
Wed Jan 08 17:48:47 CET 2014
The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
Error while rendering on unit org.corebounce.lib3d2.units.C3DBufferUnit, slot:SETUP - [main]�?�

Under Problems there is one error. But this error is related to a shape that I managed to export.
There are also some items listed under Problems - Infos:
�?�Initial geometry �??Shape 1249�?? contained: 4 0-area faces (removed);�?�.
But some of these are shapes that I did manage to export...

Do you have any suggestions on how to get to the bottom of this?
Thanks!

Re: Export hanging on "Finalizing Export"

MatthiasBuehler1 — Thu, 09 Jan 2014 08:26:13 GMT

Hi!

There's the CityEngine log ( Window > Show Log ), that's output to :
workspace/.metadata/.log

Otherwise, there's some export logs that are produced and put in the same export directory as the exported files, so usually the 'models' folder.

Since it could be 'anything', you need to track things down logically:
- layer after layer
- binary search: when a layer does not export fully, export half the shapes. if it works, the issue is in the other half.. and so on until you find the issue.

It may also depend on the data and file format you export to. Are you using GIS data ?
If so, did you try to use the 'cleanupGeometry()' operation right as the first operation on the shapes ? That sometime helps with weirdly digitized shapes or such.

Let me know..

matt