Do you know what kind of texture mapping VisualARQ is using?
As far as I can tell, VisualARQ is using the texture mapping I apply inside of Rhino.
Posts by rheinason
-
-
Hi Demian, Update from the VisualARQ guys. Did you have a look at the issue? Pretty sure it relates to blocks or similar. Could you go into a bit more detail on how I could use the Material Editor to adjust the texture mapping? I'd prefer using the Enscape Material Editor as that allows a bit more control in some areas.
I meant that you could make use of the material editor in Rhino instead, as this may already be helpful with what you're trying to achieve. I've adjusted my last response accordingly.
-
Thanks a lot! I'll file a bug report for this behavior accordingly since I was able to reproduce it.
Hi Demian, any update on this?
-
Maybe it can be implemented into the bump map somehow depending upon intensity.
Often displacement and bump maps are used in unison, one for lower frequency and one for higher though.
-
+1 for both Displacement and rounded edges! I also wanted to shoutout Blenders adaptive subdivision, as far as I can read about it, it works with OpenSubDiv. It works really well and could be an efficiency boost, both for preview and render settings, even if it's more of a final render type function.
+1 from me.
And if true displacement is too hard to make maybe take a look at Steep Parallax Mapping.
Looks pretty close to real displacement and is made for realtime use. See the links below.
http://graphics.cs.brown.edu/games/SteepParallax/In the live example below click and drag the mouse to change occlusion amount. Notice the "displaced" edges.
https://www.shadertoy.com/view/MtXyz7This also looks super nice and usable, maybe there's a universe where both could be added, so that when choosing Ultra on the render settings we'd get real displacement.
-
It would be really nice and save a trip to photoshop
-
If this object has been imported/created with the VisualARQ plugin, then the corresponding texture mapping might not (yet) translate into Enscape as seen in SketchUp. You can gladly send in the project so that I can also forward this file to our developers!
In this case, if possible, I'd recommend making use of our SketchUp material editor, again, if this would be an option for you only.
Using the SketchUp Material Editor in Rhino? And how would that help with the Texture Mapping? I've gotten a response from the VisualARQ developers who are claiming some of the blame.
-
Subject is pretty self explanatory
This is a pretty critical feature, is this related to Enscape or to VisualARQ?
-
As a amplitude slider, more or less bumpiness. Just like with a bump map. This is entirely a artistic slider, whether or not this is "correct" I don't know.
Alexander Devaykin Does that make sense? I'd image it would require a bit of math, making the normal more or less flat depending on the slider.
-
+1 Here too
-
Is this a enscape material collection? How are you going to implement it? Is it going to be available for all the platforms? Pricing?
-
major Rhino release
i.e. Rhino 7? Or the next RC?
-
Hi there, what exactly are you waiting for? McNeel usually are quite quick about things like this that impact a fair few users?
Demian Gutberlet Any news on this?
-
Hi there
This is sort of a crucial feature, when someone is working from home they often create enscape materials, but when they arrive in the office the image textures are gone, even with search paths being defined in rhino and so on, this issue is only with the Enscape Material Editor, the rhino materials find the image textures and if Rhino doesn't find the image textures if gives off an error and asks for a new location:
The Enscape Material Editor on the other hand completely screws us over and we need to redo the entire material, including any adjustments we made to the brightness or amounts relating to these images.
-
A bit of development for rhino users: Here's a script from Willem Derks from this thread. I added some adjustments so that it creates a enscape capable material including roughness map in the environment slot. NOTE: This script requires that each material is placed in it's own folder, I'll be doing some adjustments in the future so that it can find a map based on the file name instead.
Display MoreCode- import rhinoscriptsyntax as rs
- import scriptcontext as sc
- import os
- import fnmatch
- def findTexture(name, path):
- for file in os.listdir(path):
- if fnmatch.fnmatch(file, name):
- return os.path.join(path,file)
- def make_material_by_diffuse():
- diffuse_file = rs.OpenFileName('get diffuse texture')
- print 'diffuse_file :',diffuse_file
- texture_path = os.path.dirname(diffuse_file)
- print 'texture_path :',texture_path
- diffuse_name = os.path.basename(diffuse_file)
- #assuming a bump.png file present alongside the diffuse texture file
- bump_file = findTexture("*nrm*", texture_path)
- print(bump_file)
- environment_file = findTexture("*rgh*", texture_path)
- print(environment_file)
- new_material_index = sc.doc.Materials.Add()
- print new_material_index
- material_table = sc.doc.Materials
- new_material = material_table.FindIndex(new_material_index)
- new_material.Name = diffuse_name + " glossyenvironment"
- new_material.SetBitmapTexture(diffuse_file)
- if os.path.isfile(bump_file):
- new_material.SetBumpTexture(bump_file)
- new_material.SetEnvironmentTexture(environment_file)
- new_material.CommitChanges()
- #I don't quickly see how to make sure the material is present in the library so I made the hack below:
- dummy_layer_name = diffuse_file
- if not rs.IsLayer(dummy_layer_name) : rs.AddLayer(dummy_layer_name)
- #dummy_layer_index = sc.doc.Layers.FindByFullPath(dummy_layer_name,True)
- dummy_layer = sc.doc.Layers.FindName(dummy_layer_name)
- dummy_layer.RenderMaterialIndex = new_material_index
- sc.doc.Views.Redraw()
- #rs.DeleteLayer(dummy_layer_name)
- make_material_by_diffuse()
-
Could you please give more details on how you see normal map sensitivity adjustment to be done? Normal maps contain normalized values which fully describe normals of the material. Scaling normals down will bring nothing - renormalization will reconstruct the original normals.
As a amplitude slider, more or less bumpiness. Just like with a bump map. This is entirely a artistic slider, whether or not this is "correct" I don't know.
-
"One additional request would be the ability to adjust the normal map bump sensitivity in the Material Editor"
Is there any progress on this? Most of our materials use normal maps and not bumps.
-
Thanks, I can file this as a feature request. Could you also let me know about the specific use case for this in your scenario, so that I can also add it as further feedback?
Sure, it's mostly related to improving the speed at which we can add new materials into a file. If there was a "+" within the Material Editor:
Or just a command for this, if the importer could then import all the image textures related to the material into the appropriate slots, it would make it quite a bit faster to load in new materials. Something as impressive as the Poliigon importer would be nice, but the main functionality, for me at least, would be to be able to select just the diffuse channel image and then automatically import all other maps.
A demo of the Poliigon one is here.
-
https://help.poliigon.com/en/a…nverter-addon-for-blender something akin to this would be awesome to have. I'm in rhino, but I'm sure most of the applications would benefit from this.
-
Hi there
I just wanted to log a few complaints,
- View Synchronization is a bit of a pain to use as it's dependent on the viewport size in rhino, this makes it a difficult to match the view between shots done by multiple team members, where a rerender is in order, but the post production is underway. Our workaround is creating a floating viewport with the exact aspect ratio our render will have, but sometimes we don't know that when starting our process. V-Ray does this perfectly, shots align as long as the same Named View is activated.
- The environment slot is used and makes it very hard to preview materials when using Roughness maps, this is for both Enscape and Rhino Materials with the "glossyenvironment" modifier. Some sort of override or similar would be great for previewing materials and their mapping before launching Enscape