Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 06/14/2020 in all areas

  1. 3 points
    Mike at BrashMonkey

    Spriter 2 FAQ

    All Spriter Pro owners have access to the Spriter 2 alpha builds which are now updated on a roughly 2 week schedule. We're really sorry for all the long delays to this point and are developing it as fast as we can while simultaneously making sure we don't rush any aspect of it's data format or code base in a way that would cripple it's development in the future. There should be an update any moment now with information on what's currently being worked on and a new build shortly after that. We're doing our best to provide frequent update builds and progress reports as we work towards getting all the core features fully functionally and tied in with each other and the required UI as soon as we can. We have big plans for features and expansions well beyond the release of version 1.0, which is a big part of why it took us so long to get to this point (making sure the core code and data format are future-proof and will easily support the more advanced features we plan down the line.)
  2. 2 points
    Mike at BrashMonkey

    Spriter 2 FAQ

    Please keep an eye out for the update notes and new builds every 2 weeks. The next few builds should get the three core features (bones, 'pins', and 'strokes') in and working together, and things should pick up momentum from then on. Our goal is to get all the core features in and working nicely as quickly as possible. Estimates are dangerous and nearly always wrong. The best way to assess progress is to keep an eye on the update build releases.
  3. 1 point
    Hello again everyone! The latest build went up Wednesday afternoon. You can find additional info in the video and changelog below. We've decided to delay bones one more build to get them working better with the other new features introduced in this build. Bones should be working nicely with the new deformation features when the next build is ready in roughly two weeks. We're pretty excited about what's up ahead and the state of the roadmap to 1.0. Once the bone build is released, one or two builds later we will reintroduce strokes, now using and interacting with all the new systems and features. The flexibility of all these features working together should allow for some really cool possibilities. After the stroke build, there are just three main 'phases' left until a feature complete beta and 1.0. Well, really more like two and a half. The first phase will consist of a bunch of small essential features that will flesh out the program and make it feel complete. These will be all the basic functions like multi-selection, animation management, copy/paste, delete, image/video export, etc. Also, during this phase we will be polishing the user experience, streamlining the workflow, and of course eliminating all the bugs we can find. Each build during this phase should feel like a substantial step toward 1.0. The second phase will be implementing the last major 1.0 feature, which will be image swapping. We want image-swapping to feel easy and natural to work with as part of the larger set of deforming features, so it's not as straightforward to implement as it might seem at first. The systems that power the image-swapping will also be a big part of what powers a lot of the post 1.0 features, so this will most likely take more than one build to fully flesh out. When image swapping is ready we will be in feature complete beta. This means the program should have all the functionality of 1.0, though it may still contain bugs or minor usability issues. Finally, the last half-phase will be any refactoring maintenance under the hood that still needs to be done. I will also take this opportunity to separate the editor portion and the runtime portion of the save format if that hasn't already been done yet. And of course, again we will squash any major known bugs before we call it 1.0. Upon 1.0 release, we will release the Mac and Linux versions as well. Thanks again everyone for your patience during this long journey. We're nearing the home stretch. New 0.0.0.18 features: Bone features delayed until 0.0.0.19: 0.0.0.18 Change Log Additions Added a new pop-up menu item when right-clicking a mesh to choose a deformer for that mesh (pin deformation has been moved here) Added quad patch deformation Added bezier patch deformation Added the ability to add additional child meshes to any deformer (see help for additional information) Changes and Enhancements Pin deformation no longer automatically applied to a mesh. It can now be accessed by right clicking a mesh, and accessing the deformer menu Help now supports multiple pages of information Known Issues Undo and Redo don't always function correctly with the new features Visual bug when dragging out new images. Sometimes image disappears momentarily Visual bug when first applying a deformer to a new child. Image sometimes shifts momentarily Double entries for images in z-order Changes to z-order in rigging mode not reflected in animation Occasional visual glitches while editing animations Save and Load not working reliably in all situations Images saved from certain image editors will acquire artifacts when they have antialiased edges where the alpha isn't fully opaque or transparent. These issues aren't exclusive to Spriter 2 and will affect any game engine that doesn't preprocess them. These pre-processing functions will be introduced in a future version, and can be ignored for now. Dragging out more than one of the same images doesn't function correctly. Changelog appears every time you open the software, instead of just the first time you open the new version
  4. 1 point
    Yes, I am on Windows, and I get the same result if I'm scrolling with either of my two mouses, the scrolling strip on my Wacom tablet or the keyboard. But I have now split it up into segments of just a few seconds each in length, which is a much better way of doing this. (I have not been working on this project since April, btw. I finished the video I was experimenting on back then without any animation, but I am now working on a simple animation for my next video. As it is my first attempt, it is very simple but still takes me a lot of time. I am making progress though, and it will be finished within a couple of days. I'll post in the "Your Works" section when it's done.) Also, I know I posted a request for movie export somewhere. (I can't find it on this forum. Maybe it was on Kickstarter?) I'm now retracting that feature request as it's not needed. Video editors (I can confirm both DaVinci Resolve and Lightworks) are smart enough to recognise the series of png files as video clips! Doing it this way is even better, as all transparency is preserved, and there are no compression artefacts. (I wish I knew that before setting up a workflow with ffmpeg and a greenscreen backdrop in Spriter.) So taking the animation from Spriter and putting it in my video is very easy.
  5. 1 point
    Sorry, he's trying to wrap up the new Spriter 2 alpha build (which got delayed... he's hoping to release it today) and updating the Construct 3 plugin will be his first task once it's out.
  6. 1 point
    If you purchase Spriter on Steam you will automatically get the Steam version of Spriter 2 as a free upgrade as soon as it becomes available.
  7. 1 point
    Sorry about the delayed reply. Edgar has it on the top of his to do list and will work on the issue as soon as he can. We'll report back here when there's a new build to try which will hopefully resolve the issue for you. Thanks for your patience.
  8. 1 point
    ekeagle

    Please post feature suggestions here.

    A standard JSON implementation to rule them all: https://github.com/ndee85/coa_tools/issues/26 There's actually software like Affinity Designer that supports exporting to Spine JSON Please make Spriter receive JSON so Spriter can receive sprites directly from graphic applications and then you (Brashmonkey) talk to Affinity so they add an option inside Affinity Designer so Spriter can be part of the workflow too. Please also add first party (developed and supported by you instead of third parties) runtimes (instead of first party converters) for Unity and most used. If possible add real time editing directly from Spriter into Unity like Toon Boom does.
×
×
  • Create New...