Help!

• 

  Access variable value from Nape body I collided with
  nape callback haxeflixel collision interaction • • Gioele-Bencivenga

  4
  4
  Posts
  33
  Views

  

  This problem was also solved thanks to a fantastic correction by @codescapade on the Discord server.
  In my player class I was setting the userData by doing

  // adding CBODY CBODYPlayer = new CbType(); body.cbTypes.add(CBODYPlayer); CBODYPlayer.userData.data = this; trace("Player's CBODY created");

  when instead I should've been doing

  // adding CBODY CBODYPlayer = new CbType(); body.cbTypes.add(CBODYPlayer); body.userData.data = this; trace("Player's CBODY created");

  Now everything works as expected and I'm able to access any field of the 2 objects colliding.

• C

  Changing size in Project.xml causes program to lag in Flash
  • CharType

  1
  1
  Posts
  41
  Views

  No one has replied

• 

  This topic is deleted!
  • TheJSHuA

  1
  1
  Posts
  2
  Views

  No one has replied

• D

  pixelPerfectRender is not perfect at all
  • droqen

  2
  2
  Posts
  285
  Views

  D

• 

  Pasting into input text in HTML5 target
  • gamahachaa

  2
  2
  Posts
  256
  Views

  

  Ok after loosing hairs with openfl or lime api and being unsuccesfull.
  Here is a pure html5 workaround (for some that would stumble upon this post)

  // some were in your state initialisation var myInput = new FlxUIInputText(); #if js //import js.Browser; //import js.html.Clipboard; //import js.html.ClipboardEvent; Browser.document.addEventListener("copy", onCopy); Browser.document.addEventListener("paste", onPaste); #elseif flash //Use Clipboard.generalClipboard #end add( myInput );

  then the listeners

  function onPaste(e: ClipboardEvent):Void { myInput.text = e.clipboardData.getData("text/plain"); } function onCopy(e: ClipboardEvent):Void { Browser.navigator.clipboard.writeText(myInput.text); }
• P

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

  2
  2
  Posts
  462
  Views

  

  I know this is old, but I was wrestling with this issue for months. This solved it, finally.

  However I'm not sure what makes this line of code necessary, that is whether it was an internal OpenFL issue or if it was an issue with my code.

• H

  Unable to create new haxeflixel project
  flixel • • Hyperion

  1
  1
  Posts
  129
  Views

  No one has replied

• 

  Understanding layouting with advanced-layout
  • niceneasy

  2
  2
  Posts
  295
  Views

  

  After some debugging I have found that advanced-layout uses a default scale setting where it sets the reference screen size to 800x600 no matter what window size you set for your game. The solution is to create a new instance of Layout and Scale with proper width and height, then set the layout to our custom one. It didn't take me very long time to figure that out but I wish there was a thing about it in advanced-layout documentation so I could spend that time more productively.

• X

  Having issues with Hashlink
  • XShell

  3
  3
  Posts
  406
  Views

  X

  Ah, thanks. I thought I read somewhere that it was supported. I'll try the "lime test" task and see how I get on with that. Cheers!

• 

  Hollow circles with nape?
  • sftwninja

  2
  2
  Posts
  234
  Views

  

  I figured out a way to make it happen that works pretty nicely. Hopefully this little code chunk helps someone else out. It composes two polygons with a number of segments, flips the second array to make it easy to connect the two vertex lists together, creates polygons from the simplifications, then uses nape's GeomPoly to simplify the solids into simpler shapes. Then we add it to the NapeSprite.

  public function createRingBody(radius:Float = 16):Void { var segments = 200; if (body != null) { destroyPhysObjects(); } centerOffsets(false); setBody(new Body(BodyType.STATIC, Vec2.weak(x, y))); // Create a poly object var p1 = Polygon.regular(radius, radius+30, segments); var p2 = Polygon.regular(radius-10, radius-10+30, segments); p2.reverse(); var gPoly = new GeomPoly(); for (p in p1) { gPoly.push(p); } gPoly.push(p1[0]); gPoly.push(p2[p2.length-1]); for (p in p2) { gPoly.push(p); } gPoly.triangularDecomposition().foreach(function (gpoly) { var verts = new Array<Vec2>(); var it = gpoly.iterator(); while (it.hasNext()) { verts.push(it.next()); } body.shapes.add(new Polygon(verts)); }); setBodyMaterial(); }
• X

  Uncaught exception - Invalid field access : objects
  lime linux error • • xNPxGames

  4
  4
  Posts
  421
  Views

  

  @xnpxgames

  That tutorial causes confusion because it includes two ways to create the map. If you're using FlxOgmoLoader map then you don't need that loop.

  From tutorial section 6:

  TiledMap does not have a built-in loadEntities() function, so for that you'll need to change this to:

  for (e in tmpMap.objects) { placeEntities(e.name, e.xmlData.x); }

  But unless you're using FlxTileMap to create the map you dont need that.
  If you're using FlxOgmoLoader , make sure to ignore the change this to ... for Tiled parts.

  There's a link to the completed project on the Conclusion page of the tutorial where you can check the code.

• N

  Android Application Crashes
  • NullStack

  3
  3
  Posts
  342
  Views

  N

  these is the other components:

• 

  Skipping splash screen crashes the game during startup.
  • pietmichal

  2
  2
  Posts
  310
  Views

  

  I've managed to fix it by running my PowerShell and VSCode as administrator.

• V

  How to make executable on Linux
  • Vanbandama

  1
  1
  Posts
  171
  Views

  No one has replied

• 

  FlxSave File Location
  • 3dmasons

  6
  6
  Posts
  577
  Views

  

  Yep, for HTML5, and it indeed is saved as a cookie. Thanks for your help.

• 

  FlxSlider Integer Value Label
  • 3dmasons

  5
  5
  Posts
  469
  Views

  

  @dean Yep, that worked. It claims that decimals is default to 0, but it definitely is not. Thanks!

• M

  FlxTypeText: resetText() not working
  • Muridae

  1
  1
  Posts
  245
  Views

  No one has replied

• 

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

  6
  6
  Posts
  3674
  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
  212
  Views

  No one has replied

• C

  Black screen/window on RPi
  • cbs6f

  1
  1
  Posts
  194
  Views

  No one has replied