Wrp File Format - 8WVR - Revision history

Mikero: /* 0WZD */ added differences

2025-11-18T02:47:22Z

0WZD: added differences

← Older revision		Revision as of 04:47, 18 November 2025
Line 130:		Line 130:
	=== 0WZD ===		=== 0WZD ===

	~~0WZD~~ files exported from DayZ Terrain Builder are identical to 8WVR. It signals to DayZ that the object IDs are generated by a version of DayZ Terrain Builder that exports with persistent object IDs.		(above is a numeric zero)
			WZD files exported from DayZ Terrain Builder are almost identical to 8WVR. The exceptions being they have no numeric format number (8WVR is type25). Nor 4 (arma) or 8 (dayz) byte Appid. 0WZD signals to the DayZ engine that the object IDs are generated by a version of DayZ Terrain Builder that exports with persistent object IDs.

	== FilePaths ==		== FilePaths ==

Jacob Mango: /* 0WDZ / to / 0WZD */

2025-11-16T23:58:48Z

0WDZ: to 0WZD

← Older revision		Revision as of 01:58, 17 November 2025
Line 128:		Line 128:
	*The last, (and possibly only) entry, has no p3d filename associated with it. This is the 'default' object specifying the 'center' of the map.		*The last, (and possibly only) entry, has no p3d filename associated with it. This is the 'default' object specifying the 'center' of the map.

	=== ~~0WDZ~~ ===		=== 0WZD ===

	~~0WDZ~~ files exported from DayZ Terrain Builder are identical to 8WVR. It signals to DayZ that the object IDs are generated by a version of DayZ Terrain Builder that exports with persistent object IDs.		0WZD files exported from DayZ Terrain Builder are identical to 8WVR. It signals to DayZ that the object IDs are generated by a version of DayZ Terrain Builder that exports with persistent object IDs.

	== FilePaths ==		== FilePaths ==

Mikero: /* DZW0 */

2025-11-10T17:57:40Z

DZW0

← Older revision		Revision as of 19:57, 10 November 2025
Line 128:		Line 128:
	*The last, (and possibly only) entry, has no p3d filename associated with it. This is the 'default' object specifying the 'center' of the map.		*The last, (and possibly only) entry, has no p3d filename associated with it. This is the 'default' object specifying the 'center' of the map.

	=== ~~DZW0~~ ===		=== 0WDZ ===

	~~DZW0~~ files exported from DayZ Terrain Builder are identical to 8WVR. It signals to DayZ that the object IDs are generated by a version of DayZ Terrain Builder that exports with persistent object IDs.		0WDZ files exported from DayZ Terrain Builder are identical to 8WVR. It signals to DayZ that the object IDs are generated by a version of DayZ Terrain Builder that exports with persistent object IDs.

	== FilePaths ==		== FilePaths ==

Mikero: /* WBV9 */

2025-11-10T17:56:32Z

WBV9

← Older revision		Revision as of 19:56, 10 November 2025
Line 109:		Line 109:
	== Changes ==		== Changes ==

	=== ~~WBV9~~ ===		=== 9VBW ===

	vbs ~~WBV9~~ files exported from Visitor 4 are identical to 8WVR except that there can be multiple rvmat layers.		vbs 9VBW files exported from Visitor 4 are identical to 8WVR except that there can be multiple rvmat layers.


	8WVR/~~WBV9~~		8WVR/9VBW
	{		{
	WRPHeader Header		WRPHeader Header

Jacob Mango: Added DZW0, restructured changes

2025-11-07T09:21:15Z

Added DZW0, restructured changes

@@ Line 46: / Line 46: @@
 == File Format ==
 :::*This file format is principally used with Armed Assault and a derivation of it was used for Elite.
 === WrpHeader ===
@@ Line 126: / Line 106: @@
 Note that unlike the cell-indexes which refer to a single unique rvmat file. There is no index-list of p3d files (but perhaps should be, because of the enormous quantity of repetitions silver oak pine trees etc).
 == FilePaths ==

Lou Montana: Text replacement - "\[\[Category:BIS( |_)File( |_)Formats\]\]" to "Category:Real Virtuality File Formats"

2025-05-08T11:27:12Z

Text replacement - "\[\[Category:BIS( |_)File( |_)Formats\]\]" to "Category:Real Virtuality File Formats"

← Older revision		Revision as of 13:27, 8 May 2025
Line 130:		Line 130:
	Note that file paths are always* hard - wired to the (virtual) PrefixRoot\ directory. Like ArmA P3d files, there is NO, relative addressing. See [[P3D_File_Format_-_ODOLV40_Revised\|P3D file formats]] for a description of the PrefixRoot\		Note that file paths are always* hard - wired to the (virtual) PrefixRoot\ directory. Like ArmA P3d files, there is NO, relative addressing. See [[P3D_File_Format_-_ODOLV40_Revised\|P3D file formats]] for a description of the PrefixRoot\

	[[Category:~~BIS_File_Formats~~]]		[[Category:Real Virtuality File Formats]]
	{{GameCategory\|arma1\|File Formats}}		{{GameCategory\|arma1\|File Formats}}

Lou Montana: Text replacement - "y[ _]\|[ _](arma[0-9]+)[ _]*\|[ _]+" to "y|$1|"

2021-06-22T12:12:35Z

Text replacement - "y[ _]*\|[ _]*(arma[0-9]+)[ _]*\|[ _]+" to "y|$1|"

← Older revision		Revision as of 14:12, 22 June 2021
Line 131:		Line 131:

	[[Category:BIS_File_Formats]]		[[Category:BIS_File_Formats]]
	{{GameCategory\|arma1\| File Formats}}		{{GameCategory\|arma1\|File Formats}}

Lou Montana: Text replacement - "{{unsupported-doc}}" to "{{Feature|UnsupportedDoc}}"

2021-02-01T13:54:32Z

Text replacement - "{{unsupported-doc}}" to "{{Feature|UnsupportedDoc}}"

← Older revision		Revision as of 15:54, 1 February 2021
Line 1:		Line 1:
	{{~~unsupported-doc~~}}		{{Feature\|UnsupportedDoc}}

	== Introduction ==		== Introduction ==

Lou Montana: Text replacement - " (={2,})([^ = ])(.)([^ = ])(={2,}) " to " $1 $2$3$4 $5 "

2021-01-31T18:11:26Z

Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 "

← Older revision		Revision as of 20:11, 31 January 2021
Line 41:		Line 41:
	For the purposes of game play, and no other reason, each, identical pine tree has a unique 'ID' number. (as does every other object). A soldier is told to goto THAT pine tree (as opposed to any other). The IDvalue, while guaranteed to be unique, is highly arbitrary. Any alterations / additions / deletions to the map and it is objects will result in different numbers for some / most / all of the objects. This represents no problem with game commands using NearestObject() style functions that return the ID of relevance, but, missions relying on a specific building ID (eg) will mostly fail if the 'island' is revised. This has particular relevance to porting OFP islands into Arma.		For the purposes of game play, and no other reason, each, identical pine tree has a unique 'ID' number. (as does every other object). A soldier is told to goto THAT pine tree (as opposed to any other). The IDvalue, while guaranteed to be unique, is highly arbitrary. Any alterations / additions / deletions to the map and it is objects will result in different numbers for some / most / all of the objects. This represents no problem with game commands using NearestObject() style functions that return the ID of relevance, but, missions relying on a specific building ID (eg) will mostly fail if the 'island' is revised. This has particular relevance to porting OFP islands into Arma.

	==Legend==		== Legend ==
	see [[Generic FileFormat Data Types]]		see [[Generic FileFormat Data Types]]

Line 47:		Line 47:
	:::*This file format is principally used with Armed Assault and a derivation of it was used for Elite.		:::*This file format is principally used with Armed Assault and a derivation of it was used for Elite.

	==8WVR/WBV9==		== 8WVR/WBV9 ==

	vbs WBV9 files exported from Visitor 4 are identical to 8WVR except that there can be multiple rvmat layers.		vbs WBV9 files exported from Visitor 4 are identical to 8WVR except that there can be multiple rvmat layers.
Line 67:		Line 67:


	===WrpHeader===		=== WrpHeader ===
	WrpHeader		WrpHeader
	{		{
Line 80:		Line 80:
	*This, Arma format, simply adds a small wrinkle of a cellGrid Size. (Formerly set at 50 meters).		*This, Arma format, simply adds a small wrinkle of a cellGrid Size. (Formerly set at 50 meters).

	===RvmatLayer===		=== RvmatLayer ===
	RvmatLayer		RvmatLayer
	{		{
Line 89:		Line 89:
	There is only one RvmatLayer for 8WVR. WBV9 has as many layers as a piece of string. The end of WBV9 layers is when NoOfMaterials=0		There is only one RvmatLayer for 8WVR. WBV9 has as many layers as a piece of string. The end of WBV9 layers is when NoOfMaterials=0

	===MaterialName===		=== MaterialName ===

	MaterialName		MaterialName
Line 109:		Line 109:
	*BufferLengthh this value is NOT a strlen. It is the number of bytes used to hold the rvmat filename. It sometimes may(WBV9), or may not (8WVR) be null terminated.		*BufferLengthh this value is NOT a strlen. It is the number of bytes used to hold the rvmat filename. It sometimes may(WBV9), or may not (8WVR) be null terminated.

	===Object===		=== Object ===
	Object		Object
	{		{
Line 127:		Line 127:
	Note that unlike the cell-indexes which refer to a single unique rvmat file. There is no index-list of p3d files (but perhaps should be, because of the enormous quantity of repetitions silver oak pine trees etc).		Note that unlike the cell-indexes which refer to a single unique rvmat file. There is no index-list of p3d files (but perhaps should be, because of the enormous quantity of repetitions silver oak pine trees etc).

	==FilePaths==		== FilePaths ==
	Note that file paths are always* hard - wired to the (virtual) PrefixRoot\ directory. Like ArmA P3d files, there is NO, relative addressing. See [[P3D_File_Format_-_ODOLV40_Revised\|P3D file formats]] for a description of the PrefixRoot\		Note that file paths are always* hard - wired to the (virtual) PrefixRoot\ directory. Like ArmA P3d files, there is NO, relative addressing. See [[P3D_File_Format_-_ODOLV40_Revised\|P3D file formats]] for a description of the PrefixRoot\

	[[Category:BIS_File_Formats]]		[[Category:BIS_File_Formats]]
	{{GameCategory\|arma1\| File Formats}}		{{GameCategory\|arma1\| File Formats}}

R3vo: Text replacement - "wasn't" to "was not"

2021-01-18T08:15:55Z

Text replacement - "wasn't" to "was not"

← Older revision		Revision as of 10:15, 18 January 2021
Line 37:		Line 37:
	Objects are independent of the cell grid structure. They are placed on the map using their own dimensional space transform. For all the engine cares, the building could be upside down and buried 10 meters under the sea.		Objects are independent of the cell grid structure. They are placed on the map using their own dimensional space transform. For all the engine cares, the building could be upside down and buried 10 meters under the sea.

	Unlike cell indexes however, each identical pine tree is listed separately, rather than simply have a table. There's no particular reason why a table (and indexes) were not used to conserve space, but done, it ~~wasn't~~.		Unlike cell indexes however, each identical pine tree is listed separately, rather than simply have a table. There's no particular reason why a table (and indexes) were not used to conserve space, but done, it was not.

	For the purposes of game play, and no other reason, each, identical pine tree has a unique 'ID' number. (as does every other object). A soldier is told to goto THAT pine tree (as opposed to any other). The IDvalue, while guaranteed to be unique, is highly arbitrary. Any alterations / additions / deletions to the map and it is objects will result in different numbers for some / most / all of the objects. This represents no problem with game commands using NearestObject() style functions that return the ID of relevance, but, missions relying on a specific building ID (eg) will mostly fail if the 'island' is revised. This has particular relevance to porting OFP islands into Arma.		For the purposes of game play, and no other reason, each, identical pine tree has a unique 'ID' number. (as does every other object). A soldier is told to goto THAT pine tree (as opposed to any other). The IDvalue, while guaranteed to be unique, is highly arbitrary. Any alterations / additions / deletions to the map and it is objects will result in different numbers for some / most / all of the objects. This represents no problem with game commands using NearestObject() style functions that return the ID of relevance, but, missions relying on a specific building ID (eg) will mostly fail if the 'island' is revised. This has particular relevance to porting OFP islands into Arma.