Arch Linux

Roken

Member

From: South Wales, UK

Registered: 2012-01-16

Posts: 1,372

Secondlife/OSgrid

I haven't had this problem since I swapped out from an ATI 6670 to an NV GT670, but here goes.

In world I'm getting stray polygons filling the  screen at random canmera angles. With the ATI Card it was down to the VBO, but I can't fix as easily with NV.

If you need screen grabs to advise, let me know, but basically. it'sd polys that shouldn't be there being there. I do 3D  gfx work and it's similar to using cloth in cinema 4D without a cloth (nurbns for pre v16 users) and effectors.

Edit - I should add  - using Teapot viewer becasue that''s the only one that fully works with video and audio

Last edited by Roken (2015-02-12 21:27:56)

---

Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus B550-F Gaming MB, 128Gb Corsair DDR4, Fractal Design Define 7 XL, 5 HD (2 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

/ is the root of all problems.

GordonGR

Member

From: Thessaloniki, Greece

Registered: 2011-11-07

Posts: 276

Re: Secondlife/OSgrid

I haven't had this problem since I swapped out from an ATI 6670 to an NV GT670, but here goes.

In world I'm getting stray polygons filling the  screen at random canmera angles. With the ATI Card it was down to the VBO, but I can't fix as easily with NV.

If you need screen grabs to advise, let me know, but basically. it'sd polys that shouldn't be there being there. I do 3D  gfx work and it's similar to using cloth in cinema 4D without a cloth (nurbns for pre v16 users) and effectors.

Edit - I should add  - using Teapot viewer becasue that''s the only one that fully works with video and audio

I had the same issue only once, with Intel card and Singularity. I logged off, cleared cache (rm ~/.secondlife/cache) and it never happened again. So it can just be something wrongly downloaded.

However, Teapot is ancient (last updated: 2012-09-08). The developer got bored, plus it was just Kokua slightly modified. I recommend you try other viewers. More importantly, I recommend you try the official viewer, see if the problem appears there. If not, it's your viewer's issue. If so, it could be the driver (ATI's problem) or LL's code (which is inherently passed to all third party viewers) and you should file a bug report with LL.

---

Intel(R) Celeron(R) CPU E3400 @ 2.60GHz, x86_64. AURs.

“No one without the knowledge of geometry may enter.“ Plato.