Yue

If I remove the occlusion system from the camera the error is not displayed. However, everything is rendered even if it is not in the camera. What I am trying to do is to create a base with small rooms and setting a respective angle to avoid the problem. If the wall is not too far away from the camera the effect is not seen.

https://www.mediafire.com/file/r97h1kbj9daz83p/AstrocucoX.rar/file Look at this simple test, in such a case if I have a box, or a terrain I have that strange effect. You remove the sky with the m key.

It is using a skybox that produces that effect, even if it is just a simple outline, a cube, with 6 walls. The problem is that the sky box and my eight gigabyte gtx 1070 graphic produces this unpleasant effect and the same if I have a terrain, even if it is 512 x 512 In such a case the solution is to create a small base on the surface, and then in another level without skybox or terrain, create the base underground. That level would not have the base would not have that skybox, and you would not see that problem. I know that in a more powerful computer the defect would be visible, but for me it is a problem when I want to show the progress of the game in a video. In such a case my gpu would not be the problem, I think it is my second generation processor an I7 from several years ago. But what is really strange for me is that if I play GTA V, that doesn't happen.

No, I don't have anything in the scene, only the last image, the error only happens when I have fog, or a terrain, or the sky. And inside a brush structure, when I rotate the camera, the wall suddenly appears and the skybox appears in the background.

#version 400 // Uniforms uniform samplerCube texture0; // Cube map uniform vec3 cameraposition; uniform vec2 camerarange; // Inputs in vec4 ex_vertexposition; in float ex_selectionstate; in vec3 ex_VertexCameraPosition; out vec4 fragData0; out vec4 fragData1; out vec4 fragData2; out vec4 fragData3; void main(void) { vec3 cubecoord = normalize(ex_vertexposition.xyz - cameraposition); vec4 outcolor = texture(texture0, cubecoord); // Calcula la distancia desde la cámara al fragmento float distanceToCamera = length(ex_vertexposition.xyz - ex_VertexCameraPosition); // Compara la distancia con el rango de la cámara para determinar si está detrás de otros objetos bool isBehind = distanceToCamera > camerarange.x && distanceToCamera < camerarange.y; if (isBehind) { // Si el fragmento está detrás de otros objetos, dibuja el skybox fragData0 = outcolor * (1.0 - ex_selectionstate) + ex_selectionstate * (outcolor * 0.5 + vec4(0.5, 0.0, 0.0, 0.0)); } else { // Si el fragmento está delante de otros objetos, no dibujes nada discard; } fragData1 = vec4(0.0); fragData2 = vec4(0.0, 0.0, 0.0, 0.0); fragData3 = vec4(ex_VertexCameraPosition, 1.0); } Looking at the skybox sahder, but everything seems to be ok, chatgpt tells me it is the occlusion system.

Likewise, disable the fog when inside an installation, the question is why this happens, it is not my graphics card that I had before, the gtx 1050 of two gigabytes, much less the one I have now gtx 1070 of eight gigabytes. But the good thing about understanding all this is that I can do something about it, and not be suffering for not understanding what is happening.

If I remove the sky and terrain, the walls of the facility do not disappear when I rotate the camera. In such a case a solution would be that when I am inside the station I can remove the sky and the terrain, I suppose that with the sky I can remove the material, but I don't know if I can hide the terrain.

New Base.

I have dismembered the whole base, and the problem is corrected the shadows of focus light, now, the problem that the walls disappear I will have if I solve it by creating a new base but taking into account several factors of design and testing. The thing is that @Josh a few years ago mentioned that it was because of my nvidia gtx 1050 gpu, now that I have a gtx 1070 of eight gigas, it happens the same. Possible solutions, create the base in another level, and in the terrain just leave a door to enter it and make the respective level change. Where on the ground will be able to store the rover in a garage.

The shadow delay is that if I put two focus lights too close together it happens. I think I will implement the debugging information and work based on this.

https://www.mediafire.com/file/kjn0redkq8hmt5t/AstrocucoX.7z/file I have problems with the walls disappearing when I am inside the structure. And the focus lights in their shadows have lag

At this point I am having performance problems on my computer. I will release a test version, I guess I have overdone the use of brushes to create a base.

I believe I have traveled the same path you have taken. Any questions I am here to give you guidance. My beginnings were also BB, BMX.

I am one of those who think that machines or video game engines are just tools, the art is in human beings, they are the ones who develop the skills, this is the case, you can say that with a coal as much as with a box of watercolors and brushes you can do great things.

The problem is that I don't know English, my native language is Spanish. And maybe the answer would be, I've learned a lot of things with Leadwerks. That's why I don't use Unity or Unreal Engine, or App Game kit, or Godot Engine, or neoaxis, because in the end it's leadwerks is a tool with which I feel very comfortable. "Thank you for making your game on the Leadwerks engine. I mean, you could have chosen any other engine, for example some more popular one, but you decided to work in this one. If you don't mind, can I ask you something ? Can you please film some tutorials on (and about) this engine or give some advice: what's worth learning, what's worth knowing, what obstacles you have to deal with. I would be very grateful because, apart from the official documentation, there are very few other tutorials. It scares me to try to subdue this monster with zero knowledge about how to work with it, what can it do."

Can someone please confirm, lost day here without documentation.