studio/marathon
2
0
Fork 0
Code Issues 121 Pull Requests Actions Packages Projects Releases Wiki Activity

Vendor bevy_pbr for materials and lighting #7

New Issue
Closed
opened 2025-12-17 01:41:00 +00:00 by siennathesane · 1 comment
siennathesane commented 2025-12-17 01:41:00 +00:00 (Migrated from github.com)
Copy Link

Vendor Bevy's PBR materials and lighting system into Marathon.

Scope:

  • Copy bevy_pbr module
  • Include metallic/roughness workflow
  • Include lighting system (point, directional, spot)
  • Include shadow rendering support

Acceptance Criteria:

  • PBR materials system compiles
  • Lighting types are available
  • Shadow rendering infrastructure present
  • Module integrates with vendored bevy_render
Vendor Bevy's PBR materials and lighting system into Marathon. **Scope:** - Copy `bevy_pbr` module - Include metallic/roughness workflow - Include lighting system (point, directional, spot) - Include shadow rendering support **Acceptance Criteria:** - [ ] PBR materials system compiles - [ ] Lighting types are available - [ ] Shadow rendering infrastructure present - [ ] Module integrates with vendored bevy_render
siennathesane commented 2025-12-23 23:59:20 +00:00 (Migrated from github.com)
Copy Link

✅ Complete

Vendored bevy_pbr to crates/libmarathon/src/render/pbr/:

  • ~34.5K LOC from 51 source files
  • Full PBR material system (metallic/roughness workflow)
  • Lighting system: point lights, directional lights, spot lights
  • Shadow rendering infrastructure included
  • StandardMaterial properly integrated

All acceptance criteria met. Part of Phase 1 completion for #2.

✅ **Complete** Vendored bevy_pbr to `crates/libmarathon/src/render/pbr/`: - ~34.5K LOC from 51 source files - Full PBR material system (metallic/roughness workflow) - Lighting system: point lights, directional lights, spot lights - Shadow rendering infrastructure included - StandardMaterial properly integrated All acceptance criteria met. Part of Phase 1 completion for #2.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/audio
Spatial audio engine, sound playback, audio mixing, music systems, 3D audio positioning
 area/content
Art assets, models, textures, audio files, dialogue trees, narrative content, game data
 area/core
Foundation systems, memory management, math libraries, data structures, core utilities
 area/docs
Documentation, technical specs, RFCs, architecture decisions, API docs, tutorials, guides
 area/infrastructure
Deployment pipelines, hosting, cloud services, monitoring, logging, DevOps, releases
 area/networking
iroh P2P, CRDT sync, gossip protocol, network replication, connection management
 area/platform
iOS/macOS platform code, cross-platform abstractions, input handling, OS integration
 area/rendering
Graphics pipeline, Bevy rendering, shaders, materials, lighting, cameras, meshes, textures
 area/rfc
RFC proposals, design discussions, architecture planning, feature specifications
 area/simulation
Agent systems, NPC behaviors, AI, game mechanics, interactions, simulation logic
 area/tooling
Build systems, CI/CD pipelines, development tools, code generation, testing infrastructure
 area/ui-ux
User interface, menus, HUD elements, input feedback, screen layouts, navigation
 dependencies
Pull requests that update a dependency file
 epic
Large body of work spanning multiple features
 rust
Pull requests that update rust code
No Label area/rendering
Milestone
No items
No Milestone v0
Projects
Clear projects
No project
Assignees
Clear assignees
gitea_admin siennathesane
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: studio/marathon#7
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?