Post

VRChat has been removing any and all content that contains the word "vore" for the past month. And now they've graduated onto banning worlds that so much as have a detailed maw.

Can I speak to someone who knows a good deal about world building in resonite? The more I learn about it the more hurdles I discover. For example, resonite only uses unity for rendering; does that mean all my unity C# scripts aren't salvageable? And can I import custom standard surtace HLSL shaders?

Resonite uses it's own custom systems and will even be dropping Unity as a renderer in the near future. Sadly it is still missing some features (we have PBS and some specialty materials, but no custom shaders yet (planed after dropping unity), but a lot of the same effects can be recreated anyways)

Resonite uses Protoflux which is a visual scripting language based on C#. So a lot of the code can be manually converted pretty 1:1, which will take some time. But there is also a bunch of things that are hard to code elsewhere easy here but also some things are missing but planned (collections)

The community is helpful however and there are quite a few vore communities in Resonite you can ask for help. Or you can ask me, while I don't always have the time I'd like but I'm always willing to help with projects like these (read: kink), same name here as discord.

Ty. I wonder, does that mean all the scripting is only done in-game?

Yesn't. The intended way is in game yes. However there are people in the community (and tools that enable external tooling to be made) that allow for external scripting. An example is ProtoGraph (Community Made):

There is plans to eventually have official WebAssembly support, but that isn't currently part of the "short term" priorities IFAIK. If you want the team to focus on this give it a 👍 on the git issue.

Yeah. Though one thing I can't stress enough is: While some existing methods of doing things are often harder in Resonite. Resonite is coming from a different angle with the DataModel, Synced Data and what I call "Analog Scripting" That honestly makes things that where hard super easy.

A prime example is if I want to make a wall more opaque to users close to it, I can check: [Local] View Position -> Distance -> (some simple math for opacity) -> Set Alpha This code is automatically ran for all users, each one seeing their own results independently of each other.

The code above as it is seen in game to make the point more clear.

hmm, for VRC and CVR I would write that directly into the shader then it'd be all on the GPU. Tho I wonder about audiosources and having them switch between audio files; im thinking mostly about what it'd take to move my big pete project over.