Better late than never, here is an e-mail one of our tool developers sent me
a few weeks ago regarding this problem.

>  We've recently had numerous customers report the same issues to us.
> Unfortunately our testing seems to indicate the problem is related to the
> latest driver implementation provided by Nvidia. The problem seems to be
> compounded by the use of multi-code/CPU machines and most OpenGL based
> applications.
>
>  Nvidia is aware of the problem and has noted issues in their release
> notes for the current driver releases which can be found here:
> http://www.nvidia.com/docs/IO/37395/93.71_open.pdf
> "There may be intermittent application compatibility issues with dual core
> CPUs.
> If you experience this issue, first make sure you have downloaded and
> installed the dual core
> patches from your CPU manufacturer and from Microsoft.  The Microsoft
> knowledge base
> article is available at:
> http://support.microsoft.com/?id=896256.
> If you still experience problems you can attempt to work around these by
> toggling off
> NVIDIA's multithread optimizations using the following instructions:
> 1  Launch regedit and determine the current primary display card by
> looking in
> HKey_Local_Machine\Hardware\DeviceMap\Video
> and note the  GUID (global unique identifier assigned by Windows), which
> is the long
> string in brackets { } at the end of the entry
> "
> \device\video0".
> 2  Look in
> HKey_Local_Machine\SYSTEM\CurrentControlSet\Control\Video\{GUID}\0000
> where {GUID} is the number derived from the previous step.
> 3  Open the "
> 0000" directory and create a new DWORD called OGL_ThreadControl and
> give it a value of
> 2.  This will disable multithreading in the driver for all OpenGL
> applications.
> 4  If you want to disable driver multithreading for all Direct3D
> applications–
> In the same "
> 0000" directory, create a new DWORD called WTD_EXECMODEL and give
> it a value of
> 0."
>
> In-house testing has showed that this fix works for certain machines but
> not all of them. One of our machines here required third party drivers
> supplied by http://www.guru3d.com/.
>
> A few other fixes that have been found to work can be found here:
>
> http://www.hardforum.com/showthread.php?t=983781
>
> We noticed on a few of the machines that if we disabled all but one
> core/CPU in the BIOS, the problem would be eliminated. However this is not a
> satisfactory solution for obvious reasons.
>
> If you check on the Nvidia forums you will see numerous posts with the
> same complaints about OpenGL based applications running on the newest
> hardware.
>
> http://forums.nvidia.com/
>
Hope this helps

On 8/17/07, Greg Udall <[EMAIL PROTECTED]> wrote:
>
> Prasant,
>
> I'm currently experiencing a similar problem. If your problem is infact
> the same as mine it appears to be a problem with dual core processors and
> multi threading rather than anything else. I've had this on both AMD and
> Intel processors.
>
> Unfortunately, I'm working out of office so I cannot give you a
> full account but I shall make an effort to post my findings on Monday.
>
> I posted this on the Nvidia developer forum a couple of weeks ago so it
> might be worth keeping an eye on this:
>
> http://developer.nvidia.com/forums/index.php?showtopic=44
>
> Regards
>
> Greg
>
>
>  On 8/16/07, Michael Ebner <[EMAIL PROTECTED]> wrote:
> >
> > Hi Prasant,
> >
> > take a look at your driver settings first, sounds to me like you are
> > using "single display performance mode", as shown here:
> >
> > http://i189.photobucket.com/albums/z201/paloooz/Untitled-1-12.png
> >
> > (something like that should apply for ATI cards too, although i don't
> > know the exact setting)
> >
> > regards,
> > Michael.
> >
> >
> > Prasant Vajjalu Rekapalli wrote:
> > > I am using OSG with VS 7.1.
> > >
> > > When I move my application window (i.e. CompositeViewer window) from
> > one screen to another on a computer with multiple monitors,
> > > my application crashes. In particular, it seems as though it is taking
> > an eternity for each frame to be processed.
> > >
> > > I am guessing that at each RESIZE (MOVE) event, I have to figure out
> > which screen the application window is now on and update
> > > the GraphicsTraits accordingly.
> > >
> > > Is this right. If yes, could anyone please tell me how to achieve
> > this. If not, please tell me what the problem is.
> > >
> > > Thanks
> > > -Prasant
> > > _______________________________________________
> > > osg-users mailing list
> > > [email protected]
> > >
> > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
> > >
> >
> > _______________________________________________
> > osg-users mailing list
> > [email protected]
> >
> > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
> >
>
>
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to