Fainder

  • 19 фев 2024
  • Регистрация: 22 июн 2017

    I tried a couple exports and it seems to work fine indeed! 😃

    Sounds great, thank you so much! 😃

    Thanks Misaki,
    I redownloaded the launcher when I first installed the new version, so I'm assuming it's the latest

    I'll email you the major offender file. With other Spine files the trend I think I'm seeing is it won't export layered PSDs if I have separate skeletons checked, but that's all I noticed

    Hello, I recently started using v 1.4 and the PSD export option seems to behave weirdly. I use the export layers option a lot, and in the most recent Spine version it is available or unavailable (seemengly?) at random
    It's present with some files, it's not in others, and it only appears in some files if I check different options. I used to do this all the time just fine in version 3.8


    I'm trying to compare and find out what's the difference between these files, but I really can't tell.
    Any suggestion as to what could interfere?
    Thank you!

    • Изменено

    oh! this may help with something else I was noticing then. After reinstalling I was noticing some jagged lines in the image exports and meant to troubleshoot that soon too. So probably I need that linear blending enabled :think:
    Anyway, thank you so much for looking into it! :rock:

    Do you mean now? Not manually for sure
    edit: no, it doesn't look like the driver was updated

    Hey Misaki, sorry for the delay on my side as well.
    After some uninstalling and reinstalling after wiping everything, it now exports correctly. I wonder what that was.
    Thank you for your prompt support as usual!

    sent, thank you!

    Strange, I just reproduced it with this brand new project with only one bone and that banana texture
    Will send though


    btw, I get the same result with spineboy, just downloaded

    • Изменено

    Hi, I found a bug possibly. This is version 4.0.55 but I did try with another 4.0 yesterday with the same results
    Basically if I try exporting a png sequence, it adds up the frames on each image instead of rendering an image per frame. It does the same if I try to render frames as PSD layers.
    Here's a simple test example I just saved:


    I did these kind of exports a thousand times in older versions with various combinations of skins, animations, whatever, so I doubt I'm screwing up some setting, though I'm open to any tip
    Thanks!

    I'm not pinning any for the export I'm attempting
    I'll send the file though, thanks!

    Tried 3.8.79, same results :/
    I had noticed when mixing skins it applied only the constraints for the selected skin, though it ignored all the constrains, this only ignores some

    Hello,I'm in Spine 3.8.76 and trying to batch export a PNG single pose for all the skins in my file and a bunch of elements that use skin constraints end up twisted, as if the export doesn't use the constraint
    The funny thing is it does apply some constraints, and not all the same across different skins. After a few tries I noticed it even ignores different constraints every time
    I was reading through the changelog, is it possible this was already fixed in newer versions, since I see some work has been done on skin bones/constraints?
    Thank you!

    ps: the constraints don't have conflicts. I checked and the file works correctly in game already. The constraints work correctly in every other situation, even single skin png exports, both current pose and animation

    • Изменено

    thank you! <3

    needless to say, it displays no issues in the editor

    Hello! Question about loading attachments at runtime: there are some attachments I tinted in spine editor, when loaded at runtime the region attachments show up colored correctly, while mesh attachments show up with the texture color, untinted.
    Is this intended?
    I did this in a few cases to reduce the number of textures in the atlas, but since all the other attachments are loaded at runtime over a single template set into spine editor, we do the same for these (which loaded correctly when not using a template)

    • Изменено