Been testing a lot lately and having repeated crashes. First off I had a scene with 10 modest sized populations of trees and grasses, 2 small but high instance populations of leaves (3million plus in each) and could make TG3 crash repeatedly at the same point when using the populator. I was trying different sizes and colours of leaves (from Walli), over an area determined by a painted shader. Even if I saved the file after each major change TG3 would crash at the same point during the repopulation. However, if I then restarted TG3 and repopulated all was o.k. Does this sound like a memory leak?
System spec = intel i7 3930K 3.2GHz , Windows Ultimate 64 bit, 32 GB Ram.
I also have regular crashes when using just 2 populations in a very basic scene i.e. default scene plus two populations. This happens when I change and image map used for smooth rocks/pebbles made with Wings 3D. The scene I have uses 5 different image maps for a set of 5 rocks. If I change all 5 maps, exit the internal node of the object being populated and then try to render I get a crash before I get chance to save the file. The only safe way is to save after each individual change of map.
Another strange and annoying thing is that after a crash the object display mode defaults back to "show as bounding boxes".
I've also noticed that sometimes an object cannot be moved at all except by directly entering different values into the translate boxes for the object. Even selecting the object by right clicking in the preview window doesn't work. The object can be highlighted but not edited. As soon as you make a move the handles are no longer there. Neither can the object be selected via placing the mouse over its' +.
This last problem happened in TG2 as well, usually in a fairly complex scene with lots of objects.
