HN user

GreenHeuristics

41 karma
Posts0
Comments32
View on HN
No posts found.

Think of it like so:

float distance_to_surface_of_model(x, y, z);

For every point in 3d space you can get the distance to the surface. So, if you have a camera you can shoot a ray into the scene and pick some points on it to ask if it is inside the model. if so you paint that pixel with the surface material of the model. Then it's just a matter of picking a good way of sampling points along the camera ray. usually this distance function is some basic math (distance to sphere or so). But here they take a 3d mesh and create a neural network that can answer the question of distance to it (since meshes are very slow at that).

Wikipedia is 20 6 years ago

If it’s controversial, the writing will tend towards the careful middle.

No, it will tend towards the side of those who has the most admin rights and most time for reverts. They will have no interest in neutrality

Often it has been that Vulkan is closer to how GPUs work simply due to GPU manufacturers having to change their GPUs to work well with Vulkan. To for example add a co-processor to the GPU so that it can do job scheduling in a more Vulkanish way.

Vulkan was after all a spec from one GPU manufacturer (AMD), there are a handfull others with their own archs developed with their own assumptions.

There is no reason why you can't run AMD/Nvidia GPUs alongside ARM chips. The GPUs do not run x86.

Further, the average laptop consumer is happy with their intel integrated graphics. All they do is browse the web and punch some numbers in excel.

No, the 14% figure is for people that self-requested testing. You can see it as an upper boundary, but it won't be the actual figure, which is likely around 8% or so.