Ashley's Forum Posts

  • I've added some on suspend/resume triggers to my todo list, but it should be fixed from the plugin really.

  • I'm not sure. Maybe try removing all third party plugins and see if it goes away.

  • It might be a browser bug - it should certainly be possible to tile power-of-two textures seamlessly at any zoom level. I'll take a look and see if it's a browser issue.

    For now the only way to guarantee seamless rendering is to turn WebGL on and set sampling to Point. It seems to be an issue with linear sampling only.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • If you apply forces or impulses anywhere on the object other than the center of mass, you'll set the object rotating (as per the laws of physics).

    The center of mass is not usually the middle of the object for any object which does not have a rectangular collision mask. Try applying the impluse/force at CenterOfMassX/Y.

  • If you use PhoneGap Build, it always builds with the latest version.

  • Pode - this might help - PDF.js:

    https://github.com/mozilla/pdf.js

    A complete PDF loader implemented in pure Javascript. It's designed for rendering PDFs, but you might be able to get it just to do a text search without displaying anything.

    Pretty crazy project, it's also gonna be pretty hefty (something like 1mb of javascript!)

  • If one particularly interests you I'm sure you could contact the owner and explain your predicament and they'll be able to send it over.

    A slightly more expensive way which might work is like Mipey's idea: rent the cheapest US server you can find. They should give you a Remote Desktop account to log in to. Now you can surf the internet from the US server, and unless your specific server is blocked you've got the internet as it is seen from the US (most countries have *some* form of blocking at the ISP level, but DropBox is definitely allowed!)

    Disclaimer: I don't know Chinese law and if this is the type of thing that could get you in to trouble, I cannot officially recommend that you do it. :P

  • I don't think such a condition would ever run, because events stop running when the app is suspended! What were you planning to use it for? Is there a trigger or something that runs while suspended?

  • This is on the todo list!

  • Most people don't have server-side scripting though, or don't know how to set it up. So downloading files is still a better option IMO.

  • Perhaps I should have suggested a feature filtering the code that affects a single selected object rather than a whole layer.

    Try just typing the name of an object in to the 'Event search' box on the ribbon.

  • The bug in Chrome screws up timers so badly even if you use dt the game runs at the wrong speed or changes speed. It's a pretty annoying bug.

  • Hmm, you're right, I'll see if I can get this sorted for the next build.

  • Sorry, by "tell-tale" I mean a giveaway, as in the diagonal line indicates a driver bug. Seams along the edges of the tiles are one thing, but diagonal lines inside a tile usually means the graphics driver is old and crappy and can't draw a 2D image without screwing up the contents :P (I don't see any diagonal lines on my machine)

    Lines along the edges of tiles are a different issue though. I'm not sure why they are there. Is WebGL on? Is it any different with WebGL off?

  • As far as I can tell there's no problem here, it's just your events are wrong.

    If you say "Spawn bullet on layer 0" (providing a number to identify the layer), then add a new layer which you set to the bottom, that is now layer 0 (see the numbers to the right of the layers bar, those are the layer indices). If you give layer number 0 a different name, like "Layer 2", you will just confuse yourself - it's layer number 0!

    Also note carefully each layer's transparent setting - you're putting a transparent layer beneath a non-transparent layer, which means you'll never be able to see the bottom layer.

    Refer to layers by name instead of number and you'll always get the same layer no matter where you move it.

    If you're still sure there's a bug, try making a new .capx from scratch. As it is it just looks like your project is set up wrong.