-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
[Feature Request] C# Bindings #32
Comments
Hi, I've had this request from a few people. Getting it working for "Encoded Node Trees" should be reasonably easy, since it doesn't require exposing all the node type classes. Instead of exposing all the node classes individually it probably makes more sense to expose the node type metadata, would mean the dll interface wouldn't need updating when new node types are added. I'll probably start looking at it over the next week or so, well at least the C interface DLL, but from that it should be easy to create a C# wrapper |
That's great to hear! Thanks for considering this. Love your work, and the new node-based system has been interesting to play around vs my own internal noise system. Being able to design nodes and just use the encoded node will be awesome. |
I've added DLL support to the FastNoise API and a C interface, that should let you call the functions from C#. Currently the C interface only has support for creating nodes from encoded node trees, I will look at adding direct node creation later. The C interface is in FastNoise_C.h Here are the binaries from the latest CI build, I will make a new release that has them soon too. |
@Auburn Thanks! I really appreciate that ^_^ Just now circling back around to the process of switching from my own noise generation to this. |
As the title says, C# bindings!
I would love to use this library in C#, and I'm sure it would attract attention from Unity devs as well. I have no experience with C++, and honestly didn't make much progress in attempting this myself. Somewhat compounded by some of the methods being a bit obtuse without describing comments (For me anyways).
Hopefully this isn't too large of an ask.
The text was updated successfully, but these errors were encountered: