Hi Alastair,
50-100k triangles comes down to 600-1200k floats that have to be
stored in memory. That's heavy stuff! Of course there's quite a bit of
redundancy, since many points arepart of several triangles, but I
don't think that this is considered for CGO.
There is a way though to get the trian
Hi Alastair,
The CGO file should come out something like:
cgo_obj = [
BEGIN, TRIANGLES, ALPHA, 1.0,
COLOR, 1.0, 1.0, 1.0,
NORMAL, -1.70693, -11.93375, 23.78227,
VERTEX, 39.96822, 39.96822, -36.33474,
VERTEX, 34.37814, 37.81595, -37.81595,
VERTEX, 38.78347, 35.25770,
Hi,
I'm using cgos of fairly large triangulated surfaces from other programs
and was wondering if anyone had guidance regarding the following:
- the cgo encoding of individual triangles is somewhat bulky and makes
for huge files which are slow for pymol to load. Is there an
alternative, more eff
