Kinda goofy

[stresstool]

Just to see what happened, I started OR-360 with an activity I did for the CNW. It behaves rather odd. Version 128 wasn't (and isn't) at all jerky starting the same activity. I don't know if it matters, but the activity starts with two AI trains passing in front of the player. However, v128 doesn't have these two starting AI trains. Maybe it matters? Here's a video clip:

Short clip

What does frame jitter mean? I believe you might need to review your FPS calculator. As shown in the video, with frametimes ~350Ms, I don't see how your calculated FPS should be showing 5.

The response to keyboard input and mouse movement is equally jerky.

Some system specs:
Time of this report: 9/19/2010, 16:44:39
Machine name: DESKTOP
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.100427-1636)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+, MMX, 3DNow (2 CPUs), ~2.6GHz
Memory: 3582MB RAM
Page File: 1774MB used, 3684MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode

---------------
Display Devices
---------------
Card name: NVIDIA GeForce 9800 GTX/9800 GTX+
Manufacturer: NVIDIA
Chip type: GeForce 9800 GTX/9800 GTX+
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0612&SUBSYS_C8733842&REV_A2
Display Memory: 512.0 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.9745 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 4/3/2010 15:55:31, 6432128 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 4/3/2010 15:55:31, 10232128 bytes
Device Identifier: {D7B71E3E-4552-11CF-E37D-78E803C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0612
SubSys ID: 0xC8733842
Revision ID: 0x00A2
Revision ID: 0x00A2
Video Accel: ModeMPEG2_C ModeMPEG2_D

-------------
Sound Devices
-------------
Description: SB Audigy 2 ZS Audio [9C00]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_20021102&REV_04
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 6.00.0001.1377 (English)
Driver Attributes: Final Retail
WHQL Logo'd: No
Date and Size: 3/18/2010 20:40:40, 528472 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 4000, 192000
Static/Strm HW Mix Bufs: 64, 62
Static/Strm HW 3D Bufs: 64, 62
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run

[twpol]

What does frame jitter mean? I believe you might need to review your FPS calculator. As shown in the video, with frametimes ~350Ms, I don't see how your calculated FPS should be showing 5.

Frame Jitter is the difference in Frame Time between two consecutive frames. When things are working well, this number should be under 10ms.

The FPS and Frame Times are calculated correctly, but the very high Frame Jitter is making it hard to smooth them out well and they're still correcting to true values at the end of the video.

[conrail1]

Just to see what happened, I started OR-360 with an activity I did for the CNW. It behaves rather odd. Version 128 wasn't (and isn't) at all jerky starting the same activity. I don't know if it matters, but the activity starts with two AI trains passing in front of the player. However, v128 doesn't have these two starting AI trains. Maybe it matters? Here's a video clip:

Same here.

I've been testing v360 on the two listed machines below and both systems are now showing some occasional pausing/stuttering with the Feather River Route. The frame rate performance is excellent even with the dynamic shadows turned on and I very seldom see them drop below 100 fps even at 1920x1200 resolution 8xAA/16AF. I did not get any stuttering at all with the same two machines and v128.

What I have noticed is that it seems as the consist length increases the more frequent the stuttering. As an example with one of the 10-15 car passenger train consists there is no stuttering with any of the 60+ car consists I get the stuttering.

I'm not sure but it's almost as if it might be tied to the physics and the animation (UpdaterProcess)
as they are both on the same thread.




ASUS Rampage III Extreme (1005 BIOS)
Intel Core i7-980X Extreme Edition w/Corsair H70
CorsairDOMINATOR-GT 6GB DDR3 1600 (PC3 12800) CMT6GX3M3A1600C7
EVGAGeForce GTX 480 SuperClocked (260.63)
Creative Sound Blaster X-FiTitanium Fatal1ty
WD VelociRaptor 150GB – Windows 7 Ultimate 64
WD VelociRaptor 300GB – Games/Programs
Corsair AX1200Watt
Corsair 800D w/NoiseBlocker fans

ASUS Rampage II Extreme (1802 BIOS)
Intel Core i7-975 Extreme Edition w/Thermalright Ultra-120eXtreme 1366 RT
Mushkin Redline Ascent 6GB (3 x 2GB) DDR3 1600(PC3 12800) (6-7-6-18-1N)
Asus/ATI 5870 (Catalyst 10.9)
CreativeSound Blaster X-Fi Titanium Fatal1ty
WD VelociRaptor 150GB –Windows XP/SP2 64-bit Edition
WD VelociRaptor 300GB –Games/Programs
SILVERSTONE 1500Watt SST
SILVERSTONE TJ09-B

[twpol]

What I have noticed is that it seems as the consist length increases the more frequent the stuttering. As an example with one of the 10-15 car passenger train consists there is no stuttering with any of the 60+ car consists I get the stuttering.

I'm not sure but it's almost as if it might be tied to the physics and the animation (UpdaterProcess)
as they are both on the same thread.

This matches an issue I've got scribled down here ("Stuttering on long trains?") but alas I didn't have time to properly investigate the high Update Process times that seem to go with it. As it seems to have affected long consists pretty consistently, I'm marking it high-priority to fix.

[conrail1]

This matches an issue I've got scribled down here ("Stuttering on long trains?") but alas I didn't have time to properly investigate the high Update Process times that seem to go with it. As it seems to have affected long consists pretty consistently, I'm marking it high-priority to fix.

Thanks for the response James.

The stuttering I'm seeing is more like a brief pause with the animation stopped for a split second. When it resumes it's as if the train has “skipped” ahead which does seem to coincide with you mentioning the update process times.

[twpol]

Some investigating we've done today has revealed that it may be caused by the high number of sounds involved (each wagon produces its own sounds). The "pauses" you mention do match what I've seen in testing, which seem to result from the update process occasionally spending way too long doing some work on sounds (which then stops everything else until it is done). Unfortunately there's no easy workaround for this in the release, as it suffers from a crash-on-start bug if you try to turn off sounds entirely (which we've fixed since release).