Staredit Network

for some reason, when i edit my map in SCM Draft 2 0.5.5 in terrain, I tried to edit it afterwards in Starforge 2.2. For some reason, none of the terrain changes that i made was showing up but they were showing up in the Xtra- Editor so it has to be Starforge. any answers?

<note> the sprite changes that i made were shown in Starforge but not the terrain.

many editors have special things so mixing editors is a bad idea.

you have to put them in order like putting units first then terrain.

i think moose had the problem before. go talk to him i think he knows what to do

There are two (nearly) identical sections in the CHK file that deal with terrain. Starforge uses the one that Starcraft uses. Staredit (and I assume Scmdraft, from what you say) use a secondary one that SC ignores. The true test here would be to play the map in SC and see what the terrain looks like. The bug is probably in SCMDraft.

Or it could be the both of them.
I know Heimdal knows more than me but I think I'm right this time. you said that both .chk files are different. Since they are different, obviously some parts of the terrain placing code thing has to be different so when you convert to another editor the code changes can be interpreted the wrong way and they could be screwed up.

[center]I think StarEdit is the only editor that actually uses the TILE section, seeing as how it wouldn't make much sence for SF, or SCMDraft to read the TILE section, when it really only needs to work with the MTXM section.

Key: 'TILE' = terrain section that SC doesn't read from.
'MTXM' = terrain section that SC reads[/center]

Beer, I don't really understand what you're saying. If you're saying that it's possible for the TILE section to affect how the map looks in Starcraft, you're wrong. SC completely ignores the section, and you can even remove it from the map and SC will still play it.

I don't know if (or why) SCMDraft would use TILE instead of MTXM except for SI's devotion to staying SE-Compatible, but the evidence here suggests that that is the case. Like I said: Play the map in Starcraft. I'll put money down that what you see is what you saw in Starforge.

I'll take a look, however scmdraft doesn't store MTXM and TILE seperately so I dont know what could be causing this, it should write identical data to the CHK, and then updates the data with the doodads.

yes, it is something wrong with scm draft 2 0.5.5. I tested it in Starcraft and it looked exactly like it was in Starforge so it is a big bug in SCM Draft 2 0.5.5. I did fix the problem though by just going to into the old SCM draft 2 0.4.5. and it worked.

ok, this is caused when the map has 2 MTXM sections, the first one is updated by scmdraft and the second one is the unchanged one being read by SC and SF. I'll have code in place to delete all MTXM sections next release. The issue was a missing ifdef causing the MTXM to only be removed if there was no TILE section present

ok thx, ill jsut stick to the old version for terrain for now

I dont see what you have against using real doodads instead of brushes, real isometrical terrain instead of nonworking pseudoisometrical, etc
I support the staredit format because it allows greater inoperability, and allows nicer terrain editing (no partial doodads on the map when half of it was overwritten, etc)

And thats why I open my map in SCMD2 after editing it in SF. I must revive my doodads.

I'm not saying SE-Compatibility is a bad thing; indeed I wish I had made it a higher priority. But of course, both methods have their own advantages and disadvantages.

It's SI's new plot --- make SCMDraft better and uncompatible with SF to shut Heim out. Microsoft copier.

I even added support for SF's semi protected map format, which imo weakened the possible protection level of maps

If you update SF sometime, will you fix your wav file adding code so that it also updates the WAV section properly? currently neither staredit nor scmdraft recoqnise any wavs added by SF.
The CC specs are invalid, if you dont have accurate specs you can ask me.

Heimdall, don't be beatten by SCMDraft !!! Or i'll cry everyday

All you have to do is put up with crying yourself to sleep every night.
Other than that, you can afford to switch editors.

Rexy, you used to be hardcore pro-SF too...what happened?

comon.... ;(

I guess people stopped "going with the crowd"...

...and to comment on interoperability, SI isn't more like MS. If anything, it's Heimdal: Blizzard set the map format. StarForge ignores some of its options, like the aforementioned use of doodad terrain brushes, where as StarEdit uses real doodads. This makes StarForge cause StarEdit unable to recognize the doodads since they have no entry except for terrain. Thus, if you want full map editing, you're only locked into SF.

SI, on the other hand, took time to figure out each section and its relationship towards StarEdit and StarCraft (except for the minor bug that this thread was about), and saw where CC.org was wrong and/or inaccurate. Instead of using a new, semi-working way of editing maps, he used the set Blizzard standard and achieved interoperability. That is part of the reason why I believe SCMDraft is superior.

So, apart from triggers and minor perks like custom terrain brushes, why are people still "hardcore pro-SF"?

[center]I wouldn't mind having accurate specs... It'd help me alot on some... projects...[/center]

(According to SI offhand)

The only sections that are inaccurate are WAV, MTXM, TILE, and ISOM.