Major FPrime Bug

[Matt]

Noticed something odd happening whilst setting up a scene today.

I started setting up the lights in the scene when I decided to target the main fill lights to the model so I could move them around while experimenting with their positions with Autokey turned on.

I also zeroed out the HPB for the targetted lights, then turned targetting on.

The FPrime preview was fine until I selected something else other than a targetted light, then it changed, effectively using the targetted light's original position.

Try it:

Setup a scene which has one of the the lights pointing away from the object when in its zeroed out position, then target the light to the model.

Open up the FPrime preview window (1.50) and refresh it with the targetted light selected, and then the other non-targetted lights, or the camera etc.

Unless it's my system the preview should show a difference.

Matt

[Panikos]

Targetting has a bug in LW, similarly Light Incidence doesnt work with FPrime.

It is written on Worley's web. Newtek will have it fixed in 8.3

soon ... :)

[Matt]

Doh! Yes you're right, they know about it!


FPrime is showing the wrong light angle, wrong view, or items are rotated incorrectly in FPrime 1.5. FPrime 1.0 worked fine.

This is likely the result of a LightWave 8.2 bug, which provides incorrect information to FPrime when items are using LightWave targeting. The symptoms vary, since the values are not always wrong, so if you see any strange views or light directions, make sure targeting is not the cause. Newtek has made progress fixing this bug.

[mav3rick]

nice to see fast responsive dev team..... i hope when they catch up with sdk lw will be on nice road to get back what it deservs . best of in 3d market

[monovich]

hmm... interesting about the lightincidence thing. I noticed that but hadn't realized it was a bug.

I also noticed that fprime doesn't correctly work with targeted cameras either.

-s

[antwik-2]

Ya i notice one more bugg,
IF you use motionfiles with fprime and use the "shift frame" option, fprime dont render that frame right when you render the entire sequency. The frame you have set on shift frame, and the frame before that dont get right. It use the last frame for does,
i guess this is not the way it should be, have anyone else notice this?

[Panikos]

antwik-2, sorry I dont understand what you mean.
If you change the motion, save the scene, reload it
Sometimes LW denies to give FPrime updated information that why the Refresh is essential.

[New2Lw]

In 8.3 Light incidence and targeting with Fprime hasn't been fixed yet, I'm assuming cause I still have the problems. Am I right?

[Panikos]

Sorry, dunno. I've been too busy lately with other things.
I will check it out.
Its easy to see if its working or not.
Try updating FPrime, use Frame Bar, disable/enable targeting etc

[mav3rick]

i have noticed problem with gradient applied on DISTANCE TO OBJECT .
for example add null object and tell your gradient to take null object distance in count.. you will notice that while u work in surface mode fprime show all fine but as soon u hit render button you will not see any affect by that gradient on your object...
workround?use pshop gradient map applied

[Matt]

Dunno about the other problems, but my issue was cleared up in :lwicon: 8.3.