Jump to content

Search the Community

Showing results for tags 'Mantra'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Lounge/General chat
    • Education
    • Jobs
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering
    • Compositing
    • Games
  • 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 183 results

  1. Hi everyone, I am trying to convert a displacement map from tif to rat with iconvert. I am getting some weird results and I am hoping anyone here might be able to tell me what the actual problem is. In the image you can see the different results I am getting. Only the original tif gives me the results I want. 8 bit is wrong of course but I thought I'd still include it. I am using the classic shader in Houdini 16. Thanks in advance
  2. Hi ! I just wanted to familiar with Mantra renderer. but It takes my time too long that I'm now just considering to buying Redshift or Octane .. Of course I know Mantra is cpu renderer. but I just added glass sphere and metal face modeling in the scene. and It takes about 5~8 minutes (default mantra setting) Did I have to do something ??? If you have some tips for Mantra rendering .. please let me know T_T and I want to know why houdini users love this renderer. I'm beginner of Houdini. Help me please !
  3. Hi! First post in this forum, I'm a newcomer to the Houdini world, recently researching Houdini FX and playing with the indie version, as I think, given time, it could be my main working tool (such an amazing beast!). I'm considering using Arnold with Houdini, as I am already familiar with it, but a question arises: what are the current limitations I will stumble upon with this choice on the long run? What kind of scenes and behaviours will need me to failback to Mantra or apply non-obvious workarounds? What worklflow issues have you found when working in a Houdini + Arnold production environment? Thanks in advance!
  4. I want to spawn some particles (rendered as sprites) and have their entire quad drawn every time -- even if it the quad is intersecting with other scene geometry! Is this possible? I have done this in OpenGL where I just disable depth testing before I draw my particle system but I couldn't find any option like that in either the POP nodes or the shaders. One terrible option would be to render every frame twice, once with the scene geometry disabled and one with the particles disabled and then composite them on top of each other... but that can't be the correct answer. I want to do this because I am trying to recreate the kirakira filter on iOS which overlays the image with jumbo starburst sprites to simulate a combination of glints and diffraction spikes hitting a lens. intersecting_sprites
  5. Greetings! To anyone using Deadline for rendering Mantra, could you advise what your successfull workflow is, please? I have a couple of questions about the HoudiniSubmitToDeadline parameters that I can't find definitions for in any docs. This url is the most useful: https://docs.thinkboxsoftware.com/products/deadline/10.0/1_User Manual/manual/app-houdini.html Q1 - machine limit & Mantra Threads defaults are 0. Do I need to change this value, or is zero ok? Q2 - "Submit Houdini Scene" is OFF by default. Is this correct? Q3 - "Ignore Inputs" is ON by default. Which inputs is it referring to?? It's currently only rendering successfully if I DONT generate .ifds first, which is obviously not correct. I am ticking on "DiskFile" in the Driver tab of /out/mantra1 Disk file = $JOB/ifds/$HIPNAME/mantra_$F4.ifd Shared Temp storage = $HIP/ifds/storage Local Temp storage = $HOUDINI_TEMP_DIR/ifds/storage I launch Render->SubmitHoudiniToDeadline Pool = 3d group = None ROP to Render = Choose = /out/mantra1 Under MantraExport Submit DependentMantraStandalone Job is checked ON Pool = 3d group = None 2 tasks are submitted, which is normal. First task generates .ifds again (I think this can be avoided by select SkipFilesThatExist in /out/mantra1 IMAGES tab Second task is supposed to write .exrs but fails. Yes, the folder is writeable. Pipeline are looking into the error: INFO: Process exit code: 1 2018-01-05 17:14:03: 0: An exception occurred: Error: Renderer returned non-zero error code, 1. Check the log for more. 2018-01-05 17:14:03: at Deadline.Plugins.PluginWrapper.RenderTasks Any pointers gratefully received. Many thanks, Olly : )
  6. Hello node friends ! I have a problem in hands here. Basically I'm doing a stadium crowd sim. So far so good. I'm then doing the shading over on the material style sheet and rendering with mantra. I also have a cloth sim with the same proprieties over on that style sheet. The problem I have here is the following: I can render the flags over on the farm with the IFD generation, I've included the SHOPs on the mantra ROP. That part is solved. When it comes to rendering the Crowd, it just renders black. I've tried caching out the results, using procedural geometries and the procedural agent SHOP but it still renders black. I can render it just fine on my machine, when it comes to the IFD rendering part, the machines can't render it. Notice that I have all the agent caches and maps over on a shared network drive that it can access, otherwise the cloth wouldn't be able to render it either. Any ideas?
  7. Hi. I don't know how many people actually go crazy with crowds and render them but after simulation fun, all the flipbooks, there's rendering nightmare. I solved many issues but this just beats me - does anybody know what could be the cause of random parts of the agents disappearing? The smaller ones, knights, are taken from Mixamo and they never flicker, but the bigger ones, baked before and and all that stuff, just go crazy. Some of them are ok the whole time, some of them partially disappear and reappear. I'm out of ideas. They're ok in the viewport. Some short videos: https://youtu.be/gxx_bYH19Hk https://youtu.be/jCpBqh-GAb0 I've attached a screenshot. Is it the scale problem? (they have a scale of 3, with some randomization). But why do we have scale then... I put them in separate network, so after the sim each group is in its own GEO node, because at first it seemed to solve the problem, but no - different frame and it's back again. I've reopened the scene, restarted the computer, rendered several times. I've removed the shader, changed it to simple Principled Shader without any adjustments - nothing helps Any tips are welcome.
  8. Space Suit

    Hello I've started with this around H 16 release. Basically wanted to explore, to which level I'd be able to use procedural modeling when it comes to characters. So, "non procedural" part here belongs to another app, exactly Maya, where I've created a base body model, rig, posing - while Houdini part is hair of all sorts (hair, eyelashes, eyebrows..), also a lot of suit. Detailed map, what exactly belongs to which app is here. Let's say that 'harness system' is what I'm considering as most successful part. Later, started with Mantra renders, which turned out in kind of addiction - here are few of around hundred renders of this thing, I did in Mantra.
  9. Hi! I have a question about mantra and world position pass. I have followed aRtye's description from this page: https://www.sidefx.com/forum/topic/34302/ and set up a P_world pass that renders in Mantra. The problem is that I get an edge when grids are overlapping each other (see image below). I have tried getting rid of the edge by lowering the opacity limit in the Mantra node, but that gives a black edge in the C pass. Removing the filter from the alpha channel in the shader gives a slightly better result, but nothing I have tried gets rid of the edge completely. Does anyone know a solution to this problem or a better approach to get a world position pass? Example file (using the Houdini butterfly image file): p_world.hip
  10. Hello, I have encountered strange difference in render outputs from different computers and I have hard time figuring out what might cause this to happen. I have created scene on my laptop and then tried to render it on workstation. Both computers have the same Houdini version installed (16.0.736) but they produce different results when rendering. I am attaching both renders - first one rendered on laptop and second on workstation. On second picture, there is strange noise and highlight around area in the middle (exactly where the point light is located inside cloud). I was rendering the same scene and I expected the result to be the same as on my laptop. The main difference is that my laptop is running on Linux while workstation is running on Windows. Also there are different CPUs in these two computers (laptop - xeon; workstation - i7), but I guess that should not make any difference. Please, does anyone know what might cause this difference in renders? Thank you very much. Best regards Trandzik cloud_test_01.mantra1.0001.exr cloud_test_01.mantra2.0001.exr cloud_test_01.hiplc
  11. Hi all, I am attempting to render out hair curves and only have them generate at the time of render. As I understand it, setting the hairgen node (created from a fresh scene from the shelf on a rubber toy object) render parameter to Hair Generation = "Generate Geometry in Mantra" is supposed to do just that. If I switch that parameter to "Use SOP Geometry", the hair renders out fine, but that defeats the purpose of not writing out the geometry beforehand and thus bloating the size of my IFDs. Otherwise none of the hair renders. Has anyone seen this happen or know what needs to be changed in the scene? Is this a bug? This is using HoudiniFX, v16.0.619 I cannot supply my scene file, nor screenshots, but this is happening in both my actual scene file and in a fresh launch of houdini with simple geometry as the only geo in the scene.
  12. Help With Speeding Up Render

    Hi all, I was determined to get a clean render out of mantra for this sequence, which I sort of managed to do, but the render times are just too high. I'm looking at over 5 hours per frame for something that is quite simple, as you can see from the attached screen shot. I could get something that looked reasonable, but to stop the highlights crawling between frames I just had to turn pixel samples up high. Nothing else seemed to sort out this problem (light quality & reflection quality just didn't work). The particular point I focused on was an area on the glass, on the centre of the image at the top - there's a small rectangular reflection from one of the lights, and where this went over the inner lip of the glass there were just always fireflies. The only thing that removed them was cutting the colour limit to 4 (from 10) which dulls the image, and turning up pixel samples to 12x12, which everyone seems to think is very high. I feel there's something I'm missing when it comes to getting a clean render. I've attached the hip file which contains the geometry and the hdr so, if anyone is able to help, just open the scene and see if you can get a better render time than I did. Petri_Dish.7z
  13. Hello guys, there are so many old threads how to render the big amount of particles, I'm guessing maybe there are some modern approaches in newer Houdini versions? Here is my workflow: I have saved 100 mln of particles (pos, vel, color) It takes 3 min to render and 30GB of Ram if I load them by Load SOP. It takes 2-3 times quicker if I use Delayed Load Shader. But it's hard to use it coz I have procedural particle scale, dynamically changing colors by vex, etc in SOP level. Re-make everything in shader seems too complicated in my case. Also, I tried Packed Disk Primitive in Load SOP. But to make color, pscale changes I must unpack it and performance drops like loading file as usual geometry. Any other suggestions how to deal with big point counts? Maybe there is any more modern way? Thank you in advance.
  14. Hey All, I am trying to instance high res geometry onto low res packed points and then render some extra image planes such as a velocity pass for compositing. I set up a scene with the instancing and rendering setup that I am currently working from. To set up the custom image planes, I use a bind node to import the velocity attribute I want written to an image plane and then wire that into a bind export node to export it to the surface context. Then in the mantra node, I create the extra image plane which reads the exported velocity attribute and writes it to an image plane. This setup seems to be working with the packed fragments but doesn't seem to be working with the packed disks. As far as I can tell, the issue lies with the first bind node not successfully importing the velocity data. I do believe that the bind export IS working which I tested by wiring a constant vector value into it. If you can think of a solution to this issue, I would very much appreciate it! Thank you! WillSoko packedDisks_v01.hipnc
  15. Hello friends, I was using Arnold for a long time while also playing with Mantra, but until now I never really had a time to dive deep to Mantra. The thing I really adore about Arnold is that in its settings it has this beatiful "Samples calculator". It seems just like a small detail but in my personal experience it was a great help for optimizing heavy renders. So few weeks ago I decided that I would try to create some similar calculator for Mantra. At first I implemented it by Arnold example which works like this (I'm not 100% sure with the equations but in my tests they work ): Camera (AA) Samples = pow(Camera (AA) samples parameter, 2) Diffuse Samples (Min) = pow(Camera (AA) samples parameter, 2) * pow(Diffuse samples parameter, 2) Diffuse Samples (Max) = pow(Camera (AA) samples parameter, 2) * pow(Diffuse samples parameter, 2) + (Diffuse depth parameter - 1) * pow(Camera (AA) samples parameter, 2) Specular Samples (Min) = pow(Camera (AA) samples parameter, 2) * pow(Specular samples parameter, 2) Specular Samples (Max) = pow(Camera (AA) samples parameter, 2) * pow(Specular samples parameter, 2) + (Specular depth parameter - 1) * pow(Camera (AA) samples parameter, 2) Transmission Samples (Min) = pow(Camera (AA) samples parameter, 2) * pow(Transmission samples parameter, 2) Transmission Samples (Max) = pow(Camera (AA) samples parameter, 2) * pow(Transmission samples parameter, 2) + (Transmission depth parameter - 1) * pow(Camera (AA) samples parameter, 2) Total (No lights) Samples (Min) = Sum of all min samples above Total (No lights) Samples (Max) = Sum of all max samples above But soon I realized that Mantra does not work this way. (Well yes, it was silly to think it works the same way ). So after reading a lot about how sampling works in Mantra and talking to my friends I came up with this calculator: ray_count_calculator.hdanc Which counts ray count like this: Camera Samples (Min) = clamp(Pixel samples X parameter, 1, ∞) * clamp(Pixel samples Y parameter, 1, ∞) Camera Samples (Max) = clamp(Pixel samples X parameter, 1, ∞) * clamp(Pixel samples Y parameter, 1, ∞) Diffuse Samples (Min) = clamp(Pixel samples X parameter, 1, ∞) * clamp(Pixel samples Y parameter, 1, ∞) * Diffuse samples parameter * Global multiplier parameter * Min ray samples parameter Diffuse Samples (Max) = clamp(Pixel samples X parameter, 1, ∞) * clamp(Pixel samples Y parameter, 1, ∞) * Diffuse samples parameter * Global multiplier parameter * Max ray samples parameter Reflection Samples (Min) = clamp(Pixel samples X parameter, 1, ∞) * clamp(Pixel samples Y parameter, 1, ∞) * Reflection samples parameter * Global multiplier parameter * Min ray samples parameter Reflection Samples (Max) = clamp(Pixel samples X parameter, 1, ∞) * clamp(Pixel samples Y parameter, 1, ∞) * Reflection samples parameter * Global multiplier parameter * Max ray samples parameter Refraction Samples (Min) = clamp(Pixel samples X parameter, 1, ∞) * clamp(Pixel samples Y parameter, 1, ∞) * Refraction samples parameter * Global multiplier parameter * Min ray samples parameter Refraction Samples (Max) = clamp(Pixel samples X parameter, 1, ∞) * clamp(Pixel samples Y parameter, 1, ∞) * Refraction samples parameter * Global multiplier parameter * Max ray samples parameter Total (No lights) Samples (Min) = Sum of all min samples above Total (No lights) Samples (Max) = Sum of all max samples above While using premise that these parameters in Arnold and Mantra influence the same things: Arnold Camera Samples = Mantra Pixel Samples Arnold Diffuse Samples = Mantra Diffuse Quality Arnold Specular Samples = Mantra Reflection Quality Arnold Transmission Samples = Mantra Refraction Quality Arnold SSS Samples = Mantra SSS Quality But there is a catch: In Arnold if you set Diffuse Samples to 0 you will get black diffuse indirect pass In Arnold if you set Specular Samples to 0 you will get black specular indirect pass In Mantra if you set Diffuse Quality to 0 you still get samples in diffuse indirect pass In Mantra if you set Reflection Quality to 0 you still get samples in reflection indirect pass So I think we can be sure that Mantra pixel samples fire also diff/refl/refr/sss samples - so when having diff/refl/refr/sss parameters set to 0, their corresponding rays cant be 0 (but I really don't know and can't find out how much of them is fired) Also pay attention to the clamping of pixel samples - in my tests pixel samples parameters were always clamped like this: clamp(Pixel samples parameter, 1, ∞) - when using values lower than 1 the result was always the same as when using 1 This catch made my calculator useless It seems that Mantra fires all kinds of rays even when using pixel samples only while Arnold does not. I personally did not expect this behavior and as far as I know it is even not documented. (Or at least I could not find it). I spent few days trying to figure out how these parameters could relate to each other but I did not find any good solution. So in my frustration I decided that it would be probably better to ask you guys if you did not try to create some calculator like this before or to find out how all Mantra parameters relate to each other I think it would be a great help for all Mantra users to find out how Mantra works "under the hood" Thank you very much for any advice and have a nice day.
  16. Do any of you experience with replicating 1 to 1 the look you have in Substance Painter in Houdini 16 using the Principled Shader? The PBR metal/rough workflow with the metallic and roughness maps seems to be straight forward, but plugging in my maps from Substance Painter as is, produces a render that is much darker than what I have in Substance Painter. Perhaps the colour space is off?
  17. Mantra render trouble

    Look at my render here... Notice I have these funny effects where some render buckets appear to not have finished rendering. I have pasted in my mantra settings to the right top and bottom. What is causing these render anomalies?
  18. This is a personal project i've been working on in houdini . so hope u like it .
  19. Does mantra do not have a motion vector pass? If so how to render it? Every explanation I found on internet is quite old from 2009 I can only hope there are new methods to do this, right? Any help will be appreciated.
  20. Hey, I am rendering to disk a 400 frame ocean simulation. The ocean mesh and foam particles are cached out. I hit render to disk, and it will randomly stop rendering. No error. It even still has render dialog up. However, the file size on frame it is "rendering" currently doesn't change and there is no mantra checkpoint. It just stays sits and does nothing. I have to keep starting the job again and again. Once I start it again it keeps rendering till it randomly stops. What could cause that? This has happened to me before on other simulations. Thanks.
  21. 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
  22. Motion vector pass for pyro

    Hi GuysI faced a problem recently while rendering out my motion vector pass for pyro.I had cached out my pyro sim with a vel multiplier through volume vop as I did not want to change the shutter offset value more than 1 as it was giving me some artifacts.While rendering the motion blur what I get is fine as I have already a premultiplied velocity in my pyro cache.the issue is when I try to get a motion vector in my aov mantra doesnot show any info when I switch off the allow image motion blur option.When I keep it on then I get to see the aov. Strangely if I keep the allow image motion blur option switched off and put a value of shutter offset 1.1 then mantra starts showing the aov.I fail to understand this as I had already had vel multipler vop while caching it out and thus I dont need any shutter offset value(its at default value 1).NOTE: I tried h14 and h16 all same results.(just thought maybe due to some bug issue)Please advice.
  23. Canary Surge V2

    Hi there! this is my new Canary Surge V2, improved workflow for whitewater, foam and shading stuffs.Please watch in HD 720. Vimeo compression kill of the fine details sorry. http://ipsvfx.com/project/canary-surge-v2/
  24. Rendering Pyro

    I'm clearly being an idiot here. Can someone explain to me why if I render a pyro sim from two different cameras it looks totally different - even the alpha is different? One is wide and far the other is close up. One directional light, mantra. Is this a scattering issue within the shader? I'm using the stock pyro material but I've removed the flame colour bits and thrown in a heat>fit>ramp into the emitcolor instead.
  25. In mantra render, Micropolygon, Ray tracing and Physically Based Rendering (PBR), which one is faster ? What is the limitation ? ( My need : still image, different materials, no motion blur, no fur) Thanks.