hi.
i have a problem with houdini console.
in vex code i have printf function that prints a lot of lines. but houdini console doesn't keep all the lines and after printing, first lines are gone.
is there anything like low buffer or something like that is causing this?

how can i solve this problem?

Configure your console program with longer buffer.

Then run houdini

houdini_setup_bash
houdini -foreground



UPDATE: only for linux

I'm new in Houdini, can you explain more?

i use on win, and this codes just run Houdini, and after that i don't know what should i do.

i hope if you can help me to solve my problem.

The houdini console on Windows is actually a little window that pops up, so configuring a shell won't help. You can set an environment variable to increase the length of the console, though, using HOUDINI_CONSOLE_LINES, which is 256 by default. You can increase it up to 65535.

I add “HOUDINI_CONSOLE_LINES = 1024” in houdini.env on my document.
but that doesn't work.

when i query variables with “hConfig -a”, HOUDINI_CONSOLE_LINES = 256.

where is my fault.

Same here, set it in the .env file as well as in the system's env var.

To no avail.

It's sad because this is the only debuging tool for python nodes that uses external libs.

Still not working as of this date ?
I tried and not working, still imited in the Houdini Console output to ~256lines, this is bit frustrating

I think LogViewer should replace console. You just check catching Standard Output and it's much better.
Way faster, has search and filters etc. On Mac it's basically the best option not requiring awkward launch from terminal.

unfortunately windows implementation is lacking

in theory HOUDINI_DISABLE_CONSOLE should work but disabling console also disabling standard output

so you left with this:


at least all entries are in viewer but still developer experience is a bit interesting console responsiveness is very bad and it blocks ui, while logviewer is instantaneous

this windows console just should go and not be an optional even