<html>
<head>
<meta http-equiv='Content-Type' content='text/html; charset=UTF-8'>
</head>
<body>
<style>
font{
line-height: 1.6;
}
ul,ol{
padding-left: 20px;
list-style-position: inside;
}
</style>
<div style = 'font-family:微软雅黑,Verdana,"Microsoft Yahei",SimSun,sans-serif; line-height:1.6;'>
<div ></div><div>
<div>
<span style="color: rgb(49, 53, 59); font-family: Verdana, 'Microsoft Yahei', SimSun, sans-serif; line-height: 22.4px;">[Help] OSG + ArKit: Problem converting coordinate system</span><br style="color: rgb(49, 53, 59); font-family: Verdana, 'Microsoft Yahei', SimSun, sans-serif; line-height: 22.4px;"><span style="color: rgb(49, 53, 59); font-family: Verdana, 'Microsoft Yahei', SimSun, sans-serif; line-height: 22.4px;">(Raymond de Vries)</span><span>
</span>
</div>
<div>
<span>
<br>
</span>
</div>
<div style="font-family:'微软雅黑'">
<div style="font-size:14px; padding: 0; margin:0;line-height:14px;">
<div style="padding-bottom:6px;margin-bottom:10px;border-bottom:1px solid #e6e6e6;display:inline-block;">
<a href="https://maas.mail.163.com/dashi-web-extend/html/proSignature.html?ftlId=1&name=jonasydy&uid=jonasydy%40gmail.com&iconUrl=https%3A%2F%2Fmail-online.nosdn.127.net%2Fqiyelogo%2FdefaultAvatar.png&items=%5B%22jonasydy%40gmail.com%22%5D" style="display:block;background:#fff; max-width: 400px; _width: 400px;padding:15px 0 10px 0;text-decoration: none; outline:none;-webkit-tap-highlight-color:transparent;-webkit-text-size-adjust:none !important;text-size-adjust:none !important;">
<table cellpadding="0" style="width: 100%; max-width: 100%; table-layout: fixed; border-collapse: collapse;color: #9b9ea1;font-size: 14px;line-height:1.3;-webkit-text-size-adjust:none !important;text-size-adjust:none !important;">
<tbody style="font-family: 'PingFang SC', 'Hiragino Sans GB','WenQuanYi Micro Hei', 'Microsoft Yahei', '微软雅黑', verdana !important; word-wrap:break-word; word-break:break-all;-webkit-text-size-adjust:none !important;text-size-adjust:none !important;">
<tr class="firstRow">
<td width="38" style="padding:0; box-sizing: border-box; width: 38px;">
<img width="38" height="38" style="vertical-align:middle; width: 38px; height: 38px; border-radius:50%;" src="https://mail-online.nosdn.127.net/qiyelogo/defaultAvatar.png">
</td>
<td style="padding: 0 0 0 10px; color: #31353b;">
<div style="font-size: 16px;font-weight:bold; width:100%; white-space: nowrap; overflow:hidden;text-overflow: ellipsis;">jonasydy</div>
</td>
</tr>
<tr width="100%" style="font-size: 14px !important; width: 100%;">
<td colspan="2" style="padding:10px 0 0 0; font-size:14px !important; width: 100%;">
<div style="width: 100%;font-size: 14px !important;word-wrap:break-word;word-break:break-all;">jonasydy@gmail.com</div>
</td>
</tr>
</tbody>
</table>
</a>
</div>
</div>
<div style="font-size:12px;color:#b5b9bd;line-height:18px;">
<span>签名由</span>
<a style="text-decoration: none;color:#4196ff;padding:0 5px;" href="https://mail.163.com/dashi/dlpro.html?from=mail81">网易邮箱大师</a>
<span>定制</span>
</div>
</div>
</div><div class="J-reply" style="background-color:#f2f2f2;color:black;padding-top:6px;padding-bottom:6px;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;margin-top:45px;margin-bottom:20px;font-family:'微软雅黑';">
<div style="font-size:12px;line-height:1.5;word-break:break-all;margin-left:10px;margin-right:10px">On <span class="mail-date">10/10/2018 04:10</span>，<a class="mail-to" style="text-decoration:none;color:#2a83f2;" href="mailto:osg-users-request@lists.openscenegraph.org"><osg-users-request@lists.openscenegraph.org></a> wrote： </div>
</div>
<blockquote id="ntes-pcmail-quote" style="margin: 0; padding: 0; font-size: 14px; font-family: '微软雅黑';">
Send osg-users mailing list submissions to<br> osg-users@lists.openscenegraph.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org<br><br>or, via email, send a message with subject or body 'help' to<br> osg-users-request@lists.openscenegraph.org<br><br>You can reach the person managing the list at<br> osg-users-owner@lists.openscenegraph.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of osg-users digest..."<br><br><br>Today's Topics:<br><br> 1. Re: porting from osg-3.4.0 to osg-3.6.3 (Robert Osfield)<br> 2. Re: [Help] OSG + ArKit: Problem converting coordinate system<br> (Raymond de Vries)<br> 3. Re: [Help] OSG + ArKit: Problem converting coordinate system<br> (Voerman, L.)<br> 4. Re: porting from osg-3.4.0 to osg-3.6.3 (Herman Varma)<br> 5. Re: [Help] OSG + ArKit: Problem converting coordinate system<br> (Rodrigo Brayner Lyra)<br> 6. Re: porting from osg-3.4.0 to osg-3.6.3 (Robert Osfield)<br> 7. Re: porting from osg-3.4.0 to osg-3.6.3 (Robert Osfield)<br> 8. Re: porting from osg-3.4.0 to osg-3.6.3 (Herman Varma)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 9 Oct 2018 07:29:28 +0100<br>From: Robert Osfield <robert.osfield@gmail.com><br>To: OpenSceneGraph Users <osg-users@lists.openscenegraph.org><br>Subject: Re: [osg-users] porting from osg-3.4.0 to osg-3.6.3<br>Message-ID:<br> <CAFN7Y+U71PCnS15Fsvr3XRoMu6Tq9r7UdKmNwFeDoEPXxy=uzg@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>Hi Herman,<br><br>Thanks for the stack trace, the crash site and value of nv suggest<br>that for some reason the application is setting up the viewer without<br>an EventVIsitior. The osgViewer assigns one by default so this must<br>have been reset, or the call to handle customized in some way that is<br>non-standard.<br><br>Have a look for any places where setEventVisitor is called in VTP.<br><br>Robert.<br>On Tue, 9 Oct 2018 at 07:15, Herman Varma <hermanvarma@eastlink.ca> wrote:<br><blockquote class="mmbqc1"><br> Hi,<br> Hi Robert<br><br><br><br> I down down further to this statement<br><br> m_pOsgViewer->frame();//<br><br> In 3.4.0 it executes and in 3.6.3 it bombs here<br><br><br> The full code is posted below<br> void vtScene::UpdateWindow(vtWindow *pWindow)<br> {<br> if (!m_bInitialized) return;<br><br> // window background color<br> osg::Vec4 color2;<br> v2s(pWindow->GetBgColor(), color2);<br> m_pOsgViewer->getCamera()->setClearColor(color2);<br><br> // window size<br> IPoint2 winsize = pWindow->GetSize();<br> if (winsize.x == 0 || winsize.y == 0)<br> {<br> VTLOG("Warning: winsize %d %d\n", winsize.x, winsize.y);<br> return;<br> }<br> m_pOsgViewer->getCamera()->setViewport(0, 0, winsize.x, winsize.y);<br><br> // As of OSG 0.9.5, we need to store our own camera params and recreate<br> // the projection matrix each frame.<br> float aspect;<br> if (winsize.x == 0 || winsize.y == 0) // safety<br> aspect = 1.0;<br> else<br> aspect = (float) winsize.x / winsize.y;<br><br> if (m_pCamera->IsOrtho())<br> {<br> // Arguments are left, right, bottom, top, zNear, zFar<br> float w2 = m_pCamera->GetWidth() /2;<br> float h2 = w2 / aspect;<br> m_pOsgViewer->getCamera()->setProjectionMatrixAsOrtho(-w2, w2, -h2, h2,<br> m_pCamera->GetHither(), m_pCamera->GetYon());<br> }<br> else<br> {<br> float fov_x = m_pCamera->GetFOV();<br> float a = tan (fov_x/2);<br> float b = a / aspect;<br> float fov_y_div2 = atan(b);<br> float fov_y_deg = osg::RadiansToDegrees(fov_y_div2 * 2);<br><br> m_pOsgViewer->getCamera()->setProjectionMatrixAsPerspective(fov_y_deg,<br> aspect, m_pCamera->GetHither(), m_pCamera->GetYon());<br> }<br><br><br> // And apply the rotation and translation of the camera itself<br> const osg::Matrix &mat2 = m_pCamera->getMatrix();<br> osg::Matrix imat;<br><br><br> imat.invert(mat2);<br><br> m_pOsgViewer->getCamera()->setViewMatrix(imat);<br> m_pOsgViewer->getCamera()->setCullMask(0x3);<br> // Also set the mask for the case of split-screen stereo<br> m_pOsgViewer->getCamera()->setCullMaskLeft(0x3);<br> m_pOsgViewer->getCamera()->setCullMaskRight(0x3);<br><br> m_pOsgViewer->frame();// ***************************It bombs on this statement<br><br><br> }<br><br> I also ran it in debug mode and posted a diagnostic.jpg of the resulting<br> debug screen<br><br> Thank you!<br><br> Cheers,<br> Herman<br><br> ------------------<br> Read this topic online here:<br> http://forum.openscenegraph.org/viewtopic.php?p=75049#75049<br><br><br><br><br> Attachments:<br> http://forum.openscenegraph.org//files/diagnostic_569.jpg<br><br><br> _______________________________________________<br> osg-users mailing list<br> osg-users@lists.openscenegraph.org<br> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org<br></blockquote><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 9 Oct 2018 09:06:04 +0200<br>From: Raymond de Vries <reedevee@gmail.com><br>To: osg-users@lists.openscenegraph.org<br>Subject: Re: [osg-users] [Help] OSG + ArKit: Problem converting<br> coordinate system<br>Message-ID: <41d00c86-c3d5-1b66-cccf-79ed6506b31b@gmail.com><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hi Rodrigo,<br><br>Without having read your mail in detail I have a suggestion. Do you know <br>artoolkit and the integration with osg? It sounds to me that you can <br>learn from that project.<br><br>https://github.com/artoolkit/artoolkit5<br>https://github.com/artoolkit/artoolkit5/tree/master/examples/simpleOSG<br><br>Please keep us/me posted. Sounds like a nice project, have fun!<br><br>Cheers,<br>Raymond<br><br><br><br><br>On 10/8/2018 9:08 PM, Rodrigo Brayner Lyra wrote:<br> <blockquote class="mmbqc1">Hi,<br><br> I'm working on a project that will render a scene using openscenegraph, and the user will have the option to work with this scene in AR. The integration of ArKit in the application is almost complete, except in the conversion of ArKit's view matrix to the coordinate system used by OSG.<br><br> I uploaded the render of the OSG axis helper and the ArKit axis helper. As you can see, the y in OSG is x in ArKit, the x in OSG is z in ArKit and the z in OSG is y in ArKit. With that, I thought that if I switched the axes directly into the view matrix it would be correct. What I have tried can be seen in the two attachments with the code fragment that converts the ArKit view matrix into an OSG view matrix (ar_conv_vector_change and ar_conv_values_change).<br> None of them worked completely except that one of them was correct in the rotations and translations of the camera, but the position and initial rotation of the scene was completely wrong (The wall should be in the same position and point of view as before at the time that the AR mode is started, but was positioned as shown in the switched_values_view image).<br><br> In the end, the camera view matrix is:<br> m_camera_matrix = m_camera_view * ar_view_matrix;<br><br> I apologize for the long text, and I ask the support of the people of this forum, and if there is, who has already gone through this situation (with ArKit or other APIs)<br><br> Thank you!<br><br> Cheers,<br> Rodrigo<br><br> ------------------<br> Read this topic online here:<br> http://forum.openscenegraph.org/viewtopic.php?p=75048#75048<br><br><br><br><br> Attachments:<br> http://forum.openscenegraph.org//files/switched_values_view_100.jpg<br> http://forum.openscenegraph.org//files/ar_conv_values_change_120.jpeg<br> http://forum.openscenegraph.org//files/ar_conv_vector_change_297.jpeg<br> http://forum.openscenegraph.org//files/osg_axis_731.png<br> http://forum.openscenegraph.org//files/arkit_axis_176.jpg<br><br><br> _______________________________________________<br> osg-users mailing list<br> osg-users@lists.openscenegraph.org<br> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org<br><br> ---<br> This email has been checked for viruses by AVG.<br> https://www.avg.com<br><br></blockquote><br><br><br>------------------------------<br><br>Message: 3<br>Date: Tue, 9 Oct 2018 09:58:35 +0200<br>From: "Voerman, L." <l.voerman@rug.nl><br>To: OpenSceneGraph Users <osg-users@lists.openscenegraph.org><br>Subject: Re: [osg-users] [Help] OSG + ArKit: Problem converting<br> coordinate system<br>Message-ID:<br> <CAG7xrZe-L3Xt0ProeUFV6G3GdzV7VpUMWN4tnER+_8yD5ocZRw@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi Rodrigo,<br>I don't fully grasp your question, but i noticed that you say you want to<br>swap axis while the matrix in ar_conv_values_change_120.jpeg<br><http://forum.openscenegraph.org//files/ar_conv_values_change_120.jpeg> has<br>a last column in a different order than the first three.<br>Laurens.<br><br>On Tue, Oct 9, 2018 at 9:06 AM Raymond de Vries <reedevee@gmail.com> wrote:<br><br> <blockquote class="mmbqc1">Hi Rodrigo,<br><br> Without having read your mail in detail I have a suggestion. Do you know<br> artoolkit and the integration with osg? It sounds to me that you can<br> learn from that project.<br><br> https://github.com/artoolkit/artoolkit5<br> https://github.com/artoolkit/artoolkit5/tree/master/examples/simpleOSG<br><br> Please keep us/me posted. Sounds like a nice project, have fun!<br><br> Cheers,<br> Raymond<br><br><br><br><br> On 10/8/2018 9:08 PM, Rodrigo Brayner Lyra wrote:<br> <blockquote class="mmbqc2">Hi,<br><br> I'm working on a project that will render a scene using openscenegraph,<br> </blockquote>and the user will have the option to work with this scene in AR. The<br> integration of ArKit in the application is almost complete, except in the<br> conversion of ArKit's view matrix to the coordinate system used by OSG.<br><blockquote class="mmbqc2"><br> I uploaded the render of the OSG axis helper and the ArKit axis helper.<br> </blockquote>As you can see, the y in OSG is x in ArKit, the x in OSG is z in ArKit and<br> the z in OSG is y in ArKit. With that, I thought that if I switched the<br> axes directly into the view matrix it would be correct. What I have tried<br> can be seen in the two attachments with the code fragment that converts the<br> ArKit view matrix into an OSG view matrix (ar_conv_vector_change and<br> ar_conv_values_change).<br> <blockquote class="mmbqc2">None of them worked completely except that one of them was correct in<br> </blockquote>the rotations and translations of the camera, but the position and initial<br> rotation of the scene was completely wrong (The wall should be in the same<br> position and point of view as before at the time that the AR mode is<br> started, but was positioned as shown in the switched_values_view image).<br><blockquote class="mmbqc2"><br> In the end, the camera view matrix is:<br> m_camera_matrix = m_camera_view * ar_view_matrix;<br><br> I apologize for the long text, and I ask the support of the people of<br> </blockquote>this forum, and if there is, who has already gone through this situation<br> (with ArKit or other APIs)<br><blockquote class="mmbqc2"><br> Thank you!<br><br> Cheers,<br> Rodrigo<br><br> ------------------<br> Read this topic online here:<br> http://forum.openscenegraph.org/viewtopic.php?p=75048#75048<br><br><br><br><br> Attachments:<br> http://forum.openscenegraph.org//files/switched_values_view_100.jpg<br> http://forum.openscenegraph.org//files/ar_conv_values_change_120.jpeg<br> http://forum.openscenegraph.org//files/ar_conv_vector_change_297.jpeg<br> http://forum.openscenegraph.org//files/osg_axis_731.png<br> http://forum.openscenegraph.org//files/arkit_axis_176.jpg<br><br><br> _______________________________________________<br> osg-users mailing list<br> osg-users@lists.openscenegraph.org<br><br> </blockquote>http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org<br><blockquote class="mmbqc2"><br> ---<br> This email has been checked for viruses by AVG.<br> https://www.avg.com<br><br></blockquote><br> _______________________________________________<br> osg-users mailing list<br> osg-users@lists.openscenegraph.org<br> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org<br><br></blockquote>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20181009/88b5d910/attachment-0001.html><br><br>------------------------------<br><br>Message: 4<br>Date: Tue, 09 Oct 2018 15:49:43 +0200<br>From: "Herman Varma" <hermanvarma@eastlink.ca><br>To: osg-users@lists.openscenegraph.org<br>Subject: Re: [osg-users] porting from osg-3.4.0 to osg-3.6.3<br>Message-ID: <1539092983.m2f.75053@forum.openscenegraph.org><br>Content-Type: text/plain; charset=UTF-8<br><br>Hi Robert<br><br><br>Yes VTP calls setEventVisitor<br><br>m_pOsgViewer->setEventVisitor(NULL);<br><br>in<br>bool vtScene::Init(int argc, char** argv, bool bStereo, int iStereoMode)<br><br>Code is listed below marked as //*******CALLED HERE<br><br><br><br><br><br>/**<br> * Initialize the vtlib library, including the display and scene graph.<br> * You should call this function only once, before any other vtlib calls.<br> *<br> * \param argc, argv Command-line arguments.<br> * \param bStereo True for a stereo display output.<br> * \param iStereoMode Currently for vtosg, supported values are 0 for<br> * Anaglyphic (red-blue) and 1 for Quad-buffer (shutter glasses).<br> */<br>bool vtScene::Init(int argc, char** argv, bool bStereo, int iStereoMode)<br>{<br> VTLOG1("vtScene::Init\n");<br><br> // Redirect cout messages (where OSG sends its messages) to our own log<br> previous_cout = std::cout.rdbuf(&g_Trap);<br> previous_cerr = std::cerr.rdbuf(&g_Trap);<br><br>#if 0<br> // If you encounter trouble in OSG that you want to debug, enable this<br> // to get a LOT of diagnostic messages from OSG.<br> osg::setNotifyLevel(osg::INFO);<br>#endif<br><br> m_pDefaultCamera = new vtCamera;<br> m_pDefaultWindow = new vtWindow;<br> SetCamera(m_pDefaultCamera);<br> AddWindow(m_pDefaultWindow);<br><br> // use an ArgumentParser object to manage the program arguments.<br> osg::ArgumentParser arguments(&argc,argv);<br><br> m_pOsgViewer = new osgViewer::Viewer(arguments);<br><br> m_pOsgViewer->setDisplaySettings(osg::DisplaySettings::instance());<br> if (bStereo)<br> {<br> osg::DisplaySettings* displaySettings = m_pOsgViewer->getDisplaySettings();<br> displaySettings->setStereo(true);<br> osg::DisplaySettings::StereoMode mode;<br> if (iStereoMode == 0) mode = osg::DisplaySettings::ANAGLYPHIC;<br> if (iStereoMode == 1) mode = osg::DisplaySettings::QUAD_BUFFER;<br> if (iStereoMode == 2) mode = osg::DisplaySettings::HORIZONTAL_SPLIT;<br> if (iStereoMode == 3) mode = osg::DisplaySettings::VERTICAL_SPLIT;<br> displaySettings->setStereoMode(mode);<br> }<br>#ifdef __DARWIN_OSX__<br> // Kill multi-threading on OSX until wxGLContext properly implemented on that platform<br> m_pOsgViewer->setThreadingModel(osgViewer::Viewer::SingleThreaded);<br>#endif<br><br> // We can't use displaySettings->setNumMultiSamples here to enable anti-<br> // aliasing, because it has to be done eariler (at the time the OpenGL<br> // context is made).<br><br>#ifdef VTP_USE_OSG_STATS<br> osgViewer::StatsHandler* pStatsHandler = new osgViewer::StatsHandler;<br> pStatsHandler->setKeyEventPrintsOutStats(0);<br> pStatsHandler->setKeyEventTogglesOnScreenStats('x'); // I dont think this is used for anything else at the moment<br> m_pOsgViewer->addEventHandler(pStatsHandler);<br>#endif<br><br> // Kill the event visitor (saves a scenegraph traversal)<br> // This will need to be restored if we need to use FRAME events etc. in the scenegraph<br> m_pOsgViewer->setEventVisitor(NULL);//*******CALLED HERE<br><br> if (bStereo)<br> {<br> // displaySettings->getScreenDistance(); default is 0.5<br> // m_pOsgSceneView->getFusionDistanceMode(); default is PROPORTIONAL_TO_SCREEN_DISTANCE<br> // m_pOsgSceneView->getFusionDistanceValue(); default is 1.0<br> // The FusionDistanceValue is only used for USE_FUSION_DISTANCE_VALUE & PROPORTIONAL_TO_SCREEN_DISTANCE modes.<br><br> // We use real-world units for fusion distance value<br> m_pOsgViewer->setFusionDistance(osgUtil::SceneView::USE_FUSION_DISTANCE_VALUE, 100.0f);<br> }<br><br> // From the OSG mailing list: You must specify the lighting mode in<br> // setDefaults() and override the default options. If you call<br> // setDefaults() with the default options, a headlight is added to the<br> // global state set of the SceneView. With the default options applied,<br> // I have tried subsequently calling setLightingMode(NO_SCENE_LIGHT)<br> // and setLight(NULL), but I still get a headlight.<br> m_pOsgViewer->setLightingMode(osg::View::NO_LIGHT);<br> m_pOsgViewer->getCamera()->setComputeNearFarMode(osg::Camera::DO_NOT_COMPUTE_NEAR_FAR);<br> m_pOsgViewer->getCamera()->setCullingMode(m_pOsgViewer->getCamera()->getCullingMode() & ~osg::CullSettings::SMALL_FEATURE_CULLING);<br><br> // We maintain a node between OSG's viewer/camera and the vtlib Root, to<br> // control global state<br> m_StateRoot = new osg::Group;<br> m_pOsgViewer->setSceneData(m_StateRoot);<br><br> // By default, things are lit, unless they ask not to be<br> m_StateRoot->getOrCreateStateSet()->setMode(GL_LIGHTING, osg::StateAttribute::ON);<br><br> //m_StateRoot->addCullCallback(new MyCull);<br> //m_StateRoot->setUpdateCallback(new MyUpdate);<br> //m_StateRoot->setEventCallback(new MyEvent);<br><br> m_bInitialized = true;<br><br> _initialTick = _timer.tick();<br> _frameTick = _initialTick;<br><br> return true;<br>}<br><br><br><br>Thank you!<br><br>Cheers,<br>Herman<br><br>------------------<br>Read this topic online here:<br>http://forum.openscenegraph.org/viewtopic.php?p=75053#75053<br><br><br><br><br><br><br><br>------------------------------<br><br>Message: 5<br>Date: Tue, 09 Oct 2018 15:57:37 +0200<br>From: "Rodrigo Brayner Lyra" <rbl2@cin.ufpe.br><br>To: osg-users@lists.openscenegraph.org<br>Subject: Re: [osg-users] [Help] OSG + ArKit: Problem converting<br> coordinate system<br>Message-ID: <1539093457.m2f.75054@forum.openscenegraph.org><br>Content-Type: text/plain; charset=UTF-8<br><br>Hi Raymond,<br><br>I took a look at the submitted sample, and from what I've noticed, unfortunately it is unfeasible to migrate now to ArToolkit because of the project structure, which was all based on OSG, and as I could understand, ArToolkit + OSG uses pure OpenGL calls. Unfortunately the deadline is very near. <br><br>Hi Laurens,<br>The last column is unchanged because it is always 0 (except the value in the last row, which is 1). so the order of the last column doesn't matter.<br><br>Thank you!<br><br>Cheers,<br>Rodrigo<br><br>------------------<br>Read this topic online here:<br>http://forum.openscenegraph.org/viewtopic.php?p=75054#75054<br><br><br><br><br><br><br><br>------------------------------<br><br>Message: 6<br>Date: Tue, 9 Oct 2018 17:20:49 +0100<br>From: Robert Osfield <robert.osfield@gmail.com><br>To: OpenSceneGraph Users <osg-users@lists.openscenegraph.org><br>Subject: Re: [osg-users] porting from osg-3.4.0 to osg-3.6.3<br>Message-ID:<br> <CAFN7Y+VW28ha8BGOx978aSnDNPtvcv=ZJYdB2HyJwjgD21e2BA@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>Hi Herman,<br><br>On Tue, 9 Oct 2018 at 16:05, Herman Varma <hermanvarma@eastlink.ca> wrote:<br> <blockquote class="mmbqc1">Yes VTP calls setEventVisitor<br><br> m_pOsgViewer->setEventVisitor(NULL);<br></blockquote><br>That's an easy one then, just comment that line out.<br><br>The motivation behind the above line is a bit mus-guided as the OSG<br>keeps track whether a scene graph has an even callbacks and for the<br>subgraphs that don't contain any it doesn't do any traversal, so if<br>you don't use event callbacks the event traversal is close to a non<br>op.<br><br>The time you do use an event callback you'll only pay the cost for the<br>traversal down to the node that has the callback.<br><br>If you really do want to switch off the event visitor then setting the<br>EventVisitor TraversalMask to 0x0 will switch off traversal.<br><br>Robert.<br><br><br>------------------------------<br><br>Message: 7<br>Date: Tue, 9 Oct 2018 17:23:16 +0100<br>From: Robert Osfield <robert.osfield@gmail.com><br>To: OpenSceneGraph Users <osg-users@lists.openscenegraph.org><br>Subject: Re: [osg-users] porting from osg-3.4.0 to osg-3.6.3<br>Message-ID:<br> <CAFN7Y+WdYQGKA6TKe=XLgkzOvFy7vFSsoKqbW=WwknGjB0kTWw@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>I wrote:<br> <blockquote class="mmbqc1">That's an easy one then, just comment that line out.<br><br> The motivation behind the above line is a bit mus-guided as the OSG keeps track whether a scene graph has an even callbacks and for the subgraphs that don't contain any it doesn't do any traversal, so if you don't use event callbacks the event traversal is close to a non op.<br><br> The time you do use an event callback you'll only pay the cost for the traversal down to the node that has the callback.<br><br> If you really do want to switch off the event visitor then setting the EventVisitor TraversalMask to 0x0 will switch off traversal.<br></blockquote><br>The above features apply along way back, possibly even the OSG-1.x era<br>so it's safe to have the event visitor attached, so even if you want<br>to compile against 3.4 and 3.6.x the remove of the<br>setEventVisitor(NULL); is perfectly safe.<br><br>Robert.<br><br><br>------------------------------<br><br>Message: 8<br>Date: Tue, 09 Oct 2018 19:39:45 +0200<br>From: "Herman Varma" <hermanvarma@eastlink.ca><br>To: osg-users@lists.openscenegraph.org<br>Subject: Re: [osg-users] porting from osg-3.4.0 to osg-3.6.3<br>Message-ID: <1539106785.m2f.75057@forum.openscenegraph.org><br>Content-Type: text/plain; charset=UTF-8<br><br>Hi Robert<br><br>I commented out setEventVisitor(NULL) statement.<br>Thanks to you everything is operating properly with openscenegraph-3.6.3<br>Now its on to bringing VTP up to spec with wxWidgets.<br>I fosrsee similar obstacles (sigh!). Hopefully I can iron them out with good people like yourself. <br><br>Thanks again<br><br>Cheers,<br>Herman<br><br>------------------<br>Read this topic online here:<br>http://forum.openscenegraph.org/viewtopic.php?p=75057#75057<br><br><br><br><br><br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>osg-users mailing list<br>osg-users@lists.openscenegraph.org<br>http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org<br><br><br>------------------------------<br><br>End of osg-users Digest, Vol 136, Issue 8<br>*****************************************<br></blockquote><!--😀-->
</div>
</body>
</html>