Distorted on Windows 7

[iwersen]

Hi, I´ve two computers running Windows 7 and I could see the "library" example at the pannellum.org front page. The other examples at https://pannellum.org/documentation/examples/simple-example/ are distorted on both computers. Any ideas?

Image OK:

Image distorted:

Thanks and happy new year!

[mpetroff]

The homepage example is a multires panorama while most of the other examples are equirectangular images; as they're different types, different rendering code is used, which is why one can work when the others don't.

Does the web console (Ctrl+Shift+K on Firefox) show any errors on the page that doesn't work?

[milleker]

I have no issues with either multires or equirectangular images in Pannellum on either Windows 7 64 or 32 bit systems and Google Chrome. Will be happy to help test with the older OS. What browser are you using?

[iwersen]

Hi,

Thanks for replying!

I´m using Windows 7 and Firefox 50.1. The console shows: Error: WebGL: texImage2D: Incurred CPU-side conversion, which is very slow. pannellum.js:20:490 Error: WebGL: texImage2D: Incurred CPU pixel conversion, which is very slow. pannellum.js:20:490 Error: WebGL: texImage2D: Chosen format/type incurred an expensive reformat: 0x1907/0x1401

The Chrome 55.0.2883.87 console doesn´t show anything.

Thanks, Eduardo

[mpetroff]

Unfortunately, none of those errors have anything to do with the issue; all three show up in recent versions of Firefox whenever a JPEG image is used as a WebGL texture.

This appears to be some sort of strange device / configuration specific WebGL rendering bug. These are quite difficult to track down and fix even when I can reproduce them; when I can't reproduce them, as in this case, they're often next to impossible to fix. Sorry to not be of more help.

The rendering artifacts look sort of like #77, but as that was an issue with iOS, this is almost certainly unrelated.

[Windowsfreak]

It happens on my computer using Chrome 56, but not on mobile phones (Android/iOS). These distorted lines appear when edges of the cube faces are visible and disappear when they aren't. It reminds me of the bugs from the old days before people used atan2 instead of atan(y/x).

These artifacts seem to disappear if you zoom in enough.

[strarsis]

I have the same issue like @Windowsfreak on a pretty old computer that has been upgraded to Windows 10, maybe it is the GPU?

[mpetroff]

The cube edge issue manifests itself in certain browser / hardware combinations when the CSS 3D transform based fallback renderer is used. This is unrelated to the bug for which this issue was opened. There are similar screenshots of the cube edge bug in https://github.com/mpetroff/pannellum/issues/248#issuecomment-245821078.

[Windowsfreak]

I have found out that Chrome now disables GPU features on certain video cards that it distrusts. Thus a CSS fallback was used. There's not much one can do besides trying some weird VRML/Flash/Java/whatever...

[outOFFspace]

I have the same issue on Windows 10 (Firefox and Chrome) And there is no errors. I had this problem, when I was use threejs. I solved this issue by adding nearest filter: material.map.minFilter = THREE.NearestFilter (instead of THREE.LinearFilter)

[mpetroff]

I created a test page that uses nearest interpolation instead of linear interpolation: https://bl.ocks.org/mpetroff/raw/188340f1e66bbb316005c988fe661289/

Can you see is that fixes it? Unfortunately, it isn't a real solution because nearest interpolation looks considerably worse, but it's another datum that may eventually lead to a proper solution.

[outOFFspace]

Unfortunately, it isn't fixed this issue

[mpetroff]

Sadly, it's a graphics card / driver related issue, so I don't think there's much I can do about it.

[outOFFspace]

Anyway, thanks for trying