Hey guannstar I just now noticed this thread. Sorry I didn't reply sooner!

Ultimately, it looks like you got all the help you possibly could have asked for haha. I don't think I could add anything that the other lovely people in this thread have posted.

Cheers.

I can't help but notice that there's no mention of the need to URLEncode user-entered data in the tutorial (https://www.scirra.com/tutorials/4897/sending-an-email-from-construct2/revisions).

I've been having trouble with POST, so I wonder if that's something I need to be exploring?

Thank you, my friend! I'll give this a try tonight.

Got my game published today. Thanks Scirra!

Thanks, eli0s!

And thank you kossbglobal for your input. I think I may have found a way to counter the errors I'm having. I'm experimenting with only having physics enabled for parts of the "line" when it is overlapping with the ball object. So far I've dropped my CPU usage by a steady 10-15%. I'll see if I can't get it to be more efficient yet.

Hey folks, how's it going?

So I've been working on a little 2D physics-based puzzle game recently, and I've gotten it to work on mobile! Sadly, once I started testing it on my Galaxy S3, I realized how slow and clunky it was. The game works fine on my desktop, but the limited processing power of mobile devices seems to be rendering my game unplayable.

I've been trying to debug the past couple hours, and the only thing I can come up with is I'm generating too many physics objects. However, I read in Ashley's tutorial that;

"Note that objects which have come completely to a stop, and are not moving or rotating at all, are "put to sleep" by the simulation. Then, they don't need processing any more. If the object is hit by another one it "wakes up" and starts using processing again. However, if the object is even moving in the slightest, it won't be put to sleep."

I think that my physics objects are "put to sleep", but I'd like to ask you folks to be sure. Below I've provided a screencap of the game, a link to the capx, and a link to the mobile version of the game.

Capx:https://dl.dropboxusercontent.com/u/248465061/Legacy%20Ball%20Test/Legacy_Ball_HelpPLS.capx

Mobile APK: dl.dropboxusercontent.com/u/248 ... debug%20(1).apk

If you'd like, feel free to take a look at these. Are my physics objects not being "put to sleep" properly, or is there something else in my code that's slowing the game down on mobile?

If you have any ideas as to what might be causing that big discrepancy, please let me know. And if it involves reworking the game's core mechanic, um, please let me know if you have any ideas as to how else I could code that properly, haha.

Thanks so much for your time!

My friend, you are a lifesaver! Thank you so much!

Hey folks, so I'm making a prototype for a little 2D physics based puzzle game. One of the mechanics I have in place is the ability to draw lines in an MS Paint-esque fashion. However, I'm hitting some problems.

The lines I'm drawing are all ending up pretty ugly. Jagged edges and whatnot. And when I move the mouse too fast, the lines sometimes refrain from connecting entirely.

I've looked around the forums for a few different ways to fix this, but nothing's helped so far. I tried using the Paster plugin, but admittedly, I am at a complete loss as how to even use that plugin. Any idea how to smooth out those lines and make them look nice?

Here's the capx. Thanks so much for any suggestions.

dropbox.com/s/bc559kp709zeqgw/DrawingHalpPls.capx

Duly noted, thank you all so much!

So I finished my second game recently, and it's done decently well. Product life cycle is about over. However, I was thinking about perhaps sending my game to some YouTubers to see if they might want to play through it for a video. I was looking for information about this topic but couldn't find much here.

Know any YouTubers who tend to play small, browser-based games who might be interested? Is this even standard practice?