Hi There,
I thought about, that the exporter would save the file in sequence, that when its exporting, it can free up some memory. I have a lots of instances, and it just unable to do the job. Not to mention I think this way it will be much faster as well. Maybe after every 500 object, it could save it.
For now I will try to split the scene and then copy and paste the whole thing toghether.
Thanks
exporting in sequence
So, lets say if I have few thousands of instances.
I start to export, the memory usage goes up to gigabytes, (I do use the instance option) Even the page file increases.
So what I thought would be good:
every after five hundred exported file, release the buffer what max uses for exporting, And then move on. THis part I am not quite familiar in maxscript, I don't know how I would be doing this, but it saves a lot of time and memory.
Thats what I figures out.
or the other way, that every after five hundred object, it closes file and start another file, putting the data into it. And on the end just joining it. Practically would use less memory and because of that would be also faster as well.
So what I am talking about that xxx.scene.igs export part. The file itself doesn't become big, but memory requirement and the time is quite much.
Thats why.
The scene is few kind of objects with hundreds/thousand of instance.
Maybe its just a bug? I am on winp64 max9 64 bit.
I start to export, the memory usage goes up to gigabytes, (I do use the instance option) Even the page file increases.
So what I thought would be good:
every after five hundred exported file, release the buffer what max uses for exporting, And then move on. THis part I am not quite familiar in maxscript, I don't know how I would be doing this, but it saves a lot of time and memory.
Thats what I figures out.
or the other way, that every after five hundred object, it closes file and start another file, putting the data into it. And on the end just joining it. Practically would use less memory and because of that would be also faster as well.
So what I am talking about that xxx.scene.igs export part. The file itself doesn't become big, but memory requirement and the time is quite much.
Thats why.
The scene is few kind of objects with hundreds/thousand of instance.
Maybe its just a bug? I am on winp64 max9 64 bit.
Is the instanced model a single model or is it grouped?
There is a bug with grouped instances that may crash the exporter.
What type of format do you use for exporting? Don't use xml.
Do you have actively linked models in your scene?
The script makes copies of the linked geometry in order to access them properly and that may double the memory usage.
Otherwise the script doesn't load the scene into memory. It loops through the scene objects and writes them out to a *.igs file "on the fly". Or at least it should behave like that
If none of the above doesn't work, then maybe you can upload some sort of example scene that has problems?
There is a bug with grouped instances that may crash the exporter.
What type of format do you use for exporting? Don't use xml.
Do you have actively linked models in your scene?
The script makes copies of the linked geometry in order to access them properly and that may double the memory usage.
Otherwise the script doesn't load the scene into memory. It loops through the scene objects and writes them out to a *.igs file "on the fly". Or at least it should behave like that
If none of the above doesn't work, then maybe you can upload some sort of example scene that has problems?
The group is true, I will try to ungroup them and see.
I am familiar with the issue otherwise I wrote the exporter for redqueen renderer some time ago. But Indigo is more comfortable and rq doesnt handle instances unfortunately.
I think max doing it for some reason.
I try to ungroup, and I let you know then.
I am familiar with the issue otherwise I wrote the exporter for redqueen renderer some time ago. But Indigo is more comfortable and rq doesnt handle instances unfortunately.
I think max doing it for some reason.
I try to ungroup, and I let you know then.
There is something else, seems obj export would work just fine, but it looks for an undefinied material, which been created by the obj exporter, and then when indigo starts it stops with missing material message.
some wirexxx material missing.
I thought maybe subobject materials are causing this, but I also tried without it and it worked.
some wirexxx material missing.
I thought maybe subobject materials are causing this, but I also tried without it and it worked.
Who is online
Users browsing this forum: No registered users and 5 guests