This list is closed, nobody may subscribe to it.
| 2004 |
Jan
(7) |
Feb
(117) |
Mar
(37) |
Apr
(46) |
May
(14) |
Jun
(255) |
Jul
(100) |
Aug
(76) |
Sep
(65) |
Oct
(38) |
Nov
(49) |
Dec
(41) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(106) |
Feb
(70) |
Mar
(9) |
Apr
(4) |
May
(42) |
Jun
(29) |
Jul
(106) |
Aug
(38) |
Sep
(11) |
Oct
(31) |
Nov
(14) |
Dec
(14) |
| 2006 |
Jan
(2) |
Feb
(9) |
Mar
(15) |
Apr
(13) |
May
(16) |
Jun
(5) |
Jul
(11) |
Aug
(1) |
Sep
(7) |
Oct
|
Nov
(9) |
Dec
(1) |
| 2007 |
Jan
(13) |
Feb
(107) |
Mar
(43) |
Apr
(43) |
May
(38) |
Jun
(38) |
Jul
(63) |
Aug
|
Sep
(30) |
Oct
(52) |
Nov
(4) |
Dec
(10) |
| 2008 |
Jan
(12) |
Feb
(10) |
Mar
(5) |
Apr
(3) |
May
(15) |
Jun
(2) |
Jul
|
Aug
(10) |
Sep
(20) |
Oct
(6) |
Nov
|
Dec
(6) |
| 2009 |
Jan
(1) |
Feb
(5) |
Mar
(3) |
Apr
(51) |
May
|
Jun
|
Jul
|
Aug
(14) |
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2010 |
Jan
(9) |
Feb
|
Mar
(8) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(7) |
Dec
(1) |
| 2012 |
Jan
|
Feb
(6) |
Mar
(3) |
Apr
|
May
(6) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: James W. W. <os...@jw...> - 2007-09-28 16:18:50
|
On Sep 28, 2007, at 8:11 AM, Sauro Agostini wrote: > Practically the latest version is faster using OpenGl and Quesa > Logo, but it is very slow with the MultiBox model, independently > of the kind of renderer, where last Quesa for Intel is slower than > Quesa 1.8 emulated with Rosetta! > > Also with our programs we have similar results, with the latest > version that is 3 times slower than Quesa 1.8 and previous versions > (12 FPS versus 36 FPS). > > Any suggestions? Use Shark to try to discover why it is slower. |
|
From: Daniele C. <dca...@in...> - 2007-09-20 07:27:49
|
James Thank's a lot for your patience. Yes I must create a little application more simple possible with V. S. 2005 so I can understand where is my problem. James Walker ha scritto: > Daniele Cavallini wrote: > >> Start with a drawcontext create from window and all is ok >> I want create a bitmap of view so I create pixmap drawcontext (I can >> create a image with large dimension). >> My masterDrawContext is the drawcontext obtain with >> Q3View_GetDrawContext from window view. >> I make the render into pixmap drawcontext >> I create a windows bitmap, for this I get drawcontext with >> Q3View_GetDrawContext obtain from pixmap drawcontext and get pixmap. >> When I have my windows bitmap I return to drawcontext create from window >> > > So, you are using the same pixels for a Windows pixmap (DIB section?) > and a Quesa pixmap draw context? That should be OK. > > Have you considered making a test program in V. S. 2005, to see if you > can get offscreen shadows in a simpler situation? Other than that, I > think I am out of ideas. > |
|
From: James W. <ja...@fr...> - 2007-09-19 17:34:35
|
Daniele Cavallini wrote: > Start with a drawcontext create from window and all is ok > I want create a bitmap of view so I create pixmap drawcontext (I can > create a image with large dimension). > My masterDrawContext is the drawcontext obtain with > Q3View_GetDrawContext from window view. > I make the render into pixmap drawcontext > I create a windows bitmap, for this I get drawcontext with > Q3View_GetDrawContext obtain from pixmap drawcontext and get pixmap. > When I have my windows bitmap I return to drawcontext create from window So, you are using the same pixels for a Windows pixmap (DIB section?) and a Quesa pixmap draw context? That should be OK. Have you considered making a test program in V. S. 2005, to see if you can get offscreen shadows in a simpler situation? Other than that, I think I am out of ideas. -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> |
|
From: Daniele C. <dca...@in...> - 2007-09-19 16:35:37
|
Start with a drawcontext create from window and all is ok I want create a bitmap of view so I create pixmap drawcontext (I can create a image with large dimension). My masterDrawContext is the drawcontext obtain with Q3View_GetDrawContext from window view. I make the render into pixmap drawcontext I create a windows bitmap, for this I get drawcontext with Q3View_GetDrawContext obtain from pixmap drawcontext and get pixmap. When I have my windows bitmap I return to drawcontext create from window James W. Walker ha scritto: > On Sep 19, 2007, at 1:30 AM, Daniele Cavallini wrote: > > >> I add the logging statements like you suggest. I obtain: >> Start view with render on video >> /When pass in GLDrawContext_New theDrawContext is 02344c98 / >> Call render in the pixmap drawcontext >> /When pass in gldrawcontext_fbo_new (//ofcourse after call to >> Q3Object_GetPoperty >> (...KQ3DrawContextPropertyAcceleretedOffscreen...))// >> masterDrawContext 02344c98. >> >> /After I recreate a window on screen with a new draw context / >> /For create the bitmap after render I use Q3View_GetDrawContext and >> Q3PixmapDrawContext_GetPixmap maybe my problem here? >> > > I'm not clear on what you're doing. You had a window draw context A > which served as a master draw context for a pixmap context B. Then > you created a new window draw context C... then what? To which view > do you apply Q3View_GetDrawContext, and to which context do you apply > Q3PixmapDrawContext_GetPixmap? > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quesa-develop mailing list > Que...@li... > https://lists.sourceforge.net/lists/listinfo/quesa-develop > > |
|
From: James W. W. <os...@jw...> - 2007-09-19 15:43:15
|
On Sep 19, 2007, at 1:30 AM, Daniele Cavallini wrote: > I add the logging statements like you suggest. I obtain: > Start view with render on video > /When pass in GLDrawContext_New theDrawContext is 02344c98 / > Call render in the pixmap drawcontext > /When pass in gldrawcontext_fbo_new (//ofcourse after call to > Q3Object_GetPoperty > (...KQ3DrawContextPropertyAcceleretedOffscreen...))// > masterDrawContext 02344c98. > > /After I recreate a window on screen with a new draw context / > /For create the bitmap after render I use Q3View_GetDrawContext and > Q3PixmapDrawContext_GetPixmap maybe my problem here? I'm not clear on what you're doing. You had a window draw context A which served as a master draw context for a pixmap context B. Then you created a new window draw context C... then what? To which view do you apply Q3View_GetDrawContext, and to which context do you apply Q3PixmapDrawContext_GetPixmap? |
|
From: Daniele C. <dca...@in...> - 2007-09-19 08:30:03
|
James Walker ha scritto: > Daniele Cavallini wrote: > >> I used OpenGL Extensions Viewer for test my video card and in report are >> present GL_EXT_framebuffer_object. >> I must control other extension? >> > > gldrawcontext_fbo_new requires that the OpenGL version is 1.2 or later, > and GL_EXT_framebuffer_object. > It seem OK > >> For to be sure to render offscreen after render onscreen I get >> drawcontext with Q3View_GetDrawContext and I use it for master draw Context, >> but Q3Object_GetProperty with KQ3DrawContextPropertyGLContext is not >> success. >> > > I'm not sure I understand you... you called Q3View_GetDrawContext on a > view that has been rendered? > > exactly > If I understand correctly, since you cannot debug Quesa, you are adding > logging statements to Quesa. I suggest that you add a log statement to > GLDrawContext_New where kQ3DrawContextPropertyGLContext is set, and > write out the value of theDrawContext. Also write out the value of > masterDrawContext in gldrawcontext_fbo_new. > I add the logging statements like you suggest. I obtain: Start view with render on video /When pass in GLDrawContext_New theDrawContext is 02344c98 / Call render in the pixmap drawcontext /When pass in gldrawcontext_fbo_new (//ofcourse after call to Q3Object_GetPoperty(...KQ3DrawContextPropertyAcceleretedOffscreen...))// masterDrawContext 02344c98. /After I recreate a window on screen with a new draw context / /For create the bitmap after render I use Q3View_GetDrawContext and Q3PixmapDrawContext_GetPixmap maybe my problem here? |
|
From: James W. <ja...@fr...> - 2007-09-18 17:32:02
|
Daniele Cavallini wrote: > I used OpenGL Extensions Viewer for test my video card and in report are > present GL_EXT_framebuffer_object. > I must control other extension? gldrawcontext_fbo_new requires that the OpenGL version is 1.2 or later, and GL_EXT_framebuffer_object. > For to be sure to render offscreen after render onscreen I get > drawcontext with Q3View_GetDrawContext and I use it for master draw Context, > but Q3Object_GetProperty with KQ3DrawContextPropertyGLContext is not > success. I'm not sure I understand you... you called Q3View_GetDrawContext on a view that has been rendered? If I understand correctly, since you cannot debug Quesa, you are adding logging statements to Quesa. I suggest that you add a log statement to GLDrawContext_New where kQ3DrawContextPropertyGLContext is set, and write out the value of theDrawContext. Also write out the value of masterDrawContext in gldrawcontext_fbo_new. -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> |
|
From: Daniele C. <dca...@in...> - 2007-09-18 14:14:46
|
I used OpenGL Extensions Viewer for test my video card and in report are present GL_EXT_framebuffer_object. I must control other extension? For to be sure to render offscreen after render onscreen I get drawcontext with Q3View_GetDrawContext and I use it for master draw Context, but Q3Object_GetProperty with KQ3DrawContextPropertyGLContext is not success. James Walker ha scritto: > Daniele Cavallini wrote: > >> I tried to set stencil bits at 0,8,32 value. >> If I create a drawcontext from video: >> >> TQ3Win32DCDrawContextData myWin32DrawContextData; >> CClientDC DC(theWindow); >> HDC hwin= (HDC) DC; >> myWin32DrawContextData.hdc = hwin; >> myDrawContext=Q3Win32DCDrawContext_New(&myWin32DrawContextData) ; >> Shadows are nicely visible. >> It is not necessary set stencil bits. >> > > True, there is a function AdjustStencilAndDepthForShadows that will set > stencil bits for you if you try to render shadows. > > >> So I think it is not a problem caused from videocard. >> > > That does not follow. If your video card lacks the FBO extension, then > you will not be able to do hardware-accelerated offscreen rendering. > > |
|
From: James W. <ja...@fr...> - 2007-09-17 17:27:22
|
Daniele Cavallini wrote: > I tried to set stencil bits at 0,8,32 value. > If I create a drawcontext from video: > > TQ3Win32DCDrawContextData myWin32DrawContextData; > CClientDC DC(theWindow); > HDC hwin= (HDC) DC; > myWin32DrawContextData.hdc = hwin; > myDrawContext=Q3Win32DCDrawContext_New(&myWin32DrawContextData) ; > Shadows are nicely visible. > It is not necessary set stencil bits. True, there is a function AdjustStencilAndDepthForShadows that will set stencil bits for you if you try to render shadows. > So I think it is not a problem caused from videocard. That does not follow. If your video card lacks the FBO extension, then you will not be able to do hardware-accelerated offscreen rendering. -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> |
|
From: James W. <ja...@fr...> - 2007-09-17 17:19:02
|
James W. Walker wrote: > On Sep 17, 2007, at 6:26 AM, Daniele Cavallini wrote: > >> With log file I found in function gldrawcontext_fbo_new >> >> (kQ3Success == Q3Object_GetProperty( propData.masterDrawContext, >> kQ3DrawContextPropertyGLContext, sizeof(TQ3GLContext), >> NULL, >> &masterGLContext )) >> >> is false >> >> Can it be usefull? > > GLDrawContext_New sets the property for every draw context, so if > propData.masterDrawContext is a valid draw context, I don't know why > it would fail. Correction: If propData.masterDrawContext is a valid draw context AND it has been rendered at least once, the property should exist. Is it possible that you are attempting to render offscreen before you have rendered onscreen? -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> |
|
From: James W. W. <os...@jw...> - 2007-09-17 16:25:24
|
On Sep 17, 2007, at 6:26 AM, Daniele Cavallini wrote: > With log file I found in function gldrawcontext_fbo_new > > (kQ3Success == Q3Object_GetProperty( propData.masterDrawContext, > kQ3DrawContextPropertyGLContext, sizeof(TQ3GLContext), > NULL, > &masterGLContext )) > > is false > > Can it be usefull? GLDrawContext_New sets the property for every draw context, so if propData.masterDrawContext is a valid draw context, I don't know why it would fail. |
|
From: Daniele C. <dca...@in...> - 2007-09-17 13:25:44
|
With log file I found in function gldrawcontext_fbo_new (kQ3Success == Q3Object_GetProperty( propData.masterDrawContext, kQ3DrawContextPropertyGLContext, sizeof(TQ3GLContext), NULL, &masterGLContext )) is false Can it be usefull? |
|
From: Daniele C. <dca...@in...> - 2007-09-17 10:34:55
|
I tried to set stencil bits at 0,8,32 value. If I create a drawcontext from video: TQ3Win32DCDrawContextData myWin32DrawContextData; CClientDC DC(theWindow); HDC hwin= (HDC) DC; myWin32DrawContextData.hdc = hwin; myDrawContext=Q3Win32DCDrawContext_New(&myWin32DrawContextData) ; Shadows are nicely visible. It is not necessary set stencil bits. So I think it is not a problem caused from videocard. I tried some windows machine but without changing. Actually I can't try walking through gldrawcontext_fbo_new in a debugger because My project is in Visual studio 6.0 and quesa is in V.S. 2005 James W. Walker ha scritto: > On Sep 14, 2007, at 2:08 AM, Daniele Cavallini wrote: > > >> Thank's a lot. I used your precious hints and now my app don't crash. >> I created drawContextDisplay from window device context and I used it >> like masterDrawContext. >> Unluckily the shadows is not still visibles. >> Also I tried to require explicity the stencil buffer using >> kQ3DrawContextPropertyGLStencilBufferDepth >> TQ3Uns32 preferredStencilBits = 0; >> > > Why 0? You need stencil bits. The usual value is 8. > > >> Q3Object_SetProperty(drawContextDisplay, >> kQ3DrawContextPropertyGLStencilBufferDepth,sizeof >> (preferredStencilBits), >> &preferredStencilBits ); >> Q3Object_SetProperty(myDrawContext, >> kQ3DrawContextPropertyGLStencilBufferDepth,sizeof >> (preferredStencilBits), >> &preferredStencilBits ); >> But nothing. >> Do you think I must give up to have images with high resolution with >> shadows using Perspective and axonometric in windows? >> > > No. I certainly expect to make offscreen images with shadows in a > future Windows version of my product, though I think it has not been > tested yet. > > Have you tried more than one Windows machine? > > Have you checked the capabilities of the video card with GLView? > <http://www.realtech-vr.com/glview/> For instance check for > GL_EXT_framebuffer_object. > > Have you tried walking through gldrawcontext_fbo_new in a debugger? > > > >> With Rayshade I obtain good images but only in Perspective view. >> >> James W. Walker ha scritto: >> >>> On Sep 13, 2007, at 3:42 AM, Daniele Cavallini wrote: >>> >>> >>> >>>> I try so: >>>> drawContextDisplay is a TQ3DrawContextObject global variable >>>> >>>> TQ3AcceleratedOffscreenPropertyData propData; >>>> myStatus = Q3View_GetDrawContext >>>> (gDocumento3D.fView,&drawContextDisplay); // I get the drawcontext >>>> display >>>> myDrawContext = MyNewDrawContext(lar,alt);// I create the >>>> Pixmap >>>> drawcontext (TQ3PixmapDrawContextData) >>>> propData.masterDrawContext=drawContextDisplay; >>>> propData.copyFromPixmapAtFrameStart=kQ3False; >>>> propData.copyToPixmapAtFrameEnd=kQ3False; >>>> >>>> myStatus = Q3Object_SetProperty(myDrawContext, >>>> kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(propData), >>>> &propData ); >>>> myStatus=Q3View_SetDrawContext >>>> (gDocumento3D.fView,myDrawContext); >>>> >>>> >>>> Do you think it is a correct operation? >>>> The variable myStatus is always True but when I call >>>> Q3View_StartRendering program crash. >>>> >>>> >>> I think you probably want to set propData.copyToPixmapAtFrameEnd to >>> kQ3True, if you want to see a rendered image in the Pixmap. You >>> would only set propData.copyToPixmapAtFrameEnd to kQ3False if you >>> want to get the image in some other way such as using glReadPixels. >>> >>> When you replace drawContextDisplay with myDrawContext as the draw >>> context associated with the view gDocumento3D.fView, it probably >>> means that drawContextDisplay is no longer a valid draw context, so >>> it is not a good value for propData.masterDrawContext. When I have >>> used kQ3DrawContextPropertyAcceleratedOffscreen, I used different >>> view objects for the PixMap draw context and the on-screen master >>> draw context. >>> >>> >>> >>>> James W. Walker ha scritto: >>>> >>>> >>>>> On Sep 11, 2007, at 2:35 AM, Daniele Cavallini wrote: >>>>> >>>>> >>>>> >>>>> >>>>>> You are right in Mac there is not problem. >>>>>> I work with a imac intel core due with video card ATI Radeon >>>>>> x1600 >>>>>> I can well compare mac os x and windows xp. >>>>>> >>>>>> I tried to use kQ3DrawContextPropertyAcceleratedOffscreen: >>>>>> >>>>>> TQ3Boolean theFlag = kQ3True; >>>>>> Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows,sizeof >>>>>> (theFlag), &theFlag ); >>>>>> Q3Object_SetProperty( fRenderer, >>>>>> kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(theFlag), >>>>>> &theFlag ); >>>>>> >>>>>> >>>>>> but without success. >>>>>> >>>>>> >>>>>> >>>>> kQ3DrawContextPropertyAcceleratedOffscreen is a property that >>>>> must be >>>>> set on the draw context, not the renderer. That's why it's >>>>> called a >>>>> draw context property. Also, the value is not a TQ3Boolean. >>>>> See the >>>>> documentation in QuesaDrawContext.h. >>>>> >>>>> ------------------------------------------------------------------- >>>>> -- >>>>> ---- >>>>> This SF.net email is sponsored by: Microsoft >>>>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>>> _______________________________________________ >>>>> Quesa-develop mailing list >>>>> Que...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/quesa-develop >>>>> >>>>> >>>>> >>>>> >>>> -------------------------------------------------------------------- >>>> -- >>>> --- >>>> This SF.net email is sponsored by: Microsoft >>>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> _______________________________________________ >>>> Quesa-develop mailing list >>>> Que...@li... >>>> https://lists.sourceforge.net/lists/listinfo/quesa-develop >>>> >>>> >>> --------------------------------------------------------------------- >>> ---- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Quesa-develop mailing list >>> Que...@li... >>> https://lists.sourceforge.net/lists/listinfo/quesa-develop >>> >>> >>> >> ---------------------------------------------------------------------- >> --- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Quesa-develop mailing list >> Que...@li... >> https://lists.sourceforge.net/lists/listinfo/quesa-develop >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quesa-develop mailing list > Que...@li... > https://lists.sourceforge.net/lists/listinfo/quesa-develop > > |
|
From: James W. W. <os...@jw...> - 2007-09-14 16:20:51
|
On Sep 14, 2007, at 2:08 AM, Daniele Cavallini wrote: > Thank's a lot. I used your precious hints and now my app don't crash. > I created drawContextDisplay from window device context and I used it > like masterDrawContext. > Unluckily the shadows is not still visibles. > Also I tried to require explicity the stencil buffer using > kQ3DrawContextPropertyGLStencilBufferDepth > TQ3Uns32 preferredStencilBits = 0; Why 0? You need stencil bits. The usual value is 8. > Q3Object_SetProperty(drawContextDisplay, > kQ3DrawContextPropertyGLStencilBufferDepth,sizeof > (preferredStencilBits), > &preferredStencilBits ); > Q3Object_SetProperty(myDrawContext, > kQ3DrawContextPropertyGLStencilBufferDepth,sizeof > (preferredStencilBits), > &preferredStencilBits ); > But nothing. > Do you think I must give up to have images with high resolution with > shadows using Perspective and axonometric in windows? No. I certainly expect to make offscreen images with shadows in a future Windows version of my product, though I think it has not been tested yet. Have you tried more than one Windows machine? Have you checked the capabilities of the video card with GLView? <http://www.realtech-vr.com/glview/> For instance check for GL_EXT_framebuffer_object. Have you tried walking through gldrawcontext_fbo_new in a debugger? > With Rayshade I obtain good images but only in Perspective view. > > James W. Walker ha scritto: >> On Sep 13, 2007, at 3:42 AM, Daniele Cavallini wrote: >> >> >>> I try so: >>> drawContextDisplay is a TQ3DrawContextObject global variable >>> >>> TQ3AcceleratedOffscreenPropertyData propData; >>> myStatus = Q3View_GetDrawContext >>> (gDocumento3D.fView,&drawContextDisplay); // I get the drawcontext >>> display >>> myDrawContext = MyNewDrawContext(lar,alt);// I create the >>> Pixmap >>> drawcontext (TQ3PixmapDrawContextData) >>> propData.masterDrawContext=drawContextDisplay; >>> propData.copyFromPixmapAtFrameStart=kQ3False; >>> propData.copyToPixmapAtFrameEnd=kQ3False; >>> >>> myStatus = Q3Object_SetProperty(myDrawContext, >>> kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(propData), >>> &propData ); >>> myStatus=Q3View_SetDrawContext >>> (gDocumento3D.fView,myDrawContext); >>> >>> >>> Do you think it is a correct operation? >>> The variable myStatus is always True but when I call >>> Q3View_StartRendering program crash. >>> >> >> I think you probably want to set propData.copyToPixmapAtFrameEnd to >> kQ3True, if you want to see a rendered image in the Pixmap. You >> would only set propData.copyToPixmapAtFrameEnd to kQ3False if you >> want to get the image in some other way such as using glReadPixels. >> >> When you replace drawContextDisplay with myDrawContext as the draw >> context associated with the view gDocumento3D.fView, it probably >> means that drawContextDisplay is no longer a valid draw context, so >> it is not a good value for propData.masterDrawContext. When I have >> used kQ3DrawContextPropertyAcceleratedOffscreen, I used different >> view objects for the PixMap draw context and the on-screen master >> draw context. >> >> >>> James W. Walker ha scritto: >>> >>>> On Sep 11, 2007, at 2:35 AM, Daniele Cavallini wrote: >>>> >>>> >>>> >>>>> You are right in Mac there is not problem. >>>>> I work with a imac intel core due with video card ATI Radeon >>>>> x1600 >>>>> I can well compare mac os x and windows xp. >>>>> >>>>> I tried to use kQ3DrawContextPropertyAcceleratedOffscreen: >>>>> >>>>> TQ3Boolean theFlag = kQ3True; >>>>> Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows,sizeof >>>>> (theFlag), &theFlag ); >>>>> Q3Object_SetProperty( fRenderer, >>>>> kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(theFlag), >>>>> &theFlag ); >>>>> >>>>> >>>>> but without success. >>>>> >>>>> >>>> kQ3DrawContextPropertyAcceleratedOffscreen is a property that >>>> must be >>>> set on the draw context, not the renderer. That's why it's >>>> called a >>>> draw context property. Also, the value is not a TQ3Boolean. >>>> See the >>>> documentation in QuesaDrawContext.h. >>>> >>>> ------------------------------------------------------------------- >>>> -- >>>> ---- >>>> This SF.net email is sponsored by: Microsoft >>>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> _______________________________________________ >>>> Quesa-develop mailing list >>>> Que...@li... >>>> https://lists.sourceforge.net/lists/listinfo/quesa-develop >>>> >>>> >>>> >>> -------------------------------------------------------------------- >>> -- >>> --- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Quesa-develop mailing list >>> Que...@li... >>> https://lists.sourceforge.net/lists/listinfo/quesa-develop >>> >> >> >> --------------------------------------------------------------------- >> ---- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Quesa-develop mailing list >> Que...@li... >> https://lists.sourceforge.net/lists/listinfo/quesa-develop >> >> > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quesa-develop mailing list > Que...@li... > https://lists.sourceforge.net/lists/listinfo/quesa-develop |
|
From: Roger H. <rog...@mi...> - 2007-09-14 15:53:34
|
We draw all our perspective scenes using the View Angle Aspect camera. Comparing the RayShade renderer output for a non 1:1 aspect ratio scene, with the output from the Interactive renderer ( and the Microspot Renderer ), we get a slight stretching out with RayShade. Whilst it is not critical, it is a bit annoying at times when you accurately clip (in the PhotoShop sense) the scene you want using the interactive renderer and then wait for RayShade to do its thing, but then find the clipping is wrong in the final output. |
|
From: Daniele C. <dca...@in...> - 2007-09-14 09:08:27
|
Thank's a lot. I used your precious hints and now my app don't crash. I created drawContextDisplay from window device context and I used it like masterDrawContext. Unluckily the shadows is not still visibles. Also I tried to require explicity the stencil buffer using kQ3DrawContextPropertyGLStencilBufferDepth TQ3Uns32 preferredStencilBits = 0; Q3Object_SetProperty(drawContextDisplay, kQ3DrawContextPropertyGLStencilBufferDepth,sizeof(preferredStencilBits), &preferredStencilBits ); Q3Object_SetProperty(myDrawContext, kQ3DrawContextPropertyGLStencilBufferDepth,sizeof(preferredStencilBits), &preferredStencilBits ); But nothing. Do you think I must give up to have images with high resolution with shadows using Perspective and axonometric in windows? With Rayshade I obtain good images but only in Perspective view. James W. Walker ha scritto: > On Sep 13, 2007, at 3:42 AM, Daniele Cavallini wrote: > > >> I try so: >> drawContextDisplay is a TQ3DrawContextObject global variable >> >> TQ3AcceleratedOffscreenPropertyData propData; >> myStatus = Q3View_GetDrawContext >> (gDocumento3D.fView,&drawContextDisplay); // I get the drawcontext >> display >> myDrawContext = MyNewDrawContext(lar,alt);// I create the >> Pixmap >> drawcontext (TQ3PixmapDrawContextData) >> propData.masterDrawContext=drawContextDisplay; >> propData.copyFromPixmapAtFrameStart=kQ3False; >> propData.copyToPixmapAtFrameEnd=kQ3False; >> >> myStatus = Q3Object_SetProperty(myDrawContext, >> kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(propData), >> &propData ); >> myStatus=Q3View_SetDrawContext >> (gDocumento3D.fView,myDrawContext); >> >> >> Do you think it is a correct operation? >> The variable myStatus is always True but when I call >> Q3View_StartRendering program crash. >> > > I think you probably want to set propData.copyToPixmapAtFrameEnd to > kQ3True, if you want to see a rendered image in the Pixmap. You > would only set propData.copyToPixmapAtFrameEnd to kQ3False if you > want to get the image in some other way such as using glReadPixels. > > When you replace drawContextDisplay with myDrawContext as the draw > context associated with the view gDocumento3D.fView, it probably > means that drawContextDisplay is no longer a valid draw context, so > it is not a good value for propData.masterDrawContext. When I have > used kQ3DrawContextPropertyAcceleratedOffscreen, I used different > view objects for the PixMap draw context and the on-screen master > draw context. > > >> James W. Walker ha scritto: >> >>> On Sep 11, 2007, at 2:35 AM, Daniele Cavallini wrote: >>> >>> >>> >>>> You are right in Mac there is not problem. >>>> I work with a imac intel core due with video card ATI Radeon x1600 >>>> I can well compare mac os x and windows xp. >>>> >>>> I tried to use kQ3DrawContextPropertyAcceleratedOffscreen: >>>> >>>> TQ3Boolean theFlag = kQ3True; >>>> Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows,sizeof >>>> (theFlag), &theFlag ); >>>> Q3Object_SetProperty( fRenderer, >>>> kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(theFlag), >>>> &theFlag ); >>>> >>>> >>>> but without success. >>>> >>>> >>> kQ3DrawContextPropertyAcceleratedOffscreen is a property that must be >>> set on the draw context, not the renderer. That's why it's called a >>> draw context property. Also, the value is not a TQ3Boolean. See the >>> documentation in QuesaDrawContext.h. >>> >>> --------------------------------------------------------------------- >>> ---- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Quesa-develop mailing list >>> Que...@li... >>> https://lists.sourceforge.net/lists/listinfo/quesa-develop >>> >>> >>> >> ---------------------------------------------------------------------- >> --- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Quesa-develop mailing list >> Que...@li... >> https://lists.sourceforge.net/lists/listinfo/quesa-develop >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quesa-develop mailing list > Que...@li... > https://lists.sourceforge.net/lists/listinfo/quesa-develop > > |
|
From: James W. W. <os...@jw...> - 2007-09-13 16:34:13
|
On Sep 13, 2007, at 3:42 AM, Daniele Cavallini wrote: > I try so: > drawContextDisplay is a TQ3DrawContextObject global variable > > TQ3AcceleratedOffscreenPropertyData propData; > myStatus = Q3View_GetDrawContext > (gDocumento3D.fView,&drawContextDisplay); // I get the drawcontext > display > myDrawContext = MyNewDrawContext(lar,alt);// I create the > Pixmap > drawcontext (TQ3PixmapDrawContextData) > propData.masterDrawContext=drawContextDisplay; > propData.copyFromPixmapAtFrameStart=kQ3False; > propData.copyToPixmapAtFrameEnd=kQ3False; > > myStatus = Q3Object_SetProperty(myDrawContext, > kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(propData), > &propData ); > myStatus=Q3View_SetDrawContext > (gDocumento3D.fView,myDrawContext); > > > Do you think it is a correct operation? > The variable myStatus is always True but when I call > Q3View_StartRendering program crash. I think you probably want to set propData.copyToPixmapAtFrameEnd to kQ3True, if you want to see a rendered image in the Pixmap. You would only set propData.copyToPixmapAtFrameEnd to kQ3False if you want to get the image in some other way such as using glReadPixels. When you replace drawContextDisplay with myDrawContext as the draw context associated with the view gDocumento3D.fView, it probably means that drawContextDisplay is no longer a valid draw context, so it is not a good value for propData.masterDrawContext. When I have used kQ3DrawContextPropertyAcceleratedOffscreen, I used different view objects for the PixMap draw context and the on-screen master draw context. > > James W. Walker ha scritto: >> On Sep 11, 2007, at 2:35 AM, Daniele Cavallini wrote: >> >> >>> You are right in Mac there is not problem. >>> I work with a imac intel core due with video card ATI Radeon x1600 >>> I can well compare mac os x and windows xp. >>> >>> I tried to use kQ3DrawContextPropertyAcceleratedOffscreen: >>> >>> TQ3Boolean theFlag = kQ3True; >>> Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows,sizeof >>> (theFlag), &theFlag ); >>> Q3Object_SetProperty( fRenderer, >>> kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(theFlag), >>> &theFlag ); >>> >>> >>> but without success. >>> >> >> kQ3DrawContextPropertyAcceleratedOffscreen is a property that must be >> set on the draw context, not the renderer. That's why it's called a >> draw context property. Also, the value is not a TQ3Boolean. See the >> documentation in QuesaDrawContext.h. >> >> --------------------------------------------------------------------- >> ---- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Quesa-develop mailing list >> Que...@li... >> https://lists.sourceforge.net/lists/listinfo/quesa-develop >> >> > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quesa-develop mailing list > Que...@li... > https://lists.sourceforge.net/lists/listinfo/quesa-develop |
|
From: Daniele C. <dca...@in...> - 2007-09-13 10:42:02
|
I try so:
drawContextDisplay is a TQ3DrawContextObject global variable
TQ3AcceleratedOffscreenPropertyData propData;
myStatus = Q3View_GetDrawContext
(gDocumento3D.fView,&drawContextDisplay); // I get the drawcontext display
myDrawContext = MyNewDrawContext(lar,alt);// I create the Pixmap
drawcontext (TQ3PixmapDrawContextData)
propData.masterDrawContext=drawContextDisplay;
propData.copyFromPixmapAtFrameStart=kQ3False;
propData.copyToPixmapAtFrameEnd=kQ3False;
myStatus = Q3Object_SetProperty(myDrawContext,
kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(propData), &propData );
myStatus=Q3View_SetDrawContext(gDocumento3D.fView,myDrawContext);
Do you think it is a correct operation?
The variable myStatus is always True but when I call
Q3View_StartRendering program crash.
James W. Walker ha scritto:
> On Sep 11, 2007, at 2:35 AM, Daniele Cavallini wrote:
>
>
>> You are right in Mac there is not problem.
>> I work with a imac intel core due with video card ATI Radeon x1600
>> I can well compare mac os x and windows xp.
>>
>> I tried to use kQ3DrawContextPropertyAcceleratedOffscreen:
>>
>> TQ3Boolean theFlag = kQ3True;
>> Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows,sizeof
>> (theFlag), &theFlag );
>> Q3Object_SetProperty( fRenderer,
>> kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(theFlag),
>> &theFlag );
>>
>>
>> but without success.
>>
>
> kQ3DrawContextPropertyAcceleratedOffscreen is a property that must be
> set on the draw context, not the renderer. That's why it's called a
> draw context property. Also, the value is not a TQ3Boolean. See the
> documentation in QuesaDrawContext.h.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Quesa-develop mailing list
> Que...@li...
> https://lists.sourceforge.net/lists/listinfo/quesa-develop
>
>
|
|
From: James W. W. <os...@jw...> - 2007-09-11 16:25:58
|
On Sep 11, 2007, at 2:35 AM, Daniele Cavallini wrote: > You are right in Mac there is not problem. > I work with a imac intel core due with video card ATI Radeon x1600 > I can well compare mac os x and windows xp. > > I tried to use kQ3DrawContextPropertyAcceleratedOffscreen: > > TQ3Boolean theFlag = kQ3True; > Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows,sizeof > (theFlag), &theFlag ); > Q3Object_SetProperty( fRenderer, > kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(theFlag), > &theFlag ); > > > but without success. kQ3DrawContextPropertyAcceleratedOffscreen is a property that must be set on the draw context, not the renderer. That's why it's called a draw context property. Also, the value is not a TQ3Boolean. See the documentation in QuesaDrawContext.h. |
|
From: Daniele C. <dca...@in...> - 2007-09-11 09:35:28
|
You are right in Mac there is not problem. I work with a imac intel core due with video card ATI Radeon x1600 I can well compare mac os x and windows xp. I tried to use kQ3DrawContextPropertyAcceleratedOffscreen: TQ3Boolean theFlag = kQ3True; Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows,sizeof(theFlag), &theFlag ); Q3Object_SetProperty( fRenderer, kQ3DrawContextPropertyAcceleratedOffscreen,sizeof(theFlag), &theFlag ); but without success. Is it correct set Property kQ3RendererPropertyShadows and after kQ3DrawContextPropertyAcceleratedOffscreen ? Do you think if I set so I have the chance it work with some video card ? thanks James W. Walker ha scritto: > On Sep 10, 2007, at 12:25 AM, Daniele Cavallini wrote: > > >> I use Mac os x 10.4.1 and windows XP. I have the same problem. >> I specific: >> TQ3Boolean theFlag = kQ3True; >> Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows, >> sizeof(theFlag), &theFlag ); >> Where fRenderer is a TQ3RendererObject. >> If I use Q3Win32DCDrawContext_New for win and Q3MacDrawContext_New in >> Mac for create an TQ3DrawContextObject shadows are present. >> > > I understand why it's not working on Windows. Microsoft's OpenGL > software renderer is very primitive, and does not have the > capabilities needed for shadows. Depending on your video card, you > might be able to get shadows using > kQ3DrawContextPropertyAcceleratedOffscreen. > > I think it ought to work on the Mac, though I wonder why you have not > updated to 10.4.10. > > >> James Walker ha scritto: >> >>> Daniele Cavallini wrote: >>> >>> >>>> For obtain an image with a good resolution I use >>>> TQ3PixmapDrawContextData. >>>> It is work fine but if I use Quesa shared render opengl I don't >>>> see shadow. >>>> >>>> >>> Are you on Mac, Windows, or Linux? >>> >>> Did you specify that you want shadows using >>> kQ3RendererPropertyShadows? >>> >>> >>> >> ---------------------------------------------------------------------- >> --- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Quesa-develop mailing list >> Que...@li... >> https://lists.sourceforge.net/lists/listinfo/quesa-develop >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quesa-develop mailing list > Que...@li... > https://lists.sourceforge.net/lists/listinfo/quesa-develop > > |
|
From: James W. W. <os...@jw...> - 2007-09-10 16:09:59
|
On Sep 10, 2007, at 12:25 AM, Daniele Cavallini wrote: > I use Mac os x 10.4.1 and windows XP. I have the same problem. > I specific: > TQ3Boolean theFlag = kQ3True; > Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows, > sizeof(theFlag), &theFlag ); > Where fRenderer is a TQ3RendererObject. > If I use Q3Win32DCDrawContext_New for win and Q3MacDrawContext_New in > Mac for create an TQ3DrawContextObject shadows are present. I understand why it's not working on Windows. Microsoft's OpenGL software renderer is very primitive, and does not have the capabilities needed for shadows. Depending on your video card, you might be able to get shadows using kQ3DrawContextPropertyAcceleratedOffscreen. I think it ought to work on the Mac, though I wonder why you have not updated to 10.4.10. > > James Walker ha scritto: >> Daniele Cavallini wrote: >> >>> For obtain an image with a good resolution I use >>> TQ3PixmapDrawContextData. >>> It is work fine but if I use Quesa shared render opengl I don't >>> see shadow. >>> >> >> Are you on Mac, Windows, or Linux? >> >> Did you specify that you want shadows using >> kQ3RendererPropertyShadows? >> >> > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quesa-develop mailing list > Que...@li... > https://lists.sourceforge.net/lists/listinfo/quesa-develop |
|
From: Daniele C. <dca...@in...> - 2007-09-10 15:07:22
|
I correct myself. If I use mac os x 10.4.1 shadows are right. James Walker ha scritto: > Daniele Cavallini wrote: > >> For obtain an image with a good resolution I use TQ3PixmapDrawContextData. >> It is work fine but if I use Quesa shared render opengl I don't see shadow. >> > > Are you on Mac, Windows, or Linux? > > Did you specify that you want shadows using kQ3RendererPropertyShadows? > > |
|
From: Daniele C. <dca...@in...> - 2007-09-10 09:42:44
|
I correct myself. In mac os x 10.4.1 shadows are right. Daniele Cavallini ha scritto: > I use Mac os x 10.4.1 and windows XP. I have the same problem. > I specific: > TQ3Boolean theFlag = kQ3True; > Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows, > sizeof(theFlag), &theFlag ); > Where fRenderer is a TQ3RendererObject. > If I use Q3Win32DCDrawContext_New for win and Q3MacDrawContext_New in > Mac for create an TQ3DrawContextObject shadows are present. > > James Walker ha scritto: > >> Daniele Cavallini wrote: >> >> >>> For obtain an image with a good resolution I use TQ3PixmapDrawContextData. >>> It is work fine but if I use Quesa shared render opengl I don't see shadow. >>> >>> >> Are you on Mac, Windows, or Linux? >> >> Did you specify that you want shadows using kQ3RendererPropertyShadows? >> >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quesa-develop mailing list > Que...@li... > https://lists.sourceforge.net/lists/listinfo/quesa-develop > > |
|
From: Daniele C. <dca...@in...> - 2007-09-10 07:24:50
|
I use Mac os x 10.4.1 and windows XP. I have the same problem. I specific: TQ3Boolean theFlag = kQ3True; Q3Object_SetProperty( fRenderer, kQ3RendererPropertyShadows, sizeof(theFlag), &theFlag ); Where fRenderer is a TQ3RendererObject. If I use Q3Win32DCDrawContext_New for win and Q3MacDrawContext_New in Mac for create an TQ3DrawContextObject shadows are present. James Walker ha scritto: > Daniele Cavallini wrote: > >> For obtain an image with a good resolution I use TQ3PixmapDrawContextData. >> It is work fine but if I use Quesa shared render opengl I don't see shadow. >> > > Are you on Mac, Windows, or Linux? > > Did you specify that you want shadows using kQ3RendererPropertyShadows? > > |
|
From: James W. <ja...@fr...> - 2007-09-07 19:17:12
|
Daniele Cavallini wrote: > For obtain an image with a good resolution I use TQ3PixmapDrawContextData. > It is work fine but if I use Quesa shared render opengl I don't see shadow. Are you on Mac, Windows, or Linux? Did you specify that you want shadows using kQ3RendererPropertyShadows? -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> |