headus 3D tools

mokosan · Posts: 150 Joined: 03 Apr 2006 Location: NZ

I've noticed that hold space to stop doesn't work when packing shells.

Is that a bug?
Also packing with 0 bleed takes much longer than a bleed of 1.
Does that sound right?

M

headus · Posted: Mon Feb 08, 2010 8:54 pm Post subject:

Hey, you're right ... Space to stop packing is broken! I was planning to upload a beta release later this week, so the fix for this will be in there.

"packing with 0 bleed takes much longer"

Yes, that's normal. The packing needs to do more work to get a tighter fit.

Phil

headus · Posted: Mon Feb 08, 2010 9:22 pm Post subject:

Actually, looks like the "space not stopping packing" and "0" bleed are related. If I have the bleed on any other value, space works as expected.

Phil

Aliastasia · Posts: 28 Joined: 10 May 2010

Did this ever get fixed ?

What helps sometimes, btw, is to click on the shell being flattened and then pressing space. For long bit.

/A

headus · Posted: Tue Feb 22, 2011 1:10 am Post subject:

It should be fixed from the 2.06.03 release onwards.

Phil

Aliastasia · Posts: 28 Joined: 10 May 2010

Not quite working for me.

give me a few, and I will rustle up a screenshot or screencap.
It works fine on stopping a Shift + F run, but is pressinf space when running a Shift + B intended to work the same way? Because pressing space usually activates a new iteration.

/A

headus · Posted: Tue Feb 22, 2011 5:29 pm Post subject:

OK, the "space to stop" bug that this thread is about is to abort the packing.

Your "space to stop" the Shift-B tool is a separate problem that I have just confirmed! If you hold down Shift-B, then it queues up all of those key presses, and so when you tap space, it gets the next queued up Shift-B and runs again. I'll fix that for the next release, but in the meantime, just tap Shift-B to run it ... don't hold down the B key.

Phil

Aliastasia · Posts: 28 Joined: 10 May 2010

Cool - I wasn't sure if it was a bug or feature - because it does stop, when you press space, eventually but only after it's run it's course a few times, and it stops easier if the wire has been optimised.

C

SLI_Fallen · Posts: 66 Joined: 19 Dec 2008

In some programming circles, bugs are considered "features"

You know i'm just kidding, Phil. Wink

headus · Posted: Wed Feb 23, 2011 7:53 pm Post subject:

"... bugs are considered "features""

Seriously, sometimes they are! Back in my student days, when the internet first appeared, a couple of us discovered (via news groups probably) that the BSD unix our school's PDP11 was running had a bug that allowed root access to normal users. Its was something to do with setuid access on shells scripts. Anyway, we were well behaved and only used it for good deeds, but from our point of view it was definitely a feature :)

Phil

Aliastasia · Posts: 28 Joined: 10 May 2010

I hear you Smile

When I don't work in threedie, I work as a project manager, having worked my way up from sysadmin>test manager>etc.
I worked at a webbrowser company once - one of the garbage handling routines worked a little too well, so it caused crashes. But we liked the functionality it provided so well, we only got rid of the crash, instead of the whole bug Smile

That's why I was wondering about the Shift + B thing - it seemed logical to me that maybe it only stopped after a few iterations of flattening, instead of thinking it was a bug. it wasn't until I was doing a screencap in my pet hate-program Camtasia I got so effing fed up with the reiterations I did a search. And voilá...

/A