P: Problem when viewing images and video full screen (F key related)

Hello Ben, I am afraid this is not fixed. I am running the latest version of CC on a Dell XPS 15" (late 2015 version 16GB, 1TB SSD) running Windows 10, and clicking F often causes problems, sometimes the screen flickers fast between the photo and Lightroom, and I have to crash the page. Zooming in and out when in full screen mode is stuttery and slow, and clicking F again to get back to development mode/library is also slow. This used to happen on my old laptop (windows 8.1) and I put it down to the lack of pc power, however I am now running Lightroom on a high end laptop and still the problem persists. There are other performance issues as well. Please stop pushing out enhancements and work on producing a smooth stable platform, with noticeable performance improvements. I have the greatest respect for Adobe and the power they give photographers, but one of the biggest reasons of lightroom's continued success is that there is no real competition out there that offers the same functionality, but not addressing continued issues of bugs and performance issues will alienate patrons and at some point the competition will surpass Lightroom. Patrons hear the increased profit notifications from Adobe, mainly down to the subscription service, and expect an increased service.

I am using the latest updated LR 6.3 which has resolved, as far as I am concerned, all the problems/issues raised by Rick. I have been using all the tools available in the Develop module and switched to full screen and back without encountering the lock up problem.

I am using Windows 10 and replaced a week ago my hard drive with a Solid State Disk (SSD) and boy what a difference in performance! Specifically with Lightroom. Best investment I made lately.

Antoine

I'm seeing exactly the same as Rick describes above in CC 2015.3 on Windows 10 - the only reliable way I've found to avoid it is to switch out of develop before hitting F.

Would be great to get this fixed!

Using LR 6.3 Standalone Version. I keep it updated.

When I hit F for "Full Screen Preview" the screen flashes between full screen preview and a black screen. It seems to get caught in a loop flashing back and forth.

If I hit F again a box comes up with an option to Wait of Exit LR. This makes LR just about useless when I have to keep closing it down.

I am not using Spot Removal or Adjustment Brush. This happens when I just want to see pics Full Screen after edits. Also when cropping then hitting F to see how it looks in full screen when it locks up. Esc does not help.

I have read thru these posts for an answer. No help.

It seemed to start happening once in awhile, now happens almost every time I go Full Screen. How can I stop this from happening?

From all the posts here this seems to be an ongoing problem for years.

Also I started with the trial version online then bought the standalone version. I keep getting emails to try LR online again? I am Registered but Adobe does not seem know that I have the Standalone Registered Version?

Thanks, Rick

Yay! Although it still knocks you out of Spot Removal or Adjustment Brush. I can live with that...

Lightroom CC 2015.2.1 release

Develop Module

Select Spot Removal tool.

Press 'F' for full screen view. Lightroom locks in full screen mode (without the tool available for use), or sometimes freezes between screens.

Can only recover by using command tab to switch to Finder, then force quitting Lightroom.

Happens consistently when I carry out the above sequence of actions.

Late 2014 Macbook Pro, 3Ghz i7 processor, 16GB ram.
El Capitan 10.11.1

Thanks bud. Yeah it's a beast yet LR freezes on full screen. It's like driving a Lamborghini in a school zone.

Take a function that has worked for years and break it. Then fix it. Then break it. Adobe = Absurd, indeed.

BTW, that sounds like a heck of a system you have. I've got a MacBook Pro 15" Retina with the 2 GHz processor and only 8 GB of RAM. I can go get a cup of coffee when I Export more than a few files...

Just to note that we had this problem with version 6, and it was fixed in 6.1, Now the smart guys at Adobe released 6.2.1 and reincorporated the bug that they had already fixed!! Guys just go to your files and find the fix for haven sake, and release an update.