Difference between revisions of "CNV file"

From Pikmin Technical Knowledge Base
Jump to navigation Jump to search
(Created page with "In <code>..\dataDir\objects\ufoparts\</code>, an out of place file named <code>soto5.cnv</code> can be found. It appears to be a script for the program linked by the mysterio...")
 
m
Line 1: Line 1:
In <code>..\dataDir\objects\ufoparts\</code>, an out of place file named <code>soto5.cnv</code> can be found.  It appears to be a script for the program linked by the mysterious "conversion" shortcut located in <code>..\dataDir\objects\plants\</code>.  It teaches us a few things about the proprietary [[MOD file|MOD files]] used in Pikmin 1
+
In <code>/dataDir/objects/ufoparts/</code>, an out of place file named <code>soto5.cnv</code> can be found.  It appears to be a script for the program linked by the mysterious "conversion" shortcut located in <code>/dataDir/objects/plants/</code>.  It teaches us a few things about the proprietary [[MOD file|MOD files]] used in ''Pikmin''.
  
 
For reference, <code>soto5.mod</code> is the 3D model file for the Main Engine ship part.
 
For reference, <code>soto5.mod</code> is the 3D model file for the Main Engine ship part.
Line 14: Line 14:
 
* [[DMD file|DMD files]] were used to create MOD files.
 
* [[DMD file|DMD files]] were used to create MOD files.
 
* The plaintext data at the end of a MOD file is officially an INI file of the same filename.
 
* The plaintext data at the end of a MOD file is officially an INI file of the same filename.
* [[DVW file|DVW files]] did <i>something</i>.  Who knows what.
+
* [[DVW file|DVW files]] did ''something''.  Who knows what.
 
* The <code>.h</code> files around the filesystem with enumerated joint names were likely used for the conversion process.
 
* The <code>.h</code> files around the filesystem with enumerated joint names were likely used for the conversion process.
  
 
+
A plugin called "dmdImportFilter" would have likely been a part of the conversion process.  Unfortunately, this plugin was not left on the disc of any version of ''Pikmin''.
 
 
A plugin called "dmdImportFilter" would have likely been a part of the conversion process.  Unfortunately, this plugin was not left on the disc of any version of Pikmin.
 
 
 
 
 
  
 
{{Credits|[[User:Minty_Meeo|Minty_Meeo]]}}
 
{{Credits|[[User:Minty_Meeo|Minty_Meeo]]}}

Revision as of 15:30, 6 October 2018

In /dataDir/objects/ufoparts/, an out of place file named soto5.cnv can be found. It appears to be a script for the program linked by the mysterious "conversion" shortcut located in /dataDir/objects/plants/. It teaches us a few things about the proprietary MOD files used in Pikmin.

For reference, soto5.mod is the 3D model file for the Main Engine ship part.

importdmd Z:\conversion\items\ufoparts\soto5.dmd
importanimfolder Z:\conversion\items\ufoparts\msoto5
loadini Z:\conversion\items\ufoparts\ini\soto5.ini
importdvw Z:\conversion\items\ufoparts\dvw\soto5.dvw
joint_names
exportmod Z:\conversion\dataDir\objects\ufoparts\soto5.mod
  • DMD files were used to create MOD files.
  • The plaintext data at the end of a MOD file is officially an INI file of the same filename.
  • DVW files did something. Who knows what.
  • The .h files around the filesystem with enumerated joint names were likely used for the conversion process.

A plugin called "dmdImportFilter" would have likely been a part of the conversion process. Unfortunately, this plugin was not left on the disc of any version of Pikmin.

Credits: Minty_Meeo