brandonarmour's Forum Posts

• • brandonarmour
  • 
  • • Joined 13 Sep, 2012
    • 
    • 1 topics • 3 posts
  • 1

  • 28 Aug, 2014
  • Quote

  Ashley - My apologies. It seemed like the error I was having was related to this thread but after clearing my browser and hard drive temporary files the problem ceased to occur.

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • brandonarmour
  • 
  • • Joined 13 Sep, 2012
    • 
    • 1 topics • 3 posts
  • 1

  • 26 Aug, 2014
  • Quote

  I've also been having issues since the last update...

  A small project I just started has been inexplicably not able to preview ....

  I'm getting the following error whenever I preview from any browser.

  (see attachment)

  This was working perfectly fine until I updated...

  Not really sure whats going on as I loaded some of C2s templates and they preview just fine...

• • brandonarmour
  • 
  • • Joined 13 Sep, 2012
    • 
    • 1 topics • 3 posts
  • 1

  • 4 Feb, 2013
  • Quote

  Link to .capx file (required!):

  dl.dropbox.com/u/56514647/TouchBehaviorBug.capx

  Steps to reproduce:

  1. Export to AppMobi

  2. Test on a mobile device (optional)

  3. Click/touch screen and drag finger all the way off the screen (Up, down, left, or right) and let go.

  4. The green square will follow your finger/mouse and stop at the edge of screen.

  Observed result:

  The next time you try to interact with the screen, the touch position and green square remain stuck at whatever edge of the screen you left off at no matter were you now click/touch; observed by the green square remaining still (Mainly happens if you slide off the top of the screen).

  Expected result:

  The green square should ALWAYS follow the mouse/finger when clicking/touching anywhere on the screen.

  Browsers affected:

  Direct Canvas YES

  Seems to work fine from any computer browser.

  Operating system & service pack:

  Windows 7 Ultimate SP1

  Construct 2 version:

  R 114

  This bug only seems to happen once exported with direct canvas and tested on the XDK or on a mobile device.

  I'm making my first mobile game and its going great besides this random occurrence...

  Any thoughts would be much appreciated.

  Thanks!