Hi Everyone!
The basic idea (as you wil see in the hip) is colorize a simple grid with an animated metaball with attribute transfer, and try to accumulate the color information from the grid into a prescattered pointCloud file.
To test it out I made an attribute called myvalue with an initial value of 0.2 to the pointCloud. Write it out to disk.
In the shader the pciterate loop and the pcimport function seems to work well, because of the appearance of the grey spots at the positions of the pc points. But after comparing the “myvalue” with the luminosity of the shaded pixel, do not exporting the higher value into the pointCloud file. I would expect that -after rendering the sequence- the pc-file containing the updated values than the initial ones, so I could see the “path” of the traveling white circle as the grey points becoming white.
How should I rewire the network to write back data into an existing pc file's special channel?
(btw. I have to solve this in vop, because I have to expand an allready existing shader)
I'm stucked, so any advise will help.
thx
Feri
Found 4 posts.
Search results Show results as topic list.
Technical Discussion » Point Cloud Export Vex function in Vop
- uferi
- 24 posts
- Offline
Houdini Lounge » Render starts slowly
- uferi
- 24 posts
- Offline
edward: Unfortunately not a beta issue, because I tried allready with a 8.x (non-com. lic.) and experienced the same. Your question is good btw., but the faster respond after re-rendering a frame means not 40 but 25-30 sec. On my friend´s workstation (diff.company) the respond is immediate. We couldn´t locate the problematic parameter of the architecture.
Feri
Feri
Houdini Lounge » Render starts slowly
- uferi
- 24 posts
- Offline
Houdini Lounge » Render starts slowly
- uferi
- 24 posts
- Offline
Hi everyone!
First of all I'm a quite new user of the v9 beta in fact, but I try to make a tighter friendship with this software. Maybe I don't have to explain the reasons, I think those are quite obvious for everyone in this forum.
The first experiences are very impressive and straightforward but:
for example after creating a grid and a cube on it, placing a spotlight and creating a mantra render node and of course a camera to render from, the phenomena comes up:
After hitting the render button, nothing happens first. Then at the lower left corner the text says “(0%) mantra1 frame 1 : Rendering” and houdini seems to freeze. After a 5-10 sec the soft comes alive again, but nothing else. I'm waiting and the time goes by…and suddenly, after about 40 seconds the Mplay window pops up and the render really seems to start. The rendering itself is not slow at all but to get there is disturbingly long in time. I have to say it prevents me to find out almost anything about the shading-rendering- fine tuning.
Do you have any idea to set ENV variables or tweak our firewall ar anything to speed up the hole process?
Tech.spec.:
2 quadcore Xeon at 2.66Ghz - 8 cores together - so that is why I'm expecting faster respond (I tried to use only one proc. but no diff.)
Nvidia quadroFx 3450 - so the Ati issue is not related
runs on Xp
Thx,
Ferenc Ugrai
First of all I'm a quite new user of the v9 beta in fact, but I try to make a tighter friendship with this software. Maybe I don't have to explain the reasons, I think those are quite obvious for everyone in this forum.
The first experiences are very impressive and straightforward but:
for example after creating a grid and a cube on it, placing a spotlight and creating a mantra render node and of course a camera to render from, the phenomena comes up:
After hitting the render button, nothing happens first. Then at the lower left corner the text says “(0%) mantra1 frame 1 : Rendering” and houdini seems to freeze. After a 5-10 sec the soft comes alive again, but nothing else. I'm waiting and the time goes by…and suddenly, after about 40 seconds the Mplay window pops up and the render really seems to start. The rendering itself is not slow at all but to get there is disturbingly long in time. I have to say it prevents me to find out almost anything about the shading-rendering- fine tuning.
Do you have any idea to set ENV variables or tweak our firewall ar anything to speed up the hole process?
Tech.spec.:
2 quadcore Xeon at 2.66Ghz - 8 cores together - so that is why I'm expecting faster respond (I tried to use only one proc. but no diff.)
Nvidia quadroFx 3450 - so the Ati issue is not related
runs on Xp
Thx,
Ferenc Ugrai
-
- Quick Links