cynic
/
threedee
mirror of https://github.com/kurisufriend/threedee
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
16 Commits
1 Branch
0 Tags
447 KiB
 
 
 
 
Tag: Branch: Tree: 4ed7ed1339
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '4ed7ed1339'
${ noResults }
BuildTools 4ed7ed1339
demo raycasts should be marching a full pixel for performance reasons 		5 years ago
sdl/include Add project files. 5 years ago
stuff failsafe distance limiter on rays 5 years ago
.gitattributes Add .gitignore and .gitattributes. 5 years ago
.gitignore Add .gitignore and .gitattributes. 5 years ago
README.md Update README.md 5 years ago
main.cpp demo raycasts should be marching a full pixel for performance reasons 5 years ago
threedee.sln Add project files. 5 years ago
threedee.vcxproj RAYS CAUSE WE BASED N SHIT 5 years ago
threedee.vcxproj.filters RAYS CAUSE WE BASED N SHIT 5 years ago

README.md

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 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.

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.