-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LoadShaderFromMemory Function is not working. #20
Comments
I think you are right about the |
What would that example look like? Do you just need a visual studio project with minimal code to reproduce the issue? |
a project would work, but even something like a code snippet would be fine, as long as it would obviously "work" if the bug is fixed? FYI this weekend I"m going to setup my Raylib dev env again, to do the 4.2 port and so will be looking at this then. |
@jasonswearingen I have a minimal project to show the problem. For now, I am posting the code here, if that is too cumbersome for you just tell me how to send it to you ;) -----Program.cs file------
Create a folder called shaders and put the shader in it.
In case you want to see it.
|
Was this bug fixed by now? |
I am finished updating to raylib 4.2 and looking at this now. am I correct that the failure case is that when hitting spacebar, so that "Shader from memory active" is selected, the screen is blank? and that the success case would it show the same shader as loaded from file? |
yes I think that is it. I fixed the problem, and will close this after I upload the nuget package. are you on windows or another platform? |
4.2.0alpha1 is on nuget now. |
@jasonswearingen I am on windows. It seems to work correctly now! Thanks :) |
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:
Raylib Cs Binding Code:
The text was updated successfully, but these errors were encountered: