From 49f80a5f42bf03516d1e065427c3815410673e74 Mon Sep 17 00:00:00 2001 From: sidekek Date: Mon, 25 Jan 2021 15:38:52 -0500 Subject: [PATCH 1/5] Create README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 0000000..9901d6c --- /dev/null +++ b/README.md @@ -0,0 +1,4 @@ +# threedee +concept for an ininformed 3d render/engine + +i was thinking one day and had an idea for making 3D. this might not be in a usable, or even recognizable, state at the time of reading, but i want to get this working at least a bit. From 256b92fd048882da3f443b1469fea2697bbc4672 Mon Sep 17 00:00:00 2001 From: sidekek Date: Mon, 25 Jan 2021 15:41:49 -0500 Subject: [PATCH 2/5] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 9901d6c..f97aa33 100644 --- a/README.md +++ b/README.md @@ -2,3 +2,7 @@ concept for an ininformed 3d render/engine i was thinking one day and had an idea for making 3D. this might not be in a usable, or even recognizable, state at the time of reading, but i want to get this working at least a bit. + +the idea is that you create a 3D cartesian coodinate space, create an "object/box" class that has accessible bounds and can be registered, then step set intervals in a direction for "raycasts" and inform each pixle of the screen by checking collision with the object registry. + +you could alter the rendering so that the rays with longer distance are closer to the horizon (?), or change the pixle's color based on distance. From c649c3a9820680fb3152dc0803c573afbabad6d5 Mon Sep 17 00:00:00 2001 From: sidekek Date: Mon, 25 Jan 2021 15:42:00 -0500 Subject: [PATCH 3/5] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f97aa33..fab3551 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,5 @@ # threedee -concept for an ininformed 3d render/engine +concept for an uninformed 3d render/engine i was thinking one day and had an idea for making 3D. this might not be in a usable, or even recognizable, state at the time of reading, but i want to get this working at least a bit. From 83b3f3adc3ecadf35548e411bac0dfb03fc0368c Mon Sep 17 00:00:00 2001 From: sidekek Date: Mon, 25 Jan 2021 15:42:36 -0500 Subject: [PATCH 4/5] Update README.md --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index fab3551..a2d17ba 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,8 @@ # threedee concept for an uninformed 3d render/engine +keep in mind that i have never seen or worked with a 3d rendering system like this, i'm making it all up as i go along. + i was thinking one day and had an idea for making 3D. this might not be in a usable, or even recognizable, state at the time of reading, but i want to get this working at least a bit. the idea is that you create a 3D cartesian coodinate space, create an "object/box" class that has accessible bounds and can be registered, then step set intervals in a direction for "raycasts" and inform each pixle of the screen by checking collision with the object registry. From 24044beb00a9e62d40aed63400a05e3484475321 Mon Sep 17 00:00:00 2001 From: sidekek Date: Mon, 25 Jan 2021 15:42:53 -0500 Subject: [PATCH 5/5] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a2d17ba..50c3edb 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ concept for an uninformed 3d render/engine keep in mind that i have never seen or worked with a 3d rendering system like this, i'm making it all up as i go along. -i was thinking one day and had an idea for making 3D. this might not be in a usable, or even recognizable, state at the time of reading, but i want to get this working at least a bit. +i was thinking one day and had an idea for making 3D. this might not be in a usable, or even recognizable, state at the time of reading, but i want to get it working at least a bit. the idea is that you create a 3D cartesian coodinate space, create an "object/box" class that has accessible bounds and can be registered, then step set intervals in a direction for "raycasts" and inform each pixle of the screen by checking collision with the object registry.