If you notice a reduced framerate and you can't figure it out, try opening your debugger's "Breakpoints" tab and removing them all. I've been hunting (for days) where the slowdown was occurring, profiling the engine and all of it's parts to no avail. Finally, when I couldn't see my current breakpoints (valid ones) anymore, I removed them all... lo and behold! The framerate issue disappeared.
Apparently Aptana still transmits all of the breakpoints, but just because they aren't valid doesn't mean that Firebug isn't checking them. <sigh> What a waste of my time - but a valuable lesson learned!
Hey Brett,
ReplyDeleteWhat Aptana version do you use?
I use Aptana Studio 3 beta but found no real advantages over a text editor.
Is it possible to preview the project in aptana? that would developing a lot smoother.
I use Aptana Studio 2. It links directly to Firefox 3.6.x via Firebug 1.5 so you can step through a running project. It doesn't do code completion because all of the classes are "hidden" in anonymous functions, but you can still do better debugging than using Firebug alone.
ReplyDeleteDo you use Aptana for building the Render Engine only, or can you use Aptana for building web projects and games?
ReplyDeleteIf the latter is true, how do you enable code completion and error checking for a game you are building using the Render Engine in Aptana?
Thanks,
Alex K