Blah blah first post blah right place for this blah blah.

My SCMDraft (latest) has had this issue for the longest time. Half the time, it will crash when placing a location, the other half it will crash just by selecting Location in the dropdown. There have not been any conclusive fixes I've found so far, so I'll paste the crash dump file here and hope someone knows how to fix it (since there's no telling for how long the Stormcoast authors have been missing).

Thanks for your cooperation!

Attachments:

Have you updated to 1.18?

That will cause a crash. ScMDraft 2 is not currently compatiable with 1.18.

Thanks for the quick reply by the way

I got rid of my old SC directory and configured the profile to make it draw the MPQs from the new directory.

Though I did get 1.18, I've had this problem long before 1.18 was released for ptr so it doesn't seem to be related; I haven't 'corrupted' the map by running it in SC yet regardless lol

edit: SCMdraft also runs just fine in other aspects, no crashes or anything else unrelated to locations/trigedit

First consider that it might be a problem with the map you're regularly editing rather than a flat out problem with the editor - if you can confirm that's the case then there are "real" fixes you can do.

If not, then there are things you can try but no magic bullet since none of us can go in and actually fix SCMDs code (barring SI if he's still hanging around for remaster thingies), see this and sub-links for things you can try.

Chkdraft's locations and triggers work if using it for that portion would suffice: http://www.staredit.net/sc1db/file/2741/

Alright thanks for the reply, I'm going to try both using an older ver. of scmdraft and using chkdraft for locations.

Interestingly enough, occasionally when I would put my maps through the normal editor, it seemed to have a 'purifying' effect - even if there weren't any locations on the map to begin with, the locations in scmdraft would become usable again.

There's a couple of ScmDraft 2 0.8 versions out, and some of them are more instable. But I've lost track of which is which. You can try download a couple from different sources and find out by trial and error.

But you could also go back to the previous version: 0.73 it's still quite powerful, but lacks some of the latest features. However I've found it to be pretty stable.

If just a certain map or a few maps cause the crashes then it's likely string corruption which most often happens when you're changing editors, because of the string recycling of ScmDraft which other editors do not support.
In that case upload the map and I think some people here may be able to fix the corruption (maybe just saving it in ChkDraft?). Or you can use the backup db of ScmD to go back to a stable version and import the changes via SCMIE.

Post has been edited 1 time(s), last time on Apr 5 2017, 5:46 am by NudeRaider.

If its reproducible with a particular map, PM me the map, so I can see why it is crashing. If its every map, then it becomes more difficult.



Back when I originally wrote scmdraft I was lazy with parameter validation / error checking And didn't know about various useful tools to catch errors (Or they didn't yet exist)

Post has been edited 1 time(s), last time on Apr 5 2017, 1:37 pm by Suicidal Insanity.

I've switched to CHKdraft for just locations and am using SCM for everything else.

I opened an example map (wheel of war, melee so it shouldn't have any actual triggers) and clicking Locations went fine, but clicking and dragging to make a new location caused another crash. This doesn't look map related, but something within Trigedit I assume since that's the name of the error box.

Any info you want that is relevant and could help I'd happily give.

Thanks everyone!

Attachments:

Check your ScmD program folder for a file called "backupDB.scmdDB". Sometimes this file gets too big (~2GB) and causes crashes throughout. Rename the file and see if the errors persists.
It contains all your previous map versions. So if this file is the cause, make sure you've got everything you need from it before getting rid of it.

The trigedit.dmp file is created whenever anything goes wrong, not just trigedit.


You could try changing the size of the window, or scrolling slightly to the left and bottom before creating the location and see if that helps.

I need to find the correct symbols file to take a detailed look at the crash, but its a nullptr deref so I'm not sure why that is triggered by locations immediately.

I checked the backup and it was about 2.6k kilobytes so it shouldn't be the issue.

As far as I could tell, changing the window size and scrolling in those directions didn't look to do anything.

I was able to get it not to crash as soon as selecting the Locations tab, though, by doing those things.

Thank you for your continued help and support with me on this. SCMDraft is working fine for you right? If there are any files outside my scmdraft directory that could be screwing with something _inside_ the editor let me know.

Thanks again

I'm pretty sure its a threading or memory corruption caused by scmdraft itself. I've been fixing errors as I find them, but haven't released an updated version.

Well, wherever you are, whatever you're doing, thank you so much for doing God's work. I really love making campaigns on this thing!

and a parting question - what is your stance so far on Chkdraft? would you work with its author if you ever found any free time if you could?

Oh my you popped that question,

We've so far had an ok working-relationship, you're always welcome to my concepts and code (MIT Licence - can use however).

We might be able to do more together but we both suffer from a terminal lack of time, and we probably have different priorities with the time we do have (he has an NDA with blizzard, which probably limits how much we can even discuss here, but I assume he's stabilizing SCMDraft and maybe adding a feature or two to keep with Blizzards updates, not trying to reinvent it as an open-source project).

Our codebases might be compatible... we're both in C++; I maintain the CHK sections as byte buffers (to heinermann's constant disapproval) any abstraction is used just for the current call stack and any changes land back in the byte buffers; I use the windows API for the GUI.

I'm up for most anything, except a time commitment

Its not a competition, I'm glad others are also having fun with starcraft.

I haven't taken a look at chkdraft's code yet because I always felt that would be unfair with me not sharing mine. And I never shared mine because it wasn't up to the standards I currently expect my code to have, after 10 years of coding for work. Back when chkdraft was started I started redoing some of the data file classes with the though of sharing them, but work + life happened and then chkdraft had its own versions .

If nothing ends up happening with blizzard, maybe we can still see about making a set of base classes for the data / graphics as a start.


Actually scmdraft parses all buffers into custom classes / structs with getters / setters / (And nowadays, some even have events instead of having the UI call into every other part of the UI that is depenent on the settings), only thing that is kept as a byte buffer is

Scmdraft uses win32 API as well, but the oldest windows aren't even done using dialog templates, they were done using a custom window class which creates all sub windows manually and a dialog like custom window proc. Most of those have been replaced by proper dialogs as time went by though.

It looks like everyone here is probably in the same boat then; just waiting to see what happens in the future, if eventually anything. I just hope things are going well for the both of you. Looks like there's going to be a lot more mapping coming this summer which is something I can totally get behind.

Also, I haven't always had this problem. It really seems to be hit or miss- locations will work well for a span of time, and then just kinda crap out for some reason. If I can find my old laptop charger I'd like to fire up scmd on there and test it out, because last I know it worked fine.