RTECapture - Versionsgeschichte

Steffen am 15. September 2010 um 20:00 Uhr

2010-09-15T20:00:11Z

Steffen am 15. September 2010 um 19:54 Uhr

2010-09-15T19:54:40Z

Steffen am 15. September 2010 um 19:52 Uhr

2010-09-15T19:52:22Z

Steffen am 15. September 2010 um 19:52 Uhr

2010-09-15T19:52:07Z

Steffen am 15. September 2010 um 19:51 Uhr

2010-09-15T19:51:23Z

Steffen am 15. September 2010 um 19:50 Uhr

2010-09-15T19:50:47Z

Steffen: Die Seite wurde neu angelegt: „

RTECapture and Operation Arrowhead

“

2010-09-15T19:34:11Z

Die Seite wurde neu angelegt: „<h2>RTECapture and Operation Arrowhead</h2>“

Neue Seite

<h2>RTECapture and Operation Arrowhead</h2>

@@ Zeile 1: / Zeile 1: @@
 <h2>RTECapture and Operation Arrowhead</h2>
-RTECapture was designed to save missions created in the '''R'''eal '''T'''ime '''E'''ditor, so that you could, for example, prepare missions or templates and easily import them quickly into your running game. It was designed for Armed Assault 2, and when Operation Arrowhead was released, the programme seized to work with the new application.
+RTECapture was designed to save missions created in the '''R'''eal '''T'''ime '''E'''ditor, so that you could, for example, prepare missions or templates and easily import them quickly into your running game. It was designed for ArmA2, and when Operation Arrowhead was released, the programme seized to work with the new application.
 This tutorial will show you how to enable RTECapture for Operation Arrowhead, while still receiving updates through the Six Updater and maintaining the ability to connect to the 6thSense server.

← Nächstältere Version		Version vom 15. September 2010, 19:54 Uhr
Zeile 29:		Zeile 29:
	<h3>Important notes</h3>		<h3>Important notes</h3>
	Remember to start RTECapture as ''Administrator''. The Six Updater launches ArmA2:OA with these privileges, so the capture programme needs to have equal rights to inject successfully. Also, whenever the ''Expansion\beta'' mod gets updated, remember to copy the arma2oa.exe from the respective folder to the ArmA2-directory again (and rename it to arma2.exe). This has to be done '''everytime''' the beta gets updated. The Six Updater Suite, while being awesome, will ''not'' do that for you!		Remember to start RTECapture as ''Administrator''. The Six Updater launches ArmA2:OA with these privileges, so the capture programme needs to have equal rights to inject successfully. Also, whenever the ''Expansion\beta'' mod gets updated, remember to copy the arma2oa.exe from the respective folder to the ArmA2-directory again (and rename it to arma2.exe). This has to be done '''everytime''' the beta gets updated. The Six Updater Suite, while being awesome, will ''not'' do that for you!
		+
		+	<h3>Terrible video that needs to be ignored</h3>
		+	{{#ev:youtube\|X6b1JAjeT5c}}

@@ Zeile 22: / Zeile 22: @@
 #As '''EXE''', put arma2.exe
 #'''Path''' should be set to your main Arma2 diretory, for example: ''D:\Games\Arma2''
-#Tick the ''beta''-checkbox
+#Tick the ''beta''-checkbox<br />(Not really necessary, but cosmetic)
 #Set the '''Type''' to ''ArmA2Appsetting'' (default)

@@ Zeile 10: / Zeile 10: @@
 So, here come the instructions:
-#Rename the original arma2.exe in your ArmA2 directory to something else (e.g. arma2.original)
+#Rename the original arma2.exe in your ArmA2 directory to something else (e.g. arma2.original)<br />(You could also rename it to oldgame.exe or whatever, I just assume here that you won't need it anymore, as most players will only play OpArrowhead now, and ignore ArmA2)
-#:(You could also rename it to oldgame.exe or whatever, I just assume here that you won't need it anymore, as most players will only play OpArrowhead now, and ignore ArmA2)
+#Navigate to Expansion\beta and duplicate the arma2oa.exe found there<br />(I assume you have the beta mod installed, already. If that is not the case, do it first!)
 #Rename the copy to arma2.exe and move it to the ArmA2 directory

@@ Zeile 11: / Zeile 11: @@
 So, here come the instructions:
 #Rename the original arma2.exe in your ArmA2 directory to something else (e.g. arma2.original)
-:(You could also rename it to oldgame.exe or whatever, I just assume here that you won't need it anymore, as most players will only play OpArrowhead now, and ignore ArmA2)
+#:(You could also rename it to oldgame.exe or whatever, I just assume here that you won't need it anymore, as most players will only play OpArrowhead now, and ignore ArmA2)
 #Navigate to Expansion\beta and duplicate the arma2oa.exe found there
-:(I assume you have the beta mod installed, already. If that is not the case, do it first!)
+#:(I assume you have the beta mod installed, already. If that is not the case, do it first!)
 #Rename the copy to arma2.exe and move it to the ArmA2 directory

← Nächstältere Version		Version vom 15. September 2010, 19:50 Uhr
Zeile 1:		Zeile 1:
	<h2>RTECapture and Operation Arrowhead</h2>		<h2>RTECapture and Operation Arrowhead</h2>
		+
		+	RTECapture was designed to save missions created in the '''R'''eal '''T'''ime '''E'''ditor, so that you could, for example, prepare missions or templates and easily import them quickly into your running game. It was designed for Armed Assault 2, and when Operation Arrowhead was released, the programme seized to work with the new application.
		+
		+	This tutorial will show you how to enable RTECapture for Operation Arrowhead, while still receiving updates through the Six Updater and maintaining the ability to connect to the 6thSense server.
		+
		+	<h3>How it's done</h3>
		+
		+	Basically, RTECapture would still work with Operation Arrowhead, as the differences between these two applications are very small, regarding that you can still load all of ArmA2's content into OpArrowhead. The capture programme simply cannot find the correct process, as the executable has been renamed from arma2.exe to arma2oa.exe – which is all that prevents it from functioning properly.
		+
		+	So, here come the instructions:
		+	#Rename the original arma2.exe in your ArmA2 directory to something else (e.g. arma2.original)
		+	:(You could also rename it to oldgame.exe or whatever, I just assume here that you won't need it anymore, as most players will only play OpArrowhead now, and ignore ArmA2)
		+	#Navigate to Expansion\beta and duplicate the arma2oa.exe found there
		+	:(I assume you have the beta mod installed, already. If that is not the case, do it first!)
		+	#Rename the copy to arma2.exe and move it to the ArmA2 directory
		+
		+	'''Done!''' Well, almost. You could now start up the game and inject the capture application successfully, but you will not be able to use the Six Updater to connect to the server and keep your game up-to-date.
		+	To do so, start up the Updater Suite. What you have to do is create a new settings profile. To do so, follow these instructions:
		+
		+	#Navigate to ''Configuration'' — ''Settings''
		+	#Click on ''Create New'' to create a new setting (duh)
		+	#Name it whatever you want, but makes sense. For example ''OA Beta RTE'' works for me.
		+	#As '''EXE''', put arma2.exe
		+	#'''Path''' should be set to your main Arma2 diretory, for example: ''D:\Games\Arma2''
		+	#Tick the ''beta''-checkbox
		+	:(Not really necessary, but cosmetic)
		+	#Set the '''Type''' to ''ArmA2Appsetting'' (default)
		+
		+	Now, when you connect to the server through the Six Updater, just do what you did before — except remember to choose the correct ''Setting'' for launching the game.
		+
		+	<h3>Important notes</h3>
		+	Remember to start RTECapture as ''Administrator''. The Six Updater launches ArmA2:OA with these privileges, so the capture programme needs to have equal rights to inject successfully. Also, whenever the ''Expansion\beta'' mod gets updated, remember to copy the arma2oa.exe from the respective folder to the ArmA2-directory again (and rename it to arma2.exe). This has to be done '''everytime''' the beta gets updated. The Six Updater Suite, while being awesome, will ''not'' do that for you!