PDA

View Full Version : 8.2 FPrime Bug still there, but...we have Mac Bone Tools!!!



blabberlicious
01-18-2005, 03:20 PM
To quote Worley:

================================================== ===
OSX crashes come usually 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 , but we're still working on a method to recover from LightWave's
crash on the Mac. 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.
================================================== ====


Well, unfortunately, none of the SDK changes have made any difference. So you have to 'remember' shut down Fp whenever you remove a Imagemap from a texture - or the whole app will crash. This soon becomes a real pain, quadrupling the amount FP interaction during texturing sessions.

I really thought they would have sorted that.

Oh well.


Who cares!

At last: Working Bone tools for the Mac!

Well done Scott & Co.

Lightwolf
01-19-2005, 04:07 AM
Well, unfortunately, none of the SDK changes have made any difference.
Why not, the hooks are there, now all you need is to wait for Steve to release an update that actually uses them. After all, you can't expect a plugin that is about a year old to use a function that has just been released ;)

Cheers,
Mike

blabberlicious
01-19-2005, 06:59 AM
Why not, the hooks are there, now all you need is to wait for Steve to release an update that actually uses them. After all, you can't expect a plugin that is about a year old to use a function that has just been released ;)

Cheers,
Mike

Good point. I'm glad the hooks are there. I'll take your word for it - as I have no idea about SDK. I (naively) thought the SDK changes might rectify the crashing bug without a alteration of FP code.

Oh well, it's more FPrime on/off 'tango' till FP 1.5.

Lightwolf
01-19-2005, 07:04 AM
I (naively) thought the SDK changes might rectify the crashing bug without a alteration of FP code.
No, but now FPrime can get notified by LW if an image is being deleted, as well as if geometry or a surface have been changed. So I guess in future versions this will remove the need for those little helper plugins, as well as making FPrime/LW a bit more stable.

Unfortunately, no hooks for volumetrics or shaders yet ...

Cheers,
Mike

Zarathustra
01-19-2005, 03:27 PM
Not so fast with those bonetools celebrations
Link (http://www.cgtalk.com/showthread.php?t=203268)

MacDoggie
01-20-2005, 09:20 AM
OSX crashes come usually 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 , but we're still working on a method to recover from LightWave's
crash on the Mac. 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.
==================================================

You might try clicking the pause button. When you're replacing image maps.

blabberlicious
01-20-2005, 09:43 AM
You might try clicking the pause button. When you're replacing image maps.

I am aware of that - but somethings profoundly wrong if, in the midst of editing a texture map (ie concentrating on one dialogue box), you should 'addicentally' delete a layer containing an image map , then....

boooooooom!

...end of LW scene....


Workarounds - after a year, I'm less than excited about resorting to them particularly when it sounds like FP1.5 is either not particularly immanent - or that these same issues will be there.

S'all I'm saying

MacDoggie
01-20-2005, 10:43 AM
Good point, but despite that, I still find F-Prime to be indespensible. Worely will remedy this. You of course can opt not to use F-Prime but it has paid for it's self in the time I have saved in setting up lighting and texturemap Editing. Save often Save early, seems to still hold water even with all the technological advances we have made...... :)

Still a fan.....

Cheers