Sprite Editor Fill just broke?

From the Asset Store
Supports 1D, 2D, 3D arrays. Import and export arrays in JSON format
  • all of a sudden the Sprite Editor Fill button just broke, it fills arbitrarily.

    is this happening for anyone else?

    its happening specifically when I try to change a color using fill. using r234.4

  • It works fine for me. Make sure you select the right tolerance and tick/untick "Flood fill" checkbox.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • dop2000 you have to zoom way in, its just leaving off little pixels of the previous color.

    I just retested it and its definitely happening...using solid colors so no need for tolerance.

    I mean I use construct everyday for almost 2 years straight now and all of a sudden its doing this, so its very noticeable.

    I know the Sprite editor in general is super buggy.. but this is different.

  • it does it consistently, its really not the fill-tool that's bugged. the program is not identifying colors correctly.

    so if you use paint brush 20 size or so, and click in a few random locations, if you use eye dropper and check the value it will slightly alter the color value in random places almost as if you put some noise on your brush - but its 100 hardness and 100 opacity.

    man what's with all these bugs!? its crazy how many issues I've had at since this stable update r234. this is like the 4th bug! I keep losing time researching these things!

  • I think flood fill has always been not very accurate. It's ok for some images, but if you need good quality, you should use an external editor.

  • dop2000 no, I've been in the world of pixel art and I would have noticed this before. something is definitely bugged.

  • You can just set tolerance.

    Or from looks of it, need to file multiple issues at least.

  • Yes, it has happened to me where the fill, color selection and various other buttons/actions are not working. The only thing that I have been doing to fix it is to go to another tab and then come right back. It will work after that. I am using Chrome also, so it may be browser specific.

    By the way, this just started right after one of the updates (can't remember which one now).

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)