2024-03-28 15:42 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0004138Spring engineGeneralpublic2013-11-24 01:03
ReporterGoogle_Frog 
Assigned ToKloot 
PrioritynormalSeverityblockReproducibilityalways
StatusclosedResolutionno change required 
Product Version95.0 
Target VersionFixed in Version 
Summary0004138: Jittery unit movement, timing assert often fails.
DescriptionBasically this: http://springrts.com/mantis/view.php?id=3845

It occurs for many people.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
duplicate of 0004132closedKloot Jittery camera panning on non-flat surfaces 
+Relationships

-Notes

~0012025

abma (administrator)

Last edited: 2013-11-09 17:29

View 2 revisions

@GoogleFrog
is any user without intel i7 affected?

i guess its related to the cpu boost...

~0012026

Google_Frog (reporter)

I have intel i7 and have not asked others in that much detail.

~0012027

abma (administrator)

hmmm:

http://springrts.com/phpbb/viewtopic.php?p=549775#p549775

"NP=0"

those have zero to do with timer change: you are running out of netpackets -> your connection has problems.

~0012028

silentwings (reporter)

Last edited: 2013-11-09 18:03

View 4 revisions

I also have i7 and see these with /debug, although they are not as bad as I used to see them and my CTOs are typically much lower than GFs (nearly all <2, worst ever is about 5). So for me its not a block but I can see it if I look hard enough. For me they also show NP=0 but I'm certain there is nothing wrong with my connection.

I'll make an infolog of an online game and add it.

~0012029

abma (administrator)

hmm, ok.

does AdvUnitShading=0 help? some guy reported in #sy that it helped him, but atm the information is very fragile as no engine dev can reproduce it and not all people are affected.

~0012030

abma (administrator)

also big fat note:

"Connecting to 94.23.171.71:8670" -> this server yesterday had weird connection problems, all springies were offline for a while.

~0012031

silentwings (reporter)

Last edited: 2013-11-09 18:22

View 2 revisions

AdvUnitShading=0 discussion in #sy earlier was fixing a different bug (an ati one) to do with a flashing screen.

~0012033

silentwings (reporter)

Ok, added my infolog.

The 'hang detection' was because I left it running minimized until game had got to intense phase, then alt tabbed in and did /debug.

~0012034

silentwings (reporter)

Last edited: 2013-11-09 19:18

View 3 revisions

Seems a few BA players are also reporting this issue, so far all people with i7. It seems mild (like for me) in all BA cases. I'll harvest some infologs...

~0012035

FLOZi (reporter)

Last edited: 2013-11-09 21:21

View 2 revisions

I also have i7 and get jittery middle click scrolling (but arrow button is smooth) I had unit jitter at some points throughout 94->95 dev cycle. No asserts been triggered at all though it seems.

edit: AllowModelDefferedRendering=0 fixes it for me

~0012039

Kloot (developer)

"Mild jitter" can in 99% of all cases be explained just by bad/new config settings and timing precision issues.

The kind of jitter GF wants to believe everyone is suffering from (but for which no hard evidence exists) is a system problem and can *not* be fixed by us. We can see this from his own infolog:

  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2967 : CTO=1.324138 : WSF=0.031527 : DT=42.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2968 : CTO=2.017734 : WSF=0.031527 : DT=64.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2969 : CTO=2.837438 : WSF=0.031527 : DT=90.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2970 : CTO=3.877832 : WSF=0.031527 : DT=123.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2971 : CTO=4.729064 : WSF=0.031527 : DT=150.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2972 : CTO=5.769458 : WSF=0.031527 : DT=183.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2973 : CTO=6.620689 : WSF=0.031527 : DT=210.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2974 : CTO=7.661083 : WSF=0.031527 : DT=243.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2975 : CTO=8.512315 : WSF=0.031527 : DT=270.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2976 : CTO=9.552709 : WSF=0.031527 : DT=303.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2977 : CTO=10.403940 : WSF=0.031527 : DT=330.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2978 : CTO=11.412807 : WSF=0.031527 : DT=362.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2979 : CTO=12.295566 : WSF=0.031527 : DT=390.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2980 : CTO=13.304432 : WSF=0.031527 : DT=422.000000ms : NP=0)
  [f=0025275] Error: assert(CTO <= 1.0f) failed (SF=25275 : DF=2981 : CTO=14.155663 : WSF=0.031527 : DT=449.000000ms : NP=0)

DT increases to 500ms (HALF A SECOND!!!) in 15 drawframes for the *same* simframe number which can *only* be caused by NETMSG_NEWFRAME starvation.

~0012049

Google_Frog (reporter)

Apparently you can do something about it because either 91.0 deals with the same inherent network latency as 95.0 in a much smoother way or 95.0 has introduced problems which increase latency.

~0012170

Kloot (developer)

"With the right settings the jitter seems ok for me (not much worse than 91.0)" [http://zero-k.info/Forum/Thread/6091]

...

~0012202

Kloot (developer)

Last edited: 2013-11-24 01:03

View 2 revisions

http://www.sleipnirstuff.com/forum/viewtopic.php?t=16146 ("strange tick time peaks that results into a delay of half a second every 10-15 seconds")

get in contact with this guy and compare notes

+Notes

-Issue History
Date Modified Username Field Change
2013-11-09 16:35 Google_Frog New Issue
2013-11-09 16:35 Google_Frog File Added: jitterAssertInfolog.txt
2013-11-09 17:28 abma Relationship added duplicate of 0004132
2013-11-09 17:29 abma Note Added: 0012025
2013-11-09 17:29 abma Note Edited: 0012025 View Revisions
2013-11-09 17:55 Google_Frog Note Added: 0012026
2013-11-09 17:57 abma Note Added: 0012027
2013-11-09 18:00 silentwings Note Added: 0012028
2013-11-09 18:02 silentwings Note Edited: 0012028 View Revisions
2013-11-09 18:03 silentwings Note Edited: 0012028 View Revisions
2013-11-09 18:03 silentwings Note Edited: 0012028 View Revisions
2013-11-09 18:07 abma Note Added: 0012029
2013-11-09 18:08 abma Note Added: 0012030
2013-11-09 18:21 silentwings Note Added: 0012031
2013-11-09 18:22 silentwings Note Edited: 0012031 View Revisions
2013-11-09 18:25 silentwings File Added: infolog_silentwings.txt
2013-11-09 18:26 silentwings Note Added: 0012033
2013-11-09 19:14 silentwings Note Added: 0012034
2013-11-09 19:17 silentwings Note Edited: 0012034 View Revisions
2013-11-09 19:18 silentwings Note Edited: 0012034 View Revisions
2013-11-09 21:03 FLOZi Note Added: 0012035
2013-11-09 21:21 FLOZi Note Edited: 0012035 View Revisions
2013-11-10 17:40 Kloot Note Added: 0012039
2013-11-10 17:41 Kloot Status new => closed
2013-11-10 17:41 Kloot Assigned To => Kloot
2013-11-10 17:41 Kloot Resolution open => unable to reproduce
2013-11-11 06:13 Google_Frog Note Added: 0012049
2013-11-11 06:13 Google_Frog Status closed => feedback
2013-11-11 06:13 Google_Frog Resolution unable to reproduce => reopened
2013-11-17 18:56 Kloot Note Added: 0012170
2013-11-17 18:56 Kloot Status feedback => closed
2013-11-17 18:56 Kloot Resolution reopened => unable to reproduce
2013-11-24 01:02 Kloot Assigned To Kloot =>
2013-11-24 01:02 Kloot Note Added: 0012202
2013-11-24 01:02 Kloot Status closed => feedback
2013-11-24 01:02 Kloot Resolution unable to reproduce => reopened
2013-11-24 01:02 Kloot Status feedback => closed
2013-11-24 01:02 Kloot Assigned To => Kloot
2013-11-24 01:02 Kloot Resolution reopened => no change required
2013-11-24 01:03 Kloot Status closed => feedback
2013-11-24 01:03 Kloot Resolution no change required => reopened
2013-11-24 01:03 Kloot Note Edited: 0012202 View Revisions
2013-11-24 01:03 Kloot Status feedback => closed
2013-11-24 01:03 Kloot Resolution reopened => no change required
+Issue History