Hi Rômulo,
I have had a look at the debug output and the error message is being
reported prior to any of the OSG messages. I had done a search for the
warning string in the OSG using:
cd OpenSceneGraph
grep -r "Warning: Error in reading to" .
But don't get any hits. It looks to me
Hi Nick,
On 6 November 2017 at 00:56, Trajce Nikolov NICK
wrote:
> I am trying to measure the time needed to process a frame. My first and
> somewhat naïve approach is to init the timer at the beginning of the frame
> and get the result after the
HI Julien,
The code is osg/Texture.cpp has been written a long time ago so in
theory should have been exposed to testing for many years so I am
surprised the change you have found that works is required, and I'm
not confident the change you suggest won't break things. Given how
long Texture.cpp
Hi Julien,
I can't provide an answers without digging deeply in the code, this
week I'm really busy with clients so can't look in to. Next week I'll
be getting back to the shader_pipeline branch and better able to look
into it.
Which version of the OSG are you using? Is the standard
What we're working on right now is stream WRITE ability, in order to be
able to record OSG-rendered video to any libavcodec supported writable
stream.
The frame-centeric osg ReaderWriter Plugin architecture doesn't have
exactly the proper API for writing multiple images to a single stream-file,
Could this be caused by a static osg::Image() object (or another static
object that creates the osg::Image in its constructor) that's getting
initialized before the program's main() function is even called? This is
too early, as OSG plugins would not be registered at that point. It might
work with
thanks Robert ! I am seeing there is an example too for the user stats.
Sometimes I am faster by shooting even sample questions to the user list
before doing the home work
Thanks again !
Nick
On Mon, Nov 6, 2017 at 9:37 AM, Robert Osfield
wrote:
> Hi Nick,
>
> On 6
7 matches
Mail list logo