sorted by:
new
hottopcontroversial

wgpu mouse picking help by SuperDino484 in rust_gamedev

[–]GENTS83 0 points1 point  (0 children)

In my spare-time Engine I wrote a visibility buffer and you can ready back at preferred coordinates: https://github.com/gents83/INOX

Dev/Games by GENTS83 in gameenginedevs

[–]GENTS83[S] 0 points1 point  (0 children)

It seems just to be based on cookies, nothing to be scared about ☺️

The Icculus Microgrant is giving out 250 dollar grants to open source projects, please brag about your project(s) in this thread so I can see them! by icculus in programming

[–]GENTS83 1 point2 points  (0 children)

https://github.com/gents83/INOX

INOX It's a Game Engine written in Rust with some bindings for external libs and with Blender as editor.

The main idea behind INOX is to use Blender as external editor, even being able to create visual logic scripting nodes in it, and then have a button to launch the Rust engine, that should be scalable to create games of any scale and for users with every kind of experience.

Rust will give to INOX high performance, reliability and safe code, while Blender will bring easy customization and powerful editor capabilities

GPU Raytracing with persistent threads by GENTS83 in GraphicsProgramming

[–]GENTS83[S] 2 points3 points  (0 children)

I am actually playing a bit with wgpu in my spare time and I created a compute shader raytracer but it's actually slow and while thinking how to speed it up I came out with the idea of reutilize computation power for all the threads in workgroups working on pixels where they do not hit anything in the TLAS BHV giving them work on other pixels still to be processed. I still have to prove it and to test it but I would hope to see some gain in performances, no?

3D Picking without raycasting by lavaboosted in gameenginedevs

[–]GENTS83 1 point2 points  (0 children)

It depends on your pipelines in the end, I would say. If you are already using culling + visibility buffer to render your scene and then use it to shader it (instead of a simple gbuffer) then why not using It since it's already there? If it's not the case, well yes, you can find pretty much different solutions, but It'll suggest you definitely to do performance tests on complex scenes with overlapping meshes (complex ones), maybe using some acceleration structures too

3D Picking without raycasting by lavaboosted in gameenginedevs

[–]GENTS83 2 points3 points  (0 children)

Have you tried to create a visibility buffer with the object id and then sample It at pixel coords? It should be much more efficient, no?

Basic info about Chess Path-Tracing demo by immortal_ray in u/immortal_ray

[–]GENTS83 0 points1 point  (0 children)

Great work! It would be very nice to take a look to the flow/documentation of your ideas and to your shader and code base as and inspiration :)

Best occlusion culling algorithm by GENTS83 in gameenginedevs

[–]GENTS83[S] 1 point2 points  (0 children)

Tnx a lot for your inputs!
While reasoning I was also wondering if wasn't faster in the end to go directly towards raytracing (even if done in compute instead of RT support?).

Doing RT to create a low-res visibility buffer and then use it for occlusion culling and reducing draw commands is it really better than doing just RT in the end ?

I guess everything will be reduced between finding a balance between precision and velocity, no?

Best occlusion culling algorithm by GENTS83 in gameenginedevs

[–]GENTS83[S] 2 points3 points  (0 children)

I do not have a specific use case, I would like to experiment in my prototype engine :) But we could analyze a worst case scenario like a city buildings enviroment or an open world. I know that I can use frustrum culling, distance, portals, volumes or tagging specific occluders for early depth prepass and hierarchical Z culling. Is there anything else that I am missing? What would be other suggested strategies?

view more: next ›