Sodium Reloaded (Unofficial)

Sodium Reloaded (Unofficial)

0 Downloads

PneumaticCraft: Repressurized fluid tanks render opaque gray

minimusubi opened this issue ยท 2 comments

commented

Bug Description

Sodium does not render some PneumaticCraft: Repressurized fluid tanks in-world correctly. Fluid Tanks and Liquid Hoppers should render the liquid that is stored inside, as well as the amount of fluid (as shown by the liquid's height). However, with Sodium installed, these blocks always render as fully opaque gray.

This seems to only affect Fluid Tanks and Liquid Hoppers, and only blocks placed in-world. Held versions of these blocks are not affected. Other blocks that process fluids seem to be unaffected. Several of these are shown in the screenshots below.

Visual example 1

Click to show

With Sodium

Notice that the indicated blocks are gray, and the held item versions are not.
Image

Without Sodium

Notice that both blocks and held items are correctly rendered.
Image

Visual example 2

Click to show

With Sodium

Image

Without Sodium

Image

Reproduction Steps

  1. Install
    • NeoForge 21.1.115
    • sodium-neoforge-0.6.5+mc1.21.1.jar
    • pneumaticcraft-repressurized-8.2.8+mc1.21.1.jar
  2. Launch Minecraft
  3. Create a creative world with commands enabled
  4. Open the creative inventory and get
    • Small Fluid Tank
    • Liquid Hopper
    • Water Bucket
    • Diamond Pickaxe
  5. Place one fluid tank and one liquid hopper into the world
  6. ๐Ÿ”Ž Note that the blocks render gray
  7. Right-click each one with the water bucket, several times
  8. ๐Ÿ”Ž Note that the blocks are still gray
  9. Run /gamemode survival
  10. Break each block with your pickaxe and do not pick them up
  11. ๐Ÿ”Ž Note that the items render correctly when on the ground
  12. Pick them up
  13. ๐Ÿ”Ž Note that the items render correctly in inventory
  14. Close the game and remove sodium
  15. Re-open the game and load the save
  16. Place the partially filled liquid blocks into the world
  17. ๐Ÿ”Ž Note that the blocks render correctly

Log File

latest.log

Crash Report

crash-2025-02-02_19.50.56-client.txt

commented

Thanks for the detailed reproduction steps.

commented

duplicate of #2814