Iwanz

Sorry guys, I found the solution: just click on one of the green dots of the TOP NET from STAGE.
I'm very embarrassed

hello everyone,
my question: I used the TOP file_pattern node to iterate on a series of FBX geo inside a certain folder, I then used the related attributes (filename, directories and extension) inside the STAGE component_builder to automate a series of operations (for example importing said FBX in the component_geometry).
The first time I use the system everything is ok, the problem arises if I want to repeat the operation by changing the folder on which to iterate: although in TOP everything seems to work properly (the working items produced by the file_pattern are all correct, as well as the related attributes), inside STAGE their values ​​are not updated, as if STAGE, instead of from TOP, went to read them from somewhere else, like a cache or a file that it generates autonomously.
I tried everything: from the obvious dirty and cook of the TOP nodes to deleting and redoing the TOP network from scratch, but the data in STAGE always remain those of the first iteration.
The only way I could work around this is to rename the attributes coming from the file pattern node, but it's really inconvenient and inefficient.
Do you know of any way to force STAGE to read data from TOP?
And as far as you know, is this its normal behavior or is it a bug?
Thanks in advance

Same here but, at least in my case, performances are terrible: a simple grid with 800*800 divisions is sufficient to “knock out” the view port.
I have tested the two builds (regular and Qt4) on Mint 18 and Centos 6.8 with the same results.
Waiting for new builds I stay with Houdini 15.5