Texture problem with 8800gts - Page 2

[R-MOD]Dylan · 03-21-2008, 07:07 AM

Ive had this since .5, or about that time. Its super old, and something you just have to get used to since there isnt a fix that I am aware of.

Mattias · 03-21-2008, 09:48 PM

I get the same problem with my X1950 PRO, and I don't get it with anything so it is definatly mod related. It doesn't always happen but sometimes I get it on weapons as well.

SnipingCoward · 03-22-2008, 06:11 AM

which nvidia performance setting are u using? try switching to "Performance"

after u updated drivers u should empty the cache to let bf2 reoptimize the shaders thus fixing the prob

rudd said its AA related so switching off aa might solve it (i only use ingame AA for nvidias AA messes with the chat text and becomes unreadable)

[R-DEV]Spearhead · 03-22-2008, 01:35 PM

The "melted" sandbags should be gone now in 0.75. Please report any new sightings of this since it should have been fixed by the shaders AFAIK.

GasseG · 04-02-2008, 02:01 AM

Saw a other graf-bug on youtube and someone wrote:
"Yo here's a Fix for this problem

1. go into bf2 menu and disable AntiAliasing - save and exit

2. delete the battlefield cache files (in your \Documents and Settings[username]\My

Documents\Battlefield 2\mods\bf2\cache\ directory)

3. start bf2 - play a map without AntiAliasing (for recaching without AA)

4. disconnect and set AntiAliasing back

5. restart game

Works great!!!"

Maybe works here as well!?

I have the melted sandbags problem in 0.75 by the way.

GasseG · 04-02-2008, 04:57 PM

Did what I wrote before and guess what happend!

Now I get kickad by f**kbu....sorry punkbuster, for "MD5Tool mismatch mods\pr\gamelogicinit.con (len=2048 )"!!??

I have updated my PB manually and restarted the computer but nothing seems to help! Every second time the the sandbags look ok anyway!

Does anyone know how to fix the problem without reinstalling.

krisfx · 04-03-2008, 08:39 AM

Its more than likely because we are all on directX10 me and my friend have the same problem with halo 2 pc and some others that use directX 9 =]

GasseG · 04-03-2008, 09:43 AM

Quote:

Originally Posted by krisfx

Its more than likely because we are all on directX10 me and my friend have the same problem with halo 2 pc and some others that use directX 9 =]

Should I use som older version of directX then?

Deadfast · 04-03-2008, 10:52 AM

The kick message has got nothing to do with DX version.

The file mods\pr\gamelogicinit.con is modified. Did you do something with it?

bust331 · 04-03-2008, 12:48 PM

I too have this problem with my 8600GT, it's pretty annoying.

I read somewhere it had to do with how the developers had the polygons too close to each other or some crap like that.

Do any ATI users have this problem as well?

03-21-2008, 09:48 PM	#12
Mattias Join Date: Aug 2007 Location: England Posts: 2	I get the same problem with my X1950 PRO, and I don't get it with anything so it is definatly mod related. It doesn't always happen but sometimes I get it on weapons as well.
Mattias Join Date: Aug 2007 Location: England Posts: 2

03-22-2008, 06:11 AM	#13
SnipingCoward Join Date: Dec 2007 Posts: 545	which nvidia performance setting are u using? try switching to "Performance" after u updated drivers u should empty the cache to let bf2 reoptimize the shaders thus fixing the prob rudd said its AA related so switching off aa might solve it (i only use ingame AA for nvidias AA messes with the chat text and becomes unreadable)
SnipingCoward Join Date: Dec 2007 Posts: 545	Got a PROBLEM? Check this: Project Reality Detailed Installation Guide "Hello, IT! ... Yes, have you tried turning it on and off again?" Jonny: "LAT rockets are anti-infantry"

04-02-2008, 02:01 AM	#15
GasseG Join Date: Mar 2008 Posts: 49	Saw a other graf-bug on youtube and someone wrote: "Yo here's a Fix for this problem 1. go into bf2 menu and disable AntiAliasing - save and exit 2. delete the battlefield cache files (in your \Documents and Settings[username]\My Documents\Battlefield 2\mods\bf2\cache\ directory) 3. start bf2 - play a map without AntiAliasing (for recaching without AA) 4. disconnect and set AntiAliasing back 5. restart game Works great!!!" Maybe works here as well!? I have the melted sandbags problem in 0.75 by the way.
GasseG Join Date: Mar 2008 Posts: 49
	Last edited by GasseG; 04-02-2008 at 02:29 AM.

04-02-2008, 04:57 PM	#16
GasseG Join Date: Mar 2008 Posts: 49	Did what I wrote before and guess what happend! Now I get kickad by f**kbu....sorry punkbuster, for "MD5Tool mismatch mods\pr\gamelogicinit.con (len=2048 )"!!?? I have updated my PB manually and restarted the computer but nothing seems to help! Every second time the the sandbags look ok anyway! Does anyone know how to fix the problem without reinstalling.
GasseG Join Date: Mar 2008 Posts: 49

04-03-2008, 08:39 AM	#17
krisfx Join Date: Mar 2008 Location: Leeds, UK Posts: 14	Its more than likely because we are all on directX10 me and my friend have the same problem with halo 2 pc and some others that use directX 9 =]
krisfx Join Date: Mar 2008 Location: Leeds, UK Posts: 14

03-21-2008, 07:07 AM	#11
[R-MOD]Dylan Forum Moderator Join Date: May 2006 Location: Oahu, Hawaii Posts: 3,828	Ive had this since .5, or about that time. Its super old, and something you just have to get used to since there isnt a fix that I am aware of.

03-22-2008, 01:35 PM	#14
[R-DEV]Spearhead PR Documentation Manager Join Date: May 2007 Germany Location: Frankfurt, Germany Posts: 748	The "melted" sandbags should be gone now in 0.75. Please report any new sightings of this since it should have been fixed by the shaders AFAIK.

04-03-2008, 10:52 AM	#19
Deadfast Join Date: Jul 2007 Czech republic Location: Prague Posts: 1,824	The kick message has got nothing to do with DX version. The file mods\pr\gamelogicinit.con is modified. Did you do something with it?
	Turn 360 degrees and walk away is what you should do tbh. - [R-CON]Desertfox

04-03-2008, 12:48 PM	#20
bust331 Join Date: Nov 2007 Posts: 11	I too have this problem with my 8600GT, it's pretty annoying. I read somewhere it had to do with how the developers had the polygons too close to each other or some crap like that. Do any ATI users have this problem as well?
bust331 Join Date: Nov 2007 Posts: 11

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Sponsored Links

Sponsored Links