Shht, don’t blow my cover! I’ve cultivated this human face for a long, painful period.
I don’t have that issue at all it works perfectly here.
Checked also in meters but displacement value was scaled:
@nathanletwory couldn’t resist with Cycles bridge
@huss191998 are you running the latest Rhino? I really don’t know why this issue is happening to you. Here no matter what it’s working perfectly.
Thanks @D-W but I have 2 inquires why my rhino bridge import geometry as blocks and why my displacement map is set to 10 by default even working with different rhino templates ?
solved ! But why my displacement map default value is always 10 ?
Because @lando.schumpich took his time to save your resources as this way it’s far more efficient to use this blocks and copy them around - you RAM is surely happy about this fact.
This is an interesting question. Maybe you have an old version of the bridge? It looks like it was addressed a longer while ago.
Btw. I don’t know if this will make any difference but also try setting your current renderer to Cycles this may be important (I know that from my own dev exp)
Also this may help:
It’s interesting that I have it off and it works - maybe it’s negated somewhere? This may be a silly bug just being the opposite but that’s just guesswork.
I’m working with the latest version as you can see
It weird but not that big deal I just have to decrease the value by myself and it works fine
Mhm… I admit it’s weird I see you have many plugins running maybe something is colliding? You can check that also. Just turn off all plugins and run only Bridge and check if the issue persists if not then it will be helpful to know what plugin is causing it, for sure could be valuable info for @lando.schumpich
i have disabled all the plugins that doesn’t ship with rhino and still persist
so it may problem with rhino bridge or my system
One last question, I think you’ve tested this already but to be entirely sure - did you tried with the original rhino template for eg. centimeters small/large?
IMHO this is weird as it looks that this is fault of something in rhino indeed … From my POV here we have two options first and second and first shouldn’t scale it at all… While in my case it is scaled correctly in your case it behaves like you would have set millimeters always.
@nathanletwory is it possible that RDK scales displacement somewhere? For eg when an object is scaled?
Quite possible. I forget what the current status is of that mechanism. @andy will know.
hi when will this plugin support Newer versions?(rhino 7 /quixel birdge)
hey Lando thank you for the great work that you have done!!!
I’m still having some issues with the 0.2.1 version of the plugin.
basically the rhino 07 crashes when trying to import any surfaces from Quixel bridge!
thank you
Same issue here
Hi everyone, sorry for letting this go on for so long, I yanked all versions of RhinoBridge on the PackageManager, so they cannot be found/installed from there in their broken state.
I don’t have a R7 license at the moment, so I am unable to fix the bug, but soon™, I’ll get a new R7 license and have a look what changed in the Rhino API that leads to the crash.
Don’t expect anything before christmas, but I’ll get to it.
any news
Hi @user992 ,
yes I have R7 now and am investigating. Expect a fix to be rolled out before February
I also confront with crash.
Please check and update plugin
Hello,
The problem occurs in BridgeImporter
when it tries to read metadata.
Some meta is not a string value, like tiling_direction
is an array value.
Just explicitly call the ToString
method:
mElement.value = obj.GetValue ("value").ToString ();
Also, metalness is actually not supported, and if it’s not supported, the plugins throw an error.
To have a resilient service, you can modify:
by
// var exception = new TextureTypeNotImplementedException(texture.type);
// throw exception;
if (texture.type == "metalness") return TextureType.PBR_Metallic;
Rhino.RhinoApp.WriteLine ($"Texture type " + texture.type + " is not currently supported!");
return TextureType.None;
}
jmv
any news pls?
This seems to have done the trick!
The TextureTypeNotImplementedException
was already correctly filtered out and printed to the command line in the RhinoBridgePlugin.BridgeImporterOnRaiseAssetImport()
:
but I also added an additional catch there, so there should be no more crashes at runtime. Thanks a lot @kitjmv !
I’m investigating now the weird displacement @huss191998 mentionend, this will take some more time to fix as I need to implement a smarter system to generate materials for assets.
I could already release a pre-release version with the crash hotfix though, I’ll do some more testing before that and see if I can’t get any crashes locally.
Thanks for your patience
Any more news on fixes?