I'm having major problems with corrupt files in 5.5.208 on Linux 7.3. Sorry this is gonna be a long one.
I lost most of the work I did yesterday, and now all the work I did today. When opening the file from yesterday, half of my network has red flags, and I can't remove the offending OP, replace it or bypass it. The file from today crashes instantly upon opening it in Houdini. I checked the crash log and it says “Crash report..; FUSE version 5.5.208”. I'm guessing it means there's a problem with the Fuse SOP at the bottom of my network. I tried to do something that might be stupid. I set up a network that would automatcily Mirror the model and then Merge the halves and Fuse it, and I was working above the Mirror, Merge and Fuse SOPs. If the Fuse is indeed the problem, I'm wondering if it's possible to remove it from the hipnc in an editor. I searched the file in an editor and found three instances of fuse. I'm hoping that if it is possible to salvage these files someone could give me an example of how to remove an OP from a hipnc within a text editor.
Thanks for any help.
Full Version: File Corruption
open the csh which comes with houdini.
cd to the location of your file, and type hscript filename.hip
this will open the file into hscript. the shell will look like the textport in an open file. you can do anything you want to your file. in your case i would do the following.
opcf /obj
opset -d off *
that cd's you to the object level. the opset -d turns off our you objects.
the next commands will add a dummy sop into your network so just replaced dummy with the name of the geoOP which has the grief in it.
opcf /obj/dummy
opadd -n add add1
opset -d on -r on add1
opcf /obj
mwrite newfile.hip
basically i'm trying to add an empty sop into your geoOP so that houdini doesn't cook the thing which is causing you to crash.
the mwrite command will save your file to a new name if you specify one. if not, it will just overwrite the one you opened with hscript.
a potentially bad thing to do.
there are other tricks if these don't work.
good luck
-k
cd to the location of your file, and type hscript filename.hip
this will open the file into hscript. the shell will look like the textport in an open file. you can do anything you want to your file. in your case i would do the following.
opcf /obj
opset -d off *
that cd's you to the object level. the opset -d turns off our you objects.
the next commands will add a dummy sop into your network so just replaced dummy with the name of the geoOP which has the grief in it.
opcf /obj/dummy
opadd -n add add1
opset -d on -r on add1
opcf /obj
mwrite newfile.hip
basically i'm trying to add an empty sop into your geoOP so that houdini doesn't cook the thing which is causing you to crash.
the mwrite command will save your file to a new name if you specify one. if not, it will just overwrite the one you opened with hscript.
a potentially bad thing to do.
there are other tricks if these don't work.
good luck
-k
Ugh, I guess hscript doesn't recognize non-commercial files. I get “Unknown file type” even when I try to open a hipnc I know isn't broken. Thanks though, it's good to know you can open a file in hscript with the full version. Any other suggestions?
Anyone who wants to take a look at this mess, I have linked a gzip containing one of the corrupt files. Even if you can't fix it, if it looks like I have a problematic workflow going in my network please tell me. I don't want to end up with another broken file, and if I'm doing something wrong, or not quite right I'd really like to know.
http://home.earthlink.net/~mdcronin1/images/head_13.hipnc.gz [home.earthlink.net]
ops:
http://home.earthlink.net/~mdcronin1/images/head_13.hipnc.gz [home.earthlink.net]
ops:
I am able to open your file but it seems that polySpilt109 is doing something very wrong. Did you go back and change something above this node after you put it down? Sometimes 5.5 is a bit confusing in how best model and how and when to retain procedural features.
Are you able to open this file at all?. I'm sure one of the developers can help you out.
Just a quick pointer. With the new features in 5.5 I usually save often and lock my sops in those back ups. I reduce my network so I don't have hundreds of sops floating around. It's a small thing but it makes life easier.
Hope it works out.
-k
Are you able to open this file at all?. I'm sure one of the developers can help you out.
Just a quick pointer. With the new features in 5.5 I usually save often and lock my sops in those back ups. I reduce my network so I don't have hundreds of sops floating around. It's a small thing but it makes life easier.
Hope it works out.
-k
Well, I pretty much always work with secure selection off, and sometimes errant SOPs get placed. I always delete them when I notice it happening, but it's possible I may have added a SOP or two that shouldn't be there. I always lock every 10th or SOP or so, should I be locking them all? If I lock a SOP am I then able to remove the entire network above that SOP?
Thanks for your help.
Thanks for your help.
If you cook the sop first, usually a middle click on the node to get the info pop up window is enough, then you can safely lock it and delete the SOPs above. I'm sure they will say it is prefectly fine to keep the hundreds of sops you use to do all that modelling but i wouldn't. I would save the file to disk, cook the sop, lock it, delete the items above and then start up again.
Once it is locked any changes you try to do above will not happen. The locked sop is just like a file read of a piece of a bgeo.
The more locked sops you have in your file the more heavier the file becomes. Just something to keep in mind. It be in your case you dropped down that polysplit109 and then went back above it and changed the point count, or prim ordering. Atleast that's my $.02 CDN for ya
Good luck.
Once it is locked any changes you try to do above will not happen. The locked sop is just like a file read of a piece of a bgeo.
The more locked sops you have in your file the more heavier the file becomes. Just something to keep in mind. It be in your case you dropped down that polysplit109 and then went back above it and changed the point count, or prim ordering. Atleast that's my $.02 CDN for ya
Good luck.
Just a couple of comments - the FUSE message you got isn't related to the Fuse SOP, I believe - I think it's a standard message that comes up when there's a crash. I believe FUSE used to be an internal code name for one of the uber-nets in Houdini. All I know is I have seen this many times and I've never used the Fuse SOP.
I don't know if apprentice comes with these commands, but using hdecompress will expand a hip file to it's component parts, a file heirarchy just like a project. You can peruse things, and use hcompress to rebuild it afterwards. I apologize for being thick on this since I'm not familiar with the Apprentice version at all…
What method are you using for saving? If you haven't changed it, it's probably “Override Filename” - this copies your current file into a subdir and writes out your session over top of the original. I've always been opposed to this method - it's unecessarily disk intensive and potentially prone to corruption. There's no documented evidence of this ever causing a corrupt file, but it's possible in my books. What about recent saves? Do you have a slightly older version that works? Compare file sizes. If you have no saved files other than your corrupted one, then you have just learned Lesson Number One in computer animation - save, and save OFTEN. It's a pain now, but you'll look back upon it as a valuable lesson learned. When I'm working on a shot, I have saved versions in the hundreds - nothing is more important than the time you've spent on a job!
Cheers,
J.C.
I don't know if apprentice comes with these commands, but using hdecompress will expand a hip file to it's component parts, a file heirarchy just like a project. You can peruse things, and use hcompress to rebuild it afterwards. I apologize for being thick on this since I'm not familiar with the Apprentice version at all…
What method are you using for saving? If you haven't changed it, it's probably “Override Filename” - this copies your current file into a subdir and writes out your session over top of the original. I've always been opposed to this method - it's unecessarily disk intensive and potentially prone to corruption. There's no documented evidence of this ever causing a corrupt file, but it's possible in my books. What about recent saves? Do you have a slightly older version that works? Compare file sizes. If you have no saved files other than your corrupted one, then you have just learned Lesson Number One in computer animation - save, and save OFTEN. It's a pain now, but you'll look back upon it as a valuable lesson learned. When I'm working on a shot, I have saved versions in the hundreds - nothing is more important than the time you've spent on a job!
Cheers,
J.C.
Thanks for the info about locking SOPs. I wasn't aware I could remove the entire network above a locked SOP.
Unfortunately, saving often didn't help me in this case. I have at least 25 saves of that file, and many many more backups. The version posted is the first one where the error occured. Later versions I can't even open, nor the backups. Houdini crashes instantly.
Anyway, Robert Magee informed me that unoriginal works would be disqualified from the Apprentice Challenge, and that model was based on the Hulk, so I'm working on something new. I'll get back to this model later.
Thanks for all the help, fellas.
Unfortunately, saving often didn't help me in this case. I have at least 25 saves of that file, and many many more backups. The version posted is the first one where the error occured. Later versions I can't even open, nor the backups. Houdini crashes instantly.
Anyway, Robert Magee informed me that unoriginal works would be disqualified from the Apprentice Challenge, and that model was based on the Hulk, so I'm working on something new. I'll get back to this model later.
Thanks for all the help, fellas.
Here's a tar archive for anyone having trouble with the gzip archive.
http://home.earthlink.net/~mdcronin1/images/head_13.tar.gz [home.earthlink.net]
Again thanks for all your help, but please don't waste too much time with this file. I have moved on, and now I'm just really concerned whether or not I am doing something wrong.
http://home.earthlink.net/~mdcronin1/images/head_13.tar.gz [home.earthlink.net]
Again thanks for all your help, but please don't waste too much time with this file. I have moved on, and now I'm just really concerned whether or not I am doing something wrong.
Well I just wanted to say thanks again for all the help. I worked all day today and didn't lose any work even though I broke my file twice. Exporting to bgeo and reimporting the model periodicly does the trick.