Delay in breaking blocks with Nvidium enabled

[nmackowiakk]

Java-runtime-gamma.2024.02.14.-.13.35.32.04.DVR.-.Trim.mp4

This kind of delay doesn't appear with nvidium disabled.

[Westbrooke117]

I might be having the same issue. Are you using the mod Bobby?

[nmackowiakk]

I am! Is it what causes it?

[Westbrooke117]

I’ve found the issue can be remedied by changing the viewDistanceOverwrite setting in Bobby. Despite it saying it is for the Singleplayer internal server, it’s resolved the issues on the multiplayer server I was playing on too. I’ve found that changing the setting to the chunk distance of the server works. I’m unsure though whether it is Bobby or Nvidium which causes the issue.

[MiniGwynie]

i'm getting a delay on a lot of things, including breaking blocks. opening doors (especially with pressure plates) and placing beds are where it's most noticeable. i find it only happens when render distance is above 32. this is true for both bobby and farsight. disabling singleplayer server view distance/view distance overwrite in bobby fixes it, but that also disables rendering beyond 32 chunks, at least in singleplayer. this can happen at 20 tps 200+ fps. limiting fps had no effect.

this bug does not happen when render distance is above 32 without nvidium, so this issue is specific to nvidium. i also tested with no other mods, of course.

i've had this issue in Minecraft version 1.20.4, fabric version 0.15.6, fabric api versions 0.95.4 and 0.96.1, nvidium versions 0.2.6 and 0.2.5. i'm going to try testing every version of nvidium, then every version of everything else that was made while the earliest version of nvidium existed for 1.20.4, then everything as up to date as i can get them. i will post another reply with my results if i still have enough spirit to continue existing after putting in that much effort for almost certain disappointment.

[Westbrooke117]

I am playing on 1.20.4 with the relevant mods being:

• Nvidium 0.2.6-beta
• Sodium 0.5.8
• Fabric API 0.96.1
• Bobby 5.1.0

Nvidium and Sodium are on the default settings with no advanced settings changed, and here is my Bobby config:

Here is a Singleplayer world I just created with Bobby and Nvidium at 64 chunks. There was no block or entity lag observed:

[MiniGwynie]

the issue gets worse as more chunks load. increasing memory doesn't help. issue persists on nvidium 0.2.4, sodium 0.5.4, fabric api 0.96.1, fabric 0.15.6. setting the server render distance to 1 in bobby reduces the issue but doesn't eliminate it. i'm going to try to replicate the conditions in the image above to try and isolate the issue.

[MiniGwynie]

i made a new 1.20.4 fabric profile in my mod manager, downloaded the mods below and replicated the settings shown and described in the post above. the issue persisted. the issue was probably less pronounced for the person above due to the server render distance being set to 12.

driver version (sanity check): 545.92

mods:
fabric 0.15.6
betterf3 9.0.0
bobby 5.1.0
cloth config api 13.0.121
fabric api 0.96.1
sodium 0.5.8
nvidium 0.2.6
mod menu: 9.0.0

my bobby settings:

my general settings:

my nvidium settings:

the door issue + f3:

[MiniGwynie]

sanity check: updated graphics driver, no effect

[MiniGwynie]

#141

seems related

[CoopersHyper]

the issue gets worse as more chunks load. increasing memory doesn't help. issue persists on nvidium 0.2.4, sodium 0.5.4, fabric api 0.96.1, fabric 0.15.6. setting the server render distance to 1 in bobby reduces the issue but doesn't eliminate it. i'm going to try to replicate the conditions in the image above to try and isolate the issue.

Contrary to what you may think, increasing the memory actually makes it worse. Me being me, whenever i first got the mod I whacked up the max memory at far as it could go. I enabled the automatic memory limit and my problem is solved. If you still are experiencing some issues, I would try manually setting the limit to 3/4 or even 1/2 or your GPU's memory.

Hope this helps!

[noahnao]

I’ve found the issue can be remedied by changing the viewDistanceOverwrite setting in Bobby. Despite it saying it is for the Singleplayer internal server, it’s resolved the issues on the multiplayer server I was playing on too. I’ve found that changing the setting to the chunk distance of the server works. I’m unsure though whether it is Bobby or Nvidium which causes the issue.

This did absolutely nothing for me. I set my server render distance to 75 and my client render distance to 75, as well as setting bobby max render distance to 75, and the issue still persisted.

[Briarbot2011]

I’ve found the issue can be remedied by changing the viewDistanceOverwrite setting in Bobby. Despite it saying it is for the Singleplayer internal server, it’s resolved the issues on the multiplayer server I was playing on too. I’ve found that changing the setting to the chunk distance of the server works. I’m unsure though whether it is Bobby or Nvidium which causes the issue.

This did absolutely nothing for me. I set my server render distance to 75 and my client render distance to 75, as well as setting bobby max render distance to 75, and the issue still persisted.

the way i found to resolve the issue is to turn off automatic memory limit and manually set the max memory to at or a bit below your gpu's vram in binary MB(meaning 1 GB is equal to 1024 MB)

[noahnao]

I’ve found the issue can be remedied by changing the viewDistanceOverwrite setting in Bobby. Despite it saying it is for the Singleplayer internal server, it’s resolved the issues on the multiplayer server I was playing on too. I’ve found that changing the setting to the chunk distance of the server works. I’m unsure though whether it is Bobby or Nvidium which causes the issue.

This did absolutely nothing for me. I set my server render distance to 75 and my client render distance to 75, as well as setting bobby max render distance to 75, and the issue still persisted.

the way i found to resolve the issue is to turn off automatic memory limit and manually set the max memory to at or a bit below your gpu's vram in binary MB(meaning 1 GB is equal to 1024 MB)

Thanks for sharing your solution! Unfortunately, I tried setting the max memory to 9216 MB as you suggested, but it didn't resolve the issue for me. I have an RTX 3080 with 10GB of VRAM, so I followed your advice closely. However, the problem persisted.
The only workaround that seems to work for me is turning down the render distance to vanilla, which defeats the purpose of the mod entirely. It's frustrating because the whole point of using the mod is to enjoy larger render distances. I'm still searching for a solution that allows me to utilize the mod to its full potential without encountering this issue.
If you or anyone else has any further suggestions, I'm all ears!

[Briarbot2011]

I’ve found the issue can be remedied by changing the viewDistanceOverwrite setting in Bobby. Despite it saying it is for the Singleplayer internal server, it’s resolved the issues on the multiplayer server I was playing on too. I’ve found that changing the setting to the chunk distance of the server works. I’m unsure though whether it is Bobby or Nvidium which causes the issue.

This did absolutely nothing for me. I set my server render distance to 75 and my client render distance to 75, as well as setting bobby max render distance to 75, and the issue still persisted.

the way i found to resolve the issue is to turn off automatic memory limit and manually set the max memory to at or a bit below your gpu's vram in binary MB(meaning 1 GB is equal to 1024 MB)

Thanks for sharing your solution! Unfortunately, I tried setting the max memory to 9216 MB as you suggested, but it didn't resolve the issue for me. I have an RTX 3080 with 10GB of VRAM, so I followed your advice closely. However, the problem persisted. The only workaround that seems to work for me is turning down the render distance to vanilla, which defeats the purpose of the mod entirely. It's frustrating because the whole point of using the mod is to enjoy larger render distances. I'm still searching for a solution that allows me to utilize the mod to its full potential without encountering this issue. If you or anyone else has any further suggestions, I'm all ears!

these are the configs for my personal modpack that runs on 1.20.1:

[noahnao]

I’ve found the issue can be remedied by changing the viewDistanceOverwrite setting in Bobby. Despite it saying it is for the Singleplayer internal server, it’s resolved the issues on the multiplayer server I was playing on too. I’ve found that changing the setting to the chunk distance of the server works. I’m unsure though whether it is Bobby or Nvidium which causes the issue.

This did absolutely nothing for me. I set my server render distance to 75 and my client render distance to 75, as well as setting bobby max render distance to 75, and the issue still persisted.

the way i found to resolve the issue is to turn off automatic memory limit and manually set the max memory to at or a bit below your gpu's vram in binary MB(meaning 1 GB is equal to 1024 MB)

Thanks for sharing your solution! Unfortunately, I tried setting the max memory to 9216 MB as you suggested, but it didn't resolve the issue for me. I have an RTX 3080 with 10GB of VRAM, so I followed your advice closely. However, the problem persisted. The only workaround that seems to work for me is turning down the render distance to vanilla, which defeats the purpose of the mod entirely. It's frustrating because the whole point of using the mod is to enjoy larger render distances. I'm still searching for a solution that allows me to utilize the mod to its full potential without encountering this issue. If you or anyone else has any further suggestions, I'm all ears!

these are the configs for my personal modpack that runs on 1.20.1:

I want a renderdistance larger than 32 chunks, without bugs. I am well aware that if you turn the viewdistance down to vanilla values, the bug goes away. It should be possible to run above 32 chunk renderdistance, that is why this is an issue. I know the developer is working on it, but it might be an issue with Bobby, not Nvidium.

[JoeyHamlet]

I’ve found the issue can be remedied by changing the viewDistanceOverwrite setting in Bobby. Despite it saying it is for the Singleplayer internal server, it’s resolved the issues on the multiplayer server I was playing on too. I’ve found that changing the setting to the chunk distance of the server works. I’m unsure though whether it is Bobby or Nvidium which causes the issue.

This did absolutely nothing for me. I set my server render distance to 75 and my client render distance to 75, as well as setting bobby max render distance to 75, and the issue still persisted.

the way i found to resolve the issue is to turn off automatic memory limit and manually set the max memory to at or a bit below your gpu's vram in binary MB(meaning 1 GB is equal to 1024 MB)

Thanks for sharing your solution! Unfortunately, I tried setting the max memory to 9216 MB as you suggested, but it didn't resolve the issue for me. I have an RTX 3080 with 10GB of VRAM, so I followed your advice closely. However, the problem persisted. The only workaround that seems to work for me is turning down the render distance to vanilla, which defeats the purpose of the mod entirely. It's frustrating because the whole point of using the mod is to enjoy larger render distances. I'm still searching for a solution that allows me to utilize the mod to its full potential without encountering this issue. If you or anyone else has any further suggestions, I'm all ears!

these are the configs for my personal modpack that runs on 1.20.1:

I want a renderdistance larger than 32 chunks, without bugs. I am well aware that if you turn the viewdistance down to vanilla values, the bug goes away. It should be possible to run above 32 chunk renderdistance, that is why this is an issue. I know the developer is working on it, but it might be an issue with Bobby, not Nvidium.

I believe it wouldn't be an issue with Bobby as from what I understand you're playing in singleplayer. Bobby doesn't come into effect in singleplayer unless you put the "Singleplayer Server View Distance" to anything above 0. Otherwise the "Max Render Distance" esentially only extends the range of the render distance slider in sodium. If you do have Single player view distance set to any other value it does "solve" the issue, but it does so at the expense of not loading any chunks beyond the set view distance in bobby's config.

[noahnao]

I’ve found the issue can be remedied by changing the viewDistanceOverwrite setting in Bobby. Despite it saying it is for the Singleplayer internal server, it’s resolved the issues on the multiplayer server I was playing on too. I’ve found that changing the setting to the chunk distance of the server works. I’m unsure though whether it is Bobby or Nvidium which causes the issue.

This did absolutely nothing for me. I set my server render distance to 75 and my client render distance to 75, as well as setting bobby max render distance to 75, and the issue still persisted.

the way i found to resolve the issue is to turn off automatic memory limit and manually set the max memory to at or a bit below your gpu's vram in binary MB(meaning 1 GB is equal to 1024 MB)

Thanks for sharing your solution! Unfortunately, I tried setting the max memory to 9216 MB as you suggested, but it didn't resolve the issue for me. I have an RTX 3080 with 10GB of VRAM, so I followed your advice closely. However, the problem persisted. The only workaround that seems to work for me is turning down the render distance to vanilla, which defeats the purpose of the mod entirely. It's frustrating because the whole point of using the mod is to enjoy larger render distances. I'm still searching for a solution that allows me to utilize the mod to its full potential without encountering this issue. If you or anyone else has any further suggestions, I'm all ears!

these are the configs for my personal modpack that runs on 1.20.1:

I want a renderdistance larger than 32 chunks, without bugs. I am well aware that if you turn the viewdistance down to vanilla values, the bug goes away. It should be possible to run above 32 chunk renderdistance, that is why this is an issue. I know the developer is working on it, but it might be an issue with Bobby, not Nvidium.

I believe it wouldn't be an issue with Bobby as from what I understand you're playing in singleplayer. Bobby doesn't come into effect in singleplayer unless you put the "Singleplayer Server View Distance" to anything above 0. Otherwise the "Max Render Distance" esentially only extends the range of the render distance slider in sodium. If you do have Single player view distance set to any other value it does "solve" the issue, but it does so at the expense of not loading any chunks beyond the set view distance in bobby's config.

No i am not on single player.

[JoeyHamlet]

No i am not on single player.

Ah, nvm. I should have paid more attention to your earlier comments.

[RomanSonnik]

Does somebody knows how to unlock this setting? Thanks.

[CoopersHyper]

Does somebody knows how to unlock this setting? Thanks.

Disable “Automatic memory limit”

[gabepikamole]

having the same issue. will try solutions and update to tell people whether it's fixable still or not.

[fasscass]

I have the same issue, also using bobby. Using Nvidium 0.3.1 in 1.21.1 in an online server. Solutions shown here didn't change anything. I tried changing transparency settings but none changed anything either