Page 1 of 1
problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 8:34 pm
by reberts1
When I change f-stop wit the new plug-in, it locks up the Scene Manager/Rhino.
I uninstalled the old version of the plug-in and Maxwell Render and reinstalled the 2.6.10.
Sincerely,
Rick Eberts
Re: problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 8:47 pm
by JDHill
Which version & SR of Rhino are you using, and what are the exact steps for reproducing the issue? There was once a Rhino bug where if you used TAB to move from one input box to the next, a lockup like you describe could occur, but testing here, it appears to have been fixed at some point.
Re: problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 10:37 pm
by reberts1
Rhino SR9 on Win 7 64 bit.
I reinstalled everything including Rhino and SR 9, under my account and the behavior is the same;
change the f/stop, tab or click out and Rhino 4 stops responding.
Note that it does not happen in my other Administrator account.
And actually, changing ANY numeric values in Scene manager locks it up!
Sincerely,
Rick Eberts
Re: problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 10:52 pm
by reberts1
Note now that if I pull up my file (or even a new file), click Preset, Default, Reset, I can then enter values.
But I have to do this every time I open a file. It does seem to be related to the tab issue though,
as I can pull up a new document, change the values with the GUI controls, but tab locks it up,
(unless I Reset as above). I even tried to Store Current, Save, then reopen and change settings - lock up.
: (
-Rick
Re: problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 10:59 pm
by JDHill
First, I am having a hard time telling if you are able to reproduce this without using TAB (or Enter, or any other keyboard-based method of committing the change). What happens if you change the value by rolling the mouse-wheel?
Second, does it make any difference if Maxwell Fire is running or not? Third, does the behavior change if you go to Scene Manager > Options and set Dockable Scene Manager to No?
Re: problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 11:12 pm
by reberts1
I can change it with the GUI controls and enter or click out, but definitely not tab.
Dockable Scene Manager already set to No. If I set it to Yes, then tab works!
Set it back to No - locks up if I make a change.
Not sure about Fire. But will test.
Thanks,
Rick
Re: problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 11:14 pm
by reberts1
And the tab key does not work at all when Dockable is set to Yes.
-Rick
Re: problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 11:25 pm
by JDHill
reberts1 wrote:Dockable Scene Manager already set to No. If I set it to Yes, then tab works!
reberts1 wrote:And the tab key does not work at all when Dockable is set to Yes.
Please clarify, does it work, or does it not?
Re: problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 11:28 pm
by reberts1
When Dockable is Yes, it works.
When Dockable is No, it locks up.
-Rick
Re: problems with Maxwell for Rhino 2.6.10
Posted: Thu Feb 02, 2012 11:29 pm
by JDHill
Are there any other non-standard plugins installed and/or running?
Re: problems with Maxwell for Rhino 2.6.10
Posted: Fri Feb 03, 2012 10:52 pm
by reberts1
Nope, for sure since I just reinstalled everything.
-Rick
Re: problems with Maxwell for Rhino 2.6.10
Posted: Fri Feb 03, 2012 11:02 pm
by JDHill
All I can think of, then, would be to make sure that Windows and your hardware drivers are properly updated, and then possibly trying to repair .NET on the machine (there is a blog post about this
here). For what it's worth, I develop the plugin on Win 7 x64, and I can't get it to hang here, though as I say, a problem like that did exist earlier on in the Rhino 4 development cycle.