P: The zoom does not work properly after the update.

[AARDVARK7]

After the last update, when I click on the image to zoom in, it sometimes zooms out a little, then partially zooms in, finally zooming fully. It is slow, intermittent, and infuriating.

What have Adobe done with this, as it was fine before?

[SuperFabe]

I have not experienced the same behaviour of LR. In the Library or Develop module, with or without the graphics acceleration. I using a Win 10 laptop.

[Victoria Bampton LR Queen]

Can you confirm your operating system and system specs please? Easiest way is to go to Help menu > System Info and copy/paste the contents.

[Just Shoot Me]

Check the actual size in pixels the images are. Smaller pixel dimensions will cause LR to first zoom out and then zoom in with a second click. This is a New Feature. Check the Navigator section in the Library module for FIT. FILL, 1:1, 2:1 and so on to see what exactly is happening.
With smaller pixel dimension images Fit will actually be Zoomed in. 1:1 will be a smaller image on screen and Fill will zoom in but be pixelated.

[AARDVARK7]

I'm not sure how much you want, but here it is:


Lightroom version: CC 2015.8 [ 1099473 ]
License: Creative Cloud
Operating system: Windows 10
Version: 10.0
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.5 GHz
Built-in memory: 32718.4 MB
Real memory available to Lightroom: 32718.4 MB
Real memory used by Lightroom: 786.1 MB (2.4%)
Virtual memory used by Lightroom: 873.0 MB
Memory cache size: 282.6 MB
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1200, 2) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info:
GeForce GTX 770/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 369.09
Renderer: GeForce GTX 770/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: C:\Lightroom\Lightroom Catalog.lrcat
Settings Folder: C:\Users\Peter\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) AdobeStock

Config.lua flags: None

Adapter #1: Vendor : 10de
    Device : 1184
    Subsystem : 84651043
    Revision : a1
    Video Memory : 2017
Adapter #2: Vendor : 1414
    Device : 8c
    Subsystem : 0
    Revision : 0
    Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: Uninitialized
Direct2DEnabled: false
GL_ACCUM_ALPHA_BITS: 16
GL_ACCUM_BLUE_BITS: 16
GL_ACCUM_GREEN_BITS: 16
GL_ACCUM_RED_BITS: 16
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: GeForce GTX 770/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.50 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.5.0 NVIDIA 369.09
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

[AARDVARK7]

Thanks for the help, but I do appreciate how the zoom feature should work.
In my case, it isn't doing that.

All the images are the same size, RAW files and I'm looking to zoom into 1:1. Sometimes, for a moment, they zoom out fractionally. Others they zoom in to a degree and then fully shortly afterwards.

I was wondering, for the 'zooming out' whether it was working on the reduced resolution smart preview in error, rather than the full file. I do understand that in smart preview mode I still won't get all the details, but the size should be correct.

As it is, the zoom works, but in this slow, delayed, and stuttering way. I want it fixed!

[Just Shoot Me]

So you are using Smart Previews and the files this zoom issue occurs  on have smart previews?

[AARDVARK7]

Yes, but smart previews are supposed to work like the full files, just not rendered with the same detail.

[AARDVARK7]

UPDATE!

There is another issue concerning this behaviour which I hadn't noticed immediately because I was so put off by the stuttering zoom.

Normally, you would click on the point at which you want the zoom to centre, which is fairly obvious. However, now it remains centred on the desired bit for the first part of the zoom, but when the zoom completes it centres on the whole frame, so you have to drag to the area of interest.

I just want to scream!

[Sunil_Bhaskaran]

We are not able to reproduce the issue.
I have sent you an e-mail offlist to understand the issue better.

Thanks,
Sunil

[AARDVARK7]

Sir,

I have sent you a link to a video showing the behaviour. As I mentioned in my message, there is nothing, absolutely nothing, quite as infuriating as a large company suggesting that someone with a problem is the only one in the entire world who has suffered from it. The idea is as ludicrous as it is insulting.

[Victoria Bampton LR Queen]

No one's suggesting you're the only one in the world Peter - just that they couldn't reproduce it yet (which makes it nearly impossible to fix). Sometimes this is due to a specific combination of hardware/software/drivers on your machine - and with the wide variety of hardware combinations on Windows, this is often true. Other times they're just missing a step to reproduce it. It's never intended as an insult.

[AARDVARK7]

Perhaps, in this case, it may be true, but when you have had so many occasions over the years, regarding all manner of software and hardware produced by vast businesses, and get this corporate head-scratching, it does tend to make a person very cynical.

I have had literally dozens and dozens of instances; from cars to cameras, phones to printers, graphic software to graphic tablets, and all have followed the same pattern.

First I describe the problem, so the response is to ask me to describe the problem. Then they take it to the next level and I'm blamed, so get asked to reset, reinstall, update, try again, etc.. After all, it must be me! Then we get this, "We can't reproduce it". Usually, the end consists of two possibilities: either the admission, "Ooh yes, you're right, there is a problem!", or "Yes, it doesn't work, but tough. You'll have to live with it.".

This is despite the large sums of money involved (sometimes thouands) and, even in the first instance, I could be waiting years for a solution.

So, forgive me for being blunt, but Adobe are a very rich organisation to which I have paid (and continue to pay) considerable money.

[Victoria Bampton LR Queen]

Completely understand your frustration. The reset, reinstall, update etc. routine is rarely a suggestion that you're at fault, but that there may be an issue that's easily fixed that way. It's amazing how often that works, especially with resetting preferences. Still doesn't mean it's your fault, but it's a lot quicker than dragging you through all of the debugging steps to try to find the original cause of the problem, which still might not be found. 

There are some issues that are just really horrible to try to find, because they require you to be standing on one leg, patting your head and rubbing your belly at the same time, in a specific room in your own house. Ok, silly analogy, but you get the idea.

When lots of people start reporting the same issue, it's possible to spot a common theme, but when it's just one and the engineers can't figure out how to reproduce it, it requires more troubleshooting from the user too. You can't just throw money at a problem like that, because you still won't get any closer to finding the problem. If they can reproduce the problem on their own machines, it's far far far more likely to be fixed.

[chrisbartow]

If you disable "Use Smart Previews instead of Originals for image editing", does it still do it?

[AARDVARK7]

Having checked, I'm not even sure how to answer!

If I went into preferences and unchecked the box, clicked OK, and then immediately tried to zoom, the behaviour was the same. Of course, I wasn't sure if the effect would be immediate, so I restarted Lightroom and it appeared to behave in the same way.

However, the 'Smart preview' box was ticked again without my intervention. In fact, it wouldn't remain unticked! No matter what I did, no matter how I left the preference screen, no matter how I restarted Lightroom, that box defaulted to ticked.

Even more bizarrely, having just gone back into it to confirm my steps for this reply, it now seems to have remained unticked, after dozens of attempts.

Am I missing something here??!!!???

By the way, the zoom now behaves correctly, when not using previews.

P.S. I've just tried to retick the box and it's not having it. AAAARRRGGGHHHHHHH!!!!!!!!!

[AARDVARK7]

Clearly, after some experimentation, this is a 'smart preview' issue. Not only in the implementation of zoom, but the selecting of the option to use them, or not.

I have tried to resolve a reason for it, but it doesn't seem to relate to the camera, whether smart previews are just built or created a while before, whether the cache is purged or not. In fact it seems almost random.

The next step is to completely uninstall and try again, but that is a royal PITA.

[chrisbartow]

Yea, I'm experiencing the same thing.  Since the smart previews are smaller resolution, I think it's just getting confused.  You have two choices.

1. Keep the box unchecked and use full size previews.

2. Before they added this box, you could do the same thing by 'disconnecting' the raw files which would force it to use smart previews.  So if you put your raws on an external drive, build smart previews, then disconnected the drive, Lightroom is blazing fast.  This would force it to ONLY use the smart previews so you won't have this issue.

Good luck. I hope a miracle occurs for you and Adobe fixes it.

[Sunil_Bhaskaran]

Thanks, Peter and all.
We have reproduced this issue. A fix is underway.
This should happen only once when the Smart Preview is zoomed for the first time.

Thanks,
Sunil

[AARDVARK7]

I'm sorry if I express some dismay, but your reply is bewildering.

Only now have you 'reproduced' the issue, when it wasn't out of the ordinary and, apparently, merits a fix? You have just repeated exactly the same behaviour as I described in a reply to Victoria Bampton. Why do companies do this??!?!??

What should happen is that if you have made a mistake and released software with an obvious bug, ADMIT IT!!!!!!!! Then we can get on with our lives while you do what you need to do.

Finally, you still need to explain your post. Will the fault still happen 'just once' after the fix, or are you just saying what I already know? I suspect you should have said:

"I am very sorry and apologise for the inconvenience, but we are aware of this issue. The existing problem should happen only once when the Smart Preview is zoomed for the first time, but a fix is underway and we will contact you when it is released".

[tmickow]

Peter - believe me, I'm not trying to start an argument, but all the venting here isn't doing anyone any good.

You found a bug in a new release.  Members of this community helped reproduce and identify the issue.  An Adobe rep acknowledged it and said a fix is forthcoming.  And all that happened within a couple days.  That's a pretty darn good example of how this process is supposed to work.  Now the ball's in Adobe's court to get a fix implemented in a reasonable amount of time!

Bugs are annoying and mess with your productivity, but take a deep breath and hang in there.  The sun's going to come up tomorrow and everything's going to be ok.  This is certainly not the worst bug that's slipped through the Lr QA/QC cracks over the years...

[AARDVARK7]

Thank you, Tom, for completing the full sequence of events that happens every time I raise an issue about something. It doesn't matter what it is, or where, but the pattern is repeated over and over again. I have to confess I am mystified why.

So, for my very last comment, this is a typical story:

I have a problem. Something I have paid for does not do what it should. This is not my imagination, or my fault. It is a definite problem which, ideally, needs to be rectified. Of course, it isn't the end of the world, but as I've paid good money I look for a solution.

I try to find someone who can directly address the issue but, more often than not, the business responsible make such contact very difficult indeed. I have to cast my net wider and I ask, in general terms, to the world in general if anyone knows of a solution. I don't rant and rave. I don't jump up and down and threaten to sue for compensation. I just ask a very simple question.

The first response is almost always asking me to describe the fault, despite my doing so in the very first request. Then, not always in the same order, I'm told: "There is no fault", "We don't have a fault", "It's your fault". While not of any great significance, it becomes rather tiresome, especially as I have experienced it so often before, so I wearily tell people that they are mistaken and there is a genuine problem. Often the denials and blame are repeated.

Curiously, though I'm expected to accept any criticism of my situation, people explode with indignation when I contradict them and I'm accused of being some sort of ungrateful troublemaker, neither of which is the case.

In the meantime, the people who should be dealing with the issue hide behind their anonymity. Eventually, as in this case, they do admit the problem. No one says, "We're sorry, Peter. We're sorry you have this problem and we're sorry we doubted you." If I'm very, very lucky, they'll say as they have here, "We'll fix it when we get around to it". Maybe, just maybe, a fix will appear in due course.

To go back to this particular Lightroom bug, I suspect this fix will just be the next version in another 8-12 months and when it comes along, no one will contact me to let me know it is sorted or to say thanks for informing them.

Tom, you say I should be pleased about the response I got, all within a couple of days. In reality, it has taken those days for Adobe to admit there is a problem, when it should have taken about 5 minutes.

I'm a 'one man band' and pay Adobe something like £500 per year, every year, and have paid them many thousands over the years. I think the very least I and anyone in a similar position should expect in return would be just a little support that doesn't rely on the charitable help from other private citizens. A forum that shares knowledge should be the last line of support, not the first.

Oh, by the way, the Adobe rep appears to have completely ignored my request to clarify his cryptic message. I'm not in the least surprised...

[Just Shoot Me]

QUOTE:
Thanks, Peter and all.
We have reproduced this issue. A fix is underway.
This should happen only once when the Smart Preview is zoomed for the first time.

Thanks,
Sunil
END QUOTE:
I don't find the official response cryptic.
It is a Smart Preview issue and should only happen the first time the SP is zoomed. After that it should work as normal. Zoomed in or out with no noticeable delay.

[tmickow]

Ugh...I knew I shouldn't have commented.
Good luck, Peter.  If every little issue gets you this ramped up, you're going to have a grabber before you're 50.

[Victoria Bampton LR Queen]

So just to close this off, which bit was cryptic? Just so we can make sure it's clarified for you?

When the bug is fixed - I would hope in the next update, which are usually 2-3 months, sometimes less - this thread will be updated. If you're getting email notifications, which is on by default, you will therefore be notified when it's fixed.

[AARDVARK7]

I had no intention of posting again, as I just seem to receive smart-alec comments and completely wrong assumptions. I have a fault, I explained clearly my positon, and I'm not 'ramped up'. I have no idea why people take it on themselves to jump in if they don't have an answer, or don't care. It's hardly my problem if people are unable to comprehend.

Anyway, you have asked a direct question, so the answer is this.

Sunil wrote, "A fix is underway.
This should happen only once when the Smart Preview is zoomed for the first time."

'Should' implies an intended consequence. Therefore, the way he wrote his message it appears as though when the fix has been created the behaviour will be as intended. Given that he said it 'should' happen once, it appears as though the very problem I have now will continue. If that is not what he meant, he should not have written it that way.