Staredit Network

Staredit Network -> Modding Assistance -> Why does memgraft 1.13e crash when I save?

Report, edit, etc...Posted by Ultramilkman on 2006-10-23 at 16:08:09

Modding sucks if you can't save your work...

Report, edit, etc...Posted by DiscipleOfAdun on 2006-10-23 at 16:44:34

As with any modding, I(and many others) suggest making the changes in SG and then importing into MG only to immediatly save it. MG has some bugs in the code that weren't caught soon enough for anyone with the source to care about them.

Report, edit, etc...Posted by Ultramilkman on 2006-10-23 at 17:21:04

QUOTE(DiscipleOfAdun @ Oct 23 2006, 03:44 PM)

Thanks alot, Memgraft costed me a few hours that will never be able to edit.

Report, edit, etc...Posted by DiscipleOfAdun on 2006-10-23 at 17:37:29

I wasn't as clear as I could have been. I meant save a release. Meaning you save the .mgd and the .exe file. Srry, when I re-read I realized I wasn't clear. If it isn't saving a release, then I have no clue what is going wrong.

As for another point, I didn't code MG, if you were wondering. I only hexed in proper offsets for 1.13e.

Report, edit, etc...Posted by Ultramilkman on 2006-10-23 at 22:52:53

QUOTE(DiscipleOfAdun @ Oct 23 2006, 04:37 PM)

Don't worry about it I know what you meant. (Hey I did waste my time reading to modding turtorial ) Now I am a happy boy woot!

Report, edit, etc...Posted by Corbo(MM) on 2006-10-26 at 12:14:22

As to my opinion You can work with v1.11b Memgraft, which is able to save your work, after you work with it you can just load your project from 1.13e and boom! you got your patch and no SG involved

Next Page (1)