raP File Format - Elite - Revision history

Lou Montana: Text replacement - ";[ ]+ " to "; "

2021-08-07T23:53:39Z

Text replacement - ";[ ]+ " to "; "

← Older revision		Revision as of 01:53, 8 August 2021
Line 94:		Line 94:
	ulong Always0;		ulong Always0;
	ulong Always8;		ulong Always8;
	ulong OffsetToEnums;		ulong OffsetToEnums;

	ClassBody ClassBody; // one and one only, within which, will be more class bodies		ClassBody ClassBody; // one and one only, within which, will be more class bodies
Line 179:		Line 179:
	byte Type; // 0		byte Type; // 0
	Asciiz ClassName		Asciiz ClassName
	ulong OffsetToClassBody;		ulong OffsetToClassBody;
	};		};

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

2021-02-01T13:55:44Z

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

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

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

2021-01-31T18:03:50Z

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

Show changes

R3vo: Text replacement - " ofp " to " {{ofp}} "

2021-01-18T10:53:15Z

Text replacement - " ofp " to " {{ofp}} "

← Older revision		Revision as of 12:53, 18 January 2021
Line 71:		Line 71:
	This internal tokenised data can also be held in a file (a savegame eg). But, it is a class structure regardless.		This internal tokenised data can also be held in a file (a savegame eg). But, it is a class structure regardless.

	To improve loading speed many files within the ofp tree are pre-tokenised. They were 'converted' to hold the tokenised form of the same class statements.		To improve loading speed many files within the {{ofp}} tree are pre-tokenised. They were 'converted' to hold the tokenised form of the same class statements.

	In fact, the engine does not care which 'type' of file it is dealing with. A mission.sqm can be either. If it has not been pre-tokenised (eg contains text-readable class statements) the engine converts it on the fly.		In fact, the engine does not care which 'type' of file it is dealing with. A mission.sqm can be either. If it has not been pre-tokenised (eg contains text-readable class statements) the engine converts it on the fly.
Line 271:		Line 271:
	Instead, the new types deal with all things car. (or at least the engine goes looking elsewhere, which it did, anyway, in ofp).		Instead, the new types deal with all things car. (or at least the engine goes looking elsewhere, which it did, anyway, in ofp).

	The intention '''was''' that you did not need to know '''anything''' about how the underlying class (eg CfgVehicles) is constructed. The practicalities are however that you pretty much have to declare an ofp looking tree to 'get at' any of the embedded classes (or inferred, inherited, embedded classes), of the class you're inheriting. This tree structure can become quite long, and, of necessity, accurate, thus there is no real improvement to the ofp way of doing things.		The intention '''was''' that you did not need to know '''anything''' about how the underlying class (eg CfgVehicles) is constructed. The practicalities are however that you pretty much have to declare an {{ofp}} looking tree to 'get at' any of the embedded classes (or inferred, inherited, embedded classes), of the class you're inheriting. This tree structure can become quite long, and, of necessity, accurate, thus there is no real improvement to the {{ofp}} way of doing things.

R3vo: Text replacement - "hasn't" to "has not"

2021-01-18T08:14:33Z

Text replacement - "hasn't" to "has not"

← Older revision		Revision as of 10:14, 18 January 2021
Line 73:		Line 73:
	To improve loading speed many files within the ofp tree are pre-tokenised. They were 'converted' to hold the tokenised form of the same class statements.		To improve loading speed many files within the ofp tree are pre-tokenised. They were 'converted' to hold the tokenised form of the same class statements.

	In fact, the engine does not care which 'type' of file it is dealing with. A mission.sqm can be either. If it ~~hasn't~~ been pre-tokenised (eg contains text-readable class statements) the engine converts it on the fly.		In fact, the engine does not care which 'type' of file it is dealing with. A mission.sqm can be either. If it has not been pre-tokenised (eg contains text-readable class statements) the engine converts it on the fly.

	Tokenised files have a magic signature as their first four bytes. "\0raP". The file extension is meaningless in this regard.		Tokenised files have a magic signature as their first four bytes. "\0raP". The file extension is meaningless in this regard.

R3vo: Text replacement - "aren't" to "are not"

2021-01-18T02:02:44Z

Text replacement - "aren't" to "are not"

← Older revision		Revision as of 04:02, 18 January 2021
Line 55:		Line 55:
	};		};

	Any given file that contains classes, contains nothing else but classes. There ~~aren't~~, classes, and ummm, err, ummm 'other' things.		Any given file that contains classes, contains nothing else but classes. There are not, classes, and ummm, err, ummm 'other' things.

	'''The file itself is considered an implied class!'''		'''The file itself is considered an implied class!'''

Lou Montana: Fix category

2021-01-04T12:51:47Z

Fix category

← Older revision		Revision as of 14:51, 4 January 2021
Line 318:		Line 318:


	~~[[category:Operation Flashpoint: Elite:~~ Modelling~~\|RAP]]~~		{{GameCategory\|ofpe\|Modelling}}
	[[Category:BIS_File_Formats\|RAP]]		[[Category:BIS_File_Formats\|RAP]]

Lou Montana: Text replacement - "Operation Flashpoint Elite" to "Operation Flashpoint: Elite"

2021-01-04T12:19:22Z

Text replacement - "Operation Flashpoint Elite" to "Operation Flashpoint: Elite"

← Older revision		Revision as of 14:19, 4 January 2021
Line 318:		Line 318:


	[[category:Operation Flashpoint Elite: Modelling\|RAP]]		[[category:Operation Flashpoint: Elite: Modelling\|RAP]]
	[[Category:BIS_File_Formats\|RAP]]		[[Category:BIS_File_Formats\|RAP]]

Lou Montana: Text replacement - "
" to "
"

2020-03-19T10:45:13Z

Text replacement - "<br />" to "<br>"

← Older revision		Revision as of 12:45, 19 March 2020
Line 243:		Line 243:

	===Entry type 5: Array with flags===		===Entry type 5: Array with flags===
	The only flag that exists is 1 which means the following array is supposed to be appended to a existing array. <br />		The only flag that exists is 1 which means the following array is supposed to be appended to a existing array. <br>
	If such an array to append to isn't found it behaves like a normal array. <br />		If such an array to append to isn't found it behaves like a normal array. <br>
	It has the 4 byte long flag and after that is the same as ArrayElements. <br />		It has the 4 byte long flag and after that is the same as ArrayElements. <br>
	The engine itself does a binary and with 1 to check if the add flag is set. Meaning the other bits could be filled with arbitrary data.		The engine itself does a binary and with 1 to check if the add flag is set. Meaning the other bits could be filled with arbitrary data.
	<hr>		<hr>

Dedmen at 16:24, 11 September 2018

2018-09-11T16:24:44Z

← Older revision		Revision as of 18:24, 11 September 2018
Line 160:		Line 160:
	\|align="left"\|delete\|\|4\|\|-\|\|classname\|\|-\|\|delete thing;		\|align="left"\|delete\|\|4\|\|-\|\|classname\|\|-\|\|delete thing;
	\|-		\|-
	\|align="left"\|Array~~-append~~\|\|5\|\|-\|\|name[]+=\|\|4 bytes followed by {nElements Elements[nElements]}\|\|thing[]+={1,0.2,"three",{4,5,6},{"seven"}};		\|align="left"\|Array with flag\|\|5\|\|-\|\|name[]+=\|\|4 bytes of flag followed by {nElements Elements[nElements]}\|\|thing[]+={1,0.2,"three",{4,5,6},{"seven"}};
	\|-		\|-
	\|-		\|-
Line 215:		Line 215:
	};		};

	==ArrayStruct==		====ArrayStruct====
	[[#CompressedInteger]] nElements;ArrayElements[nElements];		[[#CompressedInteger]] nElements;ArrayElements[nElements];

	nElements is a declaring how many items make up the array, zero, is a legal value		nElements is a declaring how many items make up the array, zero, is a legal value

	==ArrayElements==		====ArrayElements====

	each element of the array consists of a single subtype byte followed by appropriate data for the type. Thus		each element of the array consists of a single subtype byte followed by appropriate data for the type. Thus
Line 235:		Line 235:
	AnArray[]= { {1,2} , 3,4};		AnArray[]= { {1,2} , 3,4};

	===EntryType 3:ExternClass===		===EntryType 3: ExternClass===

	03 Asciiz Classname; // class Classname;		03 Asciiz Classname; // class Classname;

	===EntryType 4:Delete Class===		===EntryType 4: Delete Class===
	04 Asciiz Classname; // delete Classname;		04 Asciiz Classname; // delete Classname;

	===Entry type 5: ~~Append-~~Array===		===Entry type 5: Array with flags===
	~~This data-type~~ is ~~used for~~ array ~~constructs that use the += assignment operator~~. ~~Except the type specifier the only difference~~ to a "normal" array is the ~~fact that~~ the ~~type-byte~~ is ~~followed by an additional 4 bytes which do not have any meaning so far~~. ~~Therefore such an entry type can~~ be ~~processed by consuming the type-byte, skipping the next four bytes and then proceed by consuming a normal array starting~~ with ~~its variable name~~.		The only flag that exists is 1 which means the following array is supposed to be appended to a existing array. <br />
			If such an array to append to isn't found it behaves like a normal array. <br />
			It has the 4 byte long flag and after that is the same as ArrayElements. <br />
			The engine itself does a binary and with 1 to check if the add flag is set. Meaning the other bits could be filled with arbitrary data.
	<hr>		<hr>