Save
Saving
  • R
    rons

    Yes I just figured that glsl error message out. It took me a while to reproduce. Instead of changing directories to the Krom directory in the command prompt I changed it to Krom/Kinc accidentally. The VS project was then built in the wrong location. Running node Kinc/make from the Krom directory fix the problem. Everything worked by setting visual studio code to the newly compiled Krom.exe path.

    PS I'm stealing "Null Problemo".

    Thank you again for your patience.

    posted in Kode read more
  • R
    rons

    Yes the compute example works from visual studio code using Krom. Krom still does not open a window from Kode Studio but compiles correctly. Thank you again for helping me work through these issues.

    posted in Kode read more
  • R
    rons

    Got it to work. The Krom executable I finally compiled works. The Krom window stays open and works correctly from within visual studio code. Thank for all of the help.

    posted in Kode read more
  • R
    rons

    Sorry for the delay in response. I grabbed Krom and ran the node Kinc/make command to build the VS project. This was succesfull and no errors were displayed. When I try open the VS project I get this error:

    5d0fb279-f740-41d5-b5f3-d831238a6ded-image.png

    posted in Kode read more
  • R
    rons

    It does work when compiling for windows. I did run it from the command line, Krom still crashes. Thank you.

    posted in Kode read more
  • R
    rons

    Well thats interesting. It must be that I wasn't updating from git-hub properly. Because the path was defiantly set correctly. The error is gone now but the Krom window crashes in Visual studio code. No out put errors were observed. Is there a crash log ?

    Thank you again for the help.

    posted in Kode read more
  • R
    rons

    So I unistalled everything and fetched Kha again, downloaded the Krom binaries, reinstalled nodejs and set the paths from within Kode Studio. I also installed the Kha extention pak in Visual Studio Code. The build to windows now compiles in VS from Kode Studio for the compute shader example, I cant recreate this problem now. But now I get this error from Krom in Kode Studio and Visual Studio Code. Im not sure why this is showing up all of a sudden.

    C:\Devlopment\Kode\libraries\Kha\Backends\Krom/kha/compute/Compute.hx:81: characters 84-92 : kha.compute.Access has no field getIndex
    C:\Devlopment\Kode\libraries\Kha\Backends\Krom/kha/compute/Compute.hx:81: characters 162-170 : kha.compute.Access has no field getIndex

    Also Krom just doesnt run for anything in Kode Studio, no errors are shown in any terminal. I installed the Kha extention pak in Visual Studio Code and ran some projects from there Krom works.

    Im also not well versed in VS so please have patience with me.

    Did some more googling and found that there is a problem getting a krom window to open from Kode Studio.

    posted in Kode read more
  • R
    rons

    So for the heck of it I went back to the default Kha and Krom installation that comes with Kode Studio and it worked. Krom ran other examples and the compute shader example worked. But other projects im working on to learn Kha do not because some features do not exist in the default Kode Studio verrsion of Kha. Ill get the values for the varibles.

    PS thank you very much for all of your help.

    posted in Kode read more
  • R
    rons

    Sorry, yes I did update per your instructions. There is no other error in any panel. I cant see any value at that memory location.

    posted in Kode read more
  • R
    rons

    It compiles with krom but its been running for 10 min now and gives the error "Display file not found in class path (1,1)".

    In general Krom never displays anything for me.

    The VS error happend at line 277 in the ComputeImpl.cpp

    context->UpdateSubresource(shader->impl.constantBuffer, 0, nullptr, constantsMemory, 0, 0);

    posted in Kode read more