With the "Eucalyptus Tree" Node within the "Template Tree" node set to be Invisible, and the "Template Tree" node set to be Visible, the problem does not occur in v4.11.0.382Īm I missing something, or is anyone else also having this problem? With the "Eucalyptus Tree" Node within the "Template Tree" node set to be Visible, the problem occurs in v4.11.0.382 but not in v4.10.0.123 duf file of the trees in the scene, that reproduces the problem: It seems as as if v4.11.0.382 is trying to draw 30 Copies of the tree instead of 30 Instances. But anyway that should be irrelevant for the simple OpenGL "Texture Shaded" Draw Mode). Iray Instancing Optimization is set to "Speed" in both versions. If I replace the Instanced "Tree" prop with a simple cylinder having only 50 vertices and 72 facets, then v4.11.0.382 Beta performs the same as v4.10.0.123Īs far as I can tell, all DAZ Studio settings are identical in both versions (e.g. Orbiting the camera in the View Pane has no effect for about 1 second in both "Texture Shaded" and "NVIDIA Iray" Draw Modes, with the Lo-Res (pixelated) Iray display taking about 1 second to settle down to Hi-Res display. Orbiting the camera in the View Pane has instant response in both "Texture Shaded" and "NVIDIA Iray" Draw Modes, with the Lo-Res (pixelated) Iray display taking about 1 second to settle down to Hi-Res display. ![]() (that's not very many - the sfpLargetree01 prop in Stonemason's Through the Woods has 420,383 vertices and 291,322 facets). ![]() I have a scene with 30 Instances of a tree prop that has 185,274 vertices and 152,688 facets. V4.11.0.382 seems to have a problem with Instancing: In any event there haven't been any changes here for some time (pre 4.10.0.123 - ) so any chnage is probably down to external factors. I can't say I've noticed any issues in this regard, though my custom actions are not left in the Scripts menu. And I wanted the developers to know I noticed, and know how very much I appreciate the fix. Because of this, I don't know if the change was in 380 or 382, but either way, I noticed. ![]() However, 382 was released, so when I finished the project, I installed 382, skipping 380. I was in the middle of a project when 380 was released, so I intended to finish the project before updating. When 366 was released, and Update and Merge Menus was required, I took the time to save a copy of the menu.dsx file and when my custom menus, (Scripts, Favorites, and one for dForce,) disappeared, either the entries or entirely, I was able to put them back in using a text editor. I just want to say a big Thank You! for adding a way to preserve our custom menus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |