galaco / lambda-core Goto Github PK

Displacements are currently forcibly rendered at all times. Search for dispFaces to find the relevant code.

Visibility optimisation needs to incorporate displacement faces

Enable back face culling.

In theory this should be setting the opengl flag when initializing the renderer.

It may not be that simple though. scene/loader/worldspawn.go splits quad or higher faces into triangles. That code wasn't written to account for back face culling, there could be unintentional culled faces. If that is the case, splitting faces should be modified to account for face normal direction (and winding order i think) when writing vertex order for new triangles

Material loader currently cannot find these textures. It needs to be updated to search for these types.

Possibly caused by it searching for a vmt when it should be a vtf instead.

Many displacements look mostly correct, but many vertices along edges mismatch neighbouring displacement vertices, creating holes in between displacements.

This only appears to affect the z axis in tested maps, but that may be coincidence

de_dust2 vehicles have very corrupt materials. Likely related to dxt decompression.

May be an issue with external vtf library https://github.com/galaco/vtf.

de_dust2 certain props exhibit some bad faces. I know this is a lazy issue, but it should be obvious what this is referring to on loading (probably any) map

Render with lightmaps enabled seems to work consistantly without errors, but most (95% or so) of faces are corrupt or warped in some way.

This is probably due to either wrong lightmap coordinates generated for face, or incorrect samples used when generating the lightmap texture

Loaded studiomodels only apply the first referenced material in the .mdl file. All materials need to be supported and mapped to each model.

As title suggests. Valid faces with tools textures (e.g. tools/trigger) are rendered with buggy texture info. Remove rendering of these faces.

There is potential for load improvements by threading/goroutining material loading. Most materials are referenced ahead of world loading in the material dictionary. In theory these could be loaded simultaneously first, instead of consecutively as they are now

An example Texture Atlas struct exists, with relevant definitions already complete. The packing function however is not written. This needs finishing.

Lightmaps can then be refactored to use a common Atlas texture, rather than generating a texture per face from pre-calculated samples.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• Update module github.com/galaco/filesystem to v0.1.4
• Update module github.com/galaco/studiomodel to v0.2.2
• Update module github.com/galaco/vpk2 to v1

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update module github.com/galaco/bsp to v0.3.1
• Update module github.com/galaco/vtf to v1.2.0
• Update module github.com/go-gl/mathgl to v1
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Rewrite the current cubemap implementation to be less Skybox oriented.