Iris Shaders

Iris Shaders

36M Downloads

Really low fps even without shaders

Boomy639 opened this issue · 19 comments

commented

What happened?

This mod gives me lower fps than Vanilla minecraft even without the shaders and everything set to low

Vanilla Minecraft settings, Chunks: 8, Graphics: Fancy, Smooth Lighting: On/Maximum, Other things (e.g Biome blend): on
Fps= 80 to 100

IrisShaders Settings, Chunks: 2, Graphics: Fast, Smooth Lighting: Off, Other things (^): off
Fps= 20 to 40

Screenshots

No response

Relevant log output

No response

Iris and Minecraft Version

Both 1.17

Are you running Sodium along with Iris?

Yes

Operating System

Windows 10

What is your GPU?

Geforce GT710

Java Version

Java 16

Additional context

No response

commented

Should be fixed in latest commits

commented

send screenshots of your f3 debug screen, and latest.log file

commented

send screenshots of your f3 debug screen, and latest.log file

okay

commented
commented

had the same results i think its because of the "active renderer: none (vanilla)"

commented

That just means it's using the vanilla rendering api and not the fabric rendering api, it wouldn't cause the issue

commented

Having a very similar experience, originally thought it may have been my resource packs but even with them disabled and everything else set to the minimum settings I've been experiencing serious FPS drops (lowest I've seen was 7, but it quickly hopped back up to 9). It averages 13 and gets the worst when I try to turn or look up- down isn't as low as the other directions.

EDIT: Wanted to mention that it will start out great at about 60-70 fps with shaders and the works, 80-90 with just Iris, Fabric and Origins. However, after roughly 30 minutes into gameplay (no matter whether on a server or a single player world) it starts to tank into the previous mentioned drops.

commented

I have this issue aswell

commented

It seems Sodium has a leak and Iris itself has a few might want to check both vram and ram.

Edit: With a GT710 you will hit that limit fast.

commented

Log files and other information would be useful

commented

@coderbot16 maybe add something like sodium issue or ... Forgot what it was called I'll come back with a edit.

Edit: Don't we already have a issue on Iris leaks so shouldn't this be moved to the sodium repo, or closed as duplicated?

commented

Log files and other information would be useful

latest.log under the screenshot

commented

Having a very similar experience, originally thought it may have been my resource packs but even with them disabled and everything else set to the minimum settings I've been experiencing serious FPS drops (lowest I've seen was 7, but it quickly hopped back up to 9). It averages 13 and gets the worst when I try to turn or look up- down isn't as low as the other directions.

EDIT: Wanted to mention that it will start out great at about 60-70 fps with shaders and the works, 80-90 with just Iris, Fabric and Origins. However, after roughly 30 minutes into gameplay (no matter whether on a server or a single player world) it starts to tank into the previous mentioned drops.

So I played last night and decided to take some screenshots from when it tanks. I attached the logs as well. I tested it without the other mods- just Iris and Sodium and it still has the same issues so I didn't bother screenshotting them. The screenshots include the mods:

  • Iris/Sodium,
  • LambsDynamicLights,
  • OkZoomer,
  • Origins/Extra Origins/Fabric
  • ShulkerBoxToolTip
  • ModMenu
  • Music Reducer
  • Pehkui

The texture/resource packs I am using are:

  • Better Visibility of Ores
  • Better Clear Glass
  • Colorful Flora
  • Kal's Armor
  • Pride Axolotls
  • Visible Ores
  • A Vanilla Tweaks pack

I was playing for four hours at this point (from roughly 9 pm to 1 am, give or take) with Complementary Shaders on and it was running at an average of 45 fps, 75 fps without shaders. I stayed within a 70 chunk radius (working on two builds side by side, they span roughly 300 blocks in a square?) This was right before I turned the shaders off as it became unplayable:

2021-07-04_01 24 49
2021-07-04_01 25 22

It worked for the twenty or so minutes and then this happened:

2021-07-04_01 32 19
2021-07-04_01 41 16
2021-07-04_01 41 12

When looking back at the logs (attached at bottom), I mainly saw these issues:

  • *[STDRR] No uniform exists with name (ex. u_ModelViewMatrix).
  • *[] Unsupported uniform: float/mat4/vec3 (one of those 3 and then a similar or matching name to above) (this one and the one above begin anytime I start the CS pack and happens a lot. Not sure why but that's why I'm not a programmer)
  • *Shader could not find sampler named in the specified shader program. (this one varies quite a bit.)
  • Ignoring draw buffer 9 from draw buffers array [0, 5, 9] since Iris doesn't support extended color buffers yet.
  • Received passengers for unknown entity (.....Yeah no clue. Starts about 30 minutes in.)
  • *Failed to parse the block ID map entry There is no block with the name ! (It's calling on a bunch of plants. Going to completely honest here, this is partially why I included the list of mods and textures because I have no idea where these are coming from)

*Happens the most

There will also be a few errors about simple voice chat, its on the server but I don't have it; it's never been an issue and when I don't have Iris/Sodium running it's fine. It isn't the mods nor is it the server (we use Shockbyte, but it does this offline as well). My computer has ran these mods and more with no issue, so it's not a hardware issue either. I plan on trying different shaderpacks to see if certain parts of certain packs are causing conflicts or if its just a pack-wide thing.

Java 16
Windows 10
Hardware and Iris/Sodium versions in the screenshots

latest.log (pt.1).txt
latest.log (pt.2).txt
latest.log (pt.3).txt

commented

i think it gets worse when looking at lights like torches and lanterns

commented

It definitely doesn't help, that's for sure. I've also noticed that loading animals or mobs doesn't trigger it? It seems to just progressively get worse over the course of two minutes.

commented

This is known, all of it. It's being fixed behind the scene.

commented

one thing i do know is an i7 and gtx 980 should NOT be getting 0fps, jesus

commented

Once again, the issue is being fixed, it was an issue with a mem leak that is being patched by both the sodium and iris team actively, and the next release should solve all these issues

commented

Once again, the issue is being fixed, it was an issue with a mem leak that is being patched by both the sodium and iris team actively, and the next release should solve all these issues

Thank you Niko