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.
Love the artstyle. Looking forward to trying a demo of this when it's released.
Yeah, this same issue exists on the Mac. I think if you want to give the user options you'll have to have the game windowed then allow them to make it full size and close it at will.
Ah cool, in that case, yes I think the GitHub issues section would be the best place to raise this.
I'm not sure if you've checked out the HaxeFlixel channel In the Haxe Discord server, I personally haven't used the animation.reverse() method before but maybe someone in there has and will be able to answer your question.
It is much more active than the HaxeFlixel forums by the way :)
Hmmm, is there a way to just disable the collision for just the player temporarily and keep it for everything else?
Also, this has got me curious about the type of game you're making that when the player goes through a tile then other things go through it as well? What other things? Like enemies or NPCs that follow the player?
@sano98 said in Highrisers - now on Kickstarter:
Looks really good. I know Mac users don't usually buy as many games as Windows users but any chance of a Mac demo?
Interesting issue. Would you be able to share some code, please? It's difficult to visualise what is causing the problem.
I don't know if you've already fixed the issue but for me I had to add an extra bit of height to my player so the collision would kick in a bit earlier. Liks so
function fallInClouds(Tile:FlxObject, Object:FlxObject)
{
if (FlxG.keys.anyPressed([DOWN, S]))
{
Tile.allowCollisions = FlxObject.NONE;
}
else if ((Object.y + 50) > Tile.y)
{
Tile.allowCollisions = FlxObject.CEILING;
}
}
I don't have any experience with Android but I have had an issue where some save data works in HTML5 but not on native Mac and that was because of the format of my save object.
This didn't work
{
itemsSaved: [1, 2, 3]
}
but this did
{
itemsSaved: "1, 2, 3"
}
Maybe you're having a similar issue?
Just tested the exact same code and it seems to work for me. Are you able to check if you have any errors in the browser console?
Also, did you change anything int he Project.xml file?
Hmm that's odd. Have you got a link to your project on GitHub or something?
Hey guys, I'm new to Haxe and HaxeFlixel and I'm really enjoying it. I'm planning to add a few slope collision objects to a level with Nape and I'm having a bit of trouble getting flixel running with nape version 2.0.20.
I'm getting loads of these errors:
/usr/local/lib/haxe/lib/nape/2,0,20/nape/geom/Vec2.hx:522: characters 18-23 : x: Custom property accessor is no longer supported, please use `get`
/usr/local/lib/haxe/lib/nape/2,0,20/nape/geom/Vec2.hx:522: characters 24-29 : x: Custom property accessor is no longer supported, please use `set`
/usr/local/lib/haxe/lib/nape/2,0,20/nape/geom/Vec2.hx:558: characters 18-23 : y: Custom property accessor is no longer supported, please use `get`
/usr/local/lib/haxe/lib/nape/2,0,20/nape/geom/Vec2.hx:558: characters 24-29 : y: Custom property accessor is no longer supported, please use `set`
/usr/local/lib/haxe/lib/nape/2,0,20/nape/geom/Vec2.hx:598: characters 23-33 : length: Custom property accessor is no longer supported, please use `get`
/usr/local/lib/haxe/lib/nape/2,0,20/nape/geom/Vec2.hx:598: characters 34-44 : length: Custom property accessor is no longer supported, please use `set`
/usr/local/lib/haxe/lib/nape/2,0,20/nape/geom/Vec2.hx:860: characters 22-31 : angle: Custom property accessor is no longer supported, please use `get`
/usr/local/lib/haxe/lib/nape/2,0,20/nape/geom/Vec2.hx:860: characters 32-41 : angle: Custom property accessor is no longer supported, please use `set`
/usr/local/lib/haxe/lib/nape/2,0,20/nape/dynamics/ArbiterList.hx:243: characters 23
...
Does anyone know what I can do to fix them?
What you could do is change the sprite size, then update the hitbox to make the hitbox bigger. Shrink the sprite, then don't update the hitbox to keep the bigger size.
Assuming this was your code.
_playerCar.loadGraphic("assets/images/car.png", true, 50, 20);
_playerCar.setGraphicSize(100, 50);
_playerCar.updateHitbox();
_playerCar.scale.set(0.5, 0.5);
// Don't update hitbox after this
That way you'll have twice as much room to play with. I've done a similar thing but the other way round.