HaxeFlixel / HaxeFlixel/flixel

loadMapFromGraphic Fails On HTML5

Open
#2,377 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haxe
Stars
2.2k
Forks
522
Avg merge
34m
Merged PRs (30d)
1

Description

  • Haxe version: 4.1.5
  • Flixel version: ?.?.?
  • OpenFL version: ?.?.?
  • Lime version: 7.7.0
  • Affected target:
    HTML5

Code snippet reproducing the issue:

package;

import flixel.FlxState;

class PlayState extends FlxState
{
	override public function create():Void
	{
		super.create();
		var back = new FlxSprite();

		CoolFunctions.playSong('ikachan');
		CoolFunctions.fadeShit();

		bg = new FlxBackdrop("assets/images/Back.png");
		bg.scrollFactor.set(0.75, 0.75);
		add(bg);

		map.loadMapFromGraphic("assets/images/Map1.png", true, 1, [blank, a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t], "assets/images/tileset.png", 16, 16, 0, 1, 0);
		map.useScaleHack = false;
		add(map);
	}
}

Observed behavior:
Screen Shot 2021-08-10 at 9 37 59 AM

Expected behavior:
Screen Shot 2021-08-11 at 9 15 02 AM

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported loadMapFromGraphic call from the issue's Haxe snippet with an HTML5 target, comparing the observed and expected screenshots. Start at the loadMapFromGraphic entry point and trace the HTML5 loading path; done means the map renders as expected in HTML5.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.