solifly.blogg.se

1. #DESKTOP FRAME RATE TEST MOVIE#
2. #DESKTOP FRAME RATE TEST DRIVER#
3. #DESKTOP FRAME RATE TEST CODE#
4. #DESKTOP FRAME RATE TEST ZIP#

Preference names are strings you can find them by viewing the contents of the Resources/preferences folder (after running the sim normally to init preferences). Will run the sim with fps test 1 but at 1440×900 res. You can override individual settings using the ‐‐pref command the syntax is: One use of replay movies is to vary the viewpoint (by flying the plane) to get a more representative rendering load.

#DESKTOP FRAME RATE TEST ZIP#

(But shorter movies will zip more efficiently.) smo file format is fixed-size you will not save disk space with shorter movies.

#DESKTOP FRAME RATE TEST MOVIE#

The fps test will run for 90 seconds (or 30 seconds for ‐‐require_fps) regardless of movie length you should set your movie to about 90 seconds. The timedemo test contains one movie, test.smo.

fdr file is a relative path from the root of the X-Plane folder. X-Plane-i686 ‐‐fps_test=1 ‐‐load_smo=Output/movies/test.smo Normally the fps test will simply leave the plane on the runway however you can also program X-Plane to load and play a “replay movie” (.smo file) – this is a binary file containing a replay of an X-Plane flight. Note that you must use ‐‐require_fps with ‐‐fps_test. X-Plane-i686 ‐‐fps_test=1 ‐‐require_fps=30 || echo "X-Plane is running slower than 30 fps." Typically this would be used to fail an automated regression test, e.g. In this mode, the sim will run one 30 second test (with flight model and panel on) and then return 1 on success or 0 on failure. X-Plane can also be run in minimum-fps mode. Note that the fly-over interferes with some views-see preferences below. This is useful because the _tex_res_ pref seems to not be command-line controllable. Note that 1 gives you “high” tex res (4x reduction in all dimensions, 2 gives you “very high” (2x reduction) and 3 gives you “extreme” (no reduction). This controls a range of rendering settings use individual preferences for more control (see below).You can add the ‐‐verbose flag to get output for every frame, if you’d like to run a more sophisticated statistical analysis on the data than just getting the mean frame rate.Ĭurrently the framerate test numbers are built from three digits (leading zeros can be omitted): At the end, your Log.txt will contain a single summary of the replay’s performance. For flight data recorder (.fdr) files, the replay will run to completion in whichever view you specify (see “FPS Test Codes” below).30 seconds with a forward view, no panel, simulation paused.30 seconds of a forward view with no panel.30 seconds of a forward view with the panel.For X-Plane “movies” (.smo files), the replay will run for 90 seconds, in 3 stages (each of which will be output its results individually to your Log.txt file):.The basic framerate test has two modes, depending on the file type you pass it:

#DESKTOP FRAME RATE TEST CODE#

Where N is a numeric code indicating the FPS test to be run. To run a framerate test, you use the command-line option: Please note that options and preferences discussed here are accurate for RC3 but may be subject to change in the future. The framerate test is controlled by command-line options. This document is written for programmers who want to use X-Plane in a production environment, like an automated regression harness.

#DESKTOP FRAME RATE TEST DRIVER#