horacefithers
New member
For all you asset gurus/junkies out there...
My particular install of TRS19+ 106618 enters a kind of jerk jerk jerk mode when I Edit Route BCSJ-555-RHR. The jerks occur when moving around in Surveyor with Surveyor lurching from one camera position to the next at about 2 or 3 lurches per second.
However the framerate (as reported by profiler) shows between 25 and 30 frames per second. Clearly there is something happening that causes the camera movement code to take waaay more time than it should.
Even more strange, the jerk jerk jerk behavior disappears for me when I switch (ctrl-F2) to Driver and remains gone if I return to Surveyor (ctrl-F1).
Could this be a result of an asset with a script that uses an uninitialized global variable (do such things exist in Trainz???) Once in Driver the variable gets initialized to a useful value, which it retains when switched back to Surveyor? Pure conjecture.
I went back into history looking for a version of the BC&SJ that did not exhibit the jerk jerk jerk I see in Surveyor when I Edit Route BCSJ-555-RHR.
Version BCSJ-493 (not publicly released) did not exhibit the jerk jerk jerk syndrome. So I dumped recursive dependencies of the two route versions into text files then compared them looking for differences in assets that might show a possible culprit.
Problem is, I don't know squat about assets and which ones are naughty and which ones are nice.
I uploaded the output of the diff command to the web and if you're interested you can take a look at it.
The command syntax for the diff command:
diff BCSJ-493-DEPENDENCIES-RECURSIVE.txt BCSJ-555-RHR-DEPENDENCIES-RECURSIVE.txt > 555-493-differences.txt
Download/examine the differences file here:
555-493-differences.txt (at 65000 chars it's too long for a forum post... grrrr)
Do any of these assets ring a bell, as in they have attached scripts which are extremely slow and buggy, enough so that they could cause TRS19+ 106618 to take 1/3 second or so to process each camera movement?
Inquiring minds want to know,
I've filed ticket EZD-746-44219 for this behavior,
Horace Fithers
My particular install of TRS19+ 106618 enters a kind of jerk jerk jerk mode when I Edit Route BCSJ-555-RHR. The jerks occur when moving around in Surveyor with Surveyor lurching from one camera position to the next at about 2 or 3 lurches per second.
However the framerate (as reported by profiler) shows between 25 and 30 frames per second. Clearly there is something happening that causes the camera movement code to take waaay more time than it should.
Even more strange, the jerk jerk jerk behavior disappears for me when I switch (ctrl-F2) to Driver and remains gone if I return to Surveyor (ctrl-F1).
Could this be a result of an asset with a script that uses an uninitialized global variable (do such things exist in Trainz???) Once in Driver the variable gets initialized to a useful value, which it retains when switched back to Surveyor? Pure conjecture.
I went back into history looking for a version of the BC&SJ that did not exhibit the jerk jerk jerk I see in Surveyor when I Edit Route BCSJ-555-RHR.
Version BCSJ-493 (not publicly released) did not exhibit the jerk jerk jerk syndrome. So I dumped recursive dependencies of the two route versions into text files then compared them looking for differences in assets that might show a possible culprit.
Problem is, I don't know squat about assets and which ones are naughty and which ones are nice.
I uploaded the output of the diff command to the web and if you're interested you can take a look at it.
The command syntax for the diff command:
diff BCSJ-493-DEPENDENCIES-RECURSIVE.txt BCSJ-555-RHR-DEPENDENCIES-RECURSIVE.txt > 555-493-differences.txt
Download/examine the differences file here:
555-493-differences.txt (at 65000 chars it's too long for a forum post... grrrr)
Do any of these assets ring a bell, as in they have attached scripts which are extremely slow and buggy, enough so that they could cause TRS19+ 106618 to take 1/3 second or so to process each camera movement?
Inquiring minds want to know,
I've filed ticket EZD-746-44219 for this behavior,
Horace Fithers