Fixed the link, but a new version has now been released:

http://fhpubforum.warumdarum.de/index.php?topic=14075.new#new

There's not enough resolution in the texture/render to make any claim which version of the camo pattern is displayed here. I see varying claims here about colors based on pictures taken under different circumstances (lighting, camera settings/properties, monitor calibration, color perception of the human brain etc) of items that even IRL vary greatly (weathering, storage condition, dye degradation, fabric tension, age and variation of the quality of cloth, dyes and chemicals used at the time of manufacture etc)...

Lighting is incredibly complex. Outdoor lighting is affected by things like weather conditions (cloudiness, air humidity filters light differently), occlusion and reflection of nearby objects and ground, even our sun's light emittance varies from time to time (relative size in sky due to time of year, even sunspots). Indoor lighting is greatly affected by the type of light source, the chemicals in the light bulb and type of material. The colors on the walls and the chemicals and texture of the paint.

Anyone attempting to make definitive statements about color is nuts and only deluding himself. Colors and even contrast are not absolute and change continuously. As a graphics artist, I work with colors all the time and have developed an appreciation for the way nature manipulates color (and it's observers!) as it pleases. When someone asks me what my favorite color is, I honest to god don't know what to answer; for this color changes all the time. I see this as a variation of the Heisenberg principle, color changes not between observations, but changes because it is being observed.

Also, those missing the long or "greatcoats", modelling and animating them might have been more difficult than it would have been worth in the end.

Correct, this has proven to be pretty much impossible in BF2.

There was a number of minor problems and some miscommunication. A forum database table broke somehow, and at the same time the management panel went off-line due to invalid SSL certificate for unknown reason. It also didn't help that I was notified a bit late. Anyway, all should be fixed now.

The missing player model shadows is another BF2 bug to my knowledge, I doubt we can fix this.

The crash/error you get when exiting is common, most of us have it. This is a BF2 bug, which happens more frequently in FH2 because the mod uses more memory. This is benign and you can ignore this one.

BF2 doesn't unload all memory between levels, so at some point BF2 engine may run out of memory. Restarting the game fixes this.

As said, FH2 uses more RAM than BF2 vanilla, so recommended is 2GB to 3GB RAM, and 256MB to 512MB video card memory. Updating your graphics drivers can solve instability, also ensure the GPU is cooled properly and power supply is sufficient.

Switching audio from hardware mode to software mode can improve performance, quality and fix instability.

On the M10, it might occur with the turret rotated at some angles, or possibly if the swiveling MG on the turret is manned/rotated by another player. But generally this rarely happens, if it does happen frequently, please report it.

This is intentional, as Ts4EVER said, this prevents the defenders from spawning on top of the attackers.

I have released a new version of BfMeshView today (1.9.0):

http://www.bytehazard.com/bfstuff/bfmeshview/

Change log:
* fixed crash when restoring child windows under certain conditions
* fixed double clicking on texture not always opening file
* fixed error when double clicking in treeview when no BF2 mesh was opened
* fixed transparancy for some shaders
* fixed crash when selecting some .geo nodes in treeview
* fixed rare crash in normal map converter
* fixed bundledmesh shader shadow/wreck texture
* fixed bug in sample generator
* fixed assert in sample generator
* added material editing
* added UV editor
* added sample generator
* added tool to fix broken samples
* added BF2 file format version to treeview
* added BF2 vertex attribute info to treeview
* added full BF1942 tree mesh (*.tm) support
* added display of texture memory use
* added "open folder" in treeview context menu
* added support for all BF2 collisionmesh files (including weapons)
* added experimental vertex transform tool
* added normal map converter options
* invalid sample points are now no longer rendered at origin
* upgraded treeview control
* disabled annoying treeview node hover tooltips
* optimized treeview refreshing
* texture maps that fail to load are now marked in treeview
* double clicking on textures in treeview will now open the file
* can now view single unshaded texture by selecting map in treeview
* skin bone transforms are now drawn in viewport
* arrow keys now properly selects treeview node again

Most useful new features are:
1) The material editor, which allows you to change the textures and even shaders and transparency mode of exported meshes.
2) UV editor, which is useful to fix minor UV errors.
3) Texture memory indicator in status bar, can give you an idea how (in)efficient assets are.
4) Various small helpers to debug bad exports.