]]>
]]>
]]>
]]>
]]>
]]>
]]>
]]>
]]>
1st for simple mappers such as myself, who will not be so intent on creating seperate packs for thiers maps, either we are lazy or we think our work is ours alone or we just know how.
2nd have a repository for those that wish to create content packs such as texture packs (utx or whatever T:V will have), BSP brushes, Models, et al.
Of course this sort of thing will take in too much HD and Bandwidth from you.
Statistics: Posted by Roy Fokker — Thu Jul 31, 2003 9:51 pm
]]>
PreyingMantis3.myLevel
Within my new map, PreyingMentis3, there is a virtual "package" called "myLevel" where i save all my custom mesh, sounds and textures. Everything from the heightmap for the terrain to the fancy new base structures i make are saved within the map itself, within the package called "myLevel." Let me be clear, this isnt speculation. (This is how mapping is currently done 99% of the time for unreal engine games right now. Everything goes into the map, unless within a mod situation with many maps sharing custom assets. The raw simplicity of having ONE file versus 10... goes without saying.) Anyways, back to the example...
In this hypothetical... my terrain heightmap is a texture. Plus, I got cool textures. My new base made in 3dsmax is imported as a static mesh. Here's how it works within UT2k3. I suspect the only difference will be file names, not even format...
texture: PreyingMantis3.myLevel.coolTexture1 (coolTexture1.tga import)
mesh: PreyingMantis3.myLevel.PM_base1 (PM_base1.ase import)
It's all saved within the map itself. NOW, in terms of collaborating, i can do two different things. I can save my packages outside the map, instead of within myLevel.
texture: TseTseTextures1.utx
mesh: TseTseStaticMesh1.usx
If another mapper wants the "coolTexture1.tga" texture, they just load that UTX within the editor and link to it. If i had NOT done this independent file, another mapper would need to duplicate the texture from the myLevel in my map, into the myLevel of their map. That's actually really easy to do...
The other way to share, besides makin usable packages is this idea of raw files.
Texure: coolTexture1.tga
Static Mesh: PM_base1.ase
For ssometbody to now use them, they still must import and save them into a proper unreal package, either within their map's "myLevel" package or into some other file:
texture: tvmaps_texturePack1.utz
mesh: tvmaps_staticPack1.usx
I suspect what people here really, really want once they understand how this all lays out are these kinds of massive packages of submitted raw materials.
Im just saying that i dont plan to personally go out of my way to provide raw materials when they can be simply used from my map. It's extra effort. It can risk confusing assets. It's to take away from my work in making a map...
But for some people, they make "prefab" stuff. In other words, they design stuff which is useful across many maps.
I'm just not concerned about this too much at this point, really. Im babbling here... but the issue isnt worth this many words. At least, not at this point...
Statistics: Posted by TseTse — Thu Jul 31, 2003 7:09 pm
]]>
Actually, you may be right about the MyLevel package issue in terms of how content can be stored (though the maps that ship will likely draw nearly all of their content from various content packages), but keep in mind that whenever that content is exported from the editor, it will be saved to the appropriate filetype (textures -> .utx for example). Individual sounds, textures etc. must be made part of a package before they can be used (I think).
For purposes of the repository, it may be a good idea to allow users to submit both individual content pieces (.wav) and package files (.uax) as both will be usefull. Although this brings us back to the possibility of having duplicate content I think ;/
Statistics: Posted by alingis — Thu Jul 31, 2003 7:03 pm
]]>
]]>
In my mind, I've been picturing a content repository on the site where authors would submit individual files, or packages of files (in .zip format) for other authors to use. I don't mean that utx or uax (or whatever) files would be submitted. These would be individual textures (jpeg, tiff, png?), wav files, bsp files, etc.
This would provide for enforcing unique filenames at least within the context of the tribesvmaps.com content database. What individual authors actually do with the raw content is up to them ... the issue of overwriting content and causing players to get dropped from servers is a separate thing.
Statistics: Posted by Bytor — Thu Jul 31, 2003 4:08 pm
]]>
]]>