Are you ready to join Kitware’s ParaView free Webinar ?
These first two sessions will happen in March and be focused on ParaView 5.8 new features.
During these 1 hour sessions, you will not only be able to follow our explanations and hands-on demonstrations of the new features, but you will also be able to interact with the presenter via the chat and different interaction methods in order to ask questions or precisions.
On March 3, 10am GMT+1, We will focus on the new Interface Improvements of ParaView in general, with specifics such as the recent graphic overhaul, interactive data histogram and data exploration using range handles.
Please join us at : [link removed, no recording sadly] Click to add to your calendar
On march 10, 10am GMT+1, We will focus on the new rendering techniques in ParaView, with specifics such as Physically Based Rendering, Raytracing, and advanced GPU based rendering techniques.
Please rewatch it at : https://youtu.be/Xg6Y7Qui8gc Click to add to your calendar
The second webinar is tomorrow !
This time we will use youtube live to stream the webinar, which should fix our technical issues and allow us to share a recording of the webinar afterwards.
These webinar session are over ! Thanks to all that participated in it.
The second session was recorded and can be found here : https://youtu.be/Xg6Y7Qui8gc
If you have any questions or comments, please comment here.
Thanks for this very interesting webinar. It’s a great way to follow the latest developments and features in ParaView.
Following this morning webinar about rendering techniques, I had questions relatively to textures : how to manage textures on unstructured grid (OpenFOAM / Ensight multiblock datasets) or polygonal mesh (STL/OBJ files) ?
I am very new to rendering techniques, I’ve played around with OSPray and a bit of PBR and from what I understand with those datasets textures are mapped on each faces of the mesh, which kind of ruin the texture effect.
Is there a way to manage that in ParaView? Or should I just use other input formats ?
In order to map texture on your dataset, you need texture coordinates.
Here is a great explanation on how the these coordinates works: https://stackoverflow.com/a/5532670/2609654
If you do not have these coordinates, you can compute them using Texture Map to Cylinder, Texture Map to Plane, Texture Map to Sphere.
Please note that these are very naive ways to map texture coordinates to your object so you might want to rely on external tools for this (Blender for example).
Moreover, for the normal mapping texture, you will also need to have normals and tangents on your dataset. These are easily computed using Generate Surface Normals and Generate Surface Tangents filters.
Thanks Michael for your quick feedback, I think I get a better idea about how textures work.
I already used filters such as Texture Map to Plane and I would probably need to have a look to Blender (and learn how to use it!) if I want to work with a bit more complex geometries.
Hi Vincent,
The Luminous material is already integrated in ParaView.
Check under lighting property goup, there is a property called “Luminosity”. When the value is not 0, the material used is “Luminous”.
Cheers,
Michael
That’s when you use the PBR interpolation but is that the case when you try to load up a luminous material from a JSON file with the OSPRAY path tracer activated?
I’m not sure to understand, Luminous material is not related to PBR.
Here is a “Luminous” material (sphere) with a “Principled” material (box), without using any JSON file:
When we have a geometry with multiple parts that we map to materials loaded from a json file via a lookup table we cannot use the parameter that you just showed I believe. It will apply to the full geometry.
That’s why I was talking about the specific material “luminous” described in the Ospray documentation and we can apply on a part of the geometry if needed.
ParaView master let’s you define luminous materials for ospray pathtracer via the Json file and thus the lookup table. That feature missed 5.8 but will appear in 5.9.
As Michael indicates, the luminosity setting also maps to ospray luminous material type, but as you describe it applies at the actor level, and is not mappable to individual blocks or cells.
