Helli
07 Dec 2006, 17:15
Hello Coffee-Drinkers,
I am not very happy about the title of this thread.
So what do I mean:
I am using presently Arno's excellent "ObPlacer_XML" tool to place various objects over autogen landscapes.
Since I have not yet produced any objects of my own (Gmax or other), I have to use objects from available libraries.
It happened to me now several times, that for some library object the associated texture-bmps were wrong, not complete, missing or located in another part of the library.
My problem: how to determine, which texture-bmps belong to or are required for a particular library object.
I know, that this information is stored somewhere in the bgl- and mdl-file, but I am not a programmer.
The ObPlacer_XML does not provide this information (at least I have not come across it).
The only tool which I know having this feature is John Masterson's "Library Object Manager", but since it is treated there only as a kind of add-on feature, it is not the quickest and easiest way to do it.
Is there a nice and tiny tool around to be used by an amateur like me?
Has Arno something like this up his sleeve?
Or in other words, how do you solve this problem, when it catches up with you?
Helli
I am not very happy about the title of this thread.
So what do I mean:
I am using presently Arno's excellent "ObPlacer_XML" tool to place various objects over autogen landscapes.
Since I have not yet produced any objects of my own (Gmax or other), I have to use objects from available libraries.
It happened to me now several times, that for some library object the associated texture-bmps were wrong, not complete, missing or located in another part of the library.
My problem: how to determine, which texture-bmps belong to or are required for a particular library object.
I know, that this information is stored somewhere in the bgl- and mdl-file, but I am not a programmer.
The ObPlacer_XML does not provide this information (at least I have not come across it).
The only tool which I know having this feature is John Masterson's "Library Object Manager", but since it is treated there only as a kind of add-on feature, it is not the quickest and easiest way to do it.
Is there a nice and tiny tool around to be used by an amateur like me?
Has Arno something like this up his sleeve?
Or in other words, how do you solve this problem, when it catches up with you?
Helli