Recent Posts

That's fantastic!
Even more fantastic because you shared source code - thank you!
Note here: it's good example how to use your collision library https://github.com/FuzzyWuzzie/headbutt
It's collision detection library only, there are no collision response, are there?

posted in Kha read more

@Robert said:

plus another one on my todo list (heaps).

There was some good shaking hands session at last Haxe Summit :)
Can't wait to see heaps on top of Kha. Will this support hl target?

posted in Kha read more

That's convenient! Thanks!
Did you try to create such templates for building-running-debugging krom target?

posted in Kha read more

Great!
I wonder if this library implements gltf 2.0 specs?

posted in Kha read more

Hey, Robert!
I'm trying to build KodeStudio from sources and failed to clone it's repository:
git client asks for GitHub login to access this submodule repo: https://github.com/Kode/vscode-chrome-debug-core
Maybe it's still a private repo.
And there is another issue:

git.exe submodule update --init --recursive -- "extensions/kha"
error: no such remote ref 8e83118208bed2fc73a10cd29833f9027a78c188
Fetched in submodule path 'extensions/kha', but it did not contain 8e83118208bed2fc73a10cd29833f9027a78c188. Direct fetching of that commit failed.
git.exe submodule update --init --recursive -- "extensions/krom"

posted in Kode Studio read more

hey, Robert! :)
I hate to be annoying, but still
Is there any progress on this krom issue? should I wait for fix or maybe workaround this?

posted in Kha read more

thx for tip about vs version, but actually it's -v vs2015
and I didn't know what exactly should I upload so here it is - all my Krom folder

posted in Kha read more

run_krom.bat is working, thanks

but krom itself still crashes
I've managed to build it, though I've had some troubles:
using Visual Studio 2015 I got this error:

MSB8020 The build tools for v141 (Platform Toolset = 'v141') cannot be found

manually set Target Platform Version from 10.0.14393.0 to 8.1 and Platform Toolset from v141 to v140
and then I get this error when building for Win32

LNK1112 module machine type 'x64' conflicts with target machine type 'X86' Krom\build\v8.dll.lib(v8.dll)

when switched to "x64" all builds ok
but is Win32 Krom build not supported?

but it still crashes with Access violation on this line in main.cpp:

isolate = Isolate::New(create_params);

and now I don't know what to do next :(

posted in Kha read more

Thanks! I'll definitely check it out when you update windows krom binaries :)
I've tried to build it myself with this:

node Kore/make

and then opened Krom.sln, but there were build errors:

Severity    Code    Description Project File    Line    Suppression State
Error   C3861   'setBlendingModeSeparate': identifier not found Krom    Krom\Sources\main.cpp   1323    
Error   C2039   'setFloat4s': is not a member of 'Kore::Graphics'   Krom    Krom\Sources\main.cpp   988 
Error   C3861   'setFloat4s': identifier not found  Krom    Krom\Sources\main.cpp   988 
Error   C2664   'Kore::Texture::Texture(Kore::Texture &&)': cannot convert argument 1 from 'void *' to 'int'    Krom    Krom\Sources\main.cpp   1105    
Error   C2039   'clear': is not a member of 'Kore::Texture' Krom    Krom\Sources\main.cpp   1147    
Error   C2039   'setBlendingModeSeparate': is not a member of 'Kore::Graphics'  Krom    Krom\Sources\main.cpp   1323    

In the meantime could you plz add small fix to khamake?
HaxeProject.ts:247
I need this line:

    if (options.language === 'cpp') {

changed to this

    if (options.language === 'cpp' || options.system === 'krom') {

so I can run Krom right from HaxeDevelop :)

posted in Kha read more

So. should I wait for fix in nearest time or try to workaround this?

And one more thing with target krom haxedevelop generated project:
now khamake is generating it with this:

    <option testMovieCommand="krom\index.html" />

and it runs nothing
I thing it should be like with windows target, so something like this:

    <option testMovieCommand="run_krom.bat" />

so final developer may replace this bat with working path to krom

posted in Kha read more