Talk:Modifying textures: Difference between revisions

From OniGalore
Jump to navigation Jump to search
m (AE talk:ModTXMP moved to AE talk:Modifying textures: Making name clearer - article's focus is on editing and re-importing TXMPs)
m (+cat)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
===Export/Import textures===
I tried to summarize four different reasons for the new article name in my move summary, and probably did a bad job of conveying what I was thinking on at least at two of them. For anyone who cares, the reasons were:
To export a single TXMP
#Because "Modifying [blanks]" is a lot clearer way to phrase something than "Mod[blank]", obviously.
  onisplit -extract:png txmp_dir ..\GameDataFolder\level0_Final\TXMPBOSS1talking.oni
#Also, we are now (since the article was made) favoring the use of descriptive words over four-ccs in tutorial names. "But what if we modders are thinking in terms of four-ccs?" That angle will be covered quite well once I do some more work on the wiki, trust me on this. Please trust me.
To export all the [[TXMP]] files:
#I chose "modifying" instead of "importing" because I want the article to focus just a bit more on how to handle textures in the graphics app, particularly the ones with transparency. Just a sentence or two for each common graphics app (GIMP, PS...) on how to preserve the information properly. So, the article should be about both editing and importing, due to the special options for TXMPs that make them harder to import than most file types. The exporting directions can be removed, it's just duplicate information that's found on the [[OniSplit]] page, and duped information can only result in confusion and more work as things change.
  onisplit -extract:png txmp_dir ..\GameDataFolder\level0_Final.dat
#By saying "textures" and not "TXMP"s, we allow the possibility of addressing other texture-related types that might be helpful (I'm thinking [[TXMB]], personally).
TGA and DDS are also supported using -extract:tga and -extract:dds.
I probably didn't need to write all this out, but it's kind of a policy thing that goes beyond this article, as you can see, and in the past there's already been plenty of arguing over this subject; I thought I might avoid controversy this time by making the rationale clear. Or, quite possibly, nobody cares and this is a waste of text. --[[User:Iritscen|Iritscen]] 19:12, 22 December 2008 (CET)


To import image files:
[[Category:Modding tutorials]]
  onisplit -create:txmp ..\GameDataFolder\level0_Final [options] source_image_file
where options can be
  -nouwrap - set the "U wrapping disabled" flag
  -nowwrap - set the "V wrapping disabled" flag
  -format:bgr555 (or dxt1) for most of the stuff
  -format:bgr32 for skyboxes
  -format:bgra4444 for transparent/reflective stuff (in a couple of places bgra5551 is used but probably it's not big deal if bgra4444 is used instead)
  -genmipmaps - generate mipmaps if they are not already present in the source file and if the source file is not dxt1 compressed
 
Example:
  onisplit -create:txmp ..\GameDataFolder\level0_Final -format:bgr555 -genmipmaps tga\concrete.tga
To batch process a folder of image files:
  onisplit -create:txmp ..\GameDataFolder\level0_Final -format:bgr555 -genmipmaps tga\*.tga
source_image_file can be dds or tga. "Color indexed" and "black and white" tga files are not supported currently. Other image file formats (png, jpg, bmp, tif) may work depending on Mono/.NET support for them.
onisplit will automatically prepend TXMP to the output file name if the source file name does not start with TXMP already.
 
For TXMP files that contain envmaps:
  onisplit -create:txmp ..\GameDataFolder\level0_Final -format:bgra4444 -genmipmaps -envmap:envmapname imagefile.tga
The envmap name can have the TXMP prefix but it is added automatically if missing.

Latest revision as of 01:15, 4 May 2022

I tried to summarize four different reasons for the new article name in my move summary, and probably did a bad job of conveying what I was thinking on at least at two of them. For anyone who cares, the reasons were:

  1. Because "Modifying [blanks]" is a lot clearer way to phrase something than "Mod[blank]", obviously.
  2. Also, we are now (since the article was made) favoring the use of descriptive words over four-ccs in tutorial names. "But what if we modders are thinking in terms of four-ccs?" That angle will be covered quite well once I do some more work on the wiki, trust me on this. Please trust me.
  3. I chose "modifying" instead of "importing" because I want the article to focus just a bit more on how to handle textures in the graphics app, particularly the ones with transparency. Just a sentence or two for each common graphics app (GIMP, PS...) on how to preserve the information properly. So, the article should be about both editing and importing, due to the special options for TXMPs that make them harder to import than most file types. The exporting directions can be removed, it's just duplicate information that's found on the OniSplit page, and duped information can only result in confusion and more work as things change.
  4. By saying "textures" and not "TXMP"s, we allow the possibility of addressing other texture-related types that might be helpful (I'm thinking TXMB, personally).

I probably didn't need to write all this out, but it's kind of a policy thing that goes beyond this article, as you can see, and in the past there's already been plenty of arguing over this subject; I thought I might avoid controversy this time by making the rationale clear. Or, quite possibly, nobody cares and this is a waste of text. --Iritscen 19:12, 22 December 2008 (CET)