We have got the camera panning by calculating the resultant of two
vectors(previous vector before panning and changed vector after panning)
and compared its magnitude with a value to restrict its position in camera
view. But when we zoom in and zoom out the magnitude of the vector that
Hi All,
I have just tagged the OpenSceneGraph-3.6.5-rc2:
https://github.com/openscenegraph/OpenSceneGraph/tree/OpenSceneGraph-3.6.5-rc2
Please test across as many platforms and applications as you have
available, and report success or failures here on this thread so we can
track
I am trying to create a camera functionality that pans the camera side by
side but when it reaches the bounds of geometry we shouldn't be able to pan
camera anymore. The functionality also includes zoom in and zoom out
--
You received this message because you are subscribed to the Google
The osgUI NodeKit was written to be used from C++ and/or Lua script.
During development the primary focus was on making sure it was functional
via Lua script and as part of Present3D presentations (see
OpenSceneGraph/applicaton/present3D).
Due to the focus on Lua script usage I didn't write
The way I'd tackle dragging of objects in model space that are billboarded
icons would be to project the mouse coords into clip coords then into
object space using the matrices inverse of the (projection * view *
model). You'd also need to compute the depth to use, this could be
computed by
Hi Tom,
FYI, it's was a community submission back in 2009, I don't personally know
the ply format or have done anything more than cosmetic work on this
plugin. I basically in the same boat as yourself in terms of ability to
debug the format, I just have to look at the code and see what it's
Could you change you user name to a human name, it helps the community to
converse respectively.
--
You received this message because you are subscribed to the Google Groups
"OpenSceneGraph Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi Robert,
oh i didnt mean you to do a deep investigation, i just thought it was a bug
or at least you might know if im doing sth wrong.
I investigated a little.
So it seems that the comment for texture files is actively used:
comment TextureFile YourTexture_material_0_map_Kd.jpg
So that
Also it seems that its not the method
void VertexData::readVertices( PlyFile* file, const int nVertices, const int
fields )
see
https://github.com/openscenegraph/OpenSceneGraph/blob/32566420c9d68a640996d741d13852e8d1229f3e/src/osgPlugins/ply/vertexData.cpp#L48
that needs to be adapted, but
How far have you got? What problems do you have?
--
You received this message because you are subscribed to the Google Groups
"OpenSceneGraph Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to osg-users+unsubscr...@googlegroups.com.
To view this
On Tuesday, 21 January 2020 14:07:35 UTC, Tom Pollok wrote:
>
> I investigated a little.
>
> So it seems that the comment for texture files is actively used:
>
> comment TextureFile YourTexture_material_0_map_Kd.jpg
>
> So that needs to be parsed, and not ignored as just being a comment.
>
> The
I converted it to ascii using MeshLab
https://owncloud.iosb.fraunhofer.de/owncloud/s/KpZFxn5SCm0JFmN
pw: osg
Yes, using another format is probably a better idea. Do you know which
format is typically used that supports binary encoding?
Am Dienstag, 21. Januar 2020 15:41:34 UTC+1 schrieb
12 matches
Mail list logo
