#Incendium Crash Error 255 on Mac when entering Nether Reactor

19 messages · Page 1 of 1 (latest)

prisma mason
#

Hello! I've been having an issue while testing out a collection of mods for a Vanilla+ server with my partner who plays on a MacBook Pro. When I try to enter the Nether Reactor, my game will freeze and then crash about a second later with an error code 255 and the following message:

The game crashed whilst encountered exception while building chunk meshes
Error: java.lang.NullPointerException: Cannot invoke "net.minecraft.client.renderer.texture.TextureAtlasSprite.m_118367_(double)" because "sprite" is null

I've read online that 255 crashes are related to a larger issue with Apple and seem to be an unfortunately common issue with running Forge on a Mac, but was wondering if anyone else had any ideas or was experiencing the same thing?

analog mulchBOT
#
Your Support Question

Thanks for creating a thread! Be patient, and we will answer your question when we are able to. In the meantime...

• Check the FAQ by doing /faq to see if your question is already answered.
• Did you describe your issue thoroughly?
• Are relevant logs attached?
• Is your thread tagged appropriately?
• Ensure you've answered the questions outlined in our Post Guidelines.

When your question is answered, please close it with /close, or click the button. Thank you!

prisma mason
analog mulchBOT
prisma mason
#

and list of other mods

Screenshot_2023-10-28_at_2.48.02_AM.png Screenshot_2023-10-28_at_2.48.10_AM.png
cobalt acorn
#

forge has known problems when running through ARM

prisma mason
#

what is ARM?

cobalt acorn
prisma mason
#

Intel

cobalt acorn
# prisma mason Intel

Sodium seems to be causing the crash here, but you probably also want to check out citadel as it is throwing a huge amount of errors which are taking up the bulk of the file

#

you should also make sure that your drivers are updated

prisma mason
#

ah okay, makes sense as it was optifine causing the 255 when i had the issue previously. is there a specific setting in sodium that is causing it that i could potentially change or is the only solution right now getting rid of it?

prisma mason
cobalt acorn
#

from sodium's device compatability section: > We only provide support for graphics cards which have up-to-date drivers for OpenGL 4.6. Most graphics cards which have been released since year 2010 are supported, such as the...

AMD Radeon HD 7000 Series (GCN 1) or newer
NVIDIA GeForce 400 Series (Fermi) or newer
Intel HD Graphics 500 Series (Skylake) or newer

In some cases, older graphics cards may also work (so long as they have up-to-date drivers which have support for OpenGL 3.3), but they are not officially supported, and may not be compatible with future versions of Sodium.
OpenGL Compatibility Layers
Devices which need to use OpenGL translation layers (such as GL4ES, ANGLE, etc) are not supported and will very likely not work with Sodium. These translation layers do not implement required functionality and they suffer from underlying driver bugs which cannot be worked around.

#

discord markdown be goofin

prisma mason
#

oh brilliant, thanks so much for finding that! let me test updating drivers and loading with / without sodium installed and i’ll update my progress

prisma mason
#

yeah looks like it was a sodium issue, bummer. any recommendations on other performance mods i could use in its place?

cobalt acorn
prisma mason
#

no luck with embeddium unfortunately but no worries! thanks so much for your help