PBO-VBO Usage Hints Warnings

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

PBO-VBO Usage Hints Warnings

alicana
Hi All, I have an application,that renders to Texture using PBO like said here (http://www.songho.ca/opengl/gl_pbo.html) and some other drawings that are handled with VBO's.

When I run my application with '-Djogl.debug.DebugGL'  argument, I had the following messages:
GLDebugEvent[ id 0x20071
	type Warning: generic
	severity Unknown (0x826b)
	source GL API
	msg Buffer detailed info: Buffer object 1 (bound to GL_VERTEX_ARRAY_BUFFER_BINDING_ARB, and GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
	when 1433492094161
	source 3.3 (Compat profile, arb, debug, compat[ES2, ES3], FBO, hardware) - 3.3.0 - hash 0x3a3e2405]
GLDebugEvent[ id 0x20071
	type Warning: generic
	severity Unknown (0x826b)
	source GL API
	msg Buffer detailed info: Buffer object 2 (bound to GL_PIXEL_UNPACK_BUFFER_ARB, usage hint is GL_STREAM_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast).
	when 1433493019677
	source 3.3 (Compat profile, arb, debug, compat[ES2, ES3], FBO, hardware) - 3.3.0 - hash 0x7b53df31]
GLDebugEvent[ id 0x20071
	type Warning: generic
	severity Unknown (0x826b)
	source GL API
	msg Buffer detailed info: Buffer object 5 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STREAM_DRAW) will use VIDEO memory as the source for buffer object operations.
	when 1433493070611
	source 3.3 (Compat profile, arb, debug, compat[ES2, ES3], FBO, hardware) - 3.3.0 - hash 0x1aa47147]
I have NVIDIA Quadro FX 570 with the latest driver version. (With old driver version it doesn't print anything like above).

By the way, my app runs well.  

Do you guys think that I'm doing something wrong? Have you ever got any of this messages ? 

	
	
	
	
Reply | Threaded
Open this post in threaded view
|

Re: PBO-VBO Usage Hints Warnings

Xerxes Rånby
This post was updated on .
Please publish your JOGL application as a git tree.
Publish using a public domain or a free software license if you want us to publicly comment on your API usage.

Please feel welcome to contact the maintainers for commercial support inquiries, specific questions you seem not fit for public discussions or to fund the work.
http://jogamp.org/wiki/index.php/Maintainer_and_Contacts#Contact_Maintainer
Reply | Threaded
Open this post in threaded view
|

Re: PBO-VBO Usage Hints Warnings

alicana
I guess, I missrepresented my situation. It is not a commercial app, it's not even a proper project. I'm experiencing Java implementation's of Songho's tutorials. Which are published under http://www.songho.ca/opengl/gl_pbo.html.

Reply | Threaded
Open this post in threaded view
|

Re: PBO-VBO Usage Hints Warnings

Xerxes Rånby
Please publish your JOGL implementation of Songho's tutorials.
The link in your post only contain c++ examples.

Its impossible to test if we experience the same thing unless we can run the same code.
Reply | Threaded
Open this post in threaded view
|

Re: PBO-VBO Usage Hints Warnings

gouessej
Administrator
In reply to this post by alicana
In my humble opinion, there is nothing wrong in the debug messages above but you should follow Xerxes' advise if you really want us to run your code on our machines to check whether there is something not working as expected.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: PBO-VBO Usage Hints Warnings

Sven Gothel
Administrator
On 06/08/2015 11:14 AM, gouessej [via jogamp] wrote:
> In my humble opinion, there is nothing wrong in the debug messages above but
> you should follow Xerxes' advise if you really want us to run your code on our
> machines to check whether there is something not working as expected.

Yup.

With general debug enabled, i.e. '-Djogl.debug.DebugGL',
the GL debug context is chosen and all messages are being dumped to stderr.
Those messages are of verbose nature (like the ones you have shown)
critical or even error cases.

For manual fine grained control of the GL debug context,
have a look at the unit test:
   com.jogamp.opengl.test.junit.jogl.acore.TestGLDebug01NEWT

~Sven



signature.asc (828 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: PBO-VBO Usage Hints Warnings

alicana
Thank you. So far, I understand that I may ignore that debug messages.

Jogl PBO to Texture rendering implementation link: https://gist.github.com/alicanalbayrak/ace2d7f426a4e75ca008

I run the code, that I shared above, with "-Djogl.debug.DebugGL".

Console debug message:
GLDebugEvent[ id 0x20071
	type Warning: generic
	severity Unknown (0x826b)
	source GL API
	msg Buffer detailed info: Buffer object 2 (bound to GL_PIXEL_UNPACK_BUFFER_ARB, usage hint is GL_STREAM_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast).
	when 1433935497195
	source 3.3 (Compat profile, arb, debug, compat[ES2, ES3], FBO, hardware) - 3.3.0 - hash 0xef45815]
    [2]: jogamp.opengl.GLDebugMessageHandler$StdErrGLDebugListener.messageSent(GLDebugMessageHandler.java:311)
    [3]: jogamp.opengl.GLDebugMessageHandler.sendMessage(GLDebugMessageHandler.java:296)
    [4]: jogamp.opengl.GLDebugMessageHandler.glDebugMessageARB(GLDebugMessageHandler.java:322)
    [5]: jogamp.opengl.gl4.GL4bcImpl.dispatch_glMapBufferDelegate1(Native Method)
    [6]: jogamp.opengl.gl4.GL4bcImpl.glMapBufferDelegate(GL4bcImpl.java:17199)
    [7]: jogamp.opengl.gl4.GL4bcImpl.access$300(GL4bcImpl.java:29)
    [8]: jogamp.opengl.gl4.GL4bcImpl$3.mapBuffer(GL4bcImpl.java:38822)
    [9]: jogamp.opengl.GLBufferObjectTracker.mapBufferImpl(GLBufferObjectTracker.java:410)
    [10]: jogamp.opengl.GLBufferObjectTracker.mapBufferImpl(GLBufferObjectTracker.java:357)
    [11]: jogamp.opengl.GLBufferObjectTracker.mapBuffer(GLBufferObjectTracker.java:308)
    [12]: jogamp.opengl.gl4.GL4bcImpl.mapBuffer(GL4bcImpl.java:38816)
    [13]: jogamp.opengl.gl4.GL4bcImpl.glMapBuffer(GL4bcImpl.java:38812)
    [14]: com.jogamp.opengl.DebugGL4bc.glMapBuffer(DebugGL4bc.java:13482)
    [15]: pbo.PBO2Texture.renderPBO2Texture(PBO2Texture.java:194)
    [16]: pbo.PBO2Texture.display(PBO2Texture.java:96)
    [17]: jogamp.opengl.GLDrawableHelper.displayImpl(GLDrawableHelper.java:691)
    [18]: jogamp.opengl.GLDrawableHelper.display(GLDrawableHelper.java:673)
    [19]: com.jogamp.opengl.awt.GLCanvas$11.run(GLCanvas.java:1421)
    [20]: jogamp.opengl.GLDrawableHelper.invokeGLImpl(GLDrawableHelper.java:1277)
    [21]: jogamp.opengl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:1131)
    [22]: com.jogamp.opengl.awt.GLCanvas$12.run(GLCanvas.java:1435)
    [23]: java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:302)
    [24]: java.awt.EventQueue.dispatchEventImpl(EventQueue.java:738)
    [25]: java.awt.EventQueue.access$300(EventQueue.java:103)
    [26]: java.awt.EventQueue$3.run(EventQueue.java:699)
    [27]: java.awt.EventQueue$3.run(EventQueue.java:697)
    [28]: java.security.AccessController.doPrivileged(Native Method)
    [29]: java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
    [30]: java.awt.EventQueue.dispatchEvent(EventQueue.java:708)
    [31]: java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
    [32]: java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
    [33]: java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
    [34]: java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
    [35]: java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
    [36]: java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

Reply | Threaded
Open this post in threaded view
|

Re: PBO-VBO Usage Hints Warnings

Sven Gothel
Administrator
On 06/10/2015 01:39 PM, alicana [via jogamp] wrote:

> Thank you. So far, I understand that I may ignore that debug messages.
>
> Jogl PBO to Texture rendering implementation link:
> https://gist.github.com/alicanalbayrak/ace2d7f426a4e75ca008
>
> I run the code, that I shared above, with "-Djogl.debug.DebugGL".
>
> Console debug message:
>
> GLDebugEvent[ id 0x20071
> type Warning: generic
> severity Unknown (0x826b)
> source GL API
> msg Buffer detailed info: Buffer object 2 (bound to GL_PIXEL_UNPACK_BUFFER_ARB, usage hint is GL_STREAM_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast).
Maybe you want to use the hint WRITE_ONLY instead of GL_STREAM_DRAW?
You would need to check the spec of the PBO extension here, ofc,
to ensure compatibility ..

~Sven



signature.asc (828 bytes) Download Attachment