A Moogle  🏳️‍🌈 💻 🎮 🎶 🇸🇪

You need to ask yourself: Are you doing this for Forge, or are you doing this for the Community? Because it seems like shader add-ons like Optifine are doing just fine coexisting alongside Forge. Unless you want to open up a massive rift, I would leave it alone.

If you do insist on adding shader support to Forge, then I do ask that you get at me. I was supposed to be the person adding native shader support to MC, but I was perpetually blocked because Mojang didn't want to lose the 5% of the player base on anemic garbage hardware.

At the end of the day, I may be as rusty as a bucket, but as @mamedev_org's dedicated GPU fella, I still have some decent Java and GPU chops.

I would like to be able to support direct shaders in forge. It opens up interesting possibilities for mods, if there's proper shader infrastructure right in forge. Optifine is ok, but we could never have a direct dependency there. Additionally, optifine has historically

Been rather hit or miss in terms of impact in modded forge. Sometimes it's great, other times it's a complete shitshow. Shaders being part of the forge landscape simplifies a lot of things for a lot of people. It seems that vanilla isn't moving towards native support, so..

i would at least wait to release shaders via forge until the graphics engine update coming in theoretically 1.15, plus ive heard they are going to put alot of focus this update on performance improvements

This was my take, too. If they're going to finally add a requirement for basic shader support - something I was hired to do but never allowed, because heaven forbid the fewer than 5% of people already having a bad time can't run it at all - then, great. But we should wait for it.

So, the alleged performance improvements are already in progress in 1.14. the blaze3d engine is a thing now. I'm not sure how different it is from before, but the work is already in progress. I think now is the time to begin preparing for this, even if we're waiting for 1.15.