Algodoo

Nice work.

Wow! This is beyond awesome!

raytracer? if this was at the level of povray i would be suprised, but it's still nice

If this was at the level of Povray I would splash cold water in my face because I would know that I was dreaming!

AverageCoder did an excellent job given the limited capabilities of Algodoo that he had to work with.

I know its not an actual raytracer like RTX but I can probably still call it raytracing. I have bee mentally planning a REAL raytracer with light and stuff but theres a big obstacle I do not know how to combat. That big problem is that lasers do not keep track of every entity it bounces off of in a onLaserHit event. If I had some way to get a table of entities the laser bounced off of, I would contribute my algodoo playtime to it.

Im also mentally planning for visual block coding for Thyme but I don't really know what the community would want. I have two ideas in mind: A more familiar design and interface of something like Scratch, terms that are kind of related to some kind of python (The other coding language I know) and then theres a kind of new interpretation of thyme for block coding. Right now Im kind of leaning towards the first idea.

Dear (viewers who use or have used Scratch or something like it), (non coders who want to code), and (intermediate thyme coders), What idea would you like more?

I have some very, very bad memories from Scratch...
I would personally go for the reimplementation of Thyme instead -- but that's ultimately up to you!

Also, as for your keeping track of entities problem -- onLaserHit is run for each object the laser hits in order of when the object was hit!

Simply making a postStep script to create a blank table and then adding objects to it on every onLaserHit can be used to keep track of hit objects.

I hope this helps!

EDIT: I have made a simple script (well, 2 of them) that will save the entities the laser has hit into a table.

Here's the code for onLaserHit:

(e)=>{_hitObjects = _hitObjects ++ [e.geom.geomID]

And the code for postStep!

(e)=>{
"place whatever you want in postStep here";
_hitObjects = []
}

A little fun fact is that postStep appears to run before onLaserHit -- so if you pause Algodoo, the laser will still contain the list of objects!

This all assumes a table variable named _hitObjects within the object!

Thank you very much! Next update will use this to make transparent objects show the objects behind them! A real raytracer will also be planned.

No problem!

Discovering the little mirror thing was really fun! For once I could look in a mirror without seeing something horrible.

Nice additions. I don't see any instructions on how to move the raytrace camera. I don't see a method to rotate the raytrace camera.

s_noonan -- Translate camera with A,D,W,S keys, and rotate camera with left and right arrow keys.

ok uhhh so the update im working on isnt very performant so im not publishing it for now

Xray--Thanks. Got it.

idea: diffrent colision layers show difrent hights

Looks really cool, ahd honestly the rope is a very nice addition lol. I'm a bit conflicted about the reflections though, they seem odd and the "character" being the entire height of the viewport is weird. It seems that the reflected objects are taller when the camera is farther away from the mirrors, which seems odd. Also I think you should somehow add a slight effect so you know you're looking at a mirror (maybe render the mirror very slightly, and/or make the reflected objects lighter or something).

make a maze out of this

holy programming

Awesome.. It is raytracing. It is tracing rays!
This is very impressive

though the reflections'ses perspective is.. backwards??