Last Month the Japanese try to retrive this mod a little bit more. They played in the at 2pm CET. At the moment the gametracker,com Server Monitorring is off. Hope soon they turn it on. The ranking seems to work.
Registered Member #2506 Joined: [ 17:20 ] [ 02 Oct 2012 ] Posts: 25
Forcing Vsync doesn't work with latest ATI drivers (14.x) in new Windows OSs (Vista,7,8). Something to do with a Microsoft standard that ATI chose to follow that prevents Vsync forcing - officially it should only be done within the game/program's own options. And 1942 doesn't have any Vsync options *(see note). Que nasty image tearing (look at a flag pole, move side to side, see horizontal lines cutting it up). If you don't know, this is due to the framerate (in 1942, capped to 100 fps as default) differing from your monitor refresh rate (probably 60 Hz on a lcd).
So you need to synchronise the fps and refresh to 60 fps / hz each. Which turns out isn't so easy - neither CCC, Raedeon Pro, RTSS or anything else I've found actually enable Vsync at all - the following is the *only* way it can be done afaik:
2. Run it, it'll show up in the task bar. If it's not running, it won't do anything. So Just minimize the window when you're done. - Firstly, click Global in the App Profile list, and select None (you don't want it messing with other games). - Click the + butotn (lower left) and find and select your BF1942.exe in " ...EA GAMES/Battlefield 1942". - Select this in the App Profile list, and change settings as follows: Application Detection Level: High (Medium seems to work, but just to be on the safe side...) Force Tripple Buffering: Off (it doesn't work with 1942 anyway) Force Vsync: On
3. This immediately works, but will make 1942 feel slightly sluggish (it's still rendering 100 fps and dumping 40, which just makes the whole thing feel a little sluggish, like mouse lag or just a low fps). So you want to sync 1942's framerate to the vsync/refresh rate. - Open VideoDefault.com in "...EA GAMES\Battlefield 1942\Mods\bf1942\Settings". - Add a new line with "renderer.lockfps 60". the whole file will look like this:
- Save, and close. (You can actually adjust this on the fly in-game through the console, just use "renderer.lockfps 60" or change the number and experiment)
- As mentioned, trying to enable Vsync by any other method DOES NOT WORK. Only D3DOverrider actually enables vsync.* (see note)
- Altering renderer.lockfps to any value other than the refresh rate will cause various image glitches, either: If vsync is on, and lock fps is not 60, it'll cause stuttering of the image. If vsync is off and lockfps is used *at all*, even lockfps 60 (eg. you thought you were clever and could get away with just locking fps to 60 or 120 without using vsync) it'll cause even worse image tearing, and possible massive aliasing / moire (fuzzyness) around the bottom and/or top of the screen. It *only* works with both vsync and lockfps together.
*NOTE: - 1942 does have an internal vsync enabler that can be used via the console (press ` in game) but this can't be run automatically (adding it to .con files causes the game to crash on opening) and it disables itself if you ever Alt-Tab to anything. That said,
The rest you can enable via CCC - I'd do so using a profile.
AA Mode: Override AA Samples: 8x (it seems to create less aliasing than the 12x+ / EQ ones - check the edges of plane wings) Filter: Standard AA Method: Adaptive multisampling** Morphological Filtering: Off (On will cause all text to look terrible / cut up)
AF Mode: Overide AF Level: 16x Texture Filter Quality: High Quality Surface Format Opt: On
Wait For Vertical Refresh: On, unless... (doesn't really matter, it doesn't change anything anyway) OpenGL Triple Buffering:: Off (again, doesn't work with 1942)
Tessallation Mode: AMD optimized Max Tessallation: AMD Optimized
**Note: For AA Method use either Multisampling (worst - but not by much) or Adaptive Multisampling. Using Supersampling is the No. 1 cause of FPS drop in 1942 - we're talking by a factor of 10. Whilst I can get 300fps with the other two, Supersampling drops it to 30 in the same spot, and is worst with lots of tree areas, specifically with mods using vegitation models taken from BF:Vietnam (eg. EOD, FHSW). The downside to the other two is they leave a fuzzyness to some ground and water textures, made even worse if you don't use Vsync + FPS lock - but for the sake of 10x better FPS, it's a decent tradeoff.