Maxwell Render | Official public forum

Yeah.

As I select and drag a material from the materials database window or the MXM browser window, the cursor disappears as my mouse leaves the area of the window.

I'm trying to drag n drop materials onto particular Rhino layers. Which is how I usually put materials on my rhino files.

I thought maybe it was a redraw issue, as I keep all my palettes on a secondary monitor but... I didn't have this issue with the last versions of maxwell/rhinoll. But just in case, I pulled the palettes onto the primary monitor, same thing: cursor disappears as I drag material out of window.

Hi Cadhorn,

There are two ways to deal with this:

1. disable the plugin option: 'Use Custom Cursors'
2. go into your display properties and bump the hardware acceleration down a notch (it should say something like 'disable cursor acceleration')

Let me know if that helps,

JD

That did it. (disabling 'use custom cursors') Thanks JD!

Hmm have the same issue, but neither of those (or both of those) are not
fixing it for me.

- np

Hi Noah,

You're seeing a different thing here - it seems that SR4 has broken something in drag/drop. Can you confirm that it:

- works with the layers window
- does not work with any viewport

Thanks,

JD

JDHill wrote:Hi Noah,

You're seeing a different thing here - it seems that SR4 has broken something in drag/drop. Can you confirm that it:

- works with the layers window
- does not work with any viewport

Thanks,

JD

Yes, I can drop a material from the "Material Database" or from the "Scene Manager" to the Layers themselves.

But still not to any viewport.

- np

Thanks for confirming that, it's the same as what I'm seeing here. I'm now just narrowing down whether this issue is in the Rhino .Net SDK, or in Rhino itself so I can give McNeel good info.

Cheers...

Hi JD: I don't know if this is the same issue but in a slightly different manifestation. When I "Assign to Selected" from the Material Database I get a white rectangle that surrounds that material and a few above and below the selected. It eventually will disappear if I scroll my mouse over the area a few times. I haven't tried your suggestions yet... I know where the hardware acc tab is but where do I find the ability to disable custom cursors.

Thanks
Cary

Hi Cary,

No, that's a different thing - there are some glitches in the way that docked windows get re-painted. I see similar things here, but I prefer docked windows to floating (Plugin Options > Dockable [Scene/Database] Manager) even with the painting issues. When it happens, you can just click the mouse down on the top title-bar of the docked window and move sideways a pixel or two - this will cause Rhino to repaint the window. Otherwise, just don't set the windows to be dockable - when they are floating you should not see this issue.

Cheers,

JD

JDHill wrote:Thanks for confirming that, it's the same as what I'm seeing here. I'm now just narrowing down whether this issue is in the Rhino .Net SDK, or in Rhino itself so I can give McNeel good info.

Cheers...

Not sure if I lost or not. But I'm not using an SDK on my end.

- np

You're not, but the plugin is.

Plugin programmers use an SDK (Software Development Kit) provided by an application, which contains hooks that allow their own code to interface with the compiled application. So basically, the plugin uses the Rhino SDK to hook into Rhino4.exe on your machine. Therefore, by confirming that you see the same behavior, you help me to figure out whether the problem is in Rhino4.exe, or in the SDK that the plugin uses. This information will help the McNeel programmers to know where they should begin looking for the source of the problem. In an application with thousands and thousands of lines of code, narrowing things down like this can be very helpful.

Thanks JD: It is no big deal! I really like the new Database Manager- it really makes it easier setting scenes- I appreciate the work!! For some reason I like the Database Manager docked but I like my Scene Manager movable .... go figure!
Cary

JDHill wrote:You're not, but the plugin is.

Plugin programmers use an SDK (Software Development Kit) provided by an application, which contains hooks that allow their own code to interface with the compiled application. So basically, the plugin uses the Rhino SDK to hook into Rhino4.exe on your machine. Therefore, by confirming that you see the same behavior, you help me to figure out whether the problem is in Rhino4.exe, or in the SDK that the plugin uses. This information will help the McNeel programmers to know where they should begin looking for the source of the problem. In an application with thousands and thousands of lines of code, narrowing things down like this can be very helpful.

Ah, so the plugin is using the SDK. In my development of windows
applications, I reference the Platform SDK all the time. But mostly just
for windows api, etc..

- np

Oh, sorry for over-explaining then. This one looks to me like it's inside of Rhino...probably just one line of viewport code or something, but I haven't found anything I can do about it on my end yet.

JDHill wrote:Oh, sorry for over-explaining then. This one looks to me like it's inside of Rhino...probably just one line of viewport code or something, but I haven't found anything I can do about it on my end yet.

Should I open a thread on the Rhino newsgroups about it?

- np