MC-198396Chunks the player is standing in take longer to load depending on maximum render distance.
Render distance naturally lags the game, so 2 is most efficient, and 32+ is least. When in a chunk after teleporting out of your loaded chunk area, the chunk the player is currently standing in will take longer based on that render distance. In single player: under 2 seconds for 2 chunk render distance, and 2.5-3 seconds with 32 chunks selected on Fabulous graphics. On Fancy, it is a range of 1.5-2 seconds(fast being the same as fancy). It is a small, but noticeable issue.
Both photos I uploaded were taken 2 seconds apart after teleporting out of my render distance by using the command: /tp @p ~10000 ~ ~10000. Every single test used this command for the test.
SSD tests showed not difference on rendering> My SSD is Crucial BX500 240GB 3D NAND SATA 2.5-inch SSD.
Disc Drive: WD Blue WD20EZAZ - hard drive - 2 TB - SATA 6Gb/s | WD20EZAZ
Environment
CPU: 16x AMD Ryzen 7 2700 Eight-Core Processor. Java 1.8.0_51 64bit. 4096mb memory dedicated to my instance of the game. Radeon RX 580 Series Graphics.
Created Issue:
Chunks the player is standing in take longer to load depending on maximum render distance.
Render distance naturally lags the game, so 2 is most efficient, and 32+ is least. When in a chunk after teleporting out of your loaded chunk area, the chunk the player is currently standing in will take longer based on that render distance. In single player: under 2 seconds for 2 chunk render distance, and 2.5-3 seconds with 32 chunks selected on Fabulous graphics. On Fancy, it is a range of 1.5-2 seconds(fast being the same as fancy). It is a small, but noticeable issue.
Both photos I uploaded were taken 2 seconds apart after teleporting out of my render distance by using the command: /tp @p ~10000 ~ ~10000. Every single test used this command for the test.
Environment
Using 1.16.2 vanilla, fabulous graphics. CPU: 16x AMD Ryzen 7 2700 Eight-Core Processor. Java 1.8.0_51 64bit. 4096mb memory dedicated to my instance of the game. Radeon RX 580 Series Graphics.
Attachments2
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Render distance naturally lags the game, so 2 is most efficient, and 32+ is least. When in a chunk after teleporting out of your loaded chunk area, the chunk the player is currently standing in will take longer based on that render distance. In single player: under 2 seconds for 2 chunk render distance, and 2.5-3 seconds with 32 chunks selected on Fabulous graphics. On Fancy, it is a range of 1.5-2 seconds(fast being the same as fancy). It is a small, but noticeable issue.
Both photos I uploaded were taken 2 seconds apart after teleporting out of my render distance by using the command: /tp @p ~10000 ~ ~10000. Every single test used this command for the test.
SSD tests showed not difference on rendering> My SSD is Crucial BX500 240GB 3D NAND SATA 2.5-inch SSD.
Disc Drive: WD Blue WD20EZAZ - hard drive - 2 TB - SATA 6Gb/s | WD20EZAZ
![[Helper] osfanbuff63](../../../data/avatars/users/94394.png){kind=small}
Using 1.16.2 vanilla, fabulous graphics.CPU: 16x AMD Ryzen 7 2700 Eight-Core Processor. Java 1.8.0_51 64bit. 4096mb memory dedicated to my instance of the game. Radeon RX 580 Series Graphics.
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
![[Mod] Anthony Cicinelli](../../../data/avatars/users/10122.svg){kind=small}
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
I am unable to reproduce this issue in 1.17 Release Candidate 1.
I'm unable to reproduce this, the chunks the player is in are getting loaded at the same speed for me no matter the render distance - which does make me believe that it may be a hardware limitation on your end - best guess would be disk speed.
My disc speed is 5.4k RPM since I am using an instance not on my SSD. I will edit this with my SSD results.
I confirmed it for 1.16.3
Saisho Bready you don't need to comment what version it affects. Your the owner of this report just update it in the affected versions category
I can still reproduce this issue in 1.17 Release Candidate 1.