Texture reference object broken in 9.2?

[PolymerJones]

I just loaded in an old scene in which a character's eye direction is controlled by a null, which is a texture reference object for the eye image. Works like a charm in older versions of Lightwave. In 9.2, the texture will not follow the null orientation. Why?

Using XP, necessary updates, P4, 2 gigs ram, LW 9.2.

[3dworks]

i confirm, it seems to be completely broken, also on OSX! (so am i OT now? lol)

markus

[Weetos]

I experienced this problem too, but I noticed that having Autokey on fixed it up, at least in the setup I used. If I remember correctly in previous versions it was working fine though, without having to do that - so this might be a bug

[PolymerJones]

This is very bad. I didn't particiapte in the beta, so I didn't know about the broken feature until now. It kills many of my character setups. I'll have to finish a lot of work with my old Lightwave install, which means the render optimizations of 9.2, for which I specifically upgraded, won't be available to me.

Texture referencing to a null has been a lifesaver for me in Lightwave, and now it's broken? It's hard to believe no one in the beta program noticed. It's upsetting.

[PolymerJones]

Okay, update:

The failure of the reference object has been in Layers mode. So, I thought maybe using nodes would change the behavior.

I applied the eye image and slaved it to a reference null using nodes. IF the nodes panel is open, it works, but I get no real-time feedback. I have to scrub frames to see the eye position. If I close the nodes panel, the image, once again, fails to follow the node. If I leave the nodes panel open, I can render the animation with the proper effect, but that doesn't help me render legacy scenes without re-working every texture associated with a reference object.

If I render a preview with the nodes panel open, ONLY the surface with the reference-object texture effect renders in all frames after the first. If I close the nodes panel, the preview renders the entire object, but the image no longer follows the null's orientation.

This is definitely broken in a most annoying, inconvenient way. I suppose it will be quite a while before Lightwave is patched to fix this.:compbeati

[3dworks]

reported as case 5221 to NT.
markus

[Douser]

This is the first time ever I posted here, even though I've used LW for years.

I haven't updated in a while, and 9.2 looks really good, but all my character eyeballs will not work? For years, I've been using image maps for pupils and eyelids and associated displacements, and sometimes for mouths. It works so well. How do these things happen, with a popular beta testing program? It's a fatal deal-killing flaw for me. I'm glad I lucked into this post before I bought an update. I'd have to completely remake very many of my characters if I switched to 9.2, and they wouldn't look the same. I can't afford the time, because the characters are used in promotional videos that are constantly in production. I guess I'll stick with 8 until this is fixed.

[Thrill Media]

Ughhh, I have been trying to get this to work for the past 3 hours, so I decided to check out the forums to see if I was doing something wrong...has anyone found a workaround for this? Deadlines :(
Thanks,

Curtis

[Thrill Media]

I have an update provided by a user on the yahoogroups forum...

"You need to change your OGL settings; streaming works, as does GLSL with
VBOBuffered. I get instant update here and it renders fine too."

This does seem to help but it hasn't solved the issue completley for me. Your mileage may differ. :)