Not sure if this is related, but... on my Samsung Galaxy S3, my Construct 2 app worked fine in Firefox but didn't play sound in Chrome. It did work in Chrome on an iPad. (Very likely a bug in Chrome on Android.) I updated Chrome on my Samsung, then the sound worked.

Np, Sargas.

Uploading a zip of two files. The "mono" version fails to import, but the "stereo" one succeeds. Construct recognizes both as 16-bit, 22kHz files.

I realize the encoding is done by an external library. If the library chokes on certain kinds of files though, it would be really nice to document the actual specifications. The mono file I uploaded seems to fit what you described, encoded 16-bit PCM with audio rate > 8 and < 96, as far as I can tell. Also, a better error message would be nice. As it was, I had a perfectly valid WAV file that appeared to fit the specification and failed to import with a mysterious message---not a good UX.

As I said, the problem files that failed to import were PCM (8-bit OR 16-bit). The problem seemed to occur with mono-track sound.

I'm a software engineer and long-time MMF user. I've recently started using Construct 2 and like it a lot.

As I understand it, the image editor is a "work in progress" and maybe not a priority for development at the moment. I'd just like to add my 2 cents: it could really use a few more basic tools to make game prototyping (and development) even better.

Ellipse tool---I literally spent half an hour looking for this and Googling because I was so surprised it was missing. I feel like it should be a very high priority to implement.

Non-filled rectangle and ellipse

Text (nice to have)

Polygons (nice to have, but you can simulate with lines and fill tool)

I strongly suggest making an ellipse tool a priority, followed by non-filled rectangle and ellipse, even if you don't have time for other work on the image editor. It's kind of a "first impression" user experience, for anyone using the image editor for the first time. (Btw, I know about the brush tool workaround for creating a filled circle. And I realize I can use any other image editor in existence.)

If you really don't want to invest in the image editor, a more permanent solution would be to have some simple integration with an external tool---automatically open a configured external image tool from the animation editor.

Problem Description

The documentation (/manual/52/import-audio) and the instructions for importing audio say nothing about limitations on importing mono WAV audio. When I select a mono WAV file (8-bit OR 16-bit, signed PCM), to import, at first it has the green checkmark. Then when I click "import", it changes to a yellow warning and says "Converted to AAC, but failed to convert to OGG." When I convert the same file to stereo using Audacity, it imports fine.

Obviously it would be nice if Construct didn't choke on a mono wav file, but as a workaround it should at least give a more helpful error message and the instructions and documentation should be updated.

Attach a Capx

N/A, reproducible on a blank project

Description of Capx

N/A

Steps to Reproduce Bug

• Open the "import audio" dialog
• Select a 16-bit or 8-bit mono-format WAV file

Observed Result

Mysterious error message

Expected Result

Successful import, or more helpful error message and updated instructions

Affected Browsers

None

Operating System and Service Pack

Win 7 (64-bit) SP 1

Construct 2 Version ID

163 (64-bit)