To put it short, what is one supposed to be able to do with P?
I guess something like that would be used internally for projections, but there must be a reason for exposing and load/saving it?

eetu.

NURBs.

Ah, thanks, good to know

eetu.

As an added question, is there a way to access P in a shader?

The reason I'm asking - I'm rendering very heavy point clouds, and the P
values take up 25% of the .bgeo (and I have a feeling they take up memory as well).

I'd like to use that data for something useful, like age, as it has to be there.

eetu.

can you access it through uv's u,v,w are the vector values, no?

eetu
As an added question, is there a way to access P in a shader?

The reason I'm asking - I'm rendering very heavy point clouds, and the P
values take up 25% of the .bgeo (and I have a feeling they take up memory as well).

I'd like to use that data for something useful, like age, as it has to be there.

eetu.

That's probably a bad idea. Though it may be possible to overload the Pw, it may have unexpected side-effects in some areas of code (i.e. projections). The Pw is closely intertwined with the P variable.

can you access it through uv's u,v,w are the vector values, no?

Ah, gotta check that. Although I've been under the impression that the w in position x,y,z,w is different from the w in texture u,v,w..

eetu.

my bad, I somehow missed the P and was just reading the w