[128x - 32x] Dungeons, Dragons and Space Shuttles [MC1.12]

Tekkit? Feed the Beast? All texture compilations (work in progress and full releases) for mod packs.
Post Reply 
User avatar
BDcraft Web Admin
6590 Posts
 x 430

Post 06 Dec 2019, 15:24

TheMadMadigan wrote:
06 Dec 2019, 13:53
Novamanga wrote:
05 Dec 2019, 22:19
What resolution are you using? How much RAM are you allocating and how much VRAM does your graphics card have?
64x, 12g, have a 1060 strix card. With optifine installed it was grey instead of black.
Most weird OptiFine issues are fixed by disabling Fast Rendering wherever that lives in the options.
Profile pic by TsaoShin: https://www.deviantart.com/tsaoshin
If you like our work please consider becoming a Supporter and get an ad-free experience.
User avatar
4 Posts
 x 0

Post 10 Dec 2019, 15:28

64x runs flawless for me with 128x base textures and 20gb allocated for MC. Attempting to use the 128x version crashes every time with anywhere from 20gb-40gb of Ram allocated. Have a 2080RTX w/64 GB to work with. Attaching a crash log link if that can help narrow down the problem. At first look it seems like the galacticraft textures are causing the problem, but going to the project page and downloading the latest one shows their modify dates are the same so I don't know if patching that versions textures specifically down to 64x could work or just removing it would either.

https://paste.dimdev.org/ofaqujogoj.mccrash
User avatar
Patch Creator
1498 Posts
 x 139

Post 10 Dec 2019, 16:17

Line 7. The texture atlas has run out of space. This means the 8GB your 2080 has is not enough. RAM allocation helps but when the texture atlas transfers to the GPU if the VRAM is not big enough you get this crash. I believe most people who get it to work have 1080ti's or 2080ti's which have 11GB VRAM.

This is why I said try using the 128x pack but if it does not work stick with the 64x.
If anyone would like to take over any of my threads please contact me. I will continue to host what I have done but expect no further updates.
User avatar
BDcraft Web Admin
6590 Posts
 x 430

Post 10 Dec 2019, 16:32

Novamanga wrote:
10 Dec 2019, 16:17
Line 7. The texture atlas has run out of space. This means the 8GB your 2080 has is not enough. RAM allocation helps but when the texture atlas transfers to the GPU if the VRAM is not big enough you get this crash. I believe most people who get it to work have 1080ti's or 2080ti's which have 11GB VRAM.

This is why I said try using the 128x pack but if it does not work stick with the 64x.
The "Unable to fit" warning is to do with the pixel size of the atlas. Minecraft stitches all the block and item textures in to one big sheet, as well as the mipmaps.

When Java runs out of RAM it states an out of memory error. If a graphics card runs out of VRAM either the process will crash or the process will just replace random textures causing white/black textures everywhere.

Ryuuza, firstly try disabling Mipmaps in the options. If that doesn't help you'll need to use 64x (or if you feel up to it mix 128x blocks with 64x items to create a hybrid pack).
Profile pic by TsaoShin: https://www.deviantart.com/tsaoshin
User avatar
4 Posts
 x 0

Post 10 Dec 2019, 17:14

Ah, I though the ram mentioned was in reference to system RAM rather then VRAM which is more or less standardized which is why I opted to max out my system RAM when I built my current rig. I guess I'm stuck with 64x then as I didn't see the value in a TI level of RAM without a 4k monitor.

Reviewing my mods further turns out I had the default betterFPS mod installed rather then optifine. Reattempting with it OptiFine 1.12.2 HD U F5 and uninstalling betterFPS made no difference in load progress.

I'm out of options as far as I can see unless I upgrade further to a TI model of 2080's. I think prior to my current PC build I had a.... 970 GTX that ran 64x packs fine. I figured a worst I'd get poor sub 60 FPS with a 128x pack rather then this all or nothing sort of situation I seem to be in.

Thank you both for clearing things up.
User avatar
4 Posts
 x 0

Post 13 Dec 2019, 05:08

Ok, hold on guys. This isn't an issue about vRAM. vRAM doesn't even get utilized until a world is actually being generated for rendering. All the texture stitching is being done within system RAM.

In fact, this issue isn't strictly related to RAM at all. This issue is related to the way Java handles memory and the way things are being built. Simply put, with the right tuning there is no reason you shouldn't be able to launch this.

First off, I'm running a similar setup today.

System: Ryzen 2700x, GTX 1080Ti, & 32GB RAM.
Mods: DDSS mod pack + Millenaire + JourneyMap
Resources: 256x PureBD, 3D Blocks Addon, 3D Items Addon, Tech Addon, ExOf Addon, 128x DDSS Sphax, 128x Millenaire Sphax
Resolution: 4K

I've had only one issue (mentioned earlier in this thread), but I've been able to work around that and still put in nearly 100 hours of game time thus far. So what you are trying to do is certainly possible, but the issue you are having is a familiar one. Allow me to explain...

The memory you allocate in your JVM args is for the heap only. There is additional memory being allocated for other things on top of that. I've found a number of things that people typically say works well will not work at all when loading a massive amount of things like this. For example, I could never find any settings to launch using the G1 garbage collector.

There is also the issue of allocating too much memory. When texture stitching is complete, the memory usage skyrockets. If the usage jumps too quick, the JVM shuts down as it appears you encountered a memory leak. Java is greedy for memory, so if you allocate it, it will try to consume it (again, we are not strictly talking about the heap here).

I found that the args -Xms18G -Xmx18G worked the best for me. If I upped the heap settings to 20+, it would never launch and give me the same error you are seeing (again, the error just says it failed at that point).

To illustrate a few of these points, I'll share the memory usage graphs for both my system and video RAM. Take note of the call outs I made so you know where in the process it is.

Image

You'll see that video RAM isn't touched until a world is actually rendered, so if you can't get to the title screen then it has nothing to do with vRAM.
Image

Systems can be different in many ways and we are riding the edge on what is possible with Java here, so YMMV. But I'd try the following:

Use JVM args: -Xms18G -Xmx18G

Download process explorer and watch your memory curve. Post it up here if you fail to launch. I can help troubleshoot further with that info.

You can also try a different version of Java. You are using the built in version right now which is Java 8 build 51. I'd try the latest build of Java 8 (231). I've been more successful with this build. Openj9 could also work, but you'll need some more tuning arguments.

I also want to call out what Han Fox mentioned too. Mipmapping expands the size of the texture atlas, and in all likely hood, you won't be able to have mipmapping & all these textures, so you should probably set that to 0 as he suggested.
User avatar
2 Posts
 x 0

Post 24 Feb 2020, 21:35

Hey, guys, I've suddenly started to have problems with water textures behind the glass (any glass). It renders this weird white texture. (Dungeons, Dragons and Space Shuttles pack MC 1.12.2), no OptiFine. I've tried reinstalling the entire game and pack, older save, even tried OptiFine (toggled water textures and animations there), but no change.
It appears only on if you look thru glass from the side, top and bottom work fine.

Image
User avatar
Patch Creator
1498 Posts
 x 139

Post 24 Feb 2020, 23:06

Update - It appears the pack has finally updated to the latest version of Chisel. I have updated the downloads as required.

Sankurix, please redownload the pack and it should fix your issue.
If anyone would like to take over any of my threads please contact me. I will continue to host what I have done but expect no further updates.
User avatar
2 Posts
 x 0

Post 25 Feb 2020, 05:23

Novamanga wrote:
24 Feb 2020, 23:06
Update - It appears the pack has finally updated to the latest version of Chisel. I have updated the downloads as required.

Sankurix, please redownload the pack and it should fix your issue.
It did not fix the issue but I've found a workaround, thx anyway:-P
User avatar
4 Posts
 x 0

Post 28 Feb 2020, 02:37

Well, sorry for not replying but the above fix of adding -Xms18G -Xmx18G worked and stayed that way until the latest texture pack update which initially worked but had some mekanism fluid textures missing/not render for me. Tried to rollback to the old version to only end up with the old crashes happening non-stop. Downgrading to 64x sphax/current textures results in a horrible texture flickering. Mixing 128x Sphax with 64x mod textures results in crashes making this whole texture pack broken with my installation. Short of doing a full clean install of modded MC I can no longer play with this texture pack. I'll attach a crash report if I can get far enough again to get one.

EDIT: Of course the second I exhaust personal troubleshooting ability and post here for help 64x mod - 128x base works again. I'll note when rendering in game before it was giving me errors relating to mekanism and extra utilities 2.
Post Reply