~CROP(offset,0,w,h) causes honeycomb in large terrain imgs
Moderator: Forum Moderators
Forum rules
Before reporting issues in this section, you must read the following topic:
Before reporting issues in this section, you must read the following topic:
~CROP(offset,0,w,h) causes honeycomb in large terrain imgs
I tried to make an animated terrain by shifting a large image that was not fully displayed, using CROP() image path function. It is supposed to be distant terrain scrolling by.(http://forums.wesnoth.org/viewtopic.php ... 66#p482866) But instead, each hex independently slides away, the pixels it vacates show the underlying images. Here are some pictures:
On the right side of crop-error.png, there is noticeable green slash showing through the bluish chasm edge. It's like that part of the cropped image, which shouldn't show, is getting redrawn, while the parts that are supposed to be are not (the dark blue is a lower layer). Like minus sign got dropped somewhere or something like that.
This is my WML, the image names should be changed though:
As I'm writing this, it occurs to me that I did not try all mainline images, but even if that has an effect, there is still a problem. The sky-map.png image is 1814X729. Everything looks fine in the first frame.
EDIT: bug report
Spoiler:
This is my WML, the image names should be changed though:
Spoiler:
EDIT: bug report
BfW 1.12 supported, but active development only for BfW 1.13/1.14: Bad Moon Rising | Trinity | Archaic Era |
| Abandoned: Tales of the Setting Sun
GitHub link for these projects
| Abandoned: Tales of the Setting Sun
GitHub link for these projects
Re: ~CROP(offset,0,w,h) causes honeycomb in large terrain im
I've got a way to more easily recreate this.
1. I needed a large image, so I copied wesnoth-icon.png into the "terrain" folder of images.
2. Edit terrain-graphics.cfg so that one of the mainline terrains uses wesnoth-icon.png and CROP() function.
3. Open the map editor and try it out. I used shroud hexes to push the grass transitions away. I also fiddled with the crop width and height (all value 72 in the example above) and it did not behave like I'd expected.
To be clear, what I think this should do is shift a cropped wesnoth-icon.png to the left. Instead, it is making a mess.
1. I needed a large image, so I copied wesnoth-icon.png into the "terrain" folder of images.
2. Edit terrain-graphics.cfg so that one of the mainline terrains uses wesnoth-icon.png and CROP() function.
example using Rp
BfW 1.12 supported, but active development only for BfW 1.13/1.14: Bad Moon Rising | Trinity | Archaic Era |
| Abandoned: Tales of the Setting Sun
GitHub link for these projects
| Abandoned: Tales of the Setting Sun
GitHub link for these projects
Re: ~CROP(offset,0,w,h) causes honeycomb in large terrain im
Looks like a bug to me...