I'm having trouble with the windows build

[Jordan]

The animation on my platformer frame-drops from 60 to 30 despite just being a tilemap, an ogmo map, and a player sprite.

also, I'm having trouble getting the gamepad buttons to work as well.

[SruloArt]

What version of Flixel are you using? (+Lime and OpenFL versions). How big is the game window (resolution)?

Also, what do you mean by "The animation"? do you have an animation running with 60 FPS? or do you mean the general FPS of the entire game?

Did you check in the deubg mode that you don't have giant bitmaps? (there's a bitmap debug window).

Did you try debuging your game with hxscout? http://hxscout.com/haxe.html + a Flixel example: https://github.com/jcward/hxtelemetry/tree/master/test/HelloFlixel.

About the GamePad: have you checked the demo? (http://haxeflixel.com/demos/GamepadTest/).

[Jordan]

My version of flixel was 3.3.8 but I updated to 3.3.11 and I'm still having the same issues.
lime is at 2.5.0, and  is at 3.1.4 (same deal with the updating) 
the window is the default 640x480.

I meant just the game fps, sorry.

I didn't check debug mode for giant bitmaps but I'm not sure how I go about that.

I'll definitely check out Hxscout, although I'm not exactly sure how to use it after reading over the front page, though I'm sure there's more information on the site.

And I just tried the gamepad test in cpp, I'm getting the a,b,x, and y buttons registering as the d-pad, and L&R buttons registering as as start&select. also the right stick is stuck pointing right. 

Thank you very much btw!

[SruloArt]

O.K, so, there are a number of options:
* There's a bug in Lime (well, SDL really) when you enable vsync (it's on by default in your project.xml) on an Intel HD Graphics (4400/4600 for example). So, the "solution" here is to disable vsync (="false"). There are a number of other Lime/OpenFL bugs that can be responsible, but let's not go there yet.

* Debug: It's really easy - you build in debug mode, press "`" if the debug windows didn't show, and then press on the brush symbol in the upper (your) right corner. Navigate through the bitmaps to check if there is a bitmap which is much larger than the game's window (tilemaps can cause that sometimes).

* hxscout: Check out the example I gave if you have any problems (don't forget to add the "telemetry" flag to your project.xml). This is really meant for you to double-check your code, as there are many many ways you could've caused it yourself (again, mostly related to your tilemap). A simple project or some code+an asset to demonstrate your problem would be helpful here.

* The Gamepad part sounds weird, I want to say a bug, but maybe your Gamepad is just not supported (what kind is it?). Maybe you can try updating the gamepad's values based on these: https://github.com/HaxeFlixel/flixel/tree/dev/flixel/input/gamepad/id. If all things fail, open an issue on Github (https://github.com/HaxeFlixel/flixel/tree/dev).

[Jordan]

Ok, so removing vsync made the frame rate rocket up back to 60. but I'm still having trouble with the gamepad.
It's giving the same results with both the xbox one and xbox 360 controllers. Both Rock Candy brand. The gamepad test works fine with HTML and Flash but when it's in windows or neko it just maps the face buttons to the dpad, it's super weird.

[SruloArt]

Gamepad stuff: I would suggest trying out the dev branch of Flixel (there's a all new code base especially for Gamepads, really amazing stuff by Lars Doucet), but that seems like a bit of work, so you should open a new issue over the HaxeFlixel/flixel repo, or just try asking Lars over Twitter, maybe he'll have an idea.

P.S if the gamepad is working on the html target is because you're using a backend called "openfl-bitfive" (via the include.xml in the Flixel repo on your machine). It's currently not supported by any official OpenFL html backend version. That's really not important to you, but hey, free information.