A Land Far Away

Getting a system IO. end of stream exception (unable to read beyond the end of the stream) when trying to load a mod in the toolset...makeing the mod unloadable. Any way to handle this, or do I start over from scratch?

I've been get that twice on load with the 280908 version of the TSM mod aswell (I'm assuming you are loading the same).. it still loads for me though.. I just assumed it is because the mod is HUGE!

How much RAM do you have? Processor?

I wouldn't start over from scratch. Is there a folder version of the same mod in your module directory? it would look something like this

y289th8943nf48943h09gtj09jo-----alfa003_tsm_280908_AL

That should have everything BC (before corruption) in it.

Always close and save all your areas before saving a mod or folder. And always save under a new file name every time, it saves toolset crashes or at least lets you recover your work if there is a crash..

Sounds like module corruption to me, sorry to say. If you're working in directory mode, you could try to recover some of the areas or other resources; even if it's a .mod, you could try the same using nwn2packer if you want to give it a shot.

I'd just recommend using a compression program like WinRAR or 7-zip to archive backup copies of whatever you're working on in a separate directory every hour or two (or at least when you're done for the night) so you have good fallback points to work from.

If you get an unhandled exception while exporting resources into an erf file, importing that erf into another module can lead to the End of Stream error. It may creep in other ways as well.

Make sure you have Autosave disabled as well (under Options), that seems to be public enemy #1 when it comes to module corruption.

Hope not too much was lost, flag me down at #alfa-builders if you want help trying to recover whatever you were working on from that module.

I was building an area for Wynna that went into the mod recently. I was building without the acr installed, kept getting a FileNotFound error, but ignored it. Hope that's not the source of the trouble.

AcadiusLost wrote:...that seems to be public enemy #1 when it comes to module corruption.

You sure? Thought this was it.





... on a more serious note, yeah - it should be possible to excise the corrupted elements from the module (using the methods described above), saving hopefully most of your work.