> > Thanks a lot! this is the project:

> > drive.google.com/file/d/163Kj3-GBoE6nGAAnBXF6MK35Im0YZhN4/view

> >

> > If you want me to export it to another format please tell me

>

> Okay, I have leaved comments, so now all should be cleared. Ask me more if not and have a nice day!

>

> https://drive.google.com/file/d/1RDeuoL4tcsmz1mIrkH6nd5_rdvKWcUnX/view?usp=sharing

Oh my god, what a speed!!

It´s exactly that i wanted.

I will study your comments.

Many thanks! ;-)

You are welcome)) This forum is a nice place, where you can always get a help with any problem ;)

Thanks a lot! this is the project:

https://drive.google.com/file/d/163Kj3-GBoE6nGAAnBXF6MK35Im0YZhN4/view?usp=sharing

If you want me to export it to another format please tell me

Okay, I have leaved comments, so now all should be cleared. Ask me more if not and have a nice day!

https://drive.google.com/file/d/1RDeuoL4tcsmz1mIrkH6nd5_rdvKWcUnX/view?usp=sharing

Share the project, please. I can help you to do that. Ihav esome experience in making beautiful scrolling, because I am developing my own game for Android now and I have a mobile browser that.

I can show you how to do that, but it`s hard to understand all thing while the project is hidden.

For the record I covered this in more detail in a new blog post: The surprising difficulty of resizing images on spritesheets

Using any fixed size border/padding does not always solve the problem - as noted the only real solution is power-of-two size and positioning on spritesheets, which is what the downscaling quality "High" setting does in Construct.

Thank you a lot for the explanation. It`s great to see that Contruct`s author is glad to explain how his engine works) I wasn`t even hoping that my post will persuade such big and detailed answear! Thanks a lot for your great job!

I have seen these lines too. This feels like a bug to me.

There may be thousands of images in the project, cropping and adding transparent borders to them all is definitely not a solution.. Not only it's a tedious job, but this may break the game - mess up image points positions, collision polygons, require code changes etc.

Totaly agree with you. I am very scared to crop just everything because fixes can take half life :(

Just an idea: add 4+ pixels of transparency around the 'Front-End' sprite, it looks like that texture is being bi/tri linear filtered into your circle sprite rendered image (if you are zoomed in or out, you might also be at a different mip level so you may need more than 1 pixel of source transparency buffer between the images.) Also if you want to do some testing/debugging before you try that, change the bottom of the Front-end sprite to all red pixels and see if that changes the color of the 'line' at the top of your circle sprite.

Okay... The line changed to red:

So, yeah... The solution is to cut every single object in the project... Not only one object should be cutted but every his neighboor on spritesheet, too. Sounds like a trip to hell, but I am starting to do that with hope that conditions which move objects wouldn`t be broken after this.

Thanks for a good idea for the experiment. Why I haven`t knew that before?

Guess you could turn off filtering. That would answer a question.

Not the question, but here we are.

Yeah, it`s working. Game looks like the worst sheet in the world, but it definetly works...

Fib, fredriksthlm,

Nice idea to look to the spritesheets, what I have just done. But result of my research is bad. Problem is more serious, because I didn`t found green objects near the circle:

Very strange thing...

This is a very common issue, I see it often.

I believe it stems from the spritesheets. If you have background images in your projects they can bleed to the sprites close to them in the sheet. Even if you have transparent borders of your sprites. But backgrounds don't, so they bleeeed

I don't know how to come around this.

Ohhh... It seems like I understood the problem... Okay, now we should wait Ashley`s comments about this. I hope it would be not too hard to fix this visual bug by adding space around tiling objects in the spritesheet.

Try adding a transparent pixel around the border, or just click the crop button in the Sprite editor.

Done before making the post. Nothing changed.

It might be a Tiled Background wrapping around the other side of the image, or it might be spritesheet bleed from an adjacent image. As ever it's hard to say for sure without seeing a project file. If it's the latter, changing the downscaling quality may help.

I don`t have very big wanting to share my project with over 300 objects and over 2000 actions, but I have seen this bug even in new project sometimes, when at least one object exist.

I have croped the object just after meeting this bug, but this gave no result. Also I am not shure that setting a higher quality is a good practice because I have a really big project now and I am going to build it for android, so high quality downscaling would kill perfomance in the game.

I feel myself a little bit stupid. Is ther any other ways to fix such bug?

P.S.: Do you recommend me an option, which was labelled by yourself as "not reccomended"? :D