Computer-Graphics | OpenGL , Computer Graphics Algorithms | Graphics library

As quite a few people have already pointed out it is quite a poor matrix implementation: It let's you make assumptions about the internal implementation and has quite a few flaws. But I would lie if I said I would not have already seen implementations like this in research codes. ;) Instead of bashing the implementation I would like to briefly point out how it works as nonetheless it shows a few particularities of C++.

Overview

Your matrix is incorrect. Try:

The variables are wrong. https://cmake.org/cmake/help/v3.16/module/FetchContent.html states that has to be lower case. Also squareskittles is right, you shouldn't use ${SFML_LIBRARIES} / ${SFML_INCLUDE_DIR}, this is only valid if the old FindSFML.cmake is used.

This problem is not related with Three.js.

It's a security measurement implemented by browsers to protect the users from multiple threats. You can find more details about how it works in this post:

"Cross origin requests are only supported for HTTP." error when loading a local file

This is how Three.js suggests that you deal with this restriction: How to run things locally

const T &xx is a reference (&) to a const T.

By using a reference instead of simply passing T xx, a potentially expensive copy can be avoided, in case T is a complex type. (Might be premature optimization in this case, because your typical Vec3 will only be instantiated with types like float or double, but the compiler will optimize it out anyway.)

By making it a reference to a const T, the caller can be certain that the T they pass in will not be modified by the constructor. Moreover, the caller will be able to pass values that are already const, like literals (e.g. Vec3(1.0)).

The rule with const is: it always refers to the thing that precedes it. So int const *x means that x is a (mutable) pointer to a const int, whereas int *const x means that x is a const pointer to a (mutable) int. int const *const x is also possible.

But what if the const is the first token in the type, so there's nothing that precedes it? Then it "jumps over one", so const T &xx is the same as T const &xx. For consistency, I prefer to write the latter, but many people use the former because it reads more naturally from left to right.

This constructor would be useful if you want a vector set to (1, 1, 1), for instance. Of questionable mathematical meaning, but sometimes useful. For example, by multiplying a vector (x, y, z) by (1, 1, 1) we can easily compute the sum of the components of the former vector.

The fact that Adobe Illustrator is a "vector program" only means that it is designed to help users work with vectors... just as Audacity, for example, helps users to work with sound, or Notepad lets a user work with characters.

There is no difference between Adobe Illustrator and any other program as far as what the Operating System (OS) and/or hardware expects from it in terms of the way it represents graphics.

Take these three examples:

We can use the idea of a "+" symbol to show the difference between a raster and a vector:

RASTER: A 3 x 3 pixel, black-and-white RASTER of the "+" symbol:

You don't need DDA or Bresenham algorithm to find intersections of the ray with walls.

If you need one intersection with given border (or box edges) - just calculate it with ray equation and border position.

If you want to get intersections with grid cells - use voxelization algorithm like Amanatides-Woo

In case anyone else has this problem, I was able to solve it. Turns out that simply updating/upgrading everything (including the nvidia drivers/libraries) fixed the problem.