Bridge not displaying pattern/fill layers from layered files

[Dan Skizz]

I have some layered tiff files where the model has been masked out and placed on a fake background which is a pattern-fill layer in Photoshop.

Bridge is not displaying the background layer and is instead displaying white, the thumbnail starts off displaying correctly but once the preview loads, it is blank.

I have attached a section of the file as is shows in Bridge and then as it shows in Photoshop.

[Imaginerie]

Not sure if it applies to you, but when I get thumbnails previews issues, it's 100% of the time because I need to purge my previews (you can access it in the preferences )

Alternatively, check if everything is OK in the thumbnail section of the preferences

particularly the first tick (and also depending on the size of the images it can take a while to fully display)

you can check and refresh simply by hitting F5 if that helps too.

[Dan Skizz]

Hey, thanks for the reply.

I have tried clearing the cache and previews, all that happens is that the thumbnails appear correctly for a split second and then as they load the background layer disapears and is displayed as a blank white. It only occurs if the background layer is a fill layer, if it is rasterized in PS then the layer displays correctly...

[Dan Skizz]

I just tried a quick experiment and it seems to only affect the appearance when the background layer is a 'Pattern' fill layer, if it is a 'Solid color' fill layer then it displays correctly in Bridge.

[Imaginerie]

Could it be a problem with the files being too big for your displaying settings? (ie: in my second screenshot, the first entry, where mine says 1000 mb).
I am saying that because if your patterns are like mine, they generate quite big files.

also still in the preferences, you got this option, that I always untick as it slows down/glitches the previews

[Dan Skizz]

I did actually already try raising the file size thing to something ludicrous and turned off the hardware rendering... it's so weird!

[Dan Skizz]

file sizes are around 70-80mb, so they're nothing crazy

[Imaginerie]

Yes, it shouldn't be happening with those files. I'm stuck for ideas now, let's see if someone have better ones!

[Dan Skizz]

What is also strange is that this seems to only be happening to layered tifs, if the file is saved as a PSD then it displays correctly!

I've tested this out on both Mac and Windows machines and the result is the same.

[gary_sc]

Hi @Dan Skizz I'd call this a bug. Good testing (and patience).

I'd suggest you report this here: https://adobebridge.uservoice.com/

You can also link this thread in your report.

[VarunVarshney]

Hi @Dan Skizz 

Thanks for reporting this issue. We appreciate your help in reporting this to us.

For investigating further, it would be very helpful if you can share a sample image with us.

You can share it at : sharewithbr@adobe.com

We will keep you posted on the progress on this.

Regards,

Bridge team

[pankajg6675616]

Hi @Dan Skizz,

Thank you for sharing the file.

We are able to reproduce this issue and added this to our engineering issue pipeline.

We will keep you updated once the issue gets fixed.

Regards,

Bridge Team

[Dan Skizz]

Hi,

Has there been any update on this? It really is a big problem for us, and I am starting to look into a replacement for Bridge as it is currently unusable.

[Dan Skizz]

Hey, I see there's be another update for Bridge but this issues still hasn't been addressed. Do you have a timeline for when this serious issue will be fixed?

[Dan Skizz]

Hi @pankajg6675616 has there been any update for this issue? It seems to still be happening...

[Dan Skizz]

Hi,

Has there been any update on this? It has been months since this pretty serious bug has been raised with you...

[Dan Skizz]

I see that there has been another update for bridge and yet this issue is still happening, do you have a timeline for when this might be fixed?

[Felicity28079567heu8]

I have had the same issue for around a year. I rolled back to the 2022 version of bridge to resolve. Have just installed the new version and found the issue still exists for me to.