P: Unable to advance to the next photo

I understand that everyone who is on this page is still with this problem, which Adobe has not yet solved and whether it will solve at all, I do not see answers from experts here, there is no answer from Adobe itself. Are we now going to work on version 12.5 all the time ?

I am now back on 12.5, hopefully new update that solves it will come sooner than later, but 12.5. works fine after returning back.

Adding my experience to the conversation as it does seem to differ slightly from other reports in some ways.

I can't reliably replicate the issue, but I am having trouble advancing from one photo to the next with quite a bit of frequency. I'd say something like every 5-10 photos. It happens when I'm in the Develop module and, using the arrow keys to change images, the Filmstrip will advance, but the image display area does not, instead holding the previous image. Going back or forward and then returning to the desired image will fix the issue, and I'll be able to work again. Switching to the Library Module and then back to Develop will also temporarily fix the issue.

I hadn't been using Smart Previews, but read that it was potentionally part of the issue. Doing a small test, I found that images with Smart Previews resulted in no stuck images, but the loading of each image was noticeably slower. When rendering Standard Size Previews instead, I still experienced the issue, as well.

Making a change to the image settings didn't necessarily trigger the behavior. I made plenty of changes and had no issue advancing ot the next image. However, I don't recall the issue ever happening if I didn't make a change to an image, and there did seem to be some issue with advancing super-quickly after making a change, but again, this was inconsistent. Tried to replicate and couldn't reliably.

I'm not saving XMP files. I haven't tried disabling my GPU. I have restarted the program and my machine, and the behavior is unaffected. I was having the same issue on 13.0, as well.

Lightroom Classic 13.0.1

Build [202310121438-d2af310c]

Camera Raw 16.0

MSI GS66 Stealth 11UH-021
11th Gen Intel i7-11800H

NVIDIA GeForce 3080 Laptop GPU 16GB GDDR6
Installed RAM 64.0 GB (63.7 GB usable)

Edition Windows 11 Pro
Version 22H2
OS build 22621.2134
Experience Windows Feature Experience Pack 1000.22659.1000.0

Edited a couple more jobs since yesterday. It appears to be related to Smart Previews in my case. Working on 3 different catalogues, local raw files were fine and I edited as normal. Other jobs working on smart previews all had the same issue. Sometimes after editing a file, it would not advance correctly to the next file. Quickest workaround is two steps forward, one step backward. ie hit the right cursor twice, and the left cursor once, to advance by one file.
What makes it even more of a pain, is that it's seemingly random, and only affects some files.

Why adobe lauch this crap ? And the 13.01 still have the same problem. I return to 12.5 build my catalog and now turn to 13.01 and the same issue. 

I`m on Mac mini m1 base . And only working with .jpg in 3200px. Its impossible to work like that.

I did the same, it doesn't help anything, ADOBE do something this is getting tragic, instead of speeding things up you slow them down

[sorry, that should say that I can't re-render previews as I don't have the raw files]

Yep. Same problem here. Noticed mostly when working with Smart Previews. Makes work very very slow. 
I can re-render previews as I don't have the raws. I'm working on smart previews from my photographers around the country - the whole point is that they send the smart previews to speed things up, not make things painfully slow.

I also experienced this strange slowness/not displaying correct image in the filmstrip (Develop module) while scrolling through images in v13.  I reverted back to 12.5 and all edited images progressed (next/previous) fine again.  

I then installed the v13.0.1 update, opened up a catalogue that was exhibiting this issue. Selected all images, created smart and standard previews.  After that, the issue seems to have been resolved for me.  Perhaps it was a bad download/installation?  Not sure but it helped to downgrade, then install v13.0.1 and render previews.