Hi Ronald,

Just a curiosity ,

are you able to open the file in another machine ?

Thanks
Ivan

On Mon, Jan 14, 2013 at 9:48 PM, Toonafish <[email protected]> wrote:

>  I was able to retrieve some crucial bits from the corrupted scene with
> the Journal File and reloading the scene several times, so not everything
> is lost. Thanks for the tip Rob, and for the help everyone.
>
> cheers,
>
> - Ronald
>
>
>
> On 1/11/2013 18:54, Toonafish wrote:
>
> Thanks, I'll need to give it a shot if I don't want to loose a days work.
> Seems like all backups are corrupt as well.
>
> The weird thing is I was able to load the last backup scene, and saved it
> under a new name. Then started redoing what was lost. But when reloading
> the redo scene Softimage crashes again, and now I can also no longer load
> any of the backuped scenes I could retrieve one of just 20 minutes ago. A
> scene that was fine and has not been changed is suddenly corrupt...it's
> voodoo I tell you.
>
> Gonna check it tomorrow, I suspect I need some beer as well ;-)
>
> Have a nice weekend.
>
> - Ronald
>
>
>
>
> On 1/11/2013 18:33, Rob Chapman wrote:
>
> Ronald think you just give the path for the journal - default is nothing..
>
>  yes friday, drinking beer eating crisps time in the office!  :D   its
> only emergency like scene crashing if you have a client deadline!
>
>  hope it works for you but its not a magic solution, eg Fabrice here said
> 2 out 10 times success rate
>
>
>
> On 11 January 2013 17:27, Toonafish <[email protected]> wrote:
>
>>
>>  in preferences>data management as far as I remember when I last had this
>>> and was helped, it creates a text file that tells you what models are
>>> loading and then on the next load it skips the ones that it finds bad?
>>>
>>
>>  Is that the "Recovery Journal file" ? Do you remember where softimage
>> writes the text file ?
>>
>>
>>
>>> its a shot in the dark at least
>>>
>>> you do realise its friday > 5pm though and this kind of stuff is *meant*
>>> to happen.
>>>
>>
>>  I smell a conspiracy ;-)
>>
>>
>> - Ronald
>>
>
>
>
>

Reply via email to