- User Since
- Wed, Sep 25, 1:08 AM (3 w, 1 d)
Mon, Oct 14
No, that isn't enough. Working with complex models with potentially hundreds of separate objects within the same blender file, exporting each object separately, often each object is similar to other parts with slight variations, so their names have slight variations. For instance, i've been working on a builders kit for Second Life and Opensim of parts for people to construct all sorts of spiral staircases with different railing styles, clockwise vs counterclockwise, amount of turn to each section of staircase, stair pitch per turn, etc. etc. All told, there's over 260 parts that each need to be exported from this one blender file. Having blender grab the object name automatically would save a bunch of work, because when I open the export screen, I can no longer see the tree of object names to ensure I'm giving the export file name the same name as the object I'm exporting, so I frequently screw that naming up and I have to do things over again.
Tue, Oct 8
Sat, Oct 5
Sun, Sep 29
do you want i should upload a user preferences file if there is one here?
Ok attached is a Jedi temple I worked on last night, left open all night, I just saved it, then went to export it to collada, and blender 2.8 crashed. I'm including both the blender file and the 0byte dae.
Fri, Sep 27
Its pretty basic, I use normal mesh editing functions to create and edit meshes, I create materials, map the UVs, it doesnt matter whether I assign textures or not, it doesn't matter whether its a new or old file. I'm a pretty keen observer and there is no common denominator other than that I'm exporting to collada with SL/OS static operator presets after several hours of the application operating, regardless of how much or how little work I do on the blender file. It crashes and creates a 0 byte file for the export file. Like I said, I know this is hard the lack of any sort of crash logging makes this difficult to debug. Are there any logs I can access despite the crash?
Thu, Sep 26
It happens with ANY blender file open for more than several hours. I keep blender open all day every day as I use it all the time. If I've had the blender file open for, say, four to six hours, its guaranteed to crash, but if blender itself has been open for more than that, and I open another file, it will also crash if i export from the newly opened file. Again, does not matter what file it is. The only factor is time that blender has been open. the crash on collada export creates a collada file of 0kb memory. I have included several examples of the crash collada output file using several sources. Note this problem also existed under Blender 2.79. Some of these files were created with that version, the newer two were made by 2.80 in the current build I'm using. Nor is this problem unique to the computer I am using now, it exists also on my desktop running Windows 8 with blender 2.78.