Sinytra
[Feature] FRAPI support for Neo Sodium
(Connector 2.0.0-beta.7+1.21.1, Connector Extras 1.12.1+1.21.1, Sodium 0.6.9+mc1.21.1)
Right now, it doesn't look like Sodium for Neoforge supports is implementation of the fabric renderer API via Connector, which causes anything using FabriBakedModel to break. It may be disabled or not included in the Neoforge build.
Without Sodium (using Templates 2 2.4.1+1.21.1 as an example):
With Sodium:
I can provide a more full mod list if necenssary, but I'm pretty sure this is just between neo-sodium and Connector/Connextras.
I'll look into this and see what can be done, though I'm not familiar with Sodium's code / rendering in general.
In the meantime, I can recommend using Embeddium, which seems to work fine.
I was not aware of this issue. Please, in the future, report the issues on Sodium's issue tracker as well. Sinytra Connector is supposed to work with Sodium, as we actually adapt the NeoForge rendering pipeline on top of Fabric API using Sinytra's Forgified Fabric API modules.
This is not a bug with Sodium.
There seems to be an issue in the Forgified Fabric API version 3.4.0+acb05a3919 which was fixed in 3.4.0+9c40919e19. But as the version number was never bumped, and everything after the + delimiter in the version string is sorted alphabetically, NeoForge cannot correctly determine which is the "newer" version.
Furthermore, since the Fabric API modules are "embedded" in both Sodium and the Forgified Fabric API "bundle" (what a user would download), the normal logic of preferring the file in the user's mod directory does not work.
Sodium will publish an update to include the newer version of these modules, but unless Sinytra begins to bump the version of the Forgified Fabric API modules with each release, this problem will keep happening.
