Title :)

4.2 is quite some major release, I really would love to encourage you keeping it continuosly up to date, its really worth this library especially having it with .net 7 now :D

Using LoadShaderFromMemory returns a shader but when used in Raylib.BeginShaderMode(shader); the shader does not work. Doing the exact same thing in a project using Raylib cs everything works as expected.

Does the first try-statement throw an exception if "vsCode" parameter is null?

Raylib CsLo Binding Code:

public unsafe static Shader LoadShaderFromMemory(string? vsCode, string fsCode)
{
    SpanOwner<sbyte> spanOwner = vsCode.MarshalUtf8();
    try
    {
        SpanOwner<sbyte> spanOwner2 = fsCode.MarshalUtf8();
        try
        {
            return LoadShaderFromMemory(spanOwner.AsPtr(), spanOwner2.AsPtr());
        }
        finally
        {
            spanOwner2.Dispose();
        }
    }
    finally
    {
        spanOwner.Dispose();
    }
}

Raylib Cs Binding Code:

public unsafe static Shader LoadShaderFromMemory(string vsCode, string fsCode)
{
    using UTF8Buffer uTF8Buffer = vsCode.ToUTF8Buffer();
    using UTF8Buffer uTF8Buffer2 = fsCode.ToUTF8Buffer();
    return LoadShaderFromMemory(uTF8Buffer.AsPointer(), uTF8Buffer2.AsPointer());
}

Issue description

Dealing with exported resources in raylib with c# is complicated right now.

The default way is to copy the resource folder to the output directory but when distributing your game/app all resources are visible to the customer. (among many other problems with that way)

The problem is that loading resources from anywhere else than the disk is very complicated or not possible. (to my knowledge with raylib c# bindings) So my only solution would be to compress/encrypt the resources when building and then uncompress/decrypt them when the game/app is started but then the resources are visible again to the user while the game/app is running.

Raysan already implemented a solution for raylib called rres but it is only available for c right now. The resource packer can already be used to pack all the resources into a rres file but there is no way to load that rres file and transform it into raylib types like image, font, wave, etc. right now.

It would be really nice if there would be separate bindings for rres so it can be used with c# and it would make raylib with c# much more robust.

PS: At least it would be nice to know if you are interested in doing that at all. Because I don´t need it right now and if you would like to do it I am not going to look for another solution.

I will also ask ChrisDill with raylib-cs bindings.

Thanks!

W.I.P

Using the Raylib-CsLo\sub-modules\raylib\parser\raylib_api.json i can do some code generation with c# to make the C# class

What do you think about moving all safe code to a RaylibS class as I have found the overloads a bit messy with intellisense

Raylib-CsLo bundles a custom version of the Raylib native binary: it's compiled to include extras such as raygui,physac, and easings.

However Raylib 4.2 changes it's project structures. I was able to build the windows x64 binaries properly, but was unable to build either the linux or osx binaries.

as building native binaries on various platforms is not my area of expertise, I ask for help here.

In the meantime, the Raylib-CsLo 4.2 version is on Nuget as a pre-release, Win_x64 only build. The release version of CsLo's nuget package will remain 4.0 until this issue is resolved.

If you are interested in helping

See the https://github.com/NotNotTech/Raylib-CsLo/tree/main/sub-modules folder's readme for the current (broken) workflow for building linux.

When I followed the linux steps (Ubuntu 22.04 x64) This is the error I received when calling make:

Creating bin/Release.DLL Linking raylib /usr/bin/ld: obj/x64/Release.DLL/rtextures.o: relocation R_X86_64_TPOFF32 against `stbi__g_failure_reason' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: failed to set dynamic section sizes: bad value collect2: error: ld returned 1 exit status make[1]: *** [Makefile:117: bin/Release.DLL/raylib.dll] Error 1 make: *** [Makefile:36: raylib] Error 2

It seems to be something about the .sofailing to build.

• I went and added a better .editorconfig and made changed to suit the project
• Updated the bindings to use the proper commit with submodules
• Cleaned up alot of the code that was now giving errors.
• All tests still pass

Title.

calling this code with the empty string ""here WORKS: Raylib.DrawTextEx(logText.Src, "", new Vector2(pos.X, pos.Y) * 1.2f, logText.Size, 1f, Raylib.RED);

But this FAILS: Raylib.DrawTextEx(logText.Src, "A", new Vector2(pos.X, pos.Y) * 1.2f, logText.Size, 1f, Raylib.RED);

Dont mind variable "LogText" its just my custom struct either way its used in both of the above and it works in one of it.

Title.

Its bit more clearer and semantically correct to say "Color.WHITE" then "Raylib.WHITE" or even when "using static Raylib"; "WHITE"

IMHO.

Atleast think about it, nothing big of a complain here just some small hint.

Cheers nd thx for doing work to perma upgrade raylib man!

ExportWaveAsCode/ExportImageAsCode functions are meant to export to an .h file which is not directly usable in c# ... Is there any way to fix this with the bindings?

Wherever null string is accepted it is converted to a valid pointer to a '\0' instead of null. This produces a warning when using LoadShader since '\0' is not a valid file path but at least it works since raylib checks if file was loaded correctly. This completely breaks LoadShaderFromMemory however because it's trying to compile '\0' as a shader.

When I'm trying to call a RayGui method, I get this error in the console. Did I massively overlook something?

Code

using Raylib_CsLo;

namespace PixelArtGame
{
    internal class Program
    {
        static void Main(string[] args)
        {
            Raylib.InitWindow(800, 480, "PixelArtGame");
            RayGui.GuiLoadStyleDefault();
        }
    }
}

Error

Unhandled exception. System.EntryPointNotFoundException: Unable to find an entry point named 'GuiLoadStyleDefault' in DLL 'raylib'.
   at Raylib_CsLo.RayGui.GuiLoadStyleDefault()
   at CircleClicker.Program.Main(String[] args) in .\PixelArtGame\Program.cs:line 16

.\PixelArtGame\bin\Debug\net6.0\PixelArtGame.exe (process 12292) exited with code -532462766.

Hallo, i wanted to load a Shader.

So I first tried using LoadShader.. LoadShader(Textformat(string, value),Textformat(string,value))

It then showes: [11:41:07 INF] FILEIO: [Data/Scenes/Test2/Shader/base_lighting.vert] Text file loaded successfully [11:41:07 INF] FILEIO: [Data/Scenes/Test2/Shader/lighting.frag] Text file loaded successfully

but then it print out this: ` [11:41:07 WRN] SHADER: [ID 4] Failed to compile vertex shader code [11:41:07 WRN] SHADER: [ID 4] Compile error: ERROR: 0:1: '' : illegal non-ASCII character (0xef) ERROR: 0:1: '' : illegal non-ASCII character (0xbb) ERROR: 0:1: '' : illegal non-ASCII character (0xbf)

[11:41:07 WRN] SHADER: [ID 5] Failed to compile fragment shader code [11:41:07 WRN] SHADER: [ID 5] Compile error: ERROR: 0:1: '' : illegal non-ASCII character (0xef) ERROR: 0:1: '' : illegal non-ASCII character (0xbb) ERROR: 0:1: '' : illegal non-ASCII character (0xbf)

[11:41:07 WRN] SHADER: [ID 6] Failed to link shader program [11:41:07 WRN] SHADER: [ID 6] Link error: Attached vertex shader is not compiled. `

My shader Files are from the basic_lighting Example.

Have to follow SetWindowPosition with SetWindowSize

InitWindow(0, 0, "test");
SetWindowPosition(x, y);
SetWindowSize(wid, hgt);

or else the size will revert to some default.

If you use/love raylib-cslo and are interested in helping to maintain the binding, let me know. Raylib-cslo is up to date and working 100%. I just don't really use it anymore so planning ahead, now (when no fires to put out) would be a good opportunity for a new maintainer to step in. It's super easy to update the bindings on new raylib releases. The biggest problems raylib-cslo faces is building native binaries on various platforms when a new version is deployed.. Check the issues for more detail.

No rush to do this, just want to plan ahead.

Discovered issue in raylib 4.2 audio subsystem, seems to regard streaming audio.

https://github.com/raysan5/raylib/issues/2714

this issue will track progress on native fix.

This bug was found by running through the examples, which CsLo uses as verification tests. The streaming audio examples cause the next following screen to crash.

It would be nice to have an automated build process like what raylib-cs has. This would automatically build the windows,linux,osx binaries when a code change is commited.

Currently building for Windows and Linux can be done manually, which is good enough for me in the medium term, which is why I can't prioritize working on it myself for now.

Update: it seems raylib-cs doesn't actually build, it just coppies the native raylib binaries. So an actual github action to build+bundle extras seems like it would be a lot more work!