Archer_Legend

Thank you for marking this solved, this way the thread will continue on MCL-23121

Can you reopen this bug report and mark the latest one I made as duplicate?

I had to duplicate it because at release the new bugtracker didn’t allow to edit the bug report to add new versions

I can confirm this behaviour too on Windows 10.

My hardware is Core i7-8565U and MX230. The GPU driver version is 576.02

The game is run in its default location.

The bug started with the version I used in the report as it was not there before. Furthermore I am not referring to the log which gets outputted when you start a Java installation which is correctly stored in the logs subfolder in the installation location but I am speaking of the launcher_cef log which gets output every time the launcher is started. There used to be a log subfolder directly into the .minecraft folder where the launcher stored its own logs (not the logs you get when launching an installation as I said before).

With this new reporting platform it seems that I can no longer edit the affected versions / the bug details despite being the one who opened it…

The issue is still present on the latest version

I can confirm it is still present in 1.20-pre7

I can confirm that the issue is still present as of today the 21st of March 2021 in the latest launcher version for Windows 10/11.

Can confirm in 1.18.1

1.16.5: avg fps 120

1.17.0 and 1.17.1 rc1: avg fps 100 (83 when profiling)

Windows 10 Pro

Build 19043.1055
Windows Feature Experience Pack 120.2212.2020.0

Cpu: Intel Core i7 8565U running at base clock throught all the tests (1.8ghz)

Gpu: Nvidia geforce MX230, driver version is 466.77

Don't want to be negative about how this Jira report is going, but I think that reports done are not so useful.

The report is open and has normal Mojang priority so it means they are aware this bug report exists. I think that at this point we can stop hoarding numbers of our computers for a few reasons:

• the test being done is static: standing in 1 spot and measuring the "idle" fps does not represent how the game works or how we would play. A test using a moving minecart rail would be much more usueful with a frame by frame logging and not a mere avarage at the end of the test to report here

• settings are kind of CPU bound since the res. is 720p and chunck render distance is relatively low

• some results are quite odd and I think that are due to people having some issue with video drivers which they could solve by DDUing their drivers and then clean installing them again, also some results run on old drivers despite much newer ones being available for their GPU

• what we are experiencing may partly recoverable but it is definetely not a bug since the engine has changed and also chunck culling has changed so it is debatable whether we are loosing performance or the one we got before just higher due to less accurate chunck calculations or some other bug

At the end of the day the devs have their pcs too and they can for sure test performance on theirs and get complete and more accurate and more useful data compared to the one we could ever provide here and they have all the insight needed on the game changes and game engine itself.

So I would say that since this "issue" has been noted by Mojang which is the whole point of opening this thread we can for now stop reporting numbers since they will look into it and numbers here do not help them sort this out in a better or faster way.

🙂

Update is being split into 2 parts, the generation will come during the holiday update.

A lot of the blocks will come during summer update which is the 1.17 which is now under pre-release phase.

As written in every changelog if you want to test the new generation you need to download and install the datapack which is linked in the changelogs for every snapshots.

Hi guys! Unfortunately I did not see this issue before opening mine (MC-225941) ! So I eneded up making a costum run on a benchmark world I made and I used 16 as rendering distance which underlines the problem a lot better than 12 chuncks on my system. Also I run the "benchmark" in the latest release which also uses java 16 instead of java 8.

Here I re-post my report so everything is tidy and in one place:

 
I did some testing using the integrated frametime counters inside minecraft accessible via F3 + ALT

The device specification are as follows: Core i7-8565U and Nvidia MX230, the gpu driver version is the latest up to date: 466.47, windows version is 21h1.

Testing methodology

The test was run by using a client created via the launcher based on minecraft 1.16.5 with the default java (8) and another one created in snapshot 21w20a with the default java (16.0.1). Both clients received 8 GB of allocated RAM on a system total of 16GB DDR4 running at 2400mhz CL17 running in dual channel. No applications where running in the background while running the test.

To perform the test I created a world in 1.16.5 and made a minecart railtrack to be able to standardise the logging. I let the game load all the chuncks in the track at least once after I finished building the track and then I closed the game after putting myself in the minecart in the orientation to run the benchnark and then I closed the world, I run the optimise world and made a backup of it in order to be able to re-use it for further snapshots under the same conditions. I extracted another copy and optimised it in 21w20a to convert it. At this point I started benchmarking: I waited precisely 10 seconds after being spawned in the minecarft for the fps to stabilise and I begun logging and started moving with the minecart.

Furthermore I created the same world in 21w20a with the seed (no datapack) and I made the same track and I compared the results to world in 21w20a but converted from 1.16.5, both tests on the newly generated and converted world gave the same results so they are functionally the same and I will report on the converted world for simplicity also for further snapshots in which I will use a converted from 1.16.5 world.

The settings where smooth lighting to maximum, max fps to unlimited, vsync off, render distance 16, biome blend off, particles to all, entity render distance 150 per cent, fullscreen on at 1080p, clouds on and graphics was set to fancy. Via the gamerules I locked the daylight cycle, time was set to noon, weather was set to clear and mob spawning was not allowed. No mobs or items where in the benchmark rendered area because I used carefully the kill command to get rid of everything which was spawned before I type the gamerule to disable mob spawning.

Further update in comparison to the day after I created the issue: I did the same testing also by using the iGpu (intel HUD 620) and more or less the same performance degradation in percentage is experienced like what happens with the Nvdia dGpu. I have no plans to record the iGPU runs because I use the iGPU to record the screen and so this would impact the iGPU performance run, this latter does not happen when I record the dGPU since as I said it is the iGPU to do the recording job.

For further clarification I link the private youtube video I made about the 2 of the test runs I recorded.

NOTE: the clips only contain precisely the moment the cart starts moving and they end 2 seconds after going till the end of the benchmark run. The 2 benchmarks in the video have the same amount of frames and are exactly the same lenght.)

Here is the link to the private video: [https://youtu.be/QFO4NHPXb9M]

I am reporting this because Open GL 3.2 and Java 16 where introduced to modernise the game engine and to give developers new development tools. I know that Mojang has an eye of regard about how the updates can impact performance and I also know that the changes and bugfixes made with each update can change the performance and sometimes make the game run less well but only on the surface because the bug or thing which was changed was acting in an unintended and wrong way beofore the fix. Therefore personally I am fine with the appearent impact if the appearent boost we had before was due to something not acting properly, however I still wanted this to be brought to the attention of the developers just to make sure everything is acting as they intented in the current snapshots.

I hope this feedback can be useful.

Good news! I worked on it an hour last week and I found out what causes the problem and how to fix that! I will make a quick youtube video soon (if it turn out to be crap don't blame me, I am not into making vids and I want to provide a solution for everyone)

I sadly realised that in 1.15.4 I cannot right click on my cat and my dog. Is there a way to modify them via game files to fix them?