Pipeline programmers writing custom render scripts like to use
the 'rush -notes' command to put realtime status info into the
rush "Frames" reports, so users can see continuous progress info
without having to monitor logs.
Unfortunately this kind of use is 'high volume', and the docs
for 'rush -notes' have historically recommended against this
kind of use, as on large networks it would storm the server
with its high latency TCP requests.
The command was originally designed for low volume use, such as
reporting odd errors such as license failures or core dumps.
But the demand for using this command in high volume has been requested
more and more, so I've redesigned it to use the lower latency UDP
protocol which can handle the higher volume use cases.
This change will be in Rush 103.06.
I've actually been wanting to add this for years; finally gotten
to the top of my to-do list.
So look forward to that in 103.06, scheduled for release in the
next month or so. (103.05 just came out a few weeks ago).
Those companies wanting to beta test this change that have
already upgraded to Rush 103, contact me directly and I'll
set you up.
|