The non official Messiah 2.4 BUG tracker

Layer01 · 2006-03-19 05:15:53 UTC

OK so we have a new version of messiah. we’ve said our “ooh’s” and “aah’s”.
so lets start by taking it aparts, show them just how fast a public beta could stomp out bugs if we we’re given the chance, and on that note this sort of feels like that a bit anyway, as on IRC we’ve been picking it apart bit by bit.
Lets keep this civil, and constructive. So [color=Red]dont post your rants at how angry you are about a certain bug, do that in your own thread.[/color]

[color=DeepSkyBlue]Make sure you explain step by step how your bug is occuring, and provide [color=SandyBrown]screenshots where possible and if necessary a [/color][color=SandyBrown]link to the file you need to get the bug.[/color] ( www.filefront.com is a good free file host and www.photobucket.com can be used for img’s)[/color]

ok lets get started:

Layer01 · 2006-03-19 05:17:18 UTC

I found this by accident when playing around with the doll eyes scene file in 2.4. not sure if its a 2.4 only bug. but its a bug none the less.

Parsec3d · 2006-03-19 05:22:03 UTC

onion skin for undo ;)?

Layer01 · 2006-03-19 05:28:10 UTC

lol. could be onto something there

anyway i know the guys in IRC will have a bunch. it will be interesting to see what comes up in here :deal:

Layer01 · 2006-03-19 05:43:59 UTC

in the spirit of getting this rolling, i’m going to post a few that have been sent to the mailing list.

this one's from Isobar :)

isobar:

Hi guys, with the new 2.4 I'm getting a funny crash loading LW objects
that have a UV map asigned.

I made a default sphere, used the Texture Guide tool in LW to make the
UV map, then saved.

crashes;
[http://66.180.150.90/temp/test.lwo](http://66.180.150.90/temp/test.lwo)

works;
[http://66.180.150.90/temp/test.obj](http://66.180.150.90/temp/test.obj)

That's the same object, saved/exported from lightwave 8.5. It loads OK
in 2.2.



On the plus side, the default untextured surfaces render much nicer!

and in reply this was given

David Maas:

Confirmed crash with that lwo object.
After playing about, it seems that Texture Guide is the culprit. It
leaves the points separate from their given position. Not sure what that
is called, but it happens if you weld points that already have differing
uv coordinates sometimes... at least - taht's what I tip. You know, they
appear as red. Apparently saving out as obj strips this information and
re-saving the obj as a lwo also works in messiah....

Go figure.

also [color=Orange]Sil3 in #messiah3d tried loading the rhino object that comes with
Modo, which apparently caused a crash. this is as of yet unconfirmed by other modo users.
Edit: just tested it and it is a [color=Cyan]confirmed crash

Just to help consolidate bug reports into one place i’m quoting this from [color=PaleTurquoise]svintaj’s post

[/color] [/color]

Nichod · 2006-03-19 06:00:10 UTC

I’d also like to point this one out:

I think I have found one crash-bug and a broken feature so far…

( Crash ) Create a “Particles Effect”, in the Particles Surface add a new Particle Shader and connect output-color to RADIANCE.Then go to the Particle Input/Output tab and disable: “Render with Volume Intersection Method”, go to some other frame than 0 and hit F9 to render… Crash!

( Copy surface is not working ) Hit F5 and double-click on the StreakedMetal preset, it now appears in the Materials Tray, right-click on it and choose copy now go ahead and paste it on another material, it will not do a proper copy as you can see.

Can anyone confirm this?

/ Svante

Found here:
http://forums.cgsociety.org/showthread.php?t=330596

Edit: Hehe. Beat me to it!

dobermunk · 2006-03-19 06:08:45 UTC

Well, here’s an out-and-out bug, since we’re collecting them here… still in 2.4.

Taken from my page of desired small things…

More from the 2.4 as I get time. Psyched!

Layer01 · 2006-03-19 06:23:54 UTC

ok while not a show stopping bug, its still a bug.

svintaj · 2006-03-19 07:57:18 UTC

Undo are still not working on skeleton editing in Setup, like:
Add Bone, Add Child Bone, Realtime Add, Realtime Modify and Split Bone.

/ Svante

MoodyB · 2006-03-19 07:58:43 UTC

When a transparent object has part of its geometry above the horizon line in the camera view, it will show the enviroment material / texture map ’ through ’ it. This happens even when the background camera material is active.

This doesn’t happen if there is geometry behind the transparent object.

MoodyB · 2006-03-19 08:29:04 UTC

Not really a bug, but more of a suggestion :

’ Tint to Surface colour ’ in the reflection channel should default to 1.0 instead of 0.0, as if you’re not aware of it when loading an old scene / material, reflections appear overly bright / strong due to being tinted to white ( I think ) by the default value of 0.0.

The reflection bug fix on black materials is nice though

dobermunk · 2006-03-19 11:58:11 UTC

Hmm… first time I oipened the setting wasn’[t saved, but after re-saving and opening it seems to be taken care of! Can anyb ody confirm?

Julez4001 · 2006-03-19 12:51:49 UTC

Nice to see you guys taking the bug reporting by the horn.

Layer01 · 2006-03-19 16:44:47 UTC

Names don’t line up with their rows in the dope sheet

Layer01 · 2006-03-19 17:08:51 UTC

this one’s in 2.2 as well i think. but its a bug so here it goes.

the dope sheet needs a LOT of work. its insane atm to select anything in it. Ctrl clicking over groups of keys is broken. the keys that are highlighted deselect and the ones that arn’t are selected. only way to get them all is to select them individually.
if you can select them at all
high res img if you cant see the marque selections is here
this was done with the butch scene

Edit: seems this is not a bug and more a workflow error on my part. but it does however remind me of the selection problems when selecting multiple keys in the dope. and then trying to deselect them…

  [img]http://i6.photobucket.com/albums/y244/Layer01/Bug_04_a.jpg[/img]

DaveW · 2006-03-19 17:58:04 UTC

Layer01, I’ve found that the keys that don’t get selected are keys on a channel other than the current channel for the item. So if you have a box with a key on the x and y channels on frame 10, but on frame 20 only the x channel has a key, if y is the active channel then you won’t be able to select the key on frame 20 unless you shift-click it. BTW, shift-clicking would probably be less frustrating in this case than ctrl-clicking, since shift-click will only add to the selection.

A related bug that is still in 2.4, in the same situation as above if you were to select the key on frame 20 (which is a key only on x channel) and drag it to a different frame, the inactive keys associated with it will become active, thus screwing up the motion. It’s a real pain in the ass, I was hoping it would get fixed for this release.

On a more positive note, the 84.21 forceware drivers have been working flawlessly with dualcore athlon + messiah in XP32.

Layer01 · 2006-03-19 19:05:04 UTC

Thanks for pointing that out dave
i was shortly after posting told the error of my ways with Ctrl clicking but i’ll keep the channel stuff in mind

there is however one issue i still have with the dope sheet. you can shift select an area of keys, you can ctrl select and sort of boolean select the keys. but you cant deselect an area of keys …at least not that i know of.

dobermunk · 2006-03-20 04:45:08 UTC

dobermunk · 2006-03-20 07:22:09 UTC

Can anyone confirm or deny problems when using mdd’s baked with PointOven in the new 2.4? Specifically, they bake fine, but LW can’t find them (even when double-clicking them)?

Found the problem. My computer is haunted…

Layer01 · 2006-03-20 15:05:33 UTC

lol arn’t they all