Re: [Plib-devel] Work outstanding.

[Wolfram K. <w_...@rz...>]

Steve wrote:

>> >For example, it would be GREAT to know how much
>> >texture-swapping there is going on, but I doubt this can be done
>> >portably?
>> 

>However, real hardware can be VERY subtle 

Yes, I know. Generally speaking, I loved optimizing till about 10
years ago. Until then, you could pretty much tell beforehand whether a
change would speed up the program. But with several caches, pipelines
that are filled by compilers, branch prediction etc it has become much
harder and sometimes when I optimized something for speed I ended
up making it slower :-(. 

>Since this question is unanswerable in a portable manner, 

That's what I feared.

>So, these are NOT good questions to ask!

Ok, I realize that there is no portable way to measure things, no one
answer (after all, not all users have the same
hardware), its not clearly defined etc.
But I still think a ballpark figure could help enormously. I think
it can still happen that large parts of the time per frame is spent in
texture swapping.
But in PPE speak NIV10 ;-))), meaning, this wont be the next thing
that is implemented.



>
>> Well, the attraction with perfly is that it really doesn't do anything
>> apart from load and display models.
>
>Neither does PPE right now!   :-(

Lol. But PPE makes a nice 3D object converter once all those
loaders/writers work. BTW; there is a "conv3D" on SourceForge,
but I am not impressed and it seems to be deeply asleep. But maybe
they could help, for example with a *simple* POV reader/writer?


Bye bye,
Wolfram.