That's what I mean.

Sure, why not?

Yes, it's stableish. Whatever is on the master branch is usually the most stable thing there is.

Menus should never be included, so that's a bug in Kinc. Please send a pull request.

Really have a hard time to understand what you're saying but the reason you don't have any graphics is likely because you didn't set a colour.

Ah, sorry, I understand the problem now. Changing the window is not supported in the HTML5 debugger. Should work though if you compile a Windows build.

Sorry but I'm not sure what you're saying. Am I correct that you can now compile and run Kha applications but can't change window properties? If so, can you upload a sample project so I can have a look?

Hi, I'll need some more details here. Let's forget about video 4 for a moment because I don't know what that is (probably a very old video be Lewis?) and detail all initial steps.
The problem probably has to do with the weird path (C:\Usersmalre...) which somehow got the dir delimiters stripped out. I've seen a report like that before once but I don't know how it can happen.

It uses Metal directly. MoltenVK and Kha both use SPIRV-Cross though (and originally MoltenVK actually used Kha's previous shader compiler before we both moved everything to SPIRV-Cross).

Just try again (you can see the same error happening in the Actions tab, it was fixed shortly after).

Thanks!

PS: I stole Null Problemo myself from the German version of Alf.

Null Problemo. Any insights on what went wrong (for example why that error message in VS showed up)? Would help me with future problems.

Hm, so does that mean compute is now also working for you?

Sorry but I can not reproduce that and have no idea how you do that.

Can you run Krom (from https://github.com/Kode/Krom) in Visual Studio? You'll just have to put in the start parameters in the Visual Studio properties.

As I said before, try to run it from the command line. Does it work now when compiling for Windows? Because if it doesn't, the Krom crash is expected.

Fixed that Krom compile error - that not showing up before means you were using an old version of Kha.

When it worked in an older version the fix is probably simple, so... gimme those values.

Didn't ask for a value at that memory location, did ask for the values in the relevant variables. Also what happens when you run Krom from the command line?

"Display file not found" is just a code completion error and typically happens when you open code for backend X while backend Y is selected, it's not a Krom error. Do you see something in another output panel? Did you update Krom to the latest version? And can you see a 0xFFFFFFFFFFFFFFFF value in the parameters at line 277?