Vram leak prolly
dumping shortlog here with no further context. Looks like I ran out of VRAM.
Game was running for ~11 hours, and I was going in and out of nether portals around this time.
Nvidia 3070Ti (8GB VRAM), 8GB XmX G1GC, Windows 11 23H2. DH 2.2.0a with balanced cpu preset, no other setting changes. Embeddium 0.3.30+1.20.1 / Oculus 1.6.15a, no shaders or resource packs (Modpack is Gregtech New Beginnings, which uses Create, True Darkness and BiomesoPlenty).
39 Replies
im suprised that you are asking about a vram issue, and not that eveyting looks horrible, because oculus 1.6.15a does not have shader support
what mc version are you on?
1.20.1
then you should either use DH 2.1.2 with oculus 1.7, or use DH 2.2.1 with an oculus version that is only available on their github for now. as a memory leak was fixed in 2.2.0, i recommend the latter
i remember having some similar issue a couple months ago but it was definitely with physical RAM and DH 2.1.2. Create blocks didn't show up (were invisible) when using Oculus 1.7.0. Hopefully they have fixed it by now?
maybe, i dont know about that
if you cant use a oculus version higher than 1.6.15a, its better to remove either oculus or DH. the vram leak may or may not be because of those two mods not supporting each other, its hard to say.
Hmm. Last time Oculus's github updated was 7 months ago.
Maybe something will happen if I use Iris's forge build instead.
youre probably looking at the wrong branch
oh, yeah. thats it
1.16.5 is marked as the default branch on their git
so 1.20.1-new
yea
I won't touch the Oculus branch as I'm not about to install an IDE to build a .jar file
But apparently latest Iris+Embeddium+DH doesn't crash so let's see how it is ingame!
yep, all good here
matter of time for testing now
you can download the build artifact. no need to compile yourself
youre switching to 1.21.1?
no, i'm still on 1.20.1
I think the modpack would die instantly if I tried
oh, then what DH are you using?
DH 2.2.1 (should have specified *latest for this version lol)
huh weird, that shouldnt work with latest iris
create's good
what is the exact iris version?
"1.7.5+mc1.20.1"
via CurseForge, Prism Launcher
oh youre switching to fabric now?
not really
I think whatever the iris devs have done somehow enables it to work on forge perfectly fine
then it doubt its actually working
or the modpack does, no idea
no
can you share a screenshot in game? with f3 open?
gonna guess it's not enabled then
so iris is not loading
yea
forge just skips loading it because its not for forge
go here
GitHub
Upgrade support for Distant Horizons 2.2 (#702) · Asek3/Oculus@da63...
Contribute to Asek3/Oculus development by creating an account on GitHub.
and click build artifacts
then open the zip
Ok, thanks.
I immediately look to the right of any github page to see if there's any releases/packages, did not know this was a feature of Github
had to search for a while as well 😅
[Oculus] Version: 1.7.0
looks like its working, no?
shaders are just disabled
looks like
now lets hope the vram issue doesnt come back
hmm. gonna try just not running DH for a bit and see if it goes away
if it helps I'm on nvidia driver version 565.90 for win11
might be related to chromium somehow too, since whenever minecraft crashes with the OP error, it sometimes takes my browser out with it
journeymap interaction?
or journey tries to eat memory that's in use by DH. who knows
got
Crashpad_NotConnectedToHandler error in chromiumhol up
11.6GB?
why is it allocating 3 and a half more GB physical ram than XmX
istg if i have to reinstall windows
literally the only thing preventing me from going linux fulltime is meta/oculus VR
ok cool, last crash also corrupted ftbchunks map cache
thanks minecrap
think its become clear this is probably not a DH issue
Because java has different memory systems, and you allocated 8 GB to one of them. That's not a windows problem, that's just how java works
Yea that does not look like something dh would cause
best guess is something to do with adoptium vs oracle JDK, DH's 2.2.1 server interaction, or the threading / viewdistance settings (default DH viewdistance at 128, still has issues lowered down to 96 chunks and a vanilla distance of 8)
either way, I disabled DH on my client, and my local server that never had DH installed is running well under 4GB, where before it was topping out above 9GB on an 8XmX instance
might have something to do with it
this gets spammed when /backing after dying, or changing dimensions often.
-# yes the IP is exposed i don't care
either way, it hits max RAM usage very quickly this way and after setting all threads to 1 with 90% runtime except for the LOD builder threads which get 8 because of the max queue limit warning
it seems like distant generation is trying to occur way too frequently for chunks that haven't changed, or something isn't being released properly
no way to do anything about it until the mods I'm using updates to 1.21, (Create…)