Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 03 1:41 pm)
Quote - > Quote - Exporter bug, this one probably for bagginsbill:
File "L:PoserPoserPro2010RuntimePythonposerscriptsLuxPosePoserLuxExporter_alpha_1-10eluxmaticmatcore.py", line 404, in __init__<br></br> self.importFromShaderNode(v)<br></br> File "L:PoserPoserPro2010RuntimePythonposerscriptsLuxPosePoserLuxExporter_alpha_1-10eluxmaticmatcore.py", line 487, in importFromShaderNode<br></br> setattr(self, inp.name, inp.importFromShaderNode(snode))<br></br> File "L:PoserPoserPro2010RuntimePythonposerscriptsLuxPosePoserLuxExporter_alpha_1-10eluxmaticmatcore.py", line 215, in importFromShaderNode<br></br> v = inp.Value()<br></br> AttributeError: 'NoneType' object has no attribute 'Value'
After which the script dies.
Nothing happens anymore, CPU is idle.
I waited about 5 minutes and closed the window.Scene was one M4 and one V4 (clothed, haired) inside Faveral's "Hacienda" setting, a biggish outdoor setting with lots of textures, but AFAIK no complicated materials.
This means you have a node that does not have a known input - which may mean you're running this on some older version of Poser.
I don't really think so, it was Poser Pro 2010 (no SR, didn't have the time to install it yet).
And exporter version was 10e.
Quote - and the material that caused it, or a screen shot of the material.
Well, I stated it was mainly Faveral's Hacienda (plus a V4 and an M4).
Don't know which Poser material caused this though, since the Hacienda setting is huge.
I'm willing to make additional test though, I'll have some time during the weekend. Tell me what to do, I'll do it.
Quote - Will this do? https://sites.google.com/site/luxposedevelopment/
Any special reason I get "Not Found - Error 404"?
rty....the discussion on updates and testing has moved here: LuxPose Project. We're abandoning this thread because it has the name of another plugin in the thread title and that plugin has been released today. We figured it might get confusing for newcomers from here on out ;o).
You got a 404 error because the page has been deleted. It didn't meet our needs. Read up a few posts and links to the wiki page on the RO wiki and the new threads about LuxPose are there.
Laurie
Quote - I get the following error in unimesh.py:
nr_tpolys = sum([len(actor.Geometry().TexPolygons())
TypeError: len() of unsized objectI fixed that for me by changing lines 106-109 like this:
nr_polys = sum([len(actor.Geometry().Polygons()) for actor in actors if actor.Geometry().Polygons() and actor.Geometry().TexPolygons()]) nr_tpolys = sum([len(actor.Geometry().TexPolygons()) for actor in actors if actor.Geometry().Polygons() and actor.Geometry().TexPolygons()])
and adding the following after line 125: if not geom.Polygons() or not geom.TexPolygons(): continue
Hi Dizzi,
Thanks for the tip! I think I will still want to export the geometry, though, even if its UV mapping is missing or incomplete.
Do you have a figure I could test this on or instructions on how to create one? I have a feeling that just removing the UVs from the .obj file would not be enough.
Edit: Oops! Sorry for posting in an abandoned threat. It will happen again.
-- I'm not mad at you, just Westphalian.
Quote - Well, I stated it was mainly Faveral's Hacienda (plus a V4 and an M4).
Heheheh. When people say sentences like this to me, here's what it reads like (to me):
Well, I stated it was mainly somebody's something. It has a something with a something in it that probably matters but ...
You mistake me with somebody who buys things. I've never heard of Faveral.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)
Quote - For what it's worth...I've been reading the Daz forums about that other plugin ;o). Seems someone else had a problem with that exact same model with that one too. Don't know if it was the same problem, but it makes you wonder if it's not something with the model itself.
It would be very surprising if the DAZ Studio plug-in had the same material problem like the Poser one.
That been said, and despite bad vibes everywhere, I'm still willing to check out what it might be (if anybody asks me to). Whatever it is, it is sure to crop up again any time, Faveral is a skilled merchant, with quite some flight hours, so I don't think he did any stupid thing.
Quote -
That been said, and despite bad vibes everywhere, I'm still willing to check out what it might be (if anybody asks me to). Whatever it is, it is sure to crop up again any time, Faveral is a skilled merchant, with quite some flight hours, so I don't think he did any stupid thing.
It's not meant this way. For sure.
We are here to find out where the bugs are. But it's sometimes not easy to find out just by a description.
The background is: Each Poser node has a Value(). So one could be sure if it is a node, a Value() has to be there (a node without the possibility to change things isn't useful). If it is really not there, it's best to find out why. This could be a "trick" done by the creator of this nodeset, as odf said, or simply a piece of code somewhere deep inside the Exporter with a side effect. Making sure it's not a simple thing while inspecting the nodes in question is the easiest way to find out what happens. This is the reason why bagginsbill asked. Your answer didn't help mutch, but this is not your fault. It's just - because.
If you could find out what the exporter "says" before the error occurs may help to find a startpoint to search for the reason.
Quote - Has anyone done a render that looks like it couldn`t be done in poser yet?
Yes, Laurie has... the second render of that building and trees in front would have been impossible in Poser. Have a look a few pages back...
Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2
Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand]
Quote - Anyway, what did the exporter last say it was exporting before the error happened?
Here is the whole log. For simplicity's sake i loaded the Hacienda setting in an empty scene and tried to export it. Exporter used was v.12 (just downloaded):
Loading pydough.geometry_export
Loading pydough.geometry
Loading pydough.geometry
Loading pydough.submesh
Loading pydough.submesh
Loading pydough.geometry_export
Loading pydough.geometry
Loading pydough.submesh
Compiling L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticnodes.pyc
Compiling L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticnodes.pyc
Compiling L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticnodes.pyc
Loading pydough.geometry_export
Loading pydough.geometry
Loading pydough.submesh
Compiling L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticnodes.pyc
Version alpha 1.2 (exporter: alpha 1.2), exporting Lux files to
L:PoserPoserPro2010runtimepythonposerscriptsposeluxtolux
Exporting figure Figure 1
Traceback (most recent call last):
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxPoserLuxExporter.py", line 165, in ?
ExportScene(scene, globalParameters).write(f)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxworkersPoserLuxExporter_workers.py", line 407, in write
ExportFigure(fig, self.globalParameters).write(file)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxworkersPoserLuxExporter_workers.py", line 136, in write
params).write(file)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxpydoughgeometry_export.py", line 32, in init
data = self.get_data_from_unimesh()
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxpydoughgeometry_export.py", line 80, in get_data_from_unimesh
materials = [self.convert_material(mat, key) for mat in uni.materials]
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxworkersPoserLuxExporter_workers.py", line 70, in material_converter
return MatConverter(mat, key).eval()
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxworkersBBLuxMat.py", line 107, in eval
s = self.eval2(key)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxworkersBBLuxMat.py", line 116, in eval2
root = BuildFromShaderNode(st.Node(0))
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 655, in BuildFromShaderNode
node = cls(importNode=snode)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 404, in init
self.importFromShaderNode(v)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 487, in importFromShaderNode
setattr(self, inp.name, inp.importFromShaderNode(snode))
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 220, in importFromShaderNode
n = BuildFromShaderNode(n)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 655, in BuildFromShaderNode
node = cls(importNode=snode)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 404, in init
self.importFromShaderNode(v)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 487, in importFromShaderNode
setattr(self, inp.name, inp.importFromShaderNode(snode))
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 220, in importFromShaderNode
n = BuildFromShaderNode(n)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 655, in BuildFromShaderNode
node = cls(importNode=snode)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 404, in init
self.importFromShaderNode(v)
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 487, in importFromShaderNode
setattr(self, inp.name, inp.importFromShaderNode(snode))
File "L:PoserPoserPro2010RuntimePythonposerscriptsPoseLuxluxmaticmatcore.py", line 215, in importFromShaderNode
v = inp.Value()
AttributeError: 'NoneType' object has no attribute 'Value'<span style="font-family:Arial, Verdana, sans-serif;"><br></br><br></br></span>
And that's all she said...
Edited to add, the setting is one figure with a dozen body parts (the individual buildings).
Attached Link: http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2809884
Now is finished and working fine, at least one stage.Stupidity also evolves!
Quote - > Quote - Has anyone done a render that looks like it couldn`t be done in poser yet?
Yes, Laurie has... the second render of that building and trees in front would have been impossible in Poser. Have a look a few pages back...
Page 43 to be specific. Just stumbled into this thread, and was very curious about the results. In case anyone else wanted to see it, the image that Laurie created is here.
Intel Core i7-8700 6-Core 3.2 GHz (4.6 GHz Turbo), 32GB RAM, two GeForce GTX 1080 Ti GPUs
DS 4.10, Photoshop CC and CS6, Poser 11 Pro, Vue 2016, CarraraPro 64bit, Autodesk Inventor, Mudbox, and 3DS Max
One in 68 children is diagnosed with autism. One is mine. ♥
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Oh, right facepalm! So sorry about that Dizzi :o). Now we have to make links to those threads on the Wiki pages...lol.
Laurie