PMC Editing Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== ArmA 2 MoveObject ======

[[https://www.pmctactical.org/forum/viewforum.php?f=50|ArmA 2 Forum]], [[:arma2|ArmA 2 Home]], [[arma2:config|ArmA 2 Config]], [[arma2:file_formats|ArmA 2 File Formats]], [[arma2:missions|ArmA 2 Missions]], [[arma2:modeling|ArmA 2 3D Modeling]], [[arma2:scripting|ArmA 2 Scripting]], [[arma2:terrain|ArmA 2 Terrain]], [[arma2:texturing|ArmA 2 Texturing]], [[arma2:tools|ArmA 2 Tools]]

MoveObject is the successor to MoveP3d.

MoveObject will rename file paths inside *any* wrp, rvmat, bisurf or p3d, binarized or plain, including internally to pbo's

Usage
<code>
MoveObject [-options...] NameOfFile[.p3d] from to
MoveObject NameOfFile[.p3d] // list only
MoveObject NameOfFile[.p3d] replacementlist
MoveObject NameOfFolder from to or, [replacementlist]
</code>

Historically, movep3d, and fred, moved p3d files by default. Any other file type (wrp eg) must be specified.

Options (case insensitive)
<code>
-L  list only //deprecated
-F  output list to NameOfFile.lst, not screen
</code>

List example
<code>
MoveObject NameOfRVmat.rvmat OR
MoveObject -L NameOfRVmat.rvmat // deprecated
</code>

The list option is used to

a) check what paths are in the model to change\\
b) check the change took place

Rename Examples
<code>
MoveObject MyOldP3d MyGreatAddon\somewhere\data  MyNewAddon\Henry\Marbles\wherever\you\want
</code>

Moveobject will rename the p3d to old.p3d IF changes are made, and replace (in effect) the existing one, with the changed. An 'old' p3d, if it exists, is removed unconditionally. this to indicate an 'error', or 'no change' if such conditions occur.

The two tandem batch files are examples of how to make a global change to all files in a given folder.

Notes:

All renaming must be from start\of\folder.

renaming marbles will not work\\
renaming some\folder\marbles\\
will work

If you specify a leading slash, it will be ignored.

The tool handles the vagaries of this path'ing internally, by looking for the totally erroneous leading slash, if present, in some, p3d's. Why why cant bi get their act together.

Where you have differing paths, (and most models have lots of differing paths) "ca\somewhere" you need to successively Moveobject until you are complete.

Restrictions

OFP unbinarized p3d's (odol-sp3x) cannot have:
  * more than 32 character default path
  * more than 32 character texture names
  * more than 58 character proxy names

WRP unbinarized ofp files (4WVR) cannot have:
  * more than 32 character texture names
  * p3d model names > 76
  * p3d model names <3

WRP unbinarized arma files (8WVR) cannot have:
  * less that 3 characters for p3d model names\\
  * Be prepared to wait a very long time on 90meg wrp files

Parameter List

The text file must contain the following format (as if each line were passed on the command line)
<code>
OldName1 space NewName1
OldName2 space NewName2
</code>
The parser for this is very primitive and very unforgiving

Requires DePbo.dll - Check [[http://dev.withsix.com/projects/mikero-pbodll/files|Mikero tools homepage]] in Dev-Heaven.


====== Moveobject Proxy ======

How to use Moveobject to move proxys?
<code dos>
movobject.exe filename.p3d skodadriver.01 pilot.01
</code>

Where "skodadriver.01" would be the old proxy name and "pilot.01" the new one.