I have uncovered a few bugs in AView related to using python in large models, some quite serious. I opened up tech support cases, and they have all been acknowledged and reported but I figured it would be good to warn other unsuspecting users ;-) I don't know where the crossover in number of parts/forces causes bugs, but 500 parts/3000 markers/3000 forces definitely does the trick.
If you happen to create a model with hundreds of parts (see attached example) then you will start to see some very strange behavior in python. The command language is still stable.
- Adams.getCurrentModel().Markers[0] or any other __get_item__ like call to a manager with integer argument will crash AView, fixed in 2018
- Some filters on dictionary queries will crash AView, for example Adams.getCurrentModel().Parts.values('RigidBody'), not fixed yet
- Most seriously, the manager keys() and values() functions only return the first 25-30 entries, making it impossible to modify large models without keeping your own separate pointers to objects as you create them! I'm really hoping this is fixed in 2018.
- icons turn on in the view window after any python command, no a big deal but with large models with thousands of markers it gets pretty annoying- not fixed yet.
- The AView model navigation tree gets very unstable after using python to create a large model, crashing randomly as I use it.
Attached Files (2)
