One of the problems in using FS2 Open for multi is the diversity of different builds, VPs, command line attributes, installation methods etc..
Each player has their own combination of these, which results in a huge heap of variables. Often you are not sure whether to expect the game to work or not, which is discouraging.
Also, I have to admit that this complexity has a negative psychological effect on my motivation to create bug reports -- "oh darn, I've no clue what input would be required to reproduce this fault, and most likely I don't even have access to that information".
When something "strange" happens in a multi game, one starts to think stuff like:
- is it a problem on the host side connection?
- was there a problem in my connection?
- bad connection of some other player causes this?
- does the host have a fuxored setup, hardware?
- is there something wrong on my setup, hardware?
- is it some sort of an incompatibility issue between participants

?
- is there something going on with the FS2NetD server?
- and so on, and so on..
And on top of this come the possible bugs in FS2 Open.
I understand the frustration SCP team feels, but it is also understandable that many of the multi ppl resort to Toms build, just in order to make things simple and to reduce the number of unknowns possibly killing the fun. In case of SCP, one doesn't even know what could possibly affect the success of a multi game and what can not.
Alltogether, to solve some of these problems, I think more uniformity is needed in the way FS2 Open is used in multi - how to do that, I've got no idea.
Badmouthing etc. towards the SCP team is of course a silly thing to do, but I'd like to see that more like a personal attribute of certain people, rather than a standard
