Help!

• M

  FlxTypeText: resetText() not working
  • Muridae

  1
  1
  Posts
  40
  Views

  No one has replied

• 

  [SOLVED] Questions about gamepad, one at a time...
  shield tv gamepad ouya • • Txori

  6
  6
  Posts
  2873
  Views

  

  All right! After hours of testing, switching numbers, compiling Android builds and some good guessing, I managed to repair the flixel/input/gamepad/id/OUYAID.hx
  And it turns out that it was impossible for that file to work from the very start (May 21, 2015).

  Here's the current code:

  class OUYAID { public static inline var O:Int = 0; public static inline var U:Int = 3; public static inline var Y:Int = 4; public static inline var A:Int = 1; public static inline var LB:Int = 6; public static inline var RB:Int = 7; public static inline var LEFT_STICK_CLICK:Int = 10; public static inline var RIGHT_STICK_CLICK:Int = 11; public static inline var HOME:Int = 2; public static inline var LEFT_TRIGGER:Int = 8; public static inline var RIGHT_TRIGGER:Int = 9; // "fake" IDs, we manually watch for hat axis changes and then send events using these otherwise unused joystick button codes public static inline var DPAD_LEFT:Int = 13; public static inline var DPAD_RIGHT:Int = 14; public static inline var DPAD_DOWN:Int = 15; public static inline var DPAD_UP:Int = 16; // If TRIGGER axis returns value > 0 then LT is being pressed, and if it's < 0 then RT is being pressed public static var LEFT_ANALOG_STICK(default, null) = new FlxGamepadAnalogStick(0, 1, { up: 23, down: 24, left: 25, right: 26 }); public static var RIGHT_ANALOG_STICK(default, null) = new FlxGamepadAnalogStick(11, 14, { up: 27, down: 28, left: 29, right: 30 }); public static inline var LEFT_TRIGGER_ANALOG:Int = 17; public static inline var RIGHT_TRIGGER_ANALOG:Int = 18; }

  In fact, those numbers are coming from openfl-ouya/tv/ouya/console/api/OuyaController.hx

  static inline public var BUTTON_O:Int = 0; // 96; static inline public var BUTTON_U:Int = 3; // 99; static inline public var BUTTON_Y:Int = 4; // 100; static inline public var BUTTON_A:Int = 1; // 97; static inline public var BUTTON_L1:Int = 6; // 102; static inline public var BUTTON_L2:Int = 8; // 104; static inline public var BUTTON_R1:Int = 7; // 103; static inline public var BUTTON_R2:Int = 9; // 105; static inline public var BUTTON_MENU:Int = 0x01000012; // 82; static inline public var AXIS_LS_X:Int = 0; static inline public var AXIS_LS_Y:Int = 1; static inline public var AXIS_RS_X:Int = 11; static inline public var AXIS_RS_Y:Int = 14; static inline public var AXIS_L2:Int = 17; static inline public var AXIS_R2:Int = 18; static inline public var BUTTON_DPAD_UP:Int = 19; static inline public var BUTTON_DPAD_RIGHT:Int = 22; static inline public var BUTTON_DPAD_DOWN:Int = 20; static inline public var BUTTON_DPAD_LEFT:Int = 21; static inline public var BUTTON_R3:Int = 11; // 107; static inline public var BUTTON_L3:Int = 10; // 106;

  And it is entirely possible that it was never tested back in 2015. After a brief search through the forum, maybe I was the only one making games for the OUYA using HaxeFlixel? Anyway, here are the correct numbers:

  class OUYAID { public static inline var O:Int = 6; public static inline var U:Int = 8; public static inline var Y:Int = 9; public static inline var A:Int = 7; public static inline var LB:Int = 15; public static inline var RB:Int = 16; public static inline var LEFT_STICK_CLICK:Int = 13; public static inline var RIGHT_STICK_CLICK:Int = 14; public static inline var HOME:Int = 0x01000012; // Not sure if press HOME is taken in account on OUYA public static inline var LEFT_TRIGGER:Int = 4; public static inline var RIGHT_TRIGGER:Int = 5; // "fake" IDs, we manually watch for hat axis changes and then send events using these otherwise unused joystick button codes public static inline var DPAD_LEFT:Int = 19; public static inline var DPAD_RIGHT:Int = 20; public static inline var DPAD_DOWN:Int = 18; public static inline var DPAD_UP:Int = 17; // If TRIGGER axis returns value > 0 then LT is being pressed, and if it's < 0 then RT is being pressed public static var LEFT_ANALOG_STICK(default, null) = new FlxGamepadAnalogStick(0, 1, { up: 23, down: 24, left: 25, right: 26 }); public static var RIGHT_ANALOG_STICK(default, null) = new FlxGamepadAnalogStick(2, 3, { up: 27, down: 28, left: 29, right: 30 }); }

  By the way, I removed those two lines because those vars are never used elsewhere:
  public static inline var LEFT_TRIGGER_ANALOG:Int = 17;
  public static inline var RIGHT_TRIGGER_ANALOG:Int = 18;

  One last note, I didn't manage to find the correct number for HOME. I believe this button does not work like the others on the OUYA and it needs the official OUYA lib or something.

  After four years, I'll finally be able to update my old game on this dead system. Yeah!

• 

  Detecting Android Device
  • Txori

  1
  1
  Posts
  33
  Views

  No one has replied

• C

  Black screen/window on RPi
  • cbs6f

  1
  1
  Posts
  24
  Views

  No one has replied

• 

  [SOLVED] Display japanese font on Android target
  • Txori

  4
  4
  Posts
  233
  Views

  

  Just so you know, the problem comes from OpenFL file: openfl/src/openfl/_internal/text/TextLayout.hx

  Reverting to b151041 resolves the problem on Android, but apparently, it breaks the Windows c++ build.

• S

  Query the world or QuadTree
  • stetso

  1
  1
  Posts
  53
  Views

  No one has replied

• C

  can't use flixel command
  • chrpsh

  6
  6
  Posts
  1124
  Views

  

  @commando
  $ haxelib install flixel
  You already have flixel version 4.6.3 installed

  $ flixel
  bash: flixel: command not found

  $ haxelib run flixel-tools setup

  Do you want to setup the flixel command alias? [y/n]?
  y

  Choose your default IDE:

  [0] Sublime Text
  [1] FlashDevelop
  [2] IntelliJ IDEA
  [3] Visual Studio Code
  [4] None

  3

  Do you want to automatically open the created templates and demos with Visual Studio Code? [y/n]?
  y

  Your current settings:

  Default Editor : Visual Studio Code
  Auto open with IDE : true

  flixel-tools setup completed.
  Try the 'flixel' command to test it! :)

  $ flixel
  bash: flixel: command not found

• F

  FlxTween crashes game
  • fried

  3
  3
  Posts
  108
  Views

  F

  @txori said in FlxTween crashes game:

  FlxTween.tween(scale, { "x": 0.5 }, 2, { ease:FlxEase.elasticInOut });

  Thank you @Txori. It works if I use the syntax provided.

• P

  Space key works for input on Neko build but not HTML5 build [SOLVED]
  • Paul

  1
  1
  Posts
  149
  Views

  No one has replied

• 

  Window closes when using FlxShapeCircle
  • tree786

  3
  3
  Posts
  340
  Views

  S

  @vasco Thanks for your answer. It helps a lot

• A

  No sound playing
  • axgs

  4
  4
  Posts
  2426
  Views

  

  @starry-abyss This was my issue, didn't know pressing 0 by accident could cause so much headache, thanks for your help.

• 

  Windows 10 ERROR: There is no asset library with an ID of "default"
  • AlexRamallo

  4
  4
  Posts
  678
  Views

  R

  @dean Thanks for the link!

• K

  Cannot Build for Windows - VS2017 Community Edition
  • klias

  4
  4
  Posts
  441
  Views

  E

  Thanks, very helpful

• 

  Android performance with Haxeflixel 4.4.0
  • rafadelahoz

  19
  19
  Posts
  5645
  Views

  A

  Same issue with the latest versions: haxelib list

• G

  Real low resolution
  • GiG

  2
  2
  Posts
  186
  Views

  

  There is a demo on the website that possibly demonstrates the behaviour you are looking for. Hope it helps

• M

  The name of the game has the character of the android logo
  • mongjihyo

  1
  1
  Posts
  99
  Views

  No one has replied

• G

  Rotating level
  • GiG

  5
  5
  Posts
  2105
  Views

  G

  I had an idea while at the toilette, a classic! Just a guess: do I have to use an additional camera to trim a rectangle on the current rotating camera (that I will set as a bigger square)? I think it could be the correct way to make a topdown game with a rotating camera/level, unless Flixel already embeds a method to do it.

• 

  When 2D camera moves, nothing out of the origin is rendered.
  • TheJSHuA

  2
  2
  Posts
  187
  Views

  

  resolved! was using camera.x instead of camera.scroll.x, a small mistake. just leaving this here incase anyone else needs it.

• G

  Rotating level by rotating camera
  • GiG

  1
  1
  Posts
  109
  Views

  No one has replied

• 

  FlxG.touches and multiple camera
  • wilfryed

  1
  1
  Posts
  215
  Views

  No one has replied