DC 0.5L still broken with 52.16

That graphical glitch that arrived with the 52.x drivers in Desert
Combat - it still seems to be there with the just released DC 0.5L

Wasn't that meant to be sorted out? (I have BF 1.5 too)

Nvidia has posted in the notes for the 52.16 driver that the glitch is
a problem of the driver, not the DC mod. They plan to have a fix in
their next driver.


From their release notes:

GeForce FX 5950 Ultra and GeForce4 Ti 4400, Windows XP: Rendering
corruption in Battlefield 1942 Desert Combat.
This fix will be included in the next NVIDIA.com driver release.



On Sat, 08 Nov 2003 11:19:18 +1100, "Nick (no dashes)"
wrote:

That graphical glitch that arrived with the 52.x drivers in Desert
Combat - it still seems to be there with the just released DC 0.5L

Wasn't that meant to be sorted out? (I have BF 1.5 too)

Dave

Narrator:

On a long enough timeline,
the survival rate for everyone drops to zero.

On Fri, 07 Nov 2003 22:18:30 -0500, "David L. White, Jr."
wrote:



Nvidia has posted in the notes for the 52.16 driver that the glitch is
a problem of the driver, not the DC mod. They plan to have a fix in
their next driver.


From their release notes:

GeForce FX 5950 Ultra and GeForce4 Ti 4400, Windows XP: Rendering
corruption in Battlefield 1942 Desert Combat.
This fix will be included in the next NVIDIA.com driver release.


Those who download and use drivers without reading driver Release
notes (if available) need to go back to school instead of wasting
bandwidth on this newsgroup. All the hard work done by the QC group
at nVidia is nullified by those who do not bother to read the results
of their efforts ( the 52.16 Release Notes).

The 52.16 Release notes also mention BSODs on Desert Combat in Win XP
with GF4 MX440 and GF4 44400, to be fixed in the next release of the
nVidia driver.

John Lewis




On Sat, 08 Nov 2003 11:19:18 +1100, "Nick (no dashes)"
wrote:

That graphical glitch that arrived with the 52.x drivers in Desert
Combat - it still seems to be there with the just released DC 0.5L

Wasn't that meant to be sorted out? (I have BF 1.5 too)

Dave

Narrator:

On a long enough timeline,
the survival rate for everyone drops to zero.

"John Lewis" wrote in message :

Those who download and use drivers without reading driver Release
notes (if available) need to go back to school instead of wasting
bandwidth on this newsgroup. All the hard work done by the QC group
at nVidia is nullified by those who do not bother to read the results
of their efforts ( the 52.16 Release Notes).

The 52.16 Release notes also mention BSODs on Desert Combat in Win XP
with GF4 MX440 and GF4 44400, to be fixed in the next release of the
nVidia driver.

John Lewis

My apologies but I do get sick of downloading release notes just to see what
the lastest drivers have broken yet again. nVidia should just stick to
trying to fudge their benchmark figures by getting developers to write
benchmark demos that are tailored to their cards.

David L. White, Jr. wrote:

Nvidia has posted in the notes for the 52.16 driver that the glitch is
a problem of the driver, not the DC mod. They plan to have a fix in
their next driver.


From their release notes:

GeForce FX 5950 Ultra and GeForce4 Ti 4400, Windows XP: Rendering
corruption in Battlefield 1942 Desert Combat.
This fix will be included in the next NVIDIA.com driver release.



On Sat, 08 Nov 2003 11:19:18 +1100, "Nick (no dashes)"
wrote:


That graphical glitch that arrived with the 52.x drivers in Desert
Combat - it still seems to be there with the just released DC 0.5L

Wasn't that meant to be sorted out? (I have BF 1.5 too)


Dave

Narrator:

On a long enough timeline,
the survival rate for everyone drops to zero.
Thanks David - I recall it is a driver issue, but I thought the DC team
were going to 'fudge' a fix in 0.5.

John Lewis: I had read the notes, my question doesn't suggest I hadn't.
And I doubt many schools run a class on 'reading driver release notes'
so that's a completly left field pointless suggestion.

On Sun, 09 Nov 2003 12:14:53 +1100, "Nick (no dashes)"
wrote:

David L. White, Jr. wrote:

Nvidia has posted in the notes for the 52.16 driver that the glitch is
a problem of the driver, not the DC mod. They plan to have a fix in
their next driver.


From their release notes:

GeForce FX 5950 Ultra and GeForce4 Ti 4400, Windows XP: Rendering
corruption in Battlefield 1942 Desert Combat.
This fix will be included in the next NVIDIA.com driver release.



On Sat, 08 Nov 2003 11:19:18 +1100, "Nick (no dashes)"
wrote:


That graphical glitch that arrived with the 52.x drivers in Desert
Combat - it still seems to be there with the just released DC 0.5L

Wasn't that meant to be sorted out? (I have BF 1.5 too)


Dave

Narrator:

On a long enough timeline,
the survival rate for everyone drops to zero.
Thanks David - I recall it is a driver issue, but I thought the DC team
were going to 'fudge' a fix in 0.5.

John Lewis: I had read the notes, my question doesn't suggest I hadn't.
And I doubt many schools run a class on 'reading driver release notes'
so that's a completly left field pointless suggestion.


( Just a reading-comprehension class would suffice.)

However, there is a very interesting point in this issue:-

It seems as if nVidia is bending over backwards in trying to
special-case the new Forceware drivers for the DC team, since
52.16 has no problem at all with BF1942 and its official add-ons.
A very nice gesture indeed to a popular-mod community.

Of course, if nVidia special-cases their drivers for any RETAIL games
( e.g: HL2 ) everybody ( including Valve) heaps burning-coals on their
heads.

Driver-writing must be one of the most thankless pursuits on the
planet.

John Lewis

John Lewis wrote:
On Sun, 09 Nov 2003 12:14:53 +1100, "Nick (no dashes)"
wrote:


David L. White, Jr. wrote:

Nvidia has posted in the notes for the 52.16 driver that the glitch is
a problem of the driver, not the DC mod. They plan to have a fix in
their next driver.


From their release notes:

GeForce FX 5950 Ultra and GeForce4 Ti 4400, Windows XP: Rendering
corruption in Battlefield 1942 Desert Combat.
This fix will be included in the next NVIDIA.com driver release.



On Sat, 08 Nov 2003 11:19:18 +1100, "Nick (no dashes)"
wrote:



That graphical glitch that arrived with the 52.x drivers in Desert
Combat - it still seems to be there with the just released DC 0.5L

Wasn't that meant to be sorted out? (I have BF 1.5 too)


Dave

Narrator:

On a long enough timeline,
the survival rate for everyone drops to zero.

Thanks David - I recall it is a driver issue, but I thought the DC team
were going to 'fudge' a fix in 0.5.

John Lewis: I had read the notes, my question doesn't suggest I hadn't.
And I doubt many schools run a class on 'reading driver release notes'
so that's a completly left field pointless suggestion.



( Just a reading-comprehension class would suffice.)

However, there is a very interesting point in this issue:-

It seems as if nVidia is bending over backwards in trying to
special-case the new Forceware drivers for the DC team, since
52.16 has no problem at all with BF1942 and its official add-ons.
A very nice gesture indeed to a popular-mod community.

Of course, if nVidia special-cases their drivers for any RETAIL games
( e.g: HL2 ) everybody ( including Valve) heaps burning-coals on their
heads.

Driver-writing must be one of the most thankless pursuits on the
planet.

John Lewis




And I just noticed that Eve of Destruction (that Vietnam mod) has the
terrain disappearing too - albeit less frequent.

Very annoying, I'm not going back to the 45 drivers, so just have to put
up with it I guess.