Transparent screen Avogadro - fix not available anymore on GitHub

Hello all,

Just installed the latest version on a pc running windows 10. The canvas is see through. I found that this problem has been reported, and apparently solved

However, on github there is a mention that the fix would be kept for 90 days only and doesn’t seem to be there anymore. I click the links for the executables there and it shows “page not found” On non-Mac platform, try using glBlendFuncSeparate by ghutchis · Pull Request #656 · OpenChemistry/avogadrolibs · GitHub

Is there any other way I could get these fixes? As a workaround I’ve installed the next to last version which is working fine, but I’d be happy to get the latest one.

Thanks

The current releases (1.98) should indeed have these fixes included. If you’re seeing transparency still, that’s a bug.

Oh well… sorry to hear that… The proposed fix of changing the backgroud color doesn’t work for me either. In case anyone wants to have a look, I have installed Avogadro 1.98.1 downloaded from Avogadro site. My PC is a HP Compact, Intel I5 2400. Intel (R) HD graphics 32 MB VRAM. If you want more details or information please let me know. Avogadro 1.2.0 is working fine.

I experience the same error in Ubuntu 23.10 installing through apt-get or openchemistry build. Transparent background, cannot load molecule.

@Stephen_Dale - can you provide a bit more detail on your GPU and driver? Intel as well?

00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics]
Flags: bus master, fast devsel, latency 0, IRQ 184, IOMMU group 2
Memory at 603c000000 (64-bit, non-prefetchable) [size=16M]
Memory at 4000000000 (64-bit, prefetchable) [size=256M]
I/O ports at 3000 [size=64]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities:
Kernel driver in use: i915
Kernel modules: i915

is this the information you were looking for?

That’s helpful. Seems like it might be an issue with Intel integrated graphics / drivers.

I’ll look around for a better solution.