cloudvis
Forum Newbie
Got Viz?
Posts: 14
|
I am definitely interested in using this, although I'll have to try to find someone to install it for me as I am a complete dummy on that end. Any news about further testing ?
I found interesting the comments about the cache collision problem that seemed to arise in this new version, because I think I have seen a similar thing happen in the old version. A couple times I have gotten a fatal run error indicating that object types don't match or that a macro cannot operate on the given object type. Upon further investigation, I find that instead of the field object that is expected, the string "red" or something similarly bizarre is being feed down the pipe. This occurred within a network that is stable, being run hundreds or thousands of times with no problems of this sort.
And about the cache not being flushed properly, I want to point out my experience that when DX does run out of memory, not even "Reset Server" works to restore it. Does anyone else concur with that observation ? I always have to take the more drastic action of Disconnect from Server to restore a peace conditon. Also I seem to recall that in (much) older versions, a proper warning was given when memory was running or had run out. Now the protocol seems to be that DX just starts acting totally weird and you have to waste a bunch of time trying to figure out what the problem is.
Lastly, could the caching problem you refer to be the cause of another Most Annoying DX Behaviors ? Certain macros (Compute likely the biggest contender) get corrupted sometimes and have to be replaced with a fresh icon. Again, often there is an misguided error about object types not being compatible, etc. The problem is not limited to this condition, but it seems to occur mostly after a syntax (human) error is typed in interactively as the operational statement, and then corrected upon discovery. Again, Reset Server does nothing to flush or fix the corruption. I have to say I am pretty sure Disconnect from Server doesn't work either. Replacing the corrupted icon in the VPE is the only thing that does the trick. This has happened so many times that I have learned to be quick to replace icons before wasting too much time trying to figure out whatever else could be wrong. Another offender has been the Image macro which has on occasion not reset the camera upon updated images (yes, Reset Camera was set), although not so much recently. Maybe that has been fixed (I would suspect indirectly since I've never heard mention of it) somewhere along the way.
|
Pages: 1
Threaded OpenDX w/ better memory management (Read 3557 times)
