![]() |
|
|||||||
| Performance threads All discussions about CoD performnce |
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
|||
|
|||
|
You have to add Antiepilepsy=0 manually in tour config file (docs folder, not steam folder)
the line epilepsyfilter=0 doesn't works, the switch in GUI changes epilepsyfilter from 0 to 1 but the line command is ineffective, try it works for me Cheers |
|
#2
|
|||
|
|||
|
Im going to say Placebo as well. I tested the frame rate and stutters, and they seem to be exactly the same. 45 average FPS with epilepsy filter on and off. Plus nothing looks different with the filter on or off.
Edit: I went back to check again to make sure, and it still was the same. Not one thing changes in the game no matter if the filter is on or off. All the guns still have flames coming out of the barrels, and all the flashes still happen when you hit your target. I don't understand why they would have a switch that does nothing. I hope I am mistaken by this and there is in fact a change when you turn on or off the filter. But from everything I can see, nothing changes. Last edited by [RS]Boomer; 04-07-2011 at 06:53 PM. |
|
#3
|
|||
|
|||
|
Quote:
[BOB] EpilepsyFilter=0 EpilepcyFilter=0 Epilepsyfilter=0 Epilepcyfilter=0 Antiepilepsy=0 Antiepilepcy=0 AntiEpilepsy=0 AntiEpilepcy=0 AntiEpilepsyFilter=0 AntiEpilepcyFilter=0 Antiepilepsyfilter=0 Antiepilepcyfilter=0 in both the conf.ini (docs folder & steam folder) it dose absolutely nothing what so ever and performance across many different trk files is identical with them all set to either 1 or 0 and pre or post beta patch. |
|
#4
|
|||
|
|||
|
Quote:
AntiEpilepcy=0 AntiEpilepsy=0 EpilepsyFilter=0 EpilepcyFilter=0 Nevertheless, it doesn't seem to work at all. Maybe the effect the filter adds is gone, but it's still running somehow and stealing lots of frames. Just because: Why do I get 150+fps (yes, one-hundred-and-fifty-plus!) with a 640x480 window (and that with a graphics card that isn't even supported officially, the HD3870), and just 15-20 @ 1024x768? There has to be something extremely pixel-dependant eating up the whole performance. I've never ever seen any program with such large performance differences with so little resolution steps, not even software rendered games 10+ years ago. The filter, as described running through the whole screen pixel by pixel is definately still running, maybe it just doesn't alter the pixels anymore, but it's still checking. We have to get rid of it completely. |
|
#5
|
|||
|
|||
|
so your all saying this was intended to be Anti-community-rage filter?
notfinishednotoptimisedsim = 1 |
![]() |
| Thread Tools | |
| Display Modes | |
|
|