Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'afd-5973'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 1 result

  1. Sometimes, eventhough Spine is selected as Batch builder, no spine.json file is created when exporting slices. I have to watch more closely when exactly this happens, but I'm pretty sure this is what happens: - Have a file, create slices, select Spine batch export and export the slices (spine.json gets created just fine) - Keep Affinity open and start creating a new file, create slices and go to the slices tab in the export persona: now 'Spine' is still selected as batch exporter, but it doesn't use this batch exporter when exporting the slices. It only seems to work if we manually set/refresh the batch export selection by moving to another setting in the dropdown first and than re-select Spine in the dropdown again. So it looks like the batch export method is set to 'none' when creating a new file, but the UI for it wasn't updated, so it still shows 'Spine' while in reality it's set to 'none'. This is obviously confusing and prone to errors.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.