X-Git-Url: http://www2.svjatoslav.eu/gitweb/?a=blobdiff_plain;f=doc%2Findex.html;h=e02cfb97bf45b6dda2a0cdcf258019251556223f;hb=0b35ade185c6cdb34db3b58566748f5ebdc86aa2;hp=68eafc00ad2bde46f11259e172050ccfe42f7f64;hpb=439e676d68b70ed18dc2ca83c1581d635228a49f;p=sixth-3d.git diff --git a/doc/index.html b/doc/index.html index 68eafc0..e02cfb9 100644 --- a/doc/index.html +++ b/doc/index.html @@ -1,295 +1,385 @@ - - + + + + + + Sixth 3D - 3D engine - - - - - - - -" - - - + + + + + -
-

Sixth 3D - 3D engine

-
- +
-
-

1 Project description

-
-

-In software, pure Java realtime 3D rendering engine. With the final goal of -becoming a platform for buildng 3D user interfaces. +

+

1.1. Source code

+
+
+
+
+
+

2. Project description

+
+

-System is implemented in Java because: +In software, pure Java realtime 3D rendering engine. With the final +goal of becoming a platform for buildng 3D user interfaces and +interactive data visualization for project Sixth.

-
    -
  • It scales well to handle great complexity. -
    • -
  • It is easy to refactor and experiment with. -
    • -
  • It is fast enough thanks to Java virtual machine just-in-time compiler. -
    • -
  • Easy to run on various hardware platforms and operating systems. -
    • -

-3D rendering is done in software, 100% pure Java on CPU. At least for now. -Modern CPU cores count keeps growing and therefore rendering by CPU is not as -expensive as it used to be for the old single core systems. +Sixth 3D can be also used as standalone 3D engine in your project.

+
+
+

2.1. Justification for software rendering

+

-CPU rendering performance is already good enough to implement usable 3D UI at -sufficient detail level, resolution and frame rate. +3D rendering is done in software, 100% pure Java on CPU. At least for +now. Modern CPU cores count keeps growing and therefore rendering by +CPU is not as expensive as it used to be for the old single core +systems.

-Pure Java also means easy portability and installation. No need to deal with -platform specific dependencies. +CPU rendering performance is already good enough to implement usable +3D UI at sufficient detail level, resolution and frame rate.

-Also CPU rendering allows to easily test different rendering algorithms and -retains complete control of every rendered pixel. +Also CPU rendering allows to freely test different rendering and +optimization algorithms and retains complete control of every rendered +pixel.

+
+

2.2. Justification for Java

+
+
    +
  • It is easy to refactor and experiment with.
    • + +
  • Easy portability and installation. No need to deal with platform +specific dependencies.
    • + +
  • It scales well to handle great complexity. +
      +
    • Allows to implement clever performance optimizations (instead of +going for GPU offered brute-force rendering approach).
      • +
    • + +
  • No limitations imposed by: +
      +
    • requirement for decent GPU
      • +
    • GPU missing features
      • +
    • GPU missing/incomplete/buggy drivers
      • +
    • OpenGL specification
      • +
    • + +
  • It is fast enough thanks to: +
      +
    • Java virtual machine just-in-time compiler.
      • +
    • Growing CPU cores count.
      • +
    • + +
  • As a result it is easy to run on various hardware platforms and +operating systems.
    • +
+
+
+
+ +
+

3. API documentation

+
+ -
-

2 Software development

-

-Instructions to embed Sixth-3D in your project as a library. Maven *pom.xml* -file snippet: +Note: due to a lack of time, there is still big room for improvement +on documentation.

-
+

+So far best resource is to download and explore source code for: +

+ +
+
+
+

4. Instructions to embed Sixth-3D in your project

+
+

+Maven pom.xml file snippet: +

+
<dependencies>
     ...
     <dependency>
         <groupId>eu.svjatoslav</groupId>
         <artifactId>sixth-3d</artifactId>
-        <version>1.0</version>
+        <version>1.2</version>
     </dependency>
     ...
 </dependencies>
@@ -307,24 +397,83 @@ file snippet:

-See generated code graph using this tool. +For API usage examples, see demos.

-
-
-
-

Author: Svjatoslav Agejenko

-

Created: 2017-01-22 Sun 23:18

-

Emacs 24.4.1 (Org-mode 8.2.10)

+
+

5.1. Render only visible polygons

+
+
    +
  • This would significantly reduce RAM <-> CPU traffic.
    • + +
  • General algorithm description: +
      +
    • For each horizontal scanline: +
        +
      • sort polygon edges from left to right
        • +
      • while iterating and drawing pixels over screen X axis (left to +right) track next appearing/disappearing polygons. +
          +
        • For each polygon edge update Z sorted active polygons list.
          • +
        • Only draw pixel from the top-most polygon. +
            +
          • Only if polygon area is transparent/half-transparent add +colors from the polygons below.
            • +
          • +
        • +
      • +
    • + +
  • As a bonus, this would allow to track which polygons are really +visible in the final scene for each frame. + +
      +
    • Such information allows further optimizations: + +
        +
      • Dynamic geometry simplification: +
          +
        • Dynamically detect and replace invisible objects from the +scene with simplified bounding box.
          • + +
        • Dynamically replace boudnig box with actual object once it +becomes visible.
          • +
        • + +
      • Dynamically unload unused textures from RAM.
        • +
      • +
    • +
+
+
+
+
+
+

Author: Svjatoslav Agejenko

+

Created: 2022-07-13 Wed 03:46

+

Validate

-