Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| tipsandtricks [2019/10/03 14:06] – [Threading] admin | tipsandtricks [2019/10/03 14:08] – [Threading] admin | ||
|---|---|---|---|
| Line 21: | Line 21: | ||
| The number of polygons you should use depends on the quality you require and the platform you are targeting. For mobile devices, somewhere between 300 and 1500 polygons per mesh will give good results, whereas for desktop platforms the ideal range is about 1500 to 4000. You may need to reduce the polygon count per mesh if the game has lots of characters on screen at any given time. | The number of polygons you should use depends on the quality you require and the platform you are targeting. For mobile devices, somewhere between 300 and 1500 polygons per mesh will give good results, whereas for desktop platforms the ideal range is about 1500 to 4000. You may need to reduce the polygon count per mesh if the game has lots of characters on screen at any given time. | ||
| - | ==== Changing Position, RotationAngle or Scale ==== | + | ===== Changing Position, RotationAngle or Scale ===== |
| Changing one of the transformation settings or visual properties of a 3D scene object initializes rendering implicity. | Changing one of the transformation settings or visual properties of a 3D scene object initializes rendering implicity. | ||
| Line 44: | Line 44: | ||
| </ | </ | ||
| - | ==== Threading ==== | + | ===== Threading |
| It is not uncommon to use a thread to compute visual property values. But because FMX (and also Gorilla3D) only runs in main thread, we need to synchronize somehow. | It is not uncommon to use a thread to compute visual property values. But because FMX (and also Gorilla3D) only runs in main thread, we need to synchronize somehow. | ||