nvidia 76.45!

Myself and a friend both get this same issue, we've noticed the one common factor is it happens when surfing with Firefox and some javascript on a website kicks in... seriously, it happens to me quite often and I've always got firefox open when it happens.

Fedorov.

 

Woah same here its either with azureus lime wire and java on web pages and i dont recall this ever happening before firefox hmm I really like firefox but if i find its the culprit i will probably uninstall it or something

 

I found its a problem only caused by java was reading alot of different stuff but its involving Direct draw that Java is using in 2D applets and/or applications which really does nothing to enhance it at all and causes the problems with the video card and video playback. I found 1 fix...!


1. Passing the following Java command-line flag to the VM: -Dsun.java2d.noddraw=true to disable these direct draw optimizations in Java!!
You can also try launching your application with the following command-line flag set:

-Dsun.java2d.d3d=false

 

Hope Sun comes out with an update

 

"Synopsis Java2D incorrectly renders objects with large coordinates


In this sample code, I've used Graphics.drawLine and Graphics.fillPolygon to illustrate the
behavior. I've gotten the same results using a GeneralPath with Graphics2D.draw and
Graphics2D.fill.

import java.awt.*;
import java.awt.event.*;

public class RenderBug extends Canvas {

int m_paintCase;

RenderBug(int num) {
m_paintCase = num;
}

public void paint(Graphics g) {
Image image;

switch (m_paintCase) {
case 1:
// This correctly and quickly draws the line.
drawBadLine(g);
break;

case 2:
// This hangs the VM.
image = createImage(640, 480);
drawBadLine(image.getGraphics());
g.drawImage(image, 0, 0, this);
break;

case 3:
// This incorrectly (but quickly) draws nothing.
fillBadPolygon(g);
break;

case 4:
// This correctly (but very slowly) fills the polygon.
image = createImage(640, 480);
fillBadPolygon(image.getGraphics());
g.drawImage(image, 0, 0, this);
break;
}
}


void drawBadLine(Graphics g) {
System.out.println("Drawing line...");
g.drawLine(0, 0, 55000, 20000);
System.out.println("Line is drawn.\n");
}


void fillBadPolygon(Graphics g) {
int[] x = { -90000000, 300, -40000000 };
int[] y = { -30000000, 300, -70000000 };
System.out.println("Filling polygon...");
g.setColor(Color.green);
g.fillPolygon(x, y, 3);
System.out.println("Polygon is filled.\n");
}


public static void main(String[] args) {
int num = 0;
if (args.length == 1) {
try {
num = Integer.parseInt(args[0]);
} catch (NumberFormatException ignore) {}
}
if (num < 1 || num > 4) {
System.out.println("Usage: java RenderBug { 1 | 2 | 3 | 4 }");
} else {
Frame frame = new Frame("DrawImage");
Canvas canvas = new RenderBug(num);
frame.setSize(640, 480);
frame.add("Center", canvas);
frame.addWindowListener(new WindowAdapter() {
public void windowClosing(WindowEvent e) {
System.exit(0);
}
});
frame.show();
}
}
}
(Review ID: 94393)
======================================================================

Work Around




The only workaround is to clip the coordinates ourselves. We can crudely truncate the coordinates to shorts, or we can use a more sophisticated clipping algorithm. However, this task belongs in the implementation of Graphics2D -- preferably in native code. We'd like to avoid the performance overhead of doing our own clipping, and I don't think it's unreasonable to expect well-defined rendering behavior from Graphics2D.
======================================================================

Evaluation

Test cases 2 and 4 are being addressed with the fix of bug 4376103.

The deficiencies of the platform renderers and our reliance on them
without a workaround will still be a problem even after 4376103 is
fixed. This bug provides a good test case for those additional
problems.

It is also interesting to note that whereas we know that X11 is
incapable of dealing with coordinates beyond 16 bits because of
its interfaces and protocols, the GDI interface that we use
for filling rectangles uses an array of POINT structures which use
32-bit fields to store the coordinates. Unfortunately, it looks
like they don't support the full 32-bit coordinate space even if
their interface would imply that they do. Also, this appears
to be OS and maybe even display card dependent. On my NT box
with an ATI card, cases 1 and 3 both work just fine, for instance."

 

Well my bad with all the posts i cant delete them strangly but i put my older geforce4 in and it just has the basic drivers reset settings and i dont get that problem we need to find out some sort of commonality between our cards or settings the drivers where different and cards are different so its something and it doesnt seem every one has this issue just certain folks this is irritating

 

RBEJ, that URL does not work.

Methinks you have a problem

 

I was very lazy and didn't give these drivers a go until just now. But they fixed the video corruption bug I had with the Freelancer opening movies when AA was enabled through the NVIDIA CP. A driver set that actually fixed something... imagine that!

 

the 76.45s? if so i will definatly give them another try

 

Yeah, the 76.45s, but I think I may be experiencing a different issue than what you guys are with Java or whatever the issue was, too lazy to read all the posts. My problem arises when enabling AA in the NVIDIA CP and starting Freelancer. It happened in a couple spots but that was the most notable occurrence; the right inch and a half of the screen would be corrupted. These drivers fixed that.

 

Wow what a diffrence these drivers make with the 71.89 drivers i got an 3014 score and now with these i got 3573 with an 6600gt oc edititon by bft tech I was first gona post "wtf is my sscore so low" thread but upon reading this thread I installed these drivers and tada better score ..
Also I have a athlon 3500+ winchester at stock speeds What would be the highest i could oc it on stock colling atm?

 

For a long time no new drivers are released or leaked. Any new news about a new forceware?

 

Terrible performance with newest Doom3 1.3 patch.....about 20-30% down.

 

Hmm, anyone else experience this?


A couple days ago and before I was using the 76.50 drivers.

Then I'm like hey, 76.45's look cool, i'll just install them and get coolbits 2.0 and see how I good I can tweak this baby.

Then, go to watch some ahem videos that night and alls I see on windows media player is pure purple screen where my entertainment was supposed to be.

I completely uninstalled all my graphic drivers before installing the 76.45 and did everything how it was supposed to be done, i think?

I am back with the 76.50 right now and I do like it, but I really like the 76.45 better if anybody has any ideas.

 

I haven't had any problems with these new drivers at all. Quite the opposite in fact. An increase in performance and video quality right across the boards. My Aquamark score increased by 1500 points, just with the new driver installation alone.

 

What is the bug I have heard about in this driver? I haven't noticed anything.

 

These are the finest drivers right now.

People experiencing problems are most likely doing something wrong with RivaTuner or coolbits.

 

I haven't experienced any bugs to date.

 

I had a problem with Riddick crashing whenever I tried to load it on this driver. Thats about it though, and that could be SLI related.

 

I reinstalled the drivers with the same experiment, expecting different results, and different results I got.

Instead of my windows media player having a dark purple screen when I load videos, it was lime green with scanlines and every once and a while some picture would come in pink.

I searched google and found that its a common problem, and the only thing you have to do to fix is in the windows media player options turn video performance to a medium level rather than full blast. It worked like a charm, I still gots my videos, and i'm fraggin with the best driver for my card right now.