ERROR: Not a geometry:

Issue #1211 resolved
M Schneider created an issue

I have this error really often since a few weeks. I cannot find out why and it is not happening all the time with everything. It’s like random with many different assets. Most of the time I tried to bring multiple objects over to blender. Which makes it a little annoying, since I would have to check each and every piece to find out which one ist creating this problem. I had to switch to Daz to Blender to get everything in the scene over to Blender one by one; which is kind of tiring. Is there a way to get more information about why this is happening?
I used multiple Blender versions (3.31 to 2.93) and tried also the 1.61 and 1.60 version of your tool. My guess would be something has changed with Daz Studio, since every older, already transfered scene works perfectly fine in all versions on the Blender site and there were never a problem like this for me in the past.

ERROR:
Not a geometry:
None
For details see
'C:\Users\mschn\Documents\daz_importer_errors.txt'

TRACEBACK:
File "C:\Users\mschn\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\import_daz\error.py", line 208, in execute
self.run(context)
File "C:\Users\mschn\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\import_daz\main.py", line 124, in run
self.loadDazFile(filepath, context)
File "C:\Users\mschn\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\import_daz\main.py", line 198, in loadDazFile
main = parseAssetFile(struct, toplevel=True)
File "C:\Users\mschn\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\import_daz\files.py", line 279, in parseAssetFile
return asset.parse(struct)
File "C:\Users\mschn\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\import_daz\files.py", line 107, in parse
asset = self.parseUrlAsset(nstruct)
File "C:\Users\mschn\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\import_daz\asset.py", line 157, in parseUrlAsset
asset.update(struct)
File "C:\Users\mschn\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\import_daz\node.py", line 793, in update
geonode = GeoNode(self, geo, geostruct["id"], etype)
File "C:\Users\mschn\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\import_daz\geometry.py", line 63, in init
reportError(msg, trigger=(2,3))
File "C:\Users\mschn\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\import_daz\error.py", line 93, in reportError
raise DazError(msg)

Comments (4)

  1. Thomas Larsson repo owner

    I don’t have this asset so the errors I get are about missing assets. I imported some assets that are bundled with DS from DS 4.21, but didn’t notice anything unusual. There are some small changes in the last commit, but it is unlikely that it changes much.

    Verbosity seems to be set to 3. If you lower verbosity to 2 the errors should have been ignored, but that happens at verbosity = 3 too now. There will probably be other problems down the road, though.

  2. M Schneider reporter

    You are right. With verbosity on 2 there seems at first a lot very strange. But it helped a lot!
    But there is another problem, saving the settings file itself, when there are wrong paths down the road. (I also had to change verboity manually) I did not realize that there are other changes. Some of them because of my new folder structure for different asset types. This also was no problem at the time I started with 1.5 or 1.6 of your tool. But at this time I’ve not done very much with the assets from the folders I includet manually. (freebies) The structures looked very out of place:

    On top the old ones:
    // "DazContent001" : "D:/DAZ_Content/My DAZ 3D Library",
    // "DazContent002" : "D:/DAZ_Content/DAZStudio4/shaders/iray",
    // "DazContent003" : "D:/DAZ_Content/Studio/My DAZ 3D Library",
    // "DazContent004" : "E:/Daz Freebies/#3 My Library (external freebies)",
    // "DazContent005" : "F:/My_daz_3d_ORG_Folder/My DAZ 3D Enviroments",
    // "DazContent006" : "F:/My_daz_3d_ORG_Folder/My DAZ 3D Library"

    "DazContent001" : "E:/DAZ 3D/Studio/My Library",   
    "DazContent002" : "E:/ShareStudio/My Library",   
    "DazContent003" : "E:/Daz Freebies/#3 My Library \(external freebies\)",   
    "DazContent004" : "D:/DAZ\_Content/Studio/My DAZ 3D Library",   
    "DazContent005" : "F:/My\_daz\_3d\_ORG\_Folder/My DAZ 3D Enviroments"
    

    Could a permission error be a part of the problem itself?! I tried to save the settings manually and it worked, but not with blender itself over the settings menu. There were a lot of items not transfered after I’ve done that verbosity thing, and then I looked into the paths since some bones were in the scene, but not the asset itself. I saw multiple bones of some assets, but not the mesh itself. (for this file I put in here…)
    So far, every file I created for this test works nearly perfect since i changed the paths manually too. Some things are out of place, but that does not matter, since i place them in Blender on a new position anyways. I guess you could incklude an error handling for these situations other people might have to. So that somehow the paths will be checked and then the assets loaded. It would prevent that someone like me gets confused… Maybe you just check the folder structure of the most common folders that are used most of the time?! Something like that… and if there are not there, you throw the error that the user should check on that before trying to load something again?! I mean in generall this would be important for everything…

    I try some other files that did not work, but I am optimistic that everything woks again great! Thank you very much for that…

  3. Alessandro Padovani

    My personal advice, both for daz and blender, is to use one single content folder where you only install the assets needed for the current project. When you change project you backup and switch the content folder. Simple like that, fast efficient secure and hassle free.

    Both in daz and blender having lots of assets and content folders together in a big database is prone to errors and inefficiency.

  4. Log in to comment