If you like our work please consider becoming a Supporter and get an ad-free experience.
[128x - 32x] Project Ozone 1, 2 & 3 [MC1.7, 1.10 & 1.12]
Maybe. The amount of problems 128x seems to create with people not being able to run it and then complaining and asking why is starting to grind on me. I'll think about it. I'm working till Saturday, so there won't be any release before then.
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.
As requested I have made a 128x pack for Project Ozone 3. I will now say this once, and once only. If you cannot get the 128x pack to work, use the 64x.
128x Project Ozone 3 I have also updated the 64x and 32x with new Mekanism textures to fix the model issues with Mekanism's latest version.
128x Project Ozone 3 I have also updated the 64x and 32x with new Mekanism textures to fix the model issues with Mekanism's latest version.
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.
https://hastebin.com/odoxunavoq.rb This is new (using the 128x pack).
You're bumping in to an issue where the game is running out of RAM when building the resources (textures/models).Mythixdino wrote: ↑25 Apr 2019, 21:41https://hastebin.com/odoxunavoq.rb This is new (using the 128x pack).
Either assign more RAM to Minecraft or use lower resolution textures.
Profile pic by TsaoShin: https://www.deviantart.com/tsaoshin
Uhm, no. I don't think it's that.
I've tried with 16Gb as you can see in the crashlog. Then after that I tried 24Gb but that still crashes with the same message.
Before 128x was released for this pack I've been using the atm3 remix patch and no such issue was present. I've also ran it with atm3 remix itself (ditto).
So I would like to know why I'm able to use the remix patch but not this one (remix is bigger?)
Overall the stack trace is just complaining about an error during stitching.
The only times I've seen that sort of error are RAM/VRAM issues with Forge, which is why I suggested that first..
The error refers to openblocks:canvas-0 being the thing being worked on at the time of the error.
Besides RAM/resolution the only things I can think of are:
- check that "Fast Render" is enabled in OptiFine's settings
- try without OptiFine
- try without foamfix
- try removing any OpenBlocks textures from the pack
- try updating Forge
Profile pic by TsaoShin: https://www.deviantart.com/tsaoshin
At the time no one else stated that they were having issues.Mythixdino wrote: ↑01 May 2019, 20:43Then an admin claims I'm the only one having the issue. How counter-intuitive.
If you're going to be ungrateful when someone tries to help you may find no one will help you at all any more.
Profile pic by TsaoShin: https://www.deviantart.com/tsaoshin