Fair enough, IMO I tend to draw simple sprites and use that instead of using the shapes provided by flixel (unless it's a simple box, FlxSprite is good for that).
But yeah welcome to the world of HaxwFlixel, if you have any more questions feel free to as them in the forum, or discord channel. The community here is small but really friendly.
@Geokureli I am now an admin 👏 🎉
So if you spot any spammers I'll delete their threads and ban them 🙅🏿♂️ ⛔️
Hey Harold,
Yes, you are correct, the X and Y params are used for FlxSprite since FlxShapeArrow extends FlxShape which extends FlxSprite.
If I'm being completely honest my knowledge of the shapes in Flixel is a little rusty. Out of curiosity are you planning to move from shapes into your own custom sprites?
If you're able to check out the HaxeFlixel channel in the Haxe Discord server I feel like someone over there would be able to help out https://discord.gg/aZus3R
Nice, glad you figured it out. I'm curious as to why to used texture2D() and not flixel_texture2D() on line 20?
https://github.com/jobf/haxeflixel-pixel-scaling-shader/blob/master/source/PixelScaleShader.hx
Also for line 16 in your shader shouldn't this work as well because of swizzling?
ec2 alpha = vec2(0.07);
Man I wish I knew enough about shaders to help you out, I'm learning but I'm not quite there yet. Have you tried asking your question on the Haxe Discord server?
Maybe you can add a link to this question on there, it's much more active than the forums.
Also, I feel like there are easier ways to scale a sprite than to use a shader. Well as in if you had a large sprite you could scale it down easily but I'm not sure about scaping up a small sprite 🤔
I think the best people to answer that question are either Austin East and Will Blanton who have both worked on Ogmo. They frequent the HaxeFlixel Discord channel so if you have access to it I highly suggest you ask your question there.
Wow, I'm super flattered thanks for the offfer, but unfortunately, time isn't on my side at the moment :(
I'm happy to help with any Flixel related questions you have though.
Ah okay, yeah there's definitely a way to do that. I'm not sure what type of game you're making but you could add a collision box to the end of the level with FlxObject or something and when the player collides with it run
FlxG.switchState(new LevelTwo());
Which will contain your new map. Let me know if this makes sense.
I haven't used Ogmo before but I'm sure there is a way. What do you mean by 'writing it all together'? Do you mean linking from the level with the first map to the level with the second map?
Hey @jgedri , it's a bit old but I do have a project you can look at, https://github.com/RichardBray/Scales-A-Pangolin-Story
Basically the way I do multiple levels is to have a parent/super class LevelState.hx, which will have most of the level data, and keep unique things in the level files themselves like LevelOne.hx, LevelTwo.hx. I hope that makes sense.