rasterizer | A state-of-the-art software occlusion culling system

I'm using Selenium, Chrome, and Python 3.

Here's what I'm doing to set everything up

I am working on my Raycaster engine for some time, that I am runing on slower machines. The most challenging problem I occures was/is the efficient floor and ceiling casting.

My question is: what other faster approached can I use? (I am not sure how Doom floors and ceilings are rendered)

So far I tried two typical solutions:

• verical and horizontal - casting as described in well know lodev tutorial: https://lodev.org/cgtutor/raycasting2.html

The horizontal approach is of course much faster, but I additionally optimized it with fixed point variables.

Unfortunately even that approach is a performance killer - quite big fps drop even on faster cpus, and an slower cpus its a bottle neck.

My other ideas:

• I figure out an algorithm that was converting visible floor/ceiling map tiles to quads that I splitted to two triangles - and rasterized them as in regular scanline rasterizers. It was much faster - also I could sorted tiles by texture id to be more cache friendly. Unfortunately I got into "perspective correction texture mapping" in that case - to fix this I must add some divisions, that will lower the performacnce.. but also there are some optimalizations that can be done..

• using horizontal casting with every 2 ray (in column, row or both) - i will fill the blank spaces with averaged texture coords

• I could also try to combine my algorithm from 1 point with horizontal casting - I could sort the textures by ID then for example, I think that there would be no texture distortions

• mode 7 ?

my progres so far: https://www.youtube.com/watch?v=u3zA2Wh0NB4

EDIT (1):

The Floor and Ceiling rednering code (based od lodev tutorial the horizontal approach) but optimized with fixed point. Ceil calculations are mirrored to floor.

https://lodev.org/cgtutor/raycasting2.html

This approach is faster than the vertical approach, butlots of calculations is inner loop and random accesing to texture pixels hits the performance..

I have an object that I need to populate before using called pipelineInfo. To populate the object I use a function called createPipelineInfo. This works perfectly well when I use visual studios to compile a debug build but when I try to compile a release build the compiler "optimizes" out the entire createPipelineInfo function.

Here is the call to initialize the object and its use:

I have implemented a naive FAST corner detector using C++ boost algorithm. Currently it does not have non max suppression. I ran my implementation and the OPENCV implementation on this photo below

The output of OPENCV is

The output from my implementation is

Here is my code

Before anyone mark this as a duplicate, I referenced this stackoverflow question before posting here, I tried all solutions in that thread but still it is not working for me. I am migrating a legacy java project into spring boot application. When I start the server I am getting this stacktrace,

I'm currently working on a graphics engine and I wish to update the pipeline state at runtime. Creating a new pipeline for each single resource update (ie: enabling depth clamp, enabling color blend) at runtime and then re-binding everything to the command buffer takes up a considerable amount of performance.

So what I planned on doing was, to create a single pipeline and store all the attributes needed for its creation (ie: Rasterizer state, Multisampling state, Color blend state, etc..) and update those individual structs at runtime. After all we are passing in the address of the structs, not by value.

This brings me to my question, does the updates to a struct which is passed on in the pipeline creation, reflect on the actual draw call at runtime, without the need for recreating the pipeline again?

Thank you!

I am trying to write a small 3D game in C++, using DirectX 11. This is absolutely the first time I have attempted to write a game using only a graphics API. I have been following the tutorials on the website Rastertek.com up to Tutorial 9 for ambient lighting.

After implementing movement and collisions for the player, I increased the size of my play area. This is when I noticed my issue: the textures I am using for the walls and floor of my play area are not being rendered the way I expected them to.

Wall from close up

Wall from far away

Maybe you can tell how the lines on the wall appear strangely broken up - I was expecting them to be rendered properly at larger distances (like they are close up).

The thing that seems most weird to me, though, is that the lines can be rendered from far away, but only while moving the camera around the scene and only on certain parts of the wall. Standing still breaks the texture again. I tried capturing this effect on video, but I had no success getting it to show up in the video I took with the GeForce Experience.

I tried playing around with a bunch of the settings that DirectX offers, like the rasterizer or the depth buffer descriptions, I tried to enable and disable VSync, Antialiasing and Multisampling, I tried using Anisotropic filtering instead of linear filtering... But none of it had any effect.

I do not know where to look and what to try next. Am I just going to have to accept that my textures will look terrible at any sort of distance?

I am trying to automate a website with selenium to download an excel file. I have the following HTML for the button:

I'm trying to have a docker container running on google cloud run, which is containing a simple nodejs app and google chromium headless to create a PDF from HTML source. Unfortunately, Google Cloud Run seems to have issues with thatever solution I try.

My Docker image(s) run perfectly locally and on other providers (i.E. Azure), but GCP just does not work.

What I try:

Basically building any docker image, installing node, npm, chromium, then running chromium --headless in the background. Then running the node app. The Node app is simply trying to connect to 127.0.0.1:9222 => that doesn't work on GCP, but anywhere else.

I tried with the official node images of docker hub I tried with an alpine image I tried with a debian image All of these run fine locally, but not on google cloud run.

Here's my latest test with a debian image: