@claudio-ficara
Still wondering if Spine support is evolving with new features: I'll take a look at you dev log, I just wanted to refresh this topic ;)

I'm starting to work on a game for Android devices, but as you can guess it's going to be for the next year!

@larsiusprime Well, that was basically the most perfect response I could ask for :) thank you for taking the time to write it.

I'd say read some of the dev logs, join other parts of the community like the discord. And look at open source projects people have done in HaxeFlixel.

Hello
I am new here
thanku

kerela tour packages for couple

Yes! It is possible to use HaxeFlixel as a framework for a 2D MMORPG. I've made a 2D MMORPG using HaxeFlixel and it's been great, I've never had any regrets about choosing HaxeFlixel and would use it again if I was starting a new 2D MMORPG project. If you'd like to check out my game as an example of an MMORPG made with HaxeFlixel, you can find it here: http://www.portalwalker.com

Hello

At github, mphx is a multiplayer library for haxe flixel. At that homepage the library is said to have lag issues.

<a href=" http://www.cheapassignmenthelp.com/"> cheap assignment help</a>

Oh yeah, I had default on, it breaks when i change to something else. Chrome too

There are no plans for this.

FlxGroup can be added to other groups/states, so update() and draw() are called on all the members of the group with exists == true. Be careful, adding to two groups can lead to update() called twice resulting in 2x simulation speed (can be solved by marking the group active = false).

Use arrays when you don't want to update/draw sprites, or they are updated/drawn from other group already.

And also, as you said, use groups when APIs demand FlxGroup, like for object recycling or collision.

It's not slightly worse, it's a lot worse. Don't measure with fps, measure with milliseconds, they tend to accumulate the more code you have, and if they accumulate more than 16 ms per frame, the player will have less than 60 fps. If you have steady 60 fps, but with steady 15 ms (draw + update), you're in trouble.

@aik It works great if you use webgl like "lime test html5 -Dwebgl"

Otherwise it's slow and dirty

That said, the gamepads don't seem to work... Also, in the non working with webgl category (for flixel 4.3.0) you have the stuffs like changing sprite's color, the red turns blue, the blue turns green, colors are wrong basically, and this http://api.haxeflixel.com/flixel/addons/display/FlxTiledSprite.html doesn't work

The rest does, as far as I can tell, and sound doesn't seem super fast, but I haven't fully tested yet so maybe I'm wrong on this one

Phaser definitely have those things working, but then depending on the version some stuffs might be broken, like anchors on sprites for instance

Edit: And I just realized I'm replying to a year old post

Checking for null errors are important. The build error on neko, the invalid operation, come from uninitialized variables. To fix do var foo:int = 0. In this example, the 0 initializes that variable.

Hi, please refer to http://haxeflixel.com/documentation/install-development-flixel/

Flixel currently doesn't support the latest OpenFL, but progress is being done towards that

You can enable new OpenFL/lime versions by using a compiler command, however, isn't supported and bugs might appear. You can read more about different versions here

Personally, I've been using legacy for quite some time now and is superb. It won't stop you from creating a good game. Can't wait for the next version to come up tho!

Because it would be the slowest part of rendering. My example may not be the best, because copyPixels in new versions of OpenFL is really slow anyway, so you don't want to use it unless you are ready to do some optimization work on it
Note that I'm talking about native targets, flash target is mostly unchanged AFAIK

@bronson-sedeno

Thanks! I'll check it out.

@Gama11 How about the latest lime (5.3.0)..? If I install that then Flixel states:

Flixel is currently incompatible with Lime 3.0.0 or newer

Is there anyway we can ignore this and force a newer version of Lime instead of -3? I'm asking because i'm having some Jitter on camera follows again on a new project. Newer version of Lime just might have better SDL support and with that less Jitter. It seems to be a windows thing. I'm not seeing it on android.

There are a couple of discusion to be found with Google on this subject, but there does not seem to be a real solution.

Quote SruloArt here:

Try making vsync to only affect cpp (if="cpp" on your project.xml in the end of the relevant line) or cancel it altogether. Try FlxG.fixedTimestep = false; FlxG.maxElapsed = 0.25. Sadly, If these options won't work I wouldn't be too surprised.

A thread on github, an other one on google-groups, an interesting one on OpenFL (they talk about SLD there), and a post of myself. The problem just might not be Flixel or OpenFL, the problem can lay in Lime or SDL (or the way SDL is being used). Just playing around with stuff like:

FlxG.fixedTimeStamp, FlxG.maxElapsed, FlxObject.pixelPerfectPosition, FlxObject.pixelPerfectRender, Lerp and VSync.

Is time consuming and not fixing anything. I would love to try out a newer version of Lime, perhaps they fixed it there? :S Is it in anyways possible that i can try this? (Development version, beta version?)

I really like HaxeFlixel and enjoy using it. But this Jitter on camera while following is driving me insane! It does not happend at the beginning of the game, but after say 10 seconds it slowly starts, after that it builds up. After 2 minutes or so its very noticeable.

Does anyone have a solution for this?

Cool! Glad it could be worked out :)