Diddy + Tiled = black lines

Monkey Forums/Monkey Programming/Diddy + Tiled = black lines

Volker(Posted 2013) [#1]
Using Monkey V66, Tiled V 0.7.0 and an older version of diddy.

I'm getting little black lines between the tiles (bleeding edges?) under android.
Reading through a lot of threads told me to use Image.PaddingXY
and leaving a transparent 1 Pixel border around my tiles,
but that would force me to change the diddy code.

Anyone around here who solved this?


Goodlookinguy(Posted 2013) [#2]
I'm pretty sure this occurs when the matrix is translated to a non-whole number floating point value. I never get this issue anymore because I round translated values to the nearest whole number.


Amon(Posted 2013) [#3]
Not sure about this but try changing mojo_imagefiltering values!


Volker(Posted 2013) [#4]
when the matrix is translated to a non-whole number floating point value

I tried rounding all floats given to Tilemap.RenderMap(). No changes.


Not sure about this but try changing mojo_imagefiltering values!


Been there. Done that. No changes.


Goodlookinguy(Posted 2013) [#5]
I don't use Diddy, so it might be their rendering code that has the problem. I just made a test myself using my code and it rendered without the lines between the tiles. So, I dunno.

Also, I didn't have the padding flags or filtering stuff changed. All default settings from Monkey.


therevills(Posted 2013) [#6]
Can you supply your graphics/code? Or produce a repeatable example?


Volker(Posted 2013) [#7]
If I take the tile example from diddy (r339) and set it to landscape,
SetScreensize(800,480) I get this effect on my both android devices.




Amon(Posted 2013) [#8]
It may be better to try the latest version of diddy. You're using quite an old version.


Volker(Posted 2013) [#9]
Thanks all, with newest Monkey, newest diddy and disabling MOJO_IMAGE_FILTERING_ENABLED the black lines are gone.

But as I expected a whole bunch of new construction yards have opened.
EDIT: What the hell happened with List.Remove(object)?


Nobuyuki(Posted 2013) [#10]
List.Remove has been depreciated. Use Either RemoveEach or RemoveFirst...


MikeHart(Posted 2013) [#11]
Or node.Remove, which is the fastest method anyway.


Volker(Posted 2013) [#12]
It's back in V71b. And hopefully stays where it is :-|