Industrial Park (level editor): Difference between revisions

Content added Content deleted
Battlepedia>Igorseabra4
No edit summary
Battlepedia>Igorseabra4
No edit summary
Line 1: Line 1:
'''Industrial Park''' is a tool made by community member [[User:igorseabra4|igorseabra4]] in C# using SharpDX. It is an editor capable of opening a number of [[HIP|HIP/HOP files]] and display the level, with models and textures for level and objects, as well as edit some of the [[asset]] types. The program is still under development, so features are still planned; the latest release version is Preview 41 and the information on this page is up to date with it.
'''Industrial Park''' is a tool made by community member [[User:igorseabra4|igorseabra4]] in C# using SharpDX. It is an editor capable of opening a number of [[HIP|HIP/HOP files]] and display the level, with models and textures for level and objects, as well as edit some of the [[asset]] types. The program is still under development, so features are still planned.


This tool is based off from, and shares a lot of its source code with another one of the creator's tools: [https://info.sonicretro.org/Heroes_Power_Plant Heroes Power Plant], a tool to edit levels in [https://info.sonicretro.org/Sonic%20Heroes Sonic Heroes]. Being also based on the RenderWare engine, both games share their model format. It also gave Industrial Park the convention of being named after a level in the game.
This tool is based off from, and shares a lot of its source code with another one of the creator's tools: [https://info.sonicretro.org/Heroes_Power_Plant Heroes Power Plant], a tool to edit levels in [https://info.sonicretro.org/Sonic%20Heroes Sonic Heroes]. Being also based on the RenderWare engine, both games share their model format. It also gave Industrial Park the convention of being named after a level in the game.
Line 156: Line 156:
** '''Import HIP Archive''': Choose a HIP, HOP or Settings.ini file (from HipHopTool-style exported archive) to import. All layers and assets from the selected file will be added to the current one. Layers will be ordered by the Collapse Layers function. If an asset with the same ID is already present, you will be prompted whether to overwrite it or not, except for [[COLL]], [[JAW]], [[LODT]], [[PIPT]], [[SHDW]] and [[SNDI]], all of which will be merged into one single asset. This is useful for [[Asset porting]].
** '''Import HIP Archive''': Choose a HIP, HOP or Settings.ini file (from HipHopTool-style exported archive) to import. All layers and assets from the selected file will be added to the current one. Layers will be ordered by the Collapse Layers function. If an asset with the same ID is already present, you will be prompted whether to overwrite it or not, except for [[COLL]], [[JAW]], [[LODT]], [[PIPT]], [[SHDW]] and [[SNDI]], all of which will be merged into one single asset. This is useful for [[Asset porting]].
** '''Import Multiple Assets''': Choose any amount of files to use as external data for assets and import them. This is useful for assets which are commonly from external editors, such as textures, models and sounds. Imported sounds will automatically be sent to the [[SNDI]].
** '''Import Multiple Assets''': Choose any amount of files to use as external data for assets and import them. This is useful for assets which are commonly from external editors, such as textures, models and sounds. Imported sounds will automatically be sent to the [[SNDI]].
** '''Import Models''': This function allows you to select OBJ, DAE or DFF files to import as new [[MODL]] assets. DFFs will be imported as they are, while OBJ and DAE will be converted to DFF. Models must contain vertex positions, vertex normals and texture coordinates for the import to work. DAE files must have been exported from 3ds max's exporter; OBJs can have been exported from any 3d model editor. This does not work with rigged models and any rigging present in the files will be discarded during the conversion.
** '''Import Models''': This function allows you to select model files to import as new [[MODL]] assets. Industrial Park uses Assimp for model importing, so DFFs will be imported as they are, while other formats will be converted to DFF - using either OBJ or FBX is recommended. This does not work with rigged models and any rigging present in the files will be discarded during the conversion.
** '''Import Textures''': This function allows you to select image files to import as new [[RWTX]] assets. You can choose a few settings for the textures and also if existing textures with the same names should be overwritten or not. Supported formats: BMP, GIF, EXIF, JPG, PNG, TIFF and RWTEX (exported from Magic.TXD).
** '''Import Textures''': This function allows you to select image files to import as new [[RWTX]] assets. You can choose a few settings for the textures and also if existing textures with the same names should be overwritten or not. Supported formats: BMP, GIF, EXIF, JPG, PNG, TIFF and RWTEX (exported from Magic.TXD).
** '''TXD Archive''':
** '''TXD Archive''':
Line 257: Line 257:
|| <span style="color:#FF7F00">Edit</span>, <span style="color:#0000FF">Display</span>
|| <span style="color:#FF7F00">Edit</span>, <span style="color:#0000FF">Display</span>
|| BSP and JSP models will be displayed in the world. Industrial Park's BSP/JSP editor allows you to:
|| BSP and JSP models will be displayed in the world. Industrial Park's BSP/JSP editor allows you to:
* Edit individual mesh colors and material names (JSP only);
* Edit individual mesh colors and material names (JSP only).
* Use the Export function to export the model as OBJ - the exported file can be imported in any 3d model editor and contains vertex colors. If you don't care about keeping them, you can use any 3d model editor's OBJ importer, but if you want to keep them, you must use the importvcolorobj MAXScript for 3ds max (it's included in the release, check the Resources folder). The model will be expecting all textures as PNG in the same directory. It can also be exported as a raw BSP (BSP assets) or DFF (JSP assets);
* Use the Export function to export the model to one of the Assimp formats. OBJ or DAE are recommended. This might not work on all models; it has a higher change of working on Xbox files. It can also be exported as a raw BSP (BSP assets) or DFF (JSP assets).
* Import function grayed out as it hasn't been implemented yet.
* Import function grayed out as it hasn't been implemented yet.
Editing of the JSP asset in the JSPINFO layer is not supported.
Editing of the JSP asset in the JSPINFO layer is not supported.
Line 361: Line 361:
|| <span style="color:#FF7F00">Edit</span>, <span style="color:#0000FF">Display</span>
|| <span style="color:#FF7F00">Edit</span>, <span style="color:#0000FF">Display</span>
|| Assets with references to MINF or MODL will be displayed as that model in the world. Industrial Park's MODL editor is similar to the BSP/JSP editor and allows you to:
|| Assets with references to MINF or MODL will be displayed as that model in the world. Industrial Park's MODL editor is similar to the BSP/JSP editor and allows you to:
* Edit individual mesh colors and material names;
* Edit individual mesh colors and material names.
* Use the Export function to export the model as OBJ. The exported file can be imported in any 3d model editor. This functions the same as the BSP/JSP exporter (explained above) and thus the exported OBJ will contain vertex colors, but they are usually empty on MODL assets, so importing with or without them will likely not make a difference. The model will be expecting all textures as PNG in the same directory. It can also be exported as a raw DFF;
* Use the Export function to export the model to one of the Assimp formats. OBJ or DAE are recommended. This might not work on all models; it has a higher change of working on Xbox files. It can also be exported as a raw BSP (BSP assets) or DFF (JSP assets).
* Use the Import function to select an OBJ, DAE or DFF file to import. DFFs will be imported as they are, while OBJ and DAE will be converted to DFF. The model must contain vertex positions, vertex normals and texture coordinates for the import to work. DAE files must have been exported from 3ds max's exporter; OBJs can have been exported from any 3d model editor. This does not work with rigged models and any rigging present in the file will be discarded during the conversion.
* Use the Import function to select a model file to import. Industrial Park uses Assimp for model importing, so DFFs will be imported as they are, while other formats will be converted to DFF - using either OBJ or FBX is recommended. This does not work with rigged models and any rigging present in the files will be discarded during the conversion.
|-
|-
| align=center | [[MRKR]]
| align=center | [[MRKR]]
Retrieved from "https://heavyironmodding.org/wiki/Industrial_Park_(level_editor)"