Jump to content


  • Content Count

  • Joined

  • Last visited

About xrabidx

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I know that you Spriter folks seem to care very little for your Construct user-base, to the point of damn near neglect. Even when provided with code fixes and exact line numbers, the Spriter team still refuses to fix basic bugs in the plugin, for seemingly no reason, the excuse always given is Spriter 2, which has yet to materialize in anything other than gifs and youtube previews. Can we please for once get a timely update to the Spriter SCML plugin so that it works with the latest runtime? For something that is seemingly an enormous chunk of your users, the team shows an active disdai
  2. Okay, so my team desperately needed a fix for this, so we spent the weekend getting intimate with the C3 SCML addon. We figured out that what was actually happening was that only the last construct object in the instance array was being set, always when using "setC2toSpriterObject" It took us a bit to figure out that the .c3addon is just a renamed .zip file (lol) -- and once we had the source code, we dug deep into the "setC2toSpriterObject" function. Going through the massive run time file we eventually figured out that on line "2160" the "c2Obj" variable was being set to "getFirstPic
  3. It seems that when there are multiple instances of a Spriter object, the action "Set C2 to Spriter Object" get confused and attempts to attach to the Spriter object with the highest Instance ID (so if there is 2 Spriter objects, it will attach to Spriter with IID of 1. Meanwhile, if I set position using pointX/pointY or objectX/objectY, everything goes to the correct position, but it seems that all animation is about a single tick off. If this is a bug in the plugin, and not my own stupidity of missing something blatant, and I know that there hasn't been an update to the C3 addon in a w
  • Create New...