Akihito Okimura

akihito20x0

About Me

Connect

LOCATION
WEBSITE

Houdini Skills

Availability

Not Specified

Recent Forum Posts

Does H22 change how 456.py works? Sept. 23, 2026, 8:59 a.m.

kodoragon
No way this is the intended behavior. And if it were, that'd be a really bad design.

You think so?

Personally I don't think packages should handle 456.py.
If it's the case of 123.py, it's understandable for me though.

456.py is a startup script that runs when a scene is created or loaded.
I think it's for a designer or a machine. It's not for a system(including packages).

I also have some complaints about that.
For example, then why does it ignore my local 456.py or something like that.

But it works just like the previous version now. It works for me.

Anyway you can make a feature request.

Does H22 change how 456.py works? Sept. 22, 2026, 6:52 p.m.

Regnareb
Where in the specification does it says that?
There are bugs that were there 10 years ago, they are still bugs despite their lifespan.

If only one 456.py can execute, it means any package overrides any other package functionality. That would be crazy.
Regnareb
Where in the specification does it says that?
There are bugs that were there 10 years ago, they are still bugs despite their lifespan.

If only one 456.py can execute, it means any package overrides any other package functionality. That would be crazy.
Regnareb
Where in the specification does it says that?
There are bugs that were there 10 years ago, they are still bugs despite their lifespan.

If only one 456.py can execute, it means any package overrides any other package functionality. That would be crazy.

SideFX guys said.
Anyway I don’t think they leave a bug for 10years.
It’s normal for me.

Does H22 change how 456.py works? Sept. 22, 2026, 1:10 p.m.

Regnareb
The bug is not that Labs have a 456.pybut that Houdini don't execute all the 456.py. Each package should be able to have those files otherwise it would be a management nightmare.

This code doesn't check for recursion but it should check for all 456 files.

import os
for path in hou.houdiniPath():
    if (os.path.exists(path + '/python3.11libs/456.py')):
        exec(open(path + '/python3.11libs/456.py').read())
    if (os.path.exists(path + '/python3.13libs/456.py')):
        exec(open(path + '/python3.13libs/456.py').read())
    if (os.path.exists(path + '/456.py')):
        exec(open(path + '/456.py').read())

But previous versions or older versions are the same.
It's the specification.