Questions for development team

[conrail1]

I’ve noticed that with OpenRails even when the frame rate drops below the refresh rate of the monitor (60Hz/60 FPS) game play is still very smooth. The only applications I run that can match this level of fluid game play when the frame rate drops below 60 are some OpenGL applications that use triple buffering. As many know triple buffering is usually only available with OpenGL applications (games) which OpenRails is obviously not.

Does OpenRails use Direct3D triple buffering?



My other question is about the “Jitter” listing under the “F-5” data. What does this refer to?

[longiron]

My other question is about the “Jitter” listing under the “F-5” data. What does this refer to?

From the documentation

• Memory – displays the amount of RAM usage by Open Rails in bytes
• Jitter – measure of the differences in elapsed time between successive frame refreshes
• Primitives – measure of the amount of information the Open Rails game engine must display. A primitive is any unique combination of mesh, texture and vertex state. The term vertex state includes such things as lighting model, alpha test, Z-buffer test and MIPping.
• State Change – Number of render state changes (e.g. alpha blending, fog) per frame.
• Image Change – Number of times that a different material (unique combination of texture and lighting effects) is used per frame
• Processors – The number of logical processing units (CPUs) available for use by the Open Rails game engine
• Render Process % - the percentage of the total CPU processing power (4 cores equal 400%; 2 cores equal 200%, 1 core equals 100%) devoted to the Open Rails game rendering software thread
• Update Process % - the percentage of the total CPU processing power devoted to the Open Rails game update software thread
• Loader Process % - the percentage of the total CPU processing power devoted to the Open Rails game Loader software thread
• Total Process % - the percentage of the total CPU processing power devoted to the Open Rails software. Once the Total Process utilization rate exceed 97% of the CPU processing power, the Open Rails game “throttles down” the frame rate until the CPU processing falls below the target threshold.

All Process percentages are relative to 60 FPS target mimum

[mnjrr]

Hello,

Open Rails uses double buffering.

[conrail1]

From the documentation
Jitter – measure of the differences in elapsed time between successive frame refreshes

Thanks, I missed that list in the OpenRails documentation PDF.

Hello,

Open Rails uses double buffering.

Thanks for the response, is double buffering “forced” on with OpenRails or does the triple buffering option in the video card's control panel have to be enabled also?