

> (meshes? and) materials also share a global namespace.
Only material scripts do. Meshes are very much like Graphics.png (except for #480 *hide*).
There's also the argument that we might introduce a system to disambiguate the sounds or meshes in future.
Also, this makes it harder to completely remove a object definition - you always have to check for leftover sounds. And am I overlooking something, or won't this end up loading a lot of unnecessary sounds once we have multiple object packs? To say nothing about scenarios wanting to only load parts of an object pack or using SkipDefs.
I don't know. For things that are used by a lot of object definitions - yes, clearly. But otherwise, this doesn't really feel like an obviously good idea to me.
Also, this makes it harder to completely remove a object definition - you always have to check for leftover sounds. And am I overlooking something, or won't this end up loading a lot of unnecessary sounds once we have multiple object packs? To say nothing about scenarios wanting to only load parts of an object pack or using SkipDefs.
I don't know. For things that are used by a lot of object definitions - yes, clearly. But otherwise, this doesn't really feel like an obviously good idea to me.

> There's also the argument that we might introduce a system to disambiguate the sounds or meshes in future.
I very much doubt that. It is far, far easier to just prefix the problematic sounds, so nobody will be annoyed enough to design and implement something more complicated.
> you always have to check for leftover sounds
You have to do that anyway, lest you break other objects which also use the sound that just happened to be in that particular folder.
> And am I overlooking something, or won't this end up loading a lot of unnecessary sounds once we have multiple object packs?
In that case we could put the sounds in the toplevel directory of that object pack. But maybe we will instead change to load every object at the start of the game to shorten the scenario load times? That actually sounds more plausible to me than the hypothetical "system to disambiguate" :-)
> lest you break other objects which also use the sound that just happened to be in that particular folder.
In that case I'm all for having them in a more global folder. I'm talking about the (all-too-common) case that we have a sound that is actually very specific to one object.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill