More often than not I see people post about workflow problems that aren't package spefic or span multiple programs, so I think having it all in tech talk is good enough. If things are divided too much it lowers the visibilityof topics.
This has come up a few times and it normally gets shot down for a few reasons.
1) It fractures and segregates the forums. A max user might actually have an answer to the persons maya problem but their paths don't ever cross.
3) There are a lot of problems that are similar in other packages and how you fix it in one might lead to a solution in another. Also seeing how other apps handle it can lead to some pretty cool discussions and sometimes script or plug-ins being written or features requested.
4) Proper labeling of thread titles can tell people what they need without stuffing posts in another box, deeper in the closet. "NOrmalz HALP!!!1" vs "Normal maps, 3dsmax viewport"
Replies
1) It fractures and segregates the forums. A max user might actually have an answer to the persons maya problem but their paths don't ever cross.
3) There are a lot of problems that are similar in other packages and how you fix it in one might lead to a solution in another. Also seeing how other apps handle it can lead to some pretty cool discussions and sometimes script or plug-ins being written or features requested.
4) Proper labeling of thread titles can tell people what they need without stuffing posts in another box, deeper in the closet.
"NOrmalz HALP!!!1" vs "Normal maps, 3dsmax viewport"
just a thought !
cheers