First rought version of ply-exporter

[goldhoorn]

No description provided.

[malter]

Could you please remove the warning and if hack_aperture is not a good variable name in the mainstream you can change it to aperture_file?

[goldhoorn]

Is this really needed or could the whole "hack "block removed?

On 11.02.2015 09:22, malter wrote:

Could you please remove the warning and if hack_aperture is not a good
variable name in the mainstream you can change it to aperture_file?

—
Reply to this email directly or view it on GitHub
#28 (comment).

Dipl.-Inf. Matthias Goldhoorn
Space and Underwater Robotic

Universität Bremen
FB 3 - Mathematik und Informatik
AG Robotik
Robert-Hooke-Straße 1
28359 Bremen, Germany

Zentrale: +49 421 178 45-6611

Besuchsadresse der Nebengeschäftstelle:
Robert-Hooke-Straße 5
28359 Bremen, Germany

Tel.: +49 421 178 45-4193
Empfang: +49 421 178 45-6600
Fax: +49 421 178 45-4150
E-Mail: matthias.goldhoorn@informatik.uni-bremen.de

Weitere Informationen: http://www.informatik.uni-bremen.de/robotik

[goldhoorn]

updated

[goldhoorn]

@malter pong

[goldhoorn]

@malter : do you accept this or do i need to change something??

[malter]

It would be better if the depth texture is only created when it is used the first time?

[goldhoorn]

don't know then there might be a delay (e.G. the first frame might not have been captured?!)

[malter]

Maybe, if you want to use the ply export you have to initialize the use of the depth buffer by calling the function once at the beginning or we add a initDepthBuffer to the GraphicsManagerInterface. But still it would be better to render the depth buffer only to texture if required.
You could also add it as configuration.

[goldhoorn]

updated

[malter]

did you pushed your changes?

[goldhoorn]

Yep, but to the wrong branch ;), now this one

[goldhoorn]

pong

[goldhoorn]

@malter dupdidu

[goldhoorn]

@malter : pong?

[goldhoorn]

@malter