I went ahead and unblocked it in file properties. It did not help.
Then, ran Rhino 6 as Administrator. In that case, drag-and-drop did not work, but it installed OK from Options>Plugins>Install…
So, it worked. But it is strange that the plugins generated on your own system are ‘blocked’ there by default. I never ran into anything like this.
Can you make it work on your end following the above steps ?
@Dale, @Steve - any ideas why this is happening with plugin generated on own system ?
Strange. I also know that sometimes using RHI file instead of RHP works well (RHI being zipped and renamed RHP so Rhino Plugin Installed could recognize it).
I tried compiling your test code. The command is JBTest.
Can you try both RHP and RHI and see if any of them work on your end ?
Hi Michael,
If I look at this and I think of 5 (in words “five”) years development, I just don’t see it.
The flyer mentions the Picture command… IMO that command it’s a step back. It’s missing the SelfIllumination, EmbedBitmap and AlphaTransparency options from the PictureFrame command. How can that be a “new” feature to cripple a good command?
Ok, except for the EmbedBitmap option you can set the options in the material tab but if you like to macro things you’re out of luck.
It mentions snapshots… see my post above about it.
Realtime Raytracing viewport is fine for a mobile phone or somethin but try that for an interior of a yacht and its pretty useless.
So yeah… I don’t know. Think I need a different flyer.
P.S.: Editing fillets and SolidWorks 2017 Import (and above) are “must have” arguments for some people. But perhaps SolidWorks is absent in the ship industry, I don’t know.
hi @dale, thanks for asking. The buggy stuff on fields not updating of jumping to the wrong place when hitting tab are either fixed or harder to replicate. but the performance stuff is a killer. Especially because I use Boxedit a lot, not just for scaling but as a headsup display of the size of things. So I want to select and quick glance for a size check. Then click on the next thing and check size again.
Not a feature, but the upgrade promotion ends soon Sooner or later you’ll probably upgrade anyways…
What can one expect for such a low upgrade price once in a blue moon?
I was also a bit disappointed but that happens in any long term relationship now and then…
Box edit takes a full second to load every time you select geometry, no matter the complexity. I used box edit daily in v5. In v6, I quit even having the tab open.
Also, it forgets what you set XYZ to, i.e. min, center, max.
It ignores the increment set until you reset the increment.
You cant update the position for multiple objects with transform individually (triangle symbol).
Yeah, you’re right. I’ll buy it anyways.
It would be nice if I’d be able to use it one day… The fact that I can’t load script compiler plugins is a real bummer, and the bump map issue too. But eventually it’ll get solved (I hope).
But Jess, what are your favorite features of v6? I still believe that I simply missed a lot new stuff cause I didn’t took part in the WIP process at all…
So - the issue with bump maps is that V5 contained a pretty nasty bug when it came to rendering these in OpenGL. V6 fixes that, so files that had bumps before - and didn’t show all that well - will now show the bumps properly.
We’re sorry that this bug fix is causing you problems, but we do need to fix this kind of stuff. The solution, of course, is to edit your materials to reduce the bump amount.
It’s not about “pro” cards - the “modern display pipeline” improvements are about - well - modern cards. Your card is 7 years old - and while we certainly support it, we can’t really make use of it to accelerate your display any more than we already do.
Modern gaming cards - even at the very cheapest end of the scale - will work great with Rhino 6.
Yes, That’s what I thought. I am aware that my card is old and therefore I won’t benefit much from the new stuff. I’ll look into getting a better card soon.
That’s bad news for me… but I understand that you needed to fix that. I’ll look into the issue when upgrading Vray to 3.6. Till that time I think I need to turn off bump maps for the modeling work and turn it on for rendering.
Sooner or later you’ll probably upgrade anyways…