Mike at BrashMonkey

Please try downloading the free non-Steam version of Spriter from here and install it and tell me if it runs for you: https://brashmonkey.com/download_spriter/

I recommend you zip up your Spriter project and send it to mail@brashmonkey.com so we can take a look at it. Ideally, a screen recording showing the initial key-frame before it gets "corrupted", then you making changes to a later key-frame, and then the resulting change to the initial key-frame.

Is there a key frame for the things that are getting changed in the first place (there usually is) or are they missing? Do you know how to expand the timeline window to expose the key frames for each specific object?

It certainly sounds like something got somehow corrupted or mass duplicated but that's just a guess.

Can you try comparing the original packs like count for data and the character map and see if it's drastically different?

Which OS are you on?

Are you using something like Dropbox so you have "version control" and can revert back to older versions? (this is critical for production work so you don't lose tons of time/work due to situations like this)

If you'd like, you can email your Spriter project (zip up the entire folder with scml and all images etc) to mail@brashmonkey.com and we'll take a look when we get the chance.

Try loading the one that works and save it in whatever format you like. to be supe safe, save in both and consider the other a backup, but no one else has reported a file looking different after loading for years.

I recommend you zip up your Spriter project and send it to mail@brashmonkey.com so we can take a look at it. Ideally, a screen recording showing the initial key-frame before it gets "corrupted", then you making changes to a later key-frame, and then the resulting change to the initial key-frame.

Is there a key frame for the things that are getting changed in the first place (there usually is) or are they missing? Do you know how to expand the timeline window to expose the key frames for each specific object?

There's a new updte for the C3 Spriter plug-in. Please see if this helps:
 

Hi Everyone,
Here's a new video demonstrating the first Pro-only features to make it into Spriter B2. Namely IK, IK locking, and Rotation/Scale Inheritance toggling for child sprites or bones.

cheers,
Mike at BrashMonkey

That is great... I'll get onto it as soon as possible.
 
Thanks

Looks cool. Nice and clean. Best of luck with it!

I've just launched a free web/Android app, a "point and click" adventure called "Drained." It features quite a few characters and without Spriter I'd still be drawing frames by hand. It is undoubtedly one of the best purchases I've ever made.
URL:
https://tenterhook.net/drained
Screenshot:

Sorry for the delay. Edgar is currently tied up with work on Spriter 2 until we can release the next bit of update info for it. We'll be setting up a C3 subscription shortly for testing and development once Edgar's hands aren't so full. Hopefully it won't be too much longer.
Thanks as always for your patience and support.

I just checked and verified that at the moment collision rectangles are not supported in the C3 Spriter plug-in. It's a high priority to get that fixed, but we can't promise exactly how soon that will happen. 
I'll report back here as soon as there's a fix or progress towards one.

Sorry for the inconvenience.

If you own C2 you might want to keep your project in c@ until we can updated the C3 plugin. That's what I'll be doing with my current couple of projects.

It`s because your attached sprite scale XY axes need to match the bone XY scale axes orientation in order for their scaling to work properly. Bone "length" is the bone ScaleX axis.

The problem is that your character is not setup correctly for use with bones. You can try to rotate your character body image +90 (or -90) degrees in your image editing program (so it looks like it is lying on its side), then go back to spriter, adjust the rotation and it should scale properly.

s. We'll make an announcement when the time comes and everyone who owns Spriter Pro now, or who purchases Sprtier Pro or pre-orders Spriter 2 before the end of the current pre-order sale (Aug 3rd) will be eligible to sign up to be a tester.
Everyone who does will have to agree to an NDA (non-disclosure agreement) to do so.

I just want to close this, as fixed. Thanks.
Reference: https://www.construct.net/forum/construct-3/general-discussion-7/test-spriter-c3-addon-7-2-upda-130240/page-5?q=scml

I would also like to inform that the C3 SDK has some interesting features that you might like to use. Those include,
Editor :: Preview. Draw and Preview plugins on the editor. Potentially can be useful for showing and previewing the initial animation/frame of the Spriter Plugin even while on the editor. Custom Importer :: Drag files to import into Construct 3 and make events, objects, instances, container and families automatically like on Construct 2. Drawing :: The C3 SDK already had drawing features available on the  initial release. So, by now, it is stable enough to be supported. And a few already made use of it. There are probably a lot more. But I recommend you guys checking it out yourselves.
 
Thank you in advance.
- Chad

s. We'll make an announcement when the time comes and everyone who owns Spriter Pro now, or who purchases Sprtier Pro or pre-orders Spriter 2 before the end of the current pre-order sale (Aug 3rd) will be eligible to sign up to be a tester.
Everyone who does will have to agree to an NDA (non-disclosure agreement) to do so.

s. We'll make an announcement when the time comes and everyone who owns Spriter Pro now, or who purchases Sprtier Pro or pre-orders Spriter 2 before the end of the current pre-order sale (Aug 3rd) will be eligible to sign up to be a tester.
Everyone who does will have to agree to an NDA (non-disclosure agreement) to do so.

We're pleased to announce that Spriter 2 is far enough along in development to release a teaser video and open it up for pre-orders.
To celebrate this milestone, we're running a pre-order sale from now until August 3rd.

Use coupon code : SPRITER2 in our store to get 35 percent off your entire purchase. The retail price for Spriter 2 is not yet decided so for the duration of the pre-order sale you can pick it up for the same price as Spriter Pro.

Better still, anyone who pre-orders Spriter 2 during this sale will receive a Spriter Pro license as a free bonus.

For those who already own Spriter Pro, don't worry, you will automatically be getting Spriter 2 as a free upgrade so you do not need to pre-order or make any additional purchases. 

Both current Spriter Pro owners and those who pre-order Spriter 2 during this sale will be the first members of the community to be eligible to participate in the private beta some time in 2018. 

Stay tuned at spriter2.com, these forums, or our social media for future teasers and updates as things progress.

Please help spread the word by liking and sharing this video and our posts on social media.

 

We're pleased to announce that Spriter 2 is far enough along in development to release a teaser video and open it up for pre-orders.
To celebrate this milestone, we're running a pre-order sale from now until August 3rd.

Use coupon code : SPRITER2 in our store to get 35 percent off your entire purchase. The retail price for Spriter 2 is not yet decided so for the duration of the pre-order sale you can pick it up for the same price as Spriter Pro.

Better still, anyone who pre-orders Spriter 2 during this sale will receive a Spriter Pro license as a free bonus.

For those who already own Spriter Pro, don't worry, you will automatically be getting Spriter 2 as a free upgrade so you do not need to pre-order or make any additional purchases. 

Both current Spriter Pro owners and those who pre-order Spriter 2 during this sale will be the first members of the community to be eligible to participate in the private beta some time in 2018. 

Stay tuned at spriter2.com, these forums, or our social media for future teasers and updates as things progress.

Please help spread the word by liking and sharing this video and our posts on social media.

 

Don't worry at all. We're thrilled that you're excited about it and incredibly humbled by and appreciative of the incredible patience and support the Spriter community have shown us. We promise we're doing everything we possibly can to make Spriter 2 special ,and worth the very....very...long wait.
There will be an update with more info soon.
 

A new update coming very soon. Sorry for the very long delay and development cycle. We're building momentum now.

Edgar (Spriter's programmer) is currently focusing on Spriter 2 until it reaches its first major milestone and is ready for testing within the community. Once that happens we'll make several announcements with at least a general road-map. Spriter Pro is not abandoned and will not become obsolete because it offers specific features no other modular animation program does that make it the best choice for several types of projects, especially retro/pixel art or for projects where game performance on more humble devices is important.
Even now Spriter and Spriter Pro continue to be supported through continued development of tertiary products like our Animated Art Packs, Environment Art Packs, and even entire game engines (the first of which will be made available for testing soon).
Spriter and Spriter Pro won't be introducing any new big features in the foreseeable future, especial because Spriter 2 will be a free upgrade for everyone who currently owns Spriter Pro, and Spriter 2 is completely new, built from the ground up specifically to provide an entirely new set of features and workflow.
Spriter 2, while now making excellent progress, is still too early for any concrete estimates, but you can subscribe here for updates : https://www.spriter2.com/
 

Hey guys, I found a possible solution to the weird graphics on multiple SCML objects on a project.
I originally posted this here but noticed the problem was being discussed in this thread too.
I was having the same problem with the Spriter plugin for C3.
Problem:
Having more than one SCML object can sometimes cause that one SCML  loads the wrong sprite-sheet. This can sometimes be seen as "weird parts" cropped from the SCML object that is looking OK. This problem is compounded the more SCML objects you add to the mix. Why it happens:
Construct 3 automatically generates sprite-sheets of all its graphics for smoother runtime. However, this also includes the images imported for the base sprite-sheet parts of your SCMLs This in turn causes that, since the sprite parts are located on a bigger sprite-sheet created by C3, the position of the image parts are now different. The .scon looks for the image parts and crops them "correctly", however, the parts are now on a bigger and unpredictable sprite-sheet resulting in the issue. How to solve it (for now):
Since the problem occurs because C3 finds "spare room" to make a bigger sprite-sheet, then all we have to do is export a bigger, albeit inefficient, sprite-sheet from Spriter. This is done by following the instructions to export the animation from @lucid's post on the C3 forums -here- BUT when generating the sprite-sheet set it to FIXED instead of MAX on the Dimensions section on the bottom left side. This will cheat C3 into considering each SCML sprite-sheet animation as a single sprite-sheet on its own to export. Thus, solving the problem... for now. But won't this cause a huge spike on the size of my game?
Not really, if you notice, export both versions of the sprite-sheet (big with fixed 1024 and "max" 1024), and you'll notice they have the same size. The transparent useless space on your file does not add much to the final size of the .png, neither to the .scon file. Hope this helps you all!
Did it work for you?

Happy Spriting!