Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - lorenk

Pages: 1
Resolved Questions / Re: Stuck on "Sending to Device" with a Nexus 7
« on: March 25, 2013, 06:34:08 pm »
To get things temporarily working I did the following:

-Downloaded the latest Android SDK (
-Pulled aapt.exe, adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, and dx.jar out of the platform-tools folder and replaced the files in the platform-tools folder in Stencyl's directory. Not sure if you need to replace all of these files.
-Ran Stencyl and tested a game.
-Accepted the message on the Nexus to allow files from my computer.
-Restarted Stencyl (for some reason Stencyl went from "Sending to Device" to "Compiling" when I got the above message).
-After restart testing began working again.

Ask a Question / Re: can you anchor a background?
« on: March 24, 2013, 05:27:13 pm »
Are you trying to sync the background up to your main actor's movement, so there's some slight movement as you move through your scene?

Ask a Question / Re: Are people from stencyl in today?
« on: March 24, 2013, 05:18:10 pm »
I believe they usually respond to emails M-F. I assume you're waiting for access to download 3.0. If you haven't downloaded 2.1 yet, you could install it ( and begin learning the interface, then update once you get access.

Resolved Questions / Re: Stuck on "Sending to Device" with a Nexus 7
« on: March 24, 2013, 04:44:08 pm »
From running adb.exe devices, I receive the following:
* daemon started successfully *
List of devices attached
015d49069967f412 offline

I believe it detects a connection but it's not initializing when the game is published. I was looking at the following site and this info stood out to me.

When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.

The device was working prior to 4.2.2 being installed. I ran adb.exe version, and it looks like the version Stencyl installs is 1.0.26. Stencyl would need to install 1.0.31 for things to work with Android devices running 4.2.2 I believe.

Resolved Questions / ANDROID - Stuck on "Sending to Device"
« on: March 24, 2013, 07:14:01 am »
I read through the post about testing on Android (,13723.0.html) and followed the available directions while setting things up to test. Things were working great for a couple hours, then things got stuck on the "Sending to Device" phase of testing. I'm using a Nexus 7 running Android 4.2.2

These are the steps I've taken to try and address the problem:
-Unplugged device just in case the computer fell asleep
-Turned Developer Options off & on
-Turned USB Debugging off and on
-Uninstalled and re-installed the USB drivers from ASUS (did this twice and restarted after each time)
-Tried publishing two separate Stencyl games that previously were sent to the device without issue
-Used a file manager on the Nexus to uninstall the apps that were hanging around from the earlier tests.

I can publish to an .apk file and transfer it manually to the Nexus without issue.

Any recommendations on how to address this issue?

Archives / Controller Support
« on: March 21, 2013, 03:16:53 pm »
Built in controller support would be wonderful. There's Joy2Key, but it would be nice if the end user didn't have to jump through any hoops to play a game with a controller.

Teaching with Stencyl / Re: Education Plans for Stencyl 3.0
« on: March 18, 2013, 02:59:41 pm »
When I learned about Stencyl I immediately thought of the kids in my dad's class who could benefit from having the software available to ease them into learning how to program. Looking forward to seeing the mini-site.

Old Bugs (1.x/2.x) / Re: Image import changes color for actor
« on: March 16, 2013, 05:29:18 pm »
As an experiment I applied a background color to the transparent portion of the .png files that were having this problem on import. Doing this prevented Stencyl from adjusting the color/brightness/contrast. I don't see any rhyme or reason to this still, as other .png files that have a transparent background import fine.

Old Bugs (1.x/2.x) / Image import changes color for actor
« on: March 14, 2013, 07:52:21 pm »
I am seeing what appears to be a bug that was fixed about a year ago. Here's a link to a previous post detailing the bug from 2011:

I'm currently using version 2.2.0 (b502) on a Windows Vista system with SP1. I've attached an image showing how the brightness and saturation change on importing the image into Stencyl. The tile in the left portion of the image is prior to importing, and the tile to the right is after importing. Closing the software and re-importing doesn't fix the problem. This is not a consistent issue as some tiles I import with the same color palette look fine after import. 

I've also attached a log in case it would help.

Thanks Hectate! I did have a Cannot Exit Screen behavior associated with the actor. Removing the behavior did fix this issue. Thanks for the explanation as to why this behavior could be causing the problem to begin with.

Not sure if this would help diagnosing the issue, but if the actor is set to appear on a platform at the top of the scene, the character will spawn in the correct location. If the character is placed anywhere beneath the top 18x18 tile quadrant of in the scene, this issue appears.

The scene has gravity enabled (vertical set to 85). The actor type is normal, and Affected by Gravity is set to yes. In the advanced settings, I have not disabled physics for the actor. The actor's movement is managed by the standard Jump and Run Movement behavior.

I want the actor to be affected by gravity. The player has to navigate up a vertical shaft and needs to be able to fall. The problem here is that upon scene entry the actor is randomly spawned in an area of the scene that's incorrect (not on her starting platform, thus the falling). In the screenshot I attached I pointed out the block the actor was set to appear at in the scene.

I've been working on a game that uses tall scenes in which the character is supposed to start at the bottom of the scene. I've placed the actor at the bottom and enabled the standard Camera Follow behavior. Upon initial scene entry the actor is close to the bottom of the scene, but not in the correct position. The actor then falls down the screen. I've attached a screenshot to illustrate what's going on.

Scene dimension: 18x96 tiles (32x32 tile size)
Screen size: 18x18 tiles

Pages: 1