Hi,
I have experencied the same situation in some tests, and I agree with Andrew when he says that some form of justification is necessary.
you also have seen that a hop penalty of 10 is too high ? Can you explain your setup a bit more ?
The problems of TQ emerges when the rate of devices increase, because especially in mixed b,g,n networks TQ does not distinguish between fast and slow link. We all know that brodcast losses does not say almost nothing about link speed or load.
The only way to improve the TQ metric is a cross-layer implementation as already experienced (considering only bandwidth) in my tests. Obviously this means breaking the "universal" compatibility with network interfaces, the use of mac80211 and cfg80211 in any case can limit this problem in my opinion.
I am certain that you great ideas and that you spend a lot of time on working with batman / meshing. However, it is somewhat difficult to review / discuss / adapt your work since we have a hard time understanding your concepts without proper explications / documentation. Would it possible for you to talk/write a bit more about your stuff ?
The WBMv5 is a good opportunity to chat because you get all of us in one place. ;-)
Cheers, Marek