By JDHill
#344336
On the first, it is because this is a Rhino 4 plugin, and there was never any 64-bit V4 SDK to compile with. On the second, I know it's been requested, but I really don't know any more than that.
By JDHill
#344340
It's more complicated than that. There are several pieces to the plugin; some are 64-bit specific, but compile with no reference to Rhino code. Others are MS .NET-based, and run on 32- or 64-bit, whatever is necessary where you run them. One specific library does depend on Rhino, and this is 32-bit only, being a V4 piece -- that's the library which interfaces with RDK code.

As such, it is only RDK stuff which is affected; that won't be supported on 64-bit until the plugin becomes V5-specific.
By l1407
#344343
JDHill wrote:It's more complicated than that. There are several pieces to the plugin; some are 64-bit specific, but compile with no reference to Rhino code. Others are MS .NET-based, and run on 32- or 64-bit, whatever is necessary where you run them. One specific library does depend on Rhino, and this is 32-bit only, being a V4 piece -- that's the library which interfaces with RDK code.

As such, it is only RDK stuff which is affected; that won't be supported on 64-bit until the plugin becomes V5-specific.

rhino 5 64/32 bit is bulit-in soft-edge function, on need plug-in?
Help with swimming pool water

Hi Andreas " I would say the above "fake[…]

render engines and Maxwell

Other rendering engines are evolving day by day, m[…]