Ævar Guðmundsson

agudmund

About Me

Connect

LOCATION
Not Specified
WEBSITE

Houdini Skills

Availability

Not Specified

Recent Forum Posts

working with unicode in python Feb. 20, 2013, 10:39 a.m.

Using Fedora 12

In an interactive python shell:
>>> print ‘Porks Werfect’
Porks Werfect
>>> print u'Porks Werfect'
Porks Werfect

In Autodesk Maya Script editor:
print ‘Porks Werfect’
Porks Werfect
print u'Porks Werfect'
Porks Werfect

In sideFX Houdini python shell:
>>> print ‘Porks Werfect’
Porks Werfect
>>> print u'Porks Werfect'
Traceback (most recent call last):
File “<console>”, line 1, in <module>
File “/opt/sidefx/hfs12.1.185/houdini/python2.6libs/hou.py”, line 28613, in write
return _hou.ShellIO_write(*args)
TypeError: in method ‘ShellIO_write’, argument 2 of type ‘std::string const &’

I'm not sure, but at a quick glance and not with full access to _hou.so, this in there within in reference to the error above :

invalid null reference in method ‘ShellIO_write’, argument 2 of type ‘std::string const &’

So perhaps it's only when unicode characters are somehow returning None, that this error comes up?

Nothing major, but it does require most multi-application debug verbosity to be modified explicitly for Houdini in order to get the full printout, so any insight into what the actual bug is will be helpful.

Accidentally Cooking with the Houdini Object Module Dec. 11, 2012, 2:15 p.m.

hehe, it gets confusing even trying to describe it

I don't want to cook the scene at all, just want to open it for quick debugging.

Both methods described above result in some cooking in one form or another, and it's using a combination of hou.hipFile and hou.hscript.

It's dirty coding, but it appears to be the only way to not cook…….

Accidentally Cooking with the Houdini Object Module Dec. 11, 2012, 9:44 a.m.

edward
Shouldn't you reverse the order of the commands?

Indeed, that was my initial assumption.

What happens however, is first the viewupdate setting gets set to manual, and then the .hip file loads and cooks.

For some bizarre reason, loading the scene and then setting the viewupdate immidiately afterwards appears to stop it cooking. Don't actually see the logic in it, since it makes sense to do it the other way around, but as I said, it works, in a way, but feels backwards so I am under the impression it's not the order of commands that is backwards, but my methodology rather.