EvilEngine/JSP: Difference between revisions

From Heavy Iron Modding
Content added Content deleted
Battlepedia>Seil
mNo edit summary
Battlepedia>Seil
No edit summary
Line 1: Line 1:
{{AssetInfobox
|subtitle=JSP
|type=[[RenderWare asset|RenderWare]]
|games=Battle for Bikini Bottom<br>The SpongeBob SquarePants Movie<br>The Incredibles<br>Rise of the Underminer}}

JSP is an asset type which defines a 3D model. It's a RenderWare binary stream file. There are two types of JSP: the normal (model) has a format much similar to a DFF. They can be opened by RWAnalyze and other tools that work with RenderWare models. [https://www.gtamodding.com/wiki/RenderWare_binary_stream_file GTAModding] has a lot of useful information regarding this format. The other format is used for collision data and is very different from a normal JSP/DFF, but still follows the layout of a RenderWare binary stream file, with three custom sections.
JSP is an asset type which defines a 3D model. It's a RenderWare binary stream file. There are two types of JSP: the normal (model) has a format much similar to a DFF. They can be opened by RWAnalyze and other tools that work with RenderWare models. [https://www.gtamodding.com/wiki/RenderWare_binary_stream_file GTAModding] has a lot of useful information regarding this format. The other format is used for collision data and is very different from a normal JSP/DFF, but still follows the layout of a RenderWare binary stream file, with three custom sections.



Revision as of 19:03, 30 November 2018

JSP
JSP
TypeRenderWare
Games usedThe Incredibles

JSP is an asset type which defines a 3D model. It's a RenderWare binary stream file. There are two types of JSP: the normal (model) has a format much similar to a DFF. They can be opened by RWAnalyze and other tools that work with RenderWare models. GTAModding has a lot of useful information regarding this format. The other format is used for collision data and is very different from a normal JSP/DFF, but still follows the layout of a RenderWare binary stream file, with three custom sections.

Format (Collision JSP)

   // SECTION 1 
   int 0x00BEEF01 // section type
   int sectionSize // section size
   int 0x1400FFFF // renderware version
   char[4] CCOL
   
   int amount1
   int amount2
   unknown1[amount1]
   unknown2[amount2]
   
   struct unknown1 {
   int[2] unknown
   float[2] unknown
   }
   
   struct unknown2 {
   short[2] unknown
   byte[2] unknown
   short unknown
   }
   
   // SECTION 2
   int 0x00BEEF02 // section type
   int sectionSize // section size
   int 0x1400FFFF // renderware version
   
   // big endian
   char[4] "JSP "
   int unknownAmount1 // usually 3
   int unknownAmount2
   int unknown1usually0
   int unknown2usually0
   int unknown3usually0
   unknown3[unknownAmount2]
   
   struct unknown3{
   int[2] unknown
   }
   
   // SECTION 3 // GCN ONLY
   int 0x00BEEF03 // section type
   int sectionSize // section size
   int 0x1400FFFF // renderware version
   
   int vertexCount
   float[vertexCount][3] vertices