MissingFieldException
Closed this issue · 10 comments
I am using the nuget version
My guess is there is some issue with the native runtimes for Raylib-cs on your platform ,make sure the native DLLs are 4.5. But this is not an issue with rlImGui itself.
My guess is there is some issue with the native runtimes for Raylib-cs on your platform ,make sure the native DLLs are 4.5. But this is not an issue with rlImGui itself.
Does raylib-cs not install native binaries through nuget?
I don't know, rlImgui just links to the package.
I'm also getting the same issue in my project. To test, I directly coppied the example and tried to run that, however it gave the same issue. This is what my .csproj looks like:
<ItemGroup>
<PackageReference Include="ImGui.NET" Version="1.89.9.3" />
<PackageReference Include="Raylib-cs" Version="5.0.0" />
<PackageReference Include="rlImgui-cs" Version="1.0.3" />
</ItemGroup>When running I get
An unhandled exception of type 'System.MissingFieldException' occurred in map-editor.dll: 'Field not found: 'Raylib_cs.Texture2D.id'.'
This makes no sense.
Raylib 5.0 is not out yet, thus there can not be a raylib-cs bindiding for it.
The nuget package for rlImGui-cs uses raylib-cs 4.5.0.4
as do the projects that are checked in
So I have no clue how you got a 5.0 in there, but that is just wrong.
I got RayLib from a VScode extension that I use to search for Nuget packages. I know that RayLib 5 is very close to being finished, so I just assumed that it was out. I'm not sure how that got in there. Running the RayLib 5 also works for some reason. I guess someone might have updated the number in anticipation?
Anyways, I downgraded to 4.5.0.4 and it works. Thanks for the help. This is now my new .csproj file:
<ItemGroup>
<PackageReference Include="ImGui.NET" Version="1.89.9.3" />
<PackageReference Include="Raylib-cs" Version="4.5.0.4" />
<PackageReference Include="rlImgui-cs" Version="1.0.3" />
</ItemGroup>Raylib 5.0 has breaking changes, I will update and branch rlImGui-CS once it's fully released
@JeffM2501 Raylib-cs 5.0.0 is still using raylib 4.5.0. This is because there are breaking changes I wanted to release before raylib 5.0 so I decided to move from following raylib versions directly to a separate version instead so I could make these type of changes clearer instead of only using a build number. I will update the extras repos soon to work with this release.
@JeffM2501 Raylib-cs 5.0.0 is still using raylib 4.5.0. This is because there are breaking changes I wanted to release before raylib 5.0 so I decided to move from following raylib versions directly to a separate version instead so I could make these type of changes clearer instead of only using a build number. I will update the extras repos soon to work with this release.
I have an updated version that works with raylib-cs 5.0.0.
Thanks for clearing it up.
I have updated this codebase to work with raylib-cs 5.0.0 and made it dependent on it. A new nuget package has been made (2.0).