[vtkusers] Moving an actor, after about 1.5 hours.

[Richard Frank]

Yes, Windows.

That may X plain things.

Is there a work around? Can we reset this somewhere to - 0, current time, or something else?

Thanks 

Rick

Sent from my iPad

> On Mar 6, 2016, at 10:18 PM, David Gobbi <david.gobbi at gmail.com> wrote:
> 
> Is this on Windows?  VTK uses a 32-bit global MTime on Windows.  Call GetMTime() on your actor to see if the MTime is approaching the limit.  If you find that the MTime overflow is indeed the problem, then complain.  Complain loudly.  The MTime issue has been in the bugtracker for years.
> 
>  - David  
> 
>> On Sun, Mar 6, 2016 at 7:56 PM, Richard Frank <rickfrank at me.com> wrote:
>> We are moving an actor(s) (  assemblies ) in multiple QtViews that represent a set of surgical tools.
>> 
>> In one of our unit tests, the tools are moved for approximately 1 - 1.5 hours and after that time period the tools no longer " move" during rendering, even though different position data is being set to them via SetUserTranform.
>> 
>> There are, as far as we can tell; no reported memory leaks; no memory overwrites, and no reported OpenGL errors. When I trace into vtkOpenGLActor nothing appears to be amiss. This is on two different machines one with a quadro 5000m and the other with a high end geoforce card.
>> 
>> If we use a keystroke to remove and add the actors back into the renderer, this will usually fix the problem, but we want to get to the root cause.
>> 
>> I'd appreciate any tips on how to debug this.
>> 
>> 
>> Thanks
>> Rick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20160307/f1b1cadd/attachment.html>