Enviado: 19/Fevereiro/08 em 9:15am | IP gravado

Wavers, a Worley acaba de anunciar o Novo FPrime 3.2, ele é compatível com o LW9.3.1 e apresenta algumas melhorias.

Abraço a todos!

FPrime 3.2 change list

• Support for LW 9.3.1 new area light flags (single sided area lights)
• Automatic support for LW 9.3.1 new global light intensity.
• LW 9.2+ reversed the direction of motion blur. FPrime detects and matches this.
• Hypervoxel alpha channels weren't always correct. Fixed.
• Radiosity noise significantly reduced for 3+ bounce radiosity.
• Borderless limited region refinement could "wrap around" and show a quality of -99999. Fixed
• Bump map textures and nodes, followed by nodes which used incidence angle gradient mapping weren't showing the effects in the gradient of the bump. Fixed..
• Noise in radiosity from intense inverse square area lights is reduced.
• An animated object which scaled down on one axis to 0 size could show the wrong shape when the scale was animated to non-zero. Fixed.
• In LW 9.2+ only, FPrime was showing animated objects at the wrong position in render mode only when the first frame rendered was not frame 1. A workaround to the LW bug is now included to double-check LightWave's object positions.
• Mac only: arrow keys, fn-backspace now supported in numeric gadgets in Leopard
• Mac Leopard only: Image file requesters would often not show the file save types, not allowing you to pick a save format. Fixed.
• Vista only: On some systems with execute-bit-enabled CPU security enabled, quitting LightWave would cause a (harmless) crash after Lightwave had completely exited. Fixed.

Known LightWave Issues

• LightWave does not give FPrime proper object shape information when the camera is in Bounding Box view, or when per-object Hidden or Bounding Box mode is selected. A workaround is to just turn off Bounding Box mode and use any other mode, and reload the scene. This LightWave bug was not fixed in LightWave 9.2.
• A LightWave bug in LW 9.0 and earlier can cause objects with motion plugins or tracking to appear in the wrong places in FPrime. This bug is fixed in LightWave 9.2.
• Mac only: Crash when a texture is removed or an image changed while an FPrime window is open and active. This is LW crashing because it's deleted a texture when FPrime is still using it, and LW hasn't told FPrime yet that it's deleted it. On the PC side, we're able to transparently catch and recover from the LW crash. Unfortunately OSX doesn't have an easy solution, and while a LW SDK update would solve the problem too, that doesn't help with the problem now. The current workaround is easy but annoying. The crashes aren't random, so you can avoid them. Just make sure to close FPrime's interactive window before you delete a texture or change an image map.

Graphics Card Issues

• Some graphics card drivers (and specific versions of drivers) are uncomfortable with intensely multithreading graphic windows like FPrime's interactive preview. If you have crashes when using the preview (but FPrime render is fine) then your drivers might be the cause. Updating drivers, (or, on especially on the Mac) changing per-application driver settings like disabling FSAA usually fix these oherwise hard-to-diagnose crashes.

Known FPrime Bugs

• Cubic mapping can be incorrect on deformed objects. A workaround is to use Surface Baker to bake the color channel and then re-apply it as a UV which FPrime will render correctly.