codex: Explain VIDEO performance recording and capture files

2026-10-24T15:20:59Z

Explain VIDEO performance recording and capture files

← Older revision		Revision as of 15:20, 24 October 2026
Line 1:		Line 1:
			The '''CONFIGURATION''' dialog contains the client's interface, input, video, sound, account and network settings.

			== Performance recording ==
			Open '''CONFIGURATION''' and select '''VIDEO'''. Under '''Performance profiler''', choose '''Start recording'''. You can start or stop a recording while airborne; no relaunch or special launch option is required. Recording works on the ground, during atmospheric flight, ascent, orbital flight and descent.

			Close the dialog and fly through the slowdown. Return to '''VIDEO''' and choose '''Stop recording'''. Keep the client rendering until '''Saving recording...''' changes to '''Not recording'''. Recording does not change your flight or video settings. If recording fails, stop it, check that the installation's output folder is writable and has enough free disk space, then start again.

			Captures are saved in the '''outputs''' folder under the client's working directory, normally its installation folder. Each recording has a matching pair:
			* <code>render-profile-<PID>.csv</code>
			* <code>render-profile-<PID>.status.json</code>

			PID is the client's process ID. Subsequent recordings add a number before the extension, such as <code>render-profile-12345-1.csv</code> and <code>render-profile-12345-1.status.json</code>. Existing files are preserved. Zip and share both matching files when asked to provide a performance capture; a long recording can be large. The profiler does not upload them automatically.

			Captures include performance measurements, the client version and GPU, and sampled vehicle, altitude, frame rate, cockpit/exterior view and ascending/descending state. Your own submitted chat is also recorded as timed notes. You can send a message such as "slowdown at cloud base" to help identify the relevant part of the recording. Normal chat still goes to its selected recipients; it is not a private annotation channel. Received chat is not recorded.

			Stopping the recording saves pending samples without closing Rise. Force-closing the client can lose the unsaved tail, so use '''Stop recording''' and wait for saving to finish whenever possible. A new recording can start once saving has finished. The recording preference is not retained for the next launch.

			For recording from startup, launch <code>Rise.exe --profile-flight</code> from its installation directory. This records from the first rendered loading frame; '''Stop recording''' on VIDEO can stop it. Using the VIDEO control takes over recording control for the rest of that client session. Older executables without the '''Performance profiler''' section need an updated client to use the in-flight controls.

			== Input configuration ==
	[[File:Getting to joystick.png\|Controls]]		[[File:Getting to joystick.png\|Controls]]

	[[Category:GUI]]		[[Category:GUI]]

reskin: Created page with "Controls Category:GUI"

2020-06-18T18:13:05Z

Created page with "Controls Category:GUI"

New page

[[File:Getting to joystick.png|Controls]]

[[Category:GUI]]

Configuration - Revision history

codex: Explain VIDEO performance recording and capture files

reskin: Created page with "Controls Category:GUI"