I use X-tra to create triggers and SCMDraft for the terrain/to polish it up.
In X-tra I recently got a maximum text strings error, so I opened SCMDraft thinking it will no doubt bypass that. In SCMDraft it keeps saying Something bad has happened! I kept loading it over and over and it finally worked, only to say that same message as I was working on it 5 mins later. It keeps doing that error and it's annoying the crap out of me.
So first, does SCMDraft bypass that? It let me make new triggers with text in them for the 5 minutes that I could use the editor, but i'm still not sure. And second, what the hell is up with SCMDraft?
None.
SCMdraft is water and Xtra editor is oil.
They don't mix.
Scmdraft doesn't bypass the limit, it recycles strings, something that is very convenient but makes it difficult to work with other editors.
Yes it does. SCMDraft2 does both.
I stand corrected.
Post has been edited 2 time(s), last time on Sep 11 2008, 7:54 pm by Kaias.
None.
But why does SCMDraft crash when I open it? Works fine on x-tra
None.
We can't explain the universe, just describe it; and we don't know whether our theories are true, we just know they're not wrong. >Harald Lesch
1. Changing editors can cause trouble.
2. ScmDraft can cause trouble if you try funky things with string (such as go over the limit).
3. If you experience trouble, avoid the cause.
ScmDraft, technically can go over 1024 strings, as long as the total length of the strings (+control bytes) is under 64k. But I heard from a lot of people that they had trouble when exceeding 1024. 3. applies here.
So, as for the avoiding, why do you need over 1024 strings? Usually you only get over that limit through extensive commenting.
This is not necessary. Delete comments of simple triggers and combine comments for whole sets of triggers. That should save enough strings to finish your map with no problem.
Don't forget to load a version that hasn't yet exceeded 1024 strings for the condensing or you might carry over problems to the condensed map.
Didn't we just cover a topic almost exactly like this?
None.
Scmdraft doesn't bypass the limit, it recycles strings, something that is very convenient but makes it difficult to work with other editors.
Yes it does. You're posting incorrect information. SCMDraft2 does both.
I don't pretend to completely understand the way SCMDraft2 works (ISOM section especially), but if I were to take a random stab I would guess that SCMDraft2 is trying to rewrite identical string references (string recycling) on map load. Obviously it's doing this incorrectly and is causing a crash. String recycling does not work very well in Staredit at all.
Couple of suggestions
Try opening your map and re-saving it in a third party utility (Uberation, OSMAP, Proedit, etc). These programs recompile the strings section (and possibly other problematic sections!) on save, which may fix your problem. You may even try recycling the strings in Uberation3, then re-saving. Playing around with the functions may fix your issue.
You may have actually hit the hard-string cap depending on the length of your strings. To find out the string capacity of your map, run your map through Farty's MapStats or if you can find it, my StringAnalyzer program. If you want more elaboration on how this actually works, feel free to reply.
Hope that helped.
None.
Switch to SCM Draft completely, or stay on X-tra, avoid mixing editors as much as possible, especially with SCM Draft, as it recycles strings, something which other editors are not too keen on.
I would check my backup database in SCM Draft if I were you and try and find a working version that you haven't lost to much in.
None.
