#LightWave 3.0 CRASH BUG!
17 messages in this thread
Attention LightWave users:
I've found a few ugs in the 3.0 version that I thought I'd share with
you.
Crash Bug: In Modeler, take a cylinder and turn it into a cone by sizing
all the points of one end to 0. (True, there is a cone operator, but I was
trying to create something slightly different.) Now, select all the points
on that end and use the Merge points tool. At this point, the machine will
crash.
It appears that the problem occurs when you reduce a polygoon to
non-existence. In the above example, both ends of the cylinder have a
polygon closing them off. When one end is sized to 0, the polygon covering
that end has become a group of points all sharing the same spot. When you
reduce the points on that end down to 1, it seems to choke on the 0 size
polygon. I have verified that if the end polygon is not there, it'll
reduce the points just fine.
Weird Bug: When first creating Bones (before you've assigned any
keyframes), if you're in the Bone editor and type 'm' to bring up the
motion editor, and then immediately cancel out of it, the 'continue'
button on the bones editor will not function – there will be no appearant
way to exit the Bones editor.
It is possile to get out of this window by just selecting one of the
options on the top of the menu bar. (At least there is a work-around for
this.)
Keep On Toastin'
Erik Flom
Thanks for the info, Eric. I haven't had my T4000 in my GVP040-33 A2000 crash
yet, but T3.0 seems fairly crash-prone in my GVP030-50 A2000, though it could
be the machine and not the software…
"Save Early, Save Often"-Computer users credo Trent
'Save Early, Save Often!' – If only I practiced what I preached!
I lost another 2 hours of works the other day because of that ?#$@%^*&
Solid Preview Window in LW Modeler.!!! (Well, that, _and_ the fact I
hadn't saved in that period of time. :^)
Have you noticed that the Modeler seems REALLY unstable when using the
solid preview option? Both the old modeler, and now this one seem to lock
up whenever I have that animated preview going on…..
Keep On Toastin'
Erik Flom
Erik,
Pardon me for jumping in, but I have repeatedly experienced loss of
valuable time by a crash when selecting Solid Preview in LW Modeler 2.0.
I have not had the Toaster 4000/A4000 cmbination long enough to try this
in the new software, but my only solution in the old (2.0) software was to
religiously remember never to select Solid Preview.
Incidentally, I have really enjoyed your images in Amiga World and the
JPEG's you have uploaded to the forums. I envy your artistic talent and
the skill you demonstrate with the Toaster. I hope your business is doing
well.
Tom
well, glad to see others having trouble with that solid preview thingie in
Modeler.
(I was foolish enough to assume they had stomped on that bug between 2.0 &
3.0….Sigh.)
P.S. Thanks for the compliments on the 3-D stuff. Business has been kinda
slow. The only new call was from some guy who wanted (and got) about a
half-hour of free consultation on becoming my competitor.
(Oh well, Lee Stranahan _wants_ us to be open and friendly, and share the
wealth….:^O
Thanks,
Keep On Toastin'
Erik Flom
Maybe he thought you were from the Law Offices of Jacoby and Flom
heheheheheheh
Yaeh, that solid preview never has worked properly. It's a shame but I think
the Export function really makes up for it. I use it alot for checking tweaks
to models…
Toasting in Stereo,
Trent
Yeah, Import/Export to the Layout screen is real nice. (Though it seems to
export surface info also…I've lost surface changes by exporting from the
modeler after modifying a surface in Layout..:^(
Ditto on that 'Stereo Toaster' comment….It's kinda' nice. :^)
Keep On Toastin'
Erik Flom
Erik, Remember, you still may have two copies of the object…one in
Layout and one in Modeler… The object in Modeler doesn't know that you
updated surfaces. To be safe, you should change surfaces, save object,
import into Modeler, change object, export back. This should maintain
surface values.
I am having no problem whatsoever with the Solid Model preview. What is
the common denominator in all of your systems?
JG
That should not be happening. you may want to call NEwTek with your
systme config… It almost sounds like you may have a bad Denise…
JG
This has happened on my A3000 using 2.0, and on my A4000 using 3.0, so I
doubt it could be the Denise chip…
The common denominator seems to be when I zoom in on the object 8-16x.
It'll usually redraw once or twice, then hang. It happens consistently
enough to where I have learned to just avoid that feature like the plague.
(It can happen anywhere from 5-45 minutes into a modeling session…)
Also, since I've usually lost data whenever it crashes, the last thing on
my mind is going on a bug hunt for NewTek.
Keep On Toastin'
Erik Flom
I have the same problem with a 2000 and LW 2.0. I think it has something to do
with memory because it happens most often when I also have something loaded in
my layout screen. I' have 10Mb of RAM. Did you try this when only using
modeler?
Edward
Like I said before, I've never been in the mood to go on a bug hunt for
NewTek.
Right now, I'm trying to figure out why using a shadow map causes my
machine to CRASH CONSISTENTLY in LW3.0! This is on a machine w/16MB of
RAM.
Thanks,
Keep On Toastin'
Erik Flom
Erik,
Are you using default values for shadow map size or have you changed them
to a much higher number? This still should not make it crash tho, LW
should just tell you you don't have enough memory.
JG
Thanks for your concern, but it appears to be related to the version
of 68040.library I was using.
My A3000 _was_ running with version 37.2m while my 4000 had v37.10.
Now that I've got both using the v37.10 68040.library, my problems
seem to have gone away….. (I _was_ surprised, as LW has _never_
GURU'd on me before. I'd get low memory warnings and the like, but
it's _never_ crashed like this.)