In the dev builds that\'s a possibility. But in the current live build everyone is currently using, probably not. It is typically identified as tag -13 and for all I know it could have to do with bloom (I\'m not a programmer or anything so its my own stab in the dark and very likely wrong).
Whatever the case is, when SMedit runs into a ship with these new \"tags\", it barfs on itself. Most of them it silently skips but some make it vomit rainbows. The objects (ships) that it skips are usually not loaded and for a similar reason this prevents SMedit from seeing custom stations as well. When this happens and assuming you have run SMedit from a command prompt, that prompt window will update with a bunch of traceback messages like you\'ve been seeing in this thread for the last several pages. The most common traceback mentions a bad tag \"-13\" and others I couldn\'t begin to guess at.
Just let JJ whittle at it at his own pace. These potential suggestions like \"maybe its x or y\" may have already been persued. We can only sit and wait for good news. Until then we\'re just speculating on what the new tags that break compatibility are.
Whatever the case is, when SMedit runs into a ship with these new \"tags\", it barfs on itself. Most of them it silently skips but some make it vomit rainbows. The objects (ships) that it skips are usually not loaded and for a similar reason this prevents SMedit from seeing custom stations as well. When this happens and assuming you have run SMedit from a command prompt, that prompt window will update with a bunch of traceback messages like you\'ve been seeing in this thread for the last several pages. The most common traceback mentions a bad tag \"-13\" and others I couldn\'t begin to guess at.
Just let JJ whittle at it at his own pace. These potential suggestions like \"maybe its x or y\" may have already been persued. We can only sit and wait for good news. Until then we\'re just speculating on what the new tags that break compatibility are.