Stencyl 3.4.0 is now out. Get it now!

URGENT: Errors while building your game.

BaLaSa

  • Posts: 29
When I use Android platform to test my game, the error appears in the image and I post the logs here too. But when I use the flash platform (player), no error appears. What could be happening?

thatredallstar

  • Posts: 5
build.date=2017-02-14_00-03-17
build=9300
debug=false
ext.codeeditor.path=
ext.codeeditor=0
ext.imageeditor.path=
ext.imageeditor=0
ext.soundeditor=
ext.win8sdk.path=
ext.xcode.ignoreselect=false
ext.xcode.path=
extension.updates.notify=false
flash.player.cache=false
global.default.password=
global.default.user=
global.group=1
global.height=1020
global.iconified=true
global.locale=en
global.maximized=false
global.minimized=false
global.password=ee6b703ca864822d3fe2f529a29a090d5bc00113
global.runplatform=android
global.sf=true
global.time=2017-11-13 20:35:55
global.toolbar=true
global.training=false
global.user=thatredallstar
global.width=1024
ios.cache=false
java.path=/Library/Java/Home
lang.debug=false
logfile=/Users/stroxel15/stencylworks/logs/2017-11-14_14-47-54.log
logviewer.col.level=true
logviewer.col.source=true
logviewer.col.stacktrace=true
logviewer.col.time=false
logviewer.height=600
logviewer.maximized=false
logviewer.ontop=false
logviewer.width=800
net.timeout=8000
numbers.cache=false
once.android.device=true
once.cc.finish=false
once.cc.start=false
once.design=false
once.dm.legend=false
once.gcc=true
once.ios.device=true
once.linux64=true
once.reloaddoc=false
once.upsell.30=true
once.upsell.ios=true
once.upsell.pro=true
once.visualstudio=true
once.welcome=true
perf.effects=false
perf.tint=true
prefs.autosave=true
prefs.autoupdate=true
prefs.designmode.simplepalette=false
prefs.exportpopup=true
preview.browser=true
preview.debugdraw=false
preview.showfps=false
proxy.host=
proxy.password=
proxy.port=
proxy.username=
publish.build.type=0
publish.type=0
signin=true
talk.enabled=true
temp.path=/private/var/folders/6k/2k9d47_53zb8c7s_plc1_d1h0000gn/T/stencyl7174554757679316064
ui.import.resize=2
ui.import.scale=3x
ui.logs.autoshow=true
ui.tab.colored=false
ui.tab.layout=false
url.annotation=http://www.stencyl.com/help/
url.api=http://www.stencyl.com/developers/api/
url.base=http://www.stencyl.com/
url.faqs=http://www.stencyl.com/help/
url.lang=http://stencyl.net/language/
url.publish=http://www.stencyl.com/
url.stencylforge.static=http://static.stencyl.com/forge/
url.stencylforge=http://www.stencyl.com/forge/
url.update=http://www.stencyl.com/
url.wiki=http://www.stencyl.com/help/
version=3.4.0.beta4
welcome.show=true

thatredallstar

  • Posts: 5
these are my logs i have same problem

NickamonPoppytail

  • *
  • Posts: 629
Why are there two forum topics with the same question?

LenseOnLife

  • *
  • Posts: 121
Hi,

Ideally you should attach your zipped log output to allow people have a look at them.  The log that was attached by 'thatredallstar' is not the file that contains the more interesting information.  Usually the output from the build is where the error will be found and that is 'usually' the largest file.

Cheers,

Oliver

Mithheru

  • *
  • Posts: 19
I have found that stencyl can be very buggy if you don't use it exactly as it was intended.  Your blocks of code can get corrupted, yet the game often will still compile.  As a piece of advice, before you start each session of work, open the stencyl games folder from your desktop etc. and copy the folder containing all of your game to a backup folder and date it.  That way you never loose more than a session of work.  Always keep your old versions, don't be tempted to delete them until sometime after your project is completed

In particular here are a few things I strongly suggest you never do:

- When stencyl is saving, never try to open new actors etc. or open other things from the dashboard.  Stencyl's multitasking allows you to do this, but I have seen things get corrupted, even if you don't edit anything whilst saving (which stencyl also allows you to do!)

- Also when copying blocks between actors or scenes, I find stencyl is very buggy.  For me, if I copy code with multiple loops, stencyl usually crashes, and the blocks disappear.  Also when you reopen stencyl you often find many copies of parts of the code untidily left at the top of the events screen window, which you never created.
 They don't get incorporated into your code, but its generally an untidy mess (these can be deleted safely).

Never copy / drag blocks between scenes, actors containing local attributes.  If you do, be aware that even if your new scene, actor etc. has the same attributes the code may compile, but the attributes will not match up.  Therefore after dragging and dropping the code delete the old local attributes and put in the new ones (even if they have the same name, and look the same).  I guess this is why stencyl does not allow you to export blocks of code!  If they use local attributes, they only work in their original context.