Placing and Moving Images Changes Opacity
If I place an image and then try to move it within the bounding box, the opacity appears to change to around 50%. However, the opacity is still set to 100%. I can correct it by hitting Undo which reverts the image back to normal. From what I can tell, it is only a visual bug. Exporting the image doesn't show the change in opacity.
I haven't been able to reproduce this issue consistently but would say it happens around 80% of the time I try to move an image. Another interesting thing is that if the issue happens and I duplicate the image and change it's opacity, the original image reverts to normal again.
Brian S
shared this idea
Hi ,
Thanks for reporting this issue. We are already aware about this issue inside “InDesign CC2017”.
Hence, we have fixed this issue inside our latest release “InDesign CC2018”. Please try it out.
If you still face this issue inside our new release please do let us know.
-
Bartosz
commented
Same here. For me works transforming a frame with troublesome picture and undoing that action. After that I can freely manipulate the picture within the frame.
I've made a screen recording of the problem.https://www.youtube.com/watch?v=NpcN1486GUw
What you see here is:
1. Dragging an image to a frame
2. Moving it and it changes transparency
3. Undoing the image placement
4. Dragging the same image
5. While holding CMD I drag the frame edge so it transforms the image within the frame – This is the workaround I found that helps (other than deleting the frame or undoing the placement). Undoing the transformation makes the image not change the transparency again.
6. I place another image, manipulate it and show Effects panel that says the image is 100% opacity. -
Calvin
commented
Pictures reduces transparency to 50% on it's on when moving them by the "direct-selecting tool", without changing the transparency.
I'm working with the GPU preview, when it's disabled the problem is temporary solved.
It's really killing my workflow, and i hope to get some updates in the near future.
All the best,
Calvin.
-
Christopher Graf
commented
Same problem here. Seems linked to GPU acceleration and was introduced with one of the latest updates.