I can also add that when I launch 1.18 on bedrock edition with this same launcher and same computer, I don´t have any issues. Don´t know if you do anything with this info but nonetheless...
This is the log from my latest attempt today: https://paste.gg/p/anonymous/7986f991077f4808be2ff5ab5352d9e6
World seed on this was: 652198451882068374
I have not done anything so far in this world. Just tried to test if it works.
This happens to me in every world I try to create in 1.18 and yes I have tried many many times on different new worlds.
Did not have this problem in 1.17
It also doesn´t matter what I am doing in the world but it always lags when "saving world" occurs. I could be mining, building or chopping wood and when game starts saving the world around me freezes (I can move normally this time but if i break blocks this time, I don´t get the drops) and when saving ends the game jumps back to the position prior saving.
I have tried everything at this point. I have uninstalled the game and java and installed them again. I have updated my driver and got an advice on discord that I should rename my .minecraft folder to oldminecraft and try launch the ghame again. Did not help.
Oh and I don´t have anything else open on my computer during this besides the game and I do not try to run server either. Only trying to play single player world on my own 😞
Checked my latest game log and this was the result. I don´t know what is wrong. https://paste.gg/p/anonymous/d19157842a6044a1947da8aea99d155a
My computer specs
I don´t understand this. When I load release candidate 3 world, the whole client starts laggy and the autosave issue continues. It doesn´t matter if I create totally new world or load an older world, it is the same lag.
But when I load the game in latest release 1.17 everything works totally normal and smooth. Am I missing something? It is annoying that I can not play the new mountains feature and if this is going to be on release, then I don´t know what to do 😞
Still having this issue in pre-release 8.
Yeah, did this to me in pre-release 5 and now in 6 is still doing this. So not fixed, at least for me it seems that way :/
I don't know what you guys did but now it is working! I didn't do anything. Just started my computer today and tried if it works and it does! So at least for me it is now working.