fcvarela/gosg

Golang 3D renderer sandbox

gosg's Issues

More embedding, less casting

Remove all *system interfaces and make them structs. Embed them inside each implementation.

Bounds update doing too much work per update cycle

Something is marking node bounds dirty @each iteration, causing them to get recomputed always. This is CPU intensive, see attached profile.

profile.svg.zip

Node IDs and pass mask for picking, etc

Assign node IDs and always render a picking pass (along w/ z-prepass maybe?) into a picking texture. Expose selected object as map and node Selected method. Nodes will need selected status recalculated after picking pass.

New batching not GC friendly

Instead of autobatching, attempt to insert into pre-existing batch list of new object creation or when loading models. Right now, creating a render plan isn't GC friendly.

Explicit rendertarget texture attachments

RenderTargets create their textures/attachments based on input layer hints. This needs to be explicit, ie rt->SetDepthAttachment(depthTexture). We should also consider using array textures only in which case we'll need layer parameters as well.

use /physics bullet code independent of gosg

Would it be much of a hassle to use the /physics branch code independent of gosg ? How would I do this?