View Full Version : pwr_sweep 6.2version bug ?
rudo_fr
03-25-2010, 05:52 AM
Hi David,
I tried to use pwr_sweep tool without success with your 6.2 version. Nothing appears when i try to use it.
I do same operation on older powernurbs version without probleme.
When i updated old powernurbs version (that run) to 6.2 version pwr_sweep tool don't run.....
Could you please verify this problem because i'm loosing precious time with 6.2 version. Of course i can't go back with older powernurbs version after installing 6.2 without have 3dsmax starting error message ...
i tried v6.2 on max2009 and 2010 64 bits with same bad pwr_sweep tool results.
Thanks David.
npower
03-26-2010, 08:16 AM
Rudolf,
Hello power sweep seems to be working fine on my 6.3 internal build. Would you mind sending me what you are trying to sweep?
rudo_fr
03-26-2010, 08:43 AM
Hi,
All i try to sweep don't run with 6.2 version.
Could you please give me the link to downloading 6.3 version ?
rudo_fr
03-26-2010, 09:40 AM
I found a way to resolve problem:, push one time undo after use pwr_sweep tool to see sweep construction...
rudo_fr
03-26-2010, 11:20 AM
So, could you please give me the link to downloading 6.3 version ?
Thanks in advance,
rudo_fr.
PiXeL_MoNKeY
03-26-2010, 11:28 AM
6.3 hasn't been released yet and is an internal only build. Which probably means it isn't an installer or anything like that. They want the file to test and see if the problem is fixed for your file also.
-Eric
nPower_Dave
03-26-2010, 11:33 AM
Hi Rudolph,
Eric is right. We haven't posted the 6.3 build yet. We should release it soon. But the sweep tool seems to work fine for our pre-release build.
rudo_fr
03-30-2010, 09:00 AM
Hi,
i notice in general with this 6.2 version, i have to clic on iso line angle tol to have good curve display.
So if you can check that too.
Thanks rudo_fr.
nPower_Michael
03-30-2010, 10:37 AM
Hi Rudolf,
I've been looking into the Pwr_Sweep glitch and it is a little weird. It seems to have been inadvertently 'fixed' on some environments, but seems to be environment-sensitive, that is, I've seen it happen on one machine, and not on another, with both running the same nPower plugins version, and the same major version of Max. When you get the issue in 6.2 on Max 2010 64bit, is Max patched up to SP1 or anything like that?
I think I've found the original cause of the bug, and I've introduced an intentional fix that should resolve the issue for all environments (the fix should make it into the 7.0 version), but it would be useful to figure out why some Max environments do an 'accidental fix' for this issue, and others do not.
Also, based on the nature of this bug, the undo workaround you describe should work consistently and without any ill side effects; I would recommend that method to anyone who runs into this bug in the mean time.
EricPinkel
03-30-2010, 02:03 PM
Hi,
i notice in general with this 6.2 version, i have to clic on iso line angle tol to have good curve display.
So if you can check that too.
Thanks rudo_fr.
Should be fixed in 6.3. We have now tied the Iso curve display to the CMF mesh settings. The higher the quality of the model mesh the higher the quality of the Iso line.
rudo_fr
03-30-2010, 02:51 PM
Hi,
thanks for giving me these informations Eric and Michael.
Michael my max2010 64 bits version is updated with sp1 and last hotfixe.
Bye,
Rudo_fr
nPower_Michael
03-31-2010, 10:38 AM
Hi Rudolph,
Thanks for the tip! We think we now know what was going on. It looks like people who have 2010 SP1 or later will experience the glitch, whereas barebones 2010 and earlier do not. Basically, Max used to do something that 'hid' our glitch, but stopped taking this particular action in 2010 SP1, which caused the glitch to manifest in a user-visible way.
rudo_fr
04-01-2010, 04:06 AM
Michael,
i tried on fresh insal of max2010 32 bits without service pack installed (on other workstation (XP)) and it's the same, i need to push undo button to see my pwr_sweep model.
I hope this problem disapears with max2011 and your next 7.0 version.
Thanks,
Rudo_fr.
nPower_Michael
04-01-2010, 11:11 AM
Hmm, well that messes up the pattern a little bit. So far every 2010 environment I've seen/heard of that does NOT have this issue did not have SP1 installed. And every 64 bit 2010 environment did at some point have SP1 installed. But the pattern breaks for 32 bit. Right now there isn't really enough data to draw a reasonable conclusion. If anyone reading this has the time and inclination, posting more data (Windows version, Max version, 32 vs 64 bit, any service packs/hotfixes, and whether or not doing a sweep immediately results in a brep or requires an undo to show something) could be useful in figuring this out. I'll post more if we figure this out.
In any case, we were able to write a fix that seems to cover all environments, so this issue should hopefully disappear in 7.0.
PiXeL_MoNKeY
04-01-2010, 03:17 PM
I have seen something similar with Pwr_RailSwp. I fixed it by zooming out, once mesh appears you can zoom back in or navigate as needed. I wonder if it is a redraw problem, or something. Converting Splines and NURBS curves to Edit_Skt have redraw issues as well, in that case you must hit fix curves for it to actually draw the curve and vertices.
-Eric
nPower_Michael
04-02-2010, 10:58 AM
Hi Eric,
Although the symptoms are similar, based on what was internally causing the Pwr_Sweep glitch, and the fact that zooming out doesn't help resolve the Pwr_Sweep one, I am almost certain that the zoom-redraw issue is a separate bug.
Unfortunately, the zoom-redraw glitch seems to have one other thing in common with the Pwr_Sweep one, which is that it seems to be somewhat environment-dependent. We are investigating the zoom-redraw, and will post more if/when we resolve it.
nPower_Michael
04-05-2010, 10:13 AM
Hi Eric,
I've been looking into the zoom-redraw bug you described; we are able to reproduce it with the Boolean and Join tools, but not with the Rail Sweep. Do you happen to have a saved repro you can send our way?
vBulletin® v3.7.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.