Crashing to Desktop when i click Join Games

If you find a bug within PR:BF2 (including PRSP), please report it here.
WallEYE-(PR)
Posts: 275
Joined: 2006-02-12 19:24

Post by WallEYE-(PR) »

Also if find the error right click on your ICON and go to properties, then go to TARGET and will look like this "C:\Program Files\EA GAMES\Battlefield 2\BF2.exe" +modPath mods/pr +menu 1 +fullscreen 1, Change the 1 to 0 after FULLSCREEN and it will tell you what the error is 99% of the time
:firing: StrkTmWallEyE-(PR) :camper:
Zisko
Posts: 2
Joined: 2006-05-21 15:36

Post by Zisko »

I did it, but I have no idea what to do with it.

By the way: Normal BF2 and Special forces are running without problem, PRM craches every time since I reinstalled my whole system, using the newest drivers.

Update: With PRM 0.4 the problem is gone
You do not have the required permissions to view the files attached to this post.
Last edited by Zisko on 2006-11-18 00:49, edited 1 time in total.
-=TB=-Bubbles
Posts: 1
Joined: 2006-11-24 11:49

Post by -=TB=-Bubbles »

I've had the same problems and here's what helped on my PC:

Update your BIOS driver, update your graphics card driver, check your RAM, check your Power supply and run a disk check.

Be shure that you always have the same resolution on your desktop as in your game, I play at 1024x768

Find the file VideoDefault.con
(...\EA Games\Battlefield2\Mods\Bf2\Settings\

set: renderer.allowAllRefreshRates 1

By default this setting is set to 0, however it is strongly recommended that you set it to 1 so that your refresh rate can exceed 60Hz in Battlefield 2. In fact if you have a refresh rate fix installed, or are using a refresh rate override on your system, BF:V will not load up - usually giving an error, crashing to desktop or stopping at a black screen - if this setting is not set to 1. There is no reason this should be left set at 0.

Set: renderer.setFullScreen 1

If you want to start BF2 in a window on your Desktop as opposed to the normal full screen, set this to 0 to do so. You may experience problems or crashes if using windowed mode, however your performance should be improved. Note that if you want to use windowed mode, you should choose a Display Mode for the game which is equal to or smaller than your Windows Desktop resolution otherwise portions of the game display will be cut off.

Set: renderer.fieldOfView 1

The default Field of View (FOV) is 1. Values between 0 up to 1 (e.g. 0.85) will give you a closer (zoomed right in) FOV than normal, while values over 1 (e.g. 1.5) will give you a farther FOV than normal. Experiment with values close to 1 to see if it suits you better than the default. Values below 1 can improve performance due to a reduction of what is being drawn (visible) on screen.

Set: renderer.globalLodRadius 1

LOD is the Level of Detail. As objects get further away from the camera, the number of polygons rendered by the graphics card will be gradually reduced without any noticeable reduction in detail. This improves performance, particularly with large numbers of objects on the screen. The Global LOD Radius setting determines the radius around the character (imagine a bubble) beyond which LOD starts to reduce (at a rate based on the scale factor below). The higher this setting – given a constant (non-zero) scale factor – the higher the graphics details on objects, but the lower your fps. Increase this setting if you want crisper, more detailed objects around you, but at the cost of some fps. The default is 1, which is the lowest practical setting.

Set: renderer.globalLodRadiusScaleFactor 5

Having set the radius beyond which the Level of Detail begins to drop (see above), the LOD Radius Scale Factor setting determines the rate at which polygons are stripped from objects the further away they are from the camera outside this radius. The default is 5. Values lower than 5 decrease LOD decay (meaning higher graphics quality), values higher than 5 increase it (meaning lower graphics quality). If you want the absolute best level of detail, at the expense of some fps, choose 0, which means no reduction in LOD regardless of distance. The default 5 is a good balance, but experiment with slightly lower or higher values (e.g. 4 or 6) to see which increases your fps at the cost of minimal, if any, noticeable reduction in graphics quality.

Set: console.showstats 0

If set to 1, this option will automatically display a range of game engine statistics when a map in BF2 loads up. Not recommended for normal use. You can't disable the stats using the console.showstats command in the console - you will have to change its value back to 0 in the Videodefault.con file to remove it.

Set: renderer.useTrilinearFiltering 0

Insert this line into the Videodefault.con file, and set it to 0 to disable Trilinear filtering (and instead use Bilinear filtering). Trilinear and Bilinear Filtering are methods of texture filtering which affect the sharpness of textures as they fade into the distance. Disabling Trilinear filtering will improve performance with negligible graphics quality loss, so it is recommended you set to this to 0.

Especially the settings in the VideoDefault.con file seemed to helped my desktop crashes to zero!

Hope I've helped a little here, it helped me, but maybe it doesn't help your specific problems,

greetz Bubbles
gunpai
Posts: 17
Joined: 2006-10-21 17:24

Post by gunpai »

and even check things you wouldnt expect. I had to put in a new motherboard battery etc just when 0.4 came out. I dropped from high and medium settings to low settings with lots of crashes to desktop. I thought this was down to the patch and my comp not comin up to scratch. But in fact it was down to ....my bios was reset and put my cpu to run at 1.6ghz instead of the usual 2.17ghz. urgh damn my brain
Locked

Return to “PR:BF2 Bugs”