Jump to content

Search the Community

Showing results for tags 'redshift'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Lounge/General chat
    • Education
    • Jobs
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering
    • Compositing
    • Games
    • Tools (HDA's etc.)
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Found 51 results

  1. I’ve got a simple voronoi fracture sim with added edge detail (from Jonny Farmfield's example). An object from two Boolean’d spheres falls and breaks on the ground. Everything is working great except I can’t figure out how to get my RSNoise bump texture to stick to my fractured pieces. I’ve tried to do everything suggested from my search results, but it’s not working. I tried to create a vertex UV attribute as well as a rest SOP to no avail. I’m quite certain it’s something simple. Always is. On a side note, I am creating three point attributes from boolean and fracture groups to pass to my redshift shaders, inside, outside, and ainsideb. This works great and is picked up by RS even though I’ve not specified that the attributes get passed through my assemble SOP. When I do pass them though explicitly they get all jumbled up and don’t correspond to the right points anymore. Does redshift just figure out these attributes on it’s own. They aren’t even listed in the Geometry Spreadsheet yet work correctly. I didn’t want to assume this behavior as it might be messing up other attributes needed for the noise to work. I’ve attached a file. simple.edge.displace.v7.hiplc
  2. Hi ! I am working on RBD in Houdini 16.5.268 and I render it with redshift 2.5.56 I have some problems during the rendering : we see the edges of the fractures ! I tried a lot of things without managing to get rid of it. It works fine in mantra, no artefact. My geo has UVs, Normals and rest position. Do you have any idea of how to correct that please ? Scene is attached and some pics of the results. PS : I also had other problems while rendering rbd in redshift. In some scenes, applying two different materials with different displacement values on inside and outside groups of an object results with a gap between inside and outside faces. In other scenes, the displacement of inside surfaces flicked. It seemed that it was moving along time, I didn't find out why. I read the redshift documentation and watched several tutorials but maybe I don't work the correct way with displacement in redshift, could someone help me ? Thank you very much ! Have a good day ! no tessellation no displacement tessellation no displacement no tessellation displacement tessellation displacement mantra displacement material MAT_prob_v01.hipnc
  3. REDSHIFT AOV EMPTY

    if I render with redshift my aov are always empty, whether zdepth, gi, diffuse raw....
  4. Redshift_Mesh_Light

    I'm practicing on Redshift from Rohan Dalvi tutorials but i stuck where he using geometry light or known as Mesh light, it doesnt work for me the mesh is there and linked with the RS_light node but nothing happen
  5. Hi guys , Recently I followed some tutorials and made this guy. but when I start render at Redshift, It is too thin that I can't see. Just like this T_T When I rendered it in Mantra, It looks like has thick wire rightly, but I don't like this look. So I wanted to render this man in Redshift and looking for some clever guys giving me some tips about it. Sorry for my poor English ! and Pleas help me ! Thanks for read and have a good day
  6. My houdini version is 16.0.736 ,I read the official document the plugin 16.0.705 can compatible with Houdini 16.0 version 705 and above. But I failed. Just like this.
  7. My houdini version is 16.0.736 ,I read the official document the plugin 16.0.705 can compatible with Houdini 16.0 version 705 and above. But I failed:
  8. Hey magicians, I'm trying to render millions of particles, I'm using a method I saw in Peter Quint videos using the wedge rop, my issue is when I load lots of instances, pc gets super slow. PQ recommends to use packed disc primitive to avoid this, but when I use, I can't read attributes other than P on the instance redshift, so I can't apply things like motion blur. Any recommendations to solve this? Thanks!
  9. Hey magicians, I'm new to redshift, I'm trying to generate some sort of glossy particles to add some sexyness, but I can't get the desired result. What I tried is making 2 instances, 1 with the full point cloud, and the other with the glossy ones, but I can't make them to pop like the references. References: } What I have so far: Thanks!
  10. Hi, In building a terrain, I used Entagma's tutorial on live rendering of Heightfields in Houdini using Redshift: The issue I'm running into is that my UV's are now super stretched on the terrain from using displacement on a grid. My terrain is huge, like 8,600 units across square. If I convert to polygons, it's pretty heavy. I'm trying to figure out the best workflow that will allow me to have the detail I need, but not be so polygon heavy. Would exporting out some lower resolution geo for rendering along with a baked displacement map be a good option? I need to be able to somehow edit the UVs as well so they are not stretched on my terrain texture. Any help would be appreciated. Jim
  11. Hello, I recently went through Steven Knipping's tutorial on Rigid Bodies (Volume 2). And now I have a nice scene with a building blowing up. The simulation runs off low-res geometry and then Knipping uses instancing to replace these parts with high-res geometry that has detailing in the break-areas. The low-res geometry has about 500K points as packed disk primitives so it runs pretty fast in the editor. Also, it gets ported to Redshift in a reasonable amount of time (~10 seconds). However, when I switch to the high-res geometry, as you might guess, the 10 seconds turn into around 4 minutes, with a crash rate of about 30% due to memory. When I unpacked it I think it was 40M points, which I can understand are slow to write/read in the Houdini-Redshift bridge, but is there no way to make Redshift use the instancing and packed disk primitives? My theory kind of is that RS unpacks all of that and that's why it takes forever, because when I unpack it beforehand, it works somewhat faster - at least for the low-res. The high-res just crashes. I probably don't understand how Redshift works, and have wrong expectations. It would be nice if someone could give me an explanation. Attached you'll find an archive with the scene with one frame (Frame 18) of the simulation included as well as the folder for the saved instances of low- and high-res geometry. Thanks a lot for your help, Martin (Here's the pic of the low-res geometry, the high-res is basically every piece bricked down into ~80 times more polygons.) Martin_RBDdestr_RSproblem_archive.zip
  12. Hello All, I have created a model in Houdini which consists of 6 different sections. All those areas have their unique Point attribute, so I merged everything into one object with the help of VDB and transferred all the point attributes. I would like to have a different shader on all those 6 sections of the geometry. My approach was to create one Redshift Shader network and with the help of Blend material and Unique attributes for Blend weight, separate all shaded areas. But for one of the areas I needed to use separate Blend Material and a different displacement. So do I need to create Groups based on those Unique attributes and assign shader within the geometry node with 6 unique Redshift Shader networks? Or there is a way to assign those 6 shaders by the attribute?
  13. Hello fellow scientists,I am currently working on a shot where I want to render out an indoor-explosion over about 50 frames. Now since I can't get my mantra render-times below 20 minutes (in FHD) I had hoped to render the volume in redshift more quickly because I have had good experiences with rendering just density in RS.The problem comes up as soon as I start to use emission with redshift. I start to get very weird boxes of emission around the edges of my volume (it seems to be like 16 cubed boxes of voxels reminding me of compression.) - screen attached. Screenshot_50 has about the look I want to achieve, but with this weird halo. When I amp up the emission, the boxes become apparent.Not sure if I tried switching to VDB to render, but I'm not hopeful that would change much.Has anyone come across this issue before?Attached is also my hipfile with the way I set up my render and one cached frame so you don't have to sim again. (Including my approach to an indoor-explosion for anyone who might learn something from that - please do!)I would really appreciate any thoughts on this. (And if my decision to move away from mantra in this case is actually remotely sensible - I'm really unsure.)Thanks,Martin Grenade_RnD_v20.hip
  14. PIPELINE TD NEEDED

    Hi everyone, We're urgently looking for a solid Pipeline TD to join our growing team in Bournemouth, UK. Must be eligible to work in the UK. Desired knowledge/expertise: Maya, Houdini, Redshift, Golaem Crowd, Python, Deadline, Windows and Linux, UI design, solving per show render and data-flow challenges, liaising with department heads. We are an 80-seat full service VFX studio working on film, TV and commercials. Recent projects include Life, 47 Meters Down, Philip K Dick's Electric Dreams and Nocturnal Animals. We are looking to expand even further over the coming months to accommodate a number of big shows that we've won recently. We operate a little differently to a lot of our contemporaries, putting staff treatment first and encouraging healthy work/life balance through 7-hour working days and discretionary overtime/TOIL for the odd occasion that deadlines stack up. We're five minutes away from the beach, too. If you get the chance, please check out what we've been up to at www.outpostvfx.co.uk! IF YOU'RE INTERESTED, PLEASE EMAIL US AT TALENT@OUTPOSTVFX.CO.UK. Can't wait to hear from you!
  15. I understand the relationship between Unified max samples and so called 'local' samples. And the importance of keeping Unified samples less than Local samples. But what I find confusing is the relationship between BF, material and light 'Local' samples. Which takes priority and is there a recommended sequence of steps when reducing noise?
  16. I can't figure out how to get the output created by the "Sky Rig" shelf tool from the Cloud FX shelf to render with Redshift. I have no similar issue with the volume created by the "Cloud Rig" tool, although both seem to me like they create a VDB volume with a channel called "density" (which is what I've tried to render in Redshift with an "RS Volume" shader, which again works just fine with the kind of volume that "Cloud Rig" creates). What am I missing?
  17. Hi all, I want to import a particle simulation from houdini to Maya without using the Houdini engine and render in Redshift. I made a way around it stamping spheres into particles and exporting them as Alembic, but the file is too damn heavy. Do you have any suggestion? Thanks in advance.
  18. Seven Dancing Swirling Blobs

    This is an enhanced version of an earlier animation. This time it was rendered with a dual 1080GTX G1 and 960GTX in Redshift. So instead of taking 3 hours, it took about 1hr30 - I guess there are ways of making it quicker but I'm still in the learning process
  19. [REDSHFT] Materials

    Hi, I am looking for redshift shaders/materials to buy. I am also intrested in importing/converting fbx materaials to Redshift. Anyone have any suggestions? It seems to me that a nice set of materails would make Redshift or houdini a lot more powerful...
  20. I made this video to try out Houdini's Texture Bump mapping, Popnets and Transparency with Redshift... I also wanted to break things!
  21. What are the benefits/applications to creating an .rs proxy of a light? I only ask because I did not realize I was creating an .rs proxy of my object and the light in my scene when I created my archive. I realize now that I just have to check on the "export only selected objects" and it will exclude the light. It would have saved me a few hours of digging if that was checked on by default. Thoughts?
  22. Terrain Building in Houdini

    Hello Everyone, This training is will cover the new height field tools introduced in Houdini 16. The training comprises of 5 projects that will cover techniques to create a variety of terrains. Over the course of the projects the videos will cover a majority of the heightfield tools such as noise, pattern, mask by feature, heightfield layer, erode, heightfield wrangle etc. The training is available for Redshift, Arnold, Octane and Mantra. For more information kindly click on the link given below http://www.rohandalvi.net/terrains
  23. In order to support Stylesheets, RS has to first support Material Override, which has been completed. Next step is Stylesheet support.
  24. Im just getting into redshift and I have been googling around try to figure out if using the instancefile att is possible. I would like to instance files off disk so that I can have control over the frame of the cache that I'm instancing. I set up this simple test scene so feel free to take a look and point out what I have missed. Thanks, Stephen rs_instance.hip
  25. Hi My understanding is that any light names you enter into the Light Mask field will influence that geometry. So a wildcard ‘*’ means ALL lights will influence and by preceding the light name with a ^ symbol, you can subtract that particular light. But it is not working for me. Is there some setting in the RedshiftOBJ parameters that I am missing?
×