Don't know about any iOS audio issues. Please create an issue on GitHub and provide all the details.

I'd rather make that wav work. Please create an issue on GitHub.

khamake requires wav files so the files can be converted to whatever works best on the target system. If you want to use lossy compression set the quality parameter for your audio assets ala https://github.com/Kha-Samples/BlocksFromHeaven/blob/master/khafile.js

Yes, sadly Git just ignores submodules unless you explicitly tell it to look after them.

That's not possible. But it's also not necessary, see https://github.com/Kode/khamake/blob/master/khamake.js#L2
Can you check why that line doesn't work as expected on your system? Also, what is that system?

We can't help you here. Haxe is just a programming language, it's not a gui framework. Also, this forum is about Kha and stuff which is explicitly not designed for application gui development. Not sure how you ended up here but you will have to search elsewhere.

Aha, this is something special, a ttf font which tries to look pixely. Even Windows very own font viewer makes it look blurry in smaller sizes (though it does profit a lot from sub-pixel anti-aliasing). Better use some good old bitmap font rendering for that, putting this in a ttf renderer is just overcomplicating things.

PS: For everybody else's reference, Kode Garden version is at http://kodegarden.org/#569c262d28c43acd14fc23231fba657f1251b256

Should behave the same, GitHub issue please.

Hm? Nope.

kravur isn't currently used but Kha does basically the same thing at runtime. Some blurriness is to be expected when rendering ttf files and Kha doesn't do super-high-end font-rendering (no subpixel antialiasing for example). Turning off antialiasing is also generally a very bad idea with ttf fonts, you will likely have actual holes in your fonts. When you want super-shard pixely fonts especially at very small sizes you are better off using actual bitmap fonts.
All that said, when asking about font sharpness please provide a sample project. Most people who complained about blurry fonts actually messed up with render targets and texture filtering while I was babbling along about font rendering details.

Super nice, thank you!

We don't have that. Not sure we should have that but please feel free to create a GitHub issue about it.

Hey, look at that: https://github.com/Kode/Kha/pull/772
Please give it a try, I just merged that.

I think we should do something about it. Can you create a GitHub issue, please?

There's HoloLens support in Kore (which isn't yet exposed in Kha) but so far haven't seen a need for providing ARCore/Kit things as I thought that's mainly just an interface for some image feature recognition lib. But maybe I'm wrong, haven't looked into it.

No, it can not look the same if it's drawn at fractions. Make sure you set imageScaleQuality to high but that's all you can do. Round the positions to full pixels if you want to reproduce the original pixels exactly.

I think Kha is mighty strong. But I'm not an expert on the matter, I'll ask the HaxeHulk for his opinion. Meanwhile have a look at http://armory3d.org which is based on Kha and I think already surpasses all of your examples.

Did the aspect ratio change? The Scaler class has a mouse-coord conversion function to help you out.

That's not true: https://github.com/Kode/Kha/blob/master/Backends/Kore/kha/Image.hx#L296
But you have to make sure the image is readable. By default Kha holds image data only in GPU mem (as you have noticed that's still a todo for the HTML5 target) - project.addAssets('Assets/someimage.png', {readable: true}) does the job for images coming from files.

Fix in progress (turns out it's a bit complicated)...