disconnected shaders after HotFix2 !!! can't fix !

[NNois]

sorry, i have no solution than crossposting...

serious issues here.
after 2 or 3 days I'm loosing hope
my scenes had been created before Hotfix2

3 solutions --> 3 problems

1.
I can fix a corrupted scene with switching libraries but as stated i have to delete corrupted materials and softimage doesn't permit me (the screwed).
So if i save this corrected scene (with screwed materials disconected) the resulting scene is, again corrupted on the goog materials

2.
I use the trick "open a corrct backup scene, New scene, Open the good one (with corrupted materials)"
It's working, all my connections are OK but if I save the scene the resulting scene after an XSI restart is corrupted again, like the HotFix 2 doesn't solve anything

3.
If i use de n°1 solution but saving a wole model of my scene softimage record a model with only good materials, reimporting is OK but a save after it's corrupted again

Someone can help me on this one ?
Thanks

[ActionArt]

This information was on the SI mailing list. I've never had to use it but hope it helps you:


After speaking with QA, it seems I was missing a step (restart Softimage before reloading the scene).
Can you try this?


1. Load the corrupted scene into HotFix2.

2. Save the scene.

3. Restart Softimage.

4. Load the scene again.

5. Now you can start repairing your materials.

The connections of corrupted materials are broken upon initial load, but corrupted shaders themselves still remain. After saving, restarting XSI.exe, and reloading the scene, corrupted shaders that are not salvageable have been removed and whatever shaders remain can be used to reconstruct materials.

[Hirazi Blue]

For future reference: Stephen Blair has added this info to his Support Blog now also.

BUT: did this info help you, NNois, in any way?

[NNois]

well, mixed result
I can generate a scene with no corrupted materials
saved it
close Softimage
load it
scene OK !
...wait
saved it again
close softimage
load it.... corrupted, unbelevable

thinking it's about switching materials who didn't work as intended because of passes... i don't want to but triing erasing passes now

[jamination]

a guy at work calls it the "notfix". sadly the hotfix gave us the confidence to use 11.5 which we had avoided since it came out (because of this issue), and we've had nothing but troubles since.

[Werner]

same here. Working on a large project with hotfix2, but keep getting disconnected shader trees....even after fixing corrupt materials.
This is busy biting us in the ass, as time is running out, and passes need to be re-rendered time and again.

[Hirazi Blue]

Don't know if this is helpful, but Stephen Blair also posted a follow-up on the whole Hotfix 2 issue here

[Werner]

Thanks for the heads up Hirazi. Will give it a try.

[luceric]

Please contact stephen blair at softimage support if you have problems with hotfix 2 and shader getting disconnected.

[xsisupport]

PM me if you cannot reach me otherwise.

[Rez007]

a guy at work calls it the "notfix". sadly the hotfix gave us the confidence to use 11.5 which we had avoided since it came out (because of this issue), and we've had nothing but troubles since

I run 2011.5 (SAP) without any hotfixes right now, and I have never had any issues with materials or shaders getting disconnected... I guess I am one of the lucky ones.