[vtkusers] Re: [Paraview-developers] [LONG] Antialiasing with multisampling method

[Moreland, Kenneth]

In the past, I have added code to turn off antialiasing in ParaView when
running with parallel compositing.  I run all the time with the
IceTDesktopRenderModule and occasionally with IceTRenderModule.  The
compositing works fine there because the render modules explicitly turn
off multisampling.

Let me know if anyone is having multisampling problems so we can fix
that correctly.  It's a separate issue from regression testing.

-Ken

> -----Original Message-----
> From: 
> paraview-developers-bounces+kmorel=sandia.gov at paraview.org 
> [mailto:paraview-developers-bounces+kmorel=sandia.gov at paraview
> .org] On Behalf Of Berk Geveci
> Sent: Friday, September 23, 2005 6:42 AM
> To: Thompson, David C
> Cc: vtk-developers at vtk.org; vtkusers at vtk.org; 
> paraview-developers at paraview.org; paraview at paraview.org
> Subject: Re: [vtkusers] Re: [Paraview-developers] [LONG] 
> Antialiasing with multisampling method
> 
> I don't think this is a good enough solution. The tests may 
> pass but all users will get anti-aliasing when running 
> paraview interactively.
> Compositing does not work propery when anti-aliasing is on. 
> Also, it will slow down rendering. We should disable 
> anti-aliasing when we create the render window in paraview.
> 
> On 9/22/05, David C. Thompson <dcthomp at sandia.gov> wrote:
> > > Here is my question. There are a couple of ways to make the 
> > > regression tests not to fail because of multisampling.
> > >
> > > 1. Remove multisampling query: we will never get a multisample 
> > > context, but users may like to have antialiasing anyway.
> > > 2. Once we get a multisample context, call 
> glDisable(GL_MULTISAMPLE) 
> > > and never use multisampling. We potentially get a context with a 
> > > special buffer that allocate some video memory for nothing, when 
> > > this memory could be useful to load a lot of textures.
> > > 3. Set default value of GlobalMaximumNumberOfMultiSamples 
> to 0 instead of 8.
> > > 4. Set default value of MultiSamples to 0 instead of
> > >    GlobalMaximumNumberOfMultiSamples.
> > > 5. On each potentially failing test, call 
> SetMultiSamples(0) at the 
> > > beginning, which requires access to the concrete type of 
> RenderWindow.
> > > ... Solution 5 looks easy for VTK tests, less easy for 
> ParaView tests.
> > >
> > > Any opinion about thoses solution, or some alternate 
> solution is welcome.
> >
> > Couldn't vtkTesting::RegressionTest() call SetMultiSamples(0) if 
> > necessary before rendering? For ParaView, couldn't the same 
> thing be 
> > accomplished inside GUI/Testing/Tcl/Compare.tcl? I supposed 
> that if a 
> > test required MultiSamples turned on, it would have to explicitly 
> > request it of vtkTesting or Compare, but I suspect this 
> would be many 
> > fewer tests than the other way around.
> >
> >         David
> >
> > _______________________________________________
> > This is the private VTK discussion list.
> > Please keep messages on-topic. Check the FAQ at: 
> > http://www.vtk.org/Wiki/VTK_FAQ Follow this link to 
> subscribe/unsubscribe:
> > http://www.vtk.org/mailman/listinfo/vtkusers
> >
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
> 
>