瀏覽代碼

Fixed broken link and smart quote.

mitm 6 年之前
父節點
當前提交
977b703ffe
共有 1 個文件被更改,包括 2 次插入2 次删除
  1. 2 2
      src/docs/asciidoc/jme3/advanced/statsview.adoc

+ 2 - 2
src/docs/asciidoc/jme3/advanced/statsview.adoc

@@ -94,7 +94,7 @@ What do you want to avoid?
 .  The Object Count (Batch Count) is a very important value that indicates how many geometries were rendered in the last frame. In general, if you keep the object count around 100-200, your game will be fast and responsive. If the count is permanently higher, hand-code rules that detach remote objects, or optimize a complex multi-material scene using: `GeometryBatchFactory.optimize(complexNode, true);` or a <<jme3/advanced/texture_atlas#,Texture Atlas>>.
 .  Triangle Counts. If your game is sluggish and triangle (polygon) count is high, then you are rendering too many, too detailed meshes. Tell your graphic designers to create models with lower polygon counts, or use a <<jme3/advanced/level_of_detail#,Level of Detail>> (LOD) optimization. The limit is around 100'000 vertices for a scene, considering that the slowest currently used graphic cards cannot handle anything beyond that.
 .  Are any counts constantly increasing right before the game slows down or runs out of memory? Check whether you are accidentally adding objects in a loop, instead of only once.
-.  Verify that the numbers are plausible. If you think you generated a test scene out of “a few boxes, but the StatsView shows ten thousands of triangles, then you probably have extra objects out of sight somewhere (due to barely visible materials, overlapping with other objects, scaled too big or too small to see, etc).
+.  Verify that the numbers are plausible. If you think you generated a test scene out of "`a few`" boxes, but the StatsView shows ten thousands of triangles, then you probably have extra objects out of sight somewhere (due to barely visible materials, overlapping with other objects, scaled too big or too small to see, etc).
 **  Example: In a test scene made up of boxes, you'd expect a vertex:triangle:object ratio of 8:12:1.
 **  Terrains, models and spheres have higher counts, depending on their size and <<jme3/advanced/level_of_detail#,Level of Detail>> (LOD). A high-poly model looks pretty in Blender, but you must find a lower-poly, low-LOD compromise if you want several large objects in one scene!
 
@@ -112,5 +112,5 @@ What goal are you trying to achieve in general?
 
 See also:
 
-*  link:http://hub.jmonkeyengine.org/forum/topic/good-triangles-count/[What's a good triangle count?] Forum discussion
+*  link:https://hub.jmonkeyengine.org/t/good-triangles-count/22843[What's a good triangle count?] Forum discussion
 *  <<jme3/advanced/level_of_detail#,Level of Detail>>