occlusion culling??

[Yue]

What is it really? How can I use it to improve performance levels. If I create a lot of cubes, I have performance deterioration, so if I have a single platform I don't have problems, but if I have a lot this goes down to 20 fps.

[Josh]

Are your boxes instanced? How are they being created?

[Yue]

This is the best I can have in performance, however if I place more elements such as platforms columns walls at the base of the brushes, the fps begins to drop drastically. 

What I'm doing is creating prefabricated elements, putting them on stage and copying them and positioning ourselves to create levels. 

 

 

 

 

[Yue]

I think the point is in my computing power, it doesn't matter anymore. Initially I had an e5400 processor and I passed it to e8400, but still this hangs.

 

[Yue]

[Josh]

I would be interested in seeing your project files. Your scene does not look very complex

[reepblue]

Try making the platforms models and repeat the test. Sounds like the "If I add too many objects to my scene, it slows down" issue.

[aiaf]

Occlusion culling means that geometry not inside the view of the camera, will not be drawn, for performance reasons.

Is good to think of this when designing your level.

But your scene seem simple don't know what the problem could be.

I had at some point 800 instanced cubes in a scene, leadwerks has no problem with that.

 

 

[Josh]

If you just upload one of those models I am sure it has something drastically wrong with it, like 100 different subobjects each.

[Yue]

 

What I do is create prefabricated ones, drag them to the editor, copy them and create the scenario.

The same happens with the character, it is loaded from the stage ( map editor ).

 

 

 

 

[Yue]

32 minutes ago, aiaf said:

Occlusion culling means that geometry not inside the view of the camera, will not be drawn, for performance reasons.

Is good to think of this when designing your level.

But your scene seem simple don't know what the problem could be.

I had at some point 800 instanced cubes in a scene, leadwerks has no problem with that.

 

 

That is to say that if you marked that option in the entity, as a mesh, that mesh is not visualized, it is not rendered when the camera is not looking at it?

[Josh]

By default you don’t need to do anything. Occlusion culling works on entire chunks of the scene, automatically.

your scene has something very wrong with it but no one can tell what by looking at screenshots.

[Yue]

I have discovered something, if under the screen resolution of 1024 x 768 to 640 x 480, this is normalized.

I suppose they are my resources, my experience as a player make me remember when I played GTA IV to the minimum of details and with the smallest screen resolution possible to have a better performance.

[Yue]

640 x 480 resolution screen.

 

[Josh]

Occlusion culling means that if an object is in front of another object, the object behind the one blocking it gets skipped entirely.

[Josh]

In your scene shown above, nothing would be culled because all objects seem to be visible.

[Josh]

It's probably the post-processing effects more than anything else that are causing a slowdown, but since you have VSync enabled the FPS is locked at 60 anyways.

[Yue]

2 hours ago, Josh said:

In your scene shown above, nothing would be culled because all objects seem to be visible.

That is to say, if I have a wall and behind that wall there is a box, and the wall has the culling occlusion option marked, then the box behind that wall is not drawn, because the camera is not being visualized?

[Josh]

Just now, Iris3D Games said:

That is to say, if I have a wall and behind that wall there is a box, and the wall has the culling occlusion option marked, then the box behind that wall is not drawn, because the camera is not being visualized?

If per-object occlusion culling is enabled, it will not be drawn. Otherwise it will be skipped only if the entire octree node is hidden. But the occlusion test itself has a cost, so you should not go around enabling this on a per-object basis.

Anyways, your bottleneck is the fragment shader. SSR and SSAO are going to have the biggest performance impact.

[Yue]

I have deactivated the shaders that you mention, but obviously it has to do with the screen resolution, if I use resolution greater than 800 x 600 I have bottleneck. 

 

For example if I launch the game from the editor I have a frame rate of 23 - 25, if I launch it from the executable by closing the map editor, I have 28 - 30. I think it's because it's an open world, that I have that drawback, but if I think of a closed level with rooms, walls seems to be more manageable the drawback, because what's behind the walls is not drawn until I cross that door and the other closes, then the performance remains at 60 fps.

It's really hard for me to understand with this of the translator, I'm going to deactivate the vertical synchronization as you mentioned. 

Translated with www.DeepL.com/Translator

[Yue]

 

Sync Off 800 x 600

Sync Off 1024 x 768 42 fps.

[Josh]

What GPU is this?

[Yue]

9 hours ago, Josh said:

What GPU is this?

GTX 1050 2 G ram. 

[Yue]

 

 

In case anyone wants to try this. 
https://www.dropbox.com/sh/25uzx6yefdqlf2i/AACiWj6-ClxelluEWFRB2AO3a?dl=0

The new updates to test performance was to go to an internet room and test it on a computer with a gtx 1060 i5 processor and 6 gigs on ram. It ran very well in different screen resolutions, so it's definitely my computing power problem.  At this point nothing to do to continue with this.
 

[carlb]

60fps for me