[Domain] 에이전트 스폰 시스템 및 벽 충돌 슬라이딩 이동 로직 구현 (#15)#112
Merged
Conversation
Reflect review follow-ups: build the fixture service, keep initial placement in PopulationSpec, and add fixture coverage.
스크립트 부분 약간 다듬었습니다.
95x8x9
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
AgentSpawnSystem 구현: FacilityLayout2D의 spawnZones 데이터를 읽어와 에이전트 엔티티를 자동으로 생성하는 시스템을 구축했습니다.
MovementSystem 및 Wall-Sliding 로직: 에이전트와 벽(Barrier2D) 사이의 충돌을 감지하고, 벽을 타고 매끄럽게 흐르는 슬라이딩 이동 물리 로직을 구현했습니다.
Related Issue
Area
Architecture Check
application -> domain -> engine.src/domain.domainorapplicationdependencies tosrc/engine.src/as the include root.Verification
cmake --preset windows-debugcmake --build --preset build-debugctest --preset test-debugRisks / Follow-up
타임스텝 동기화: 현재 이동 로직에 0.016s 고정 값을 사용 중입니다. 추후 엔진의 step.dt와 연동하여 가변 프레임에서도 일정한 속도를 유지하도록 고도화가 필요합니다.
UI 연동: 엔진 내부 로직 검증은 완료되었으나, 시각적 확인을 위해 현재 작업 중인 UI/렌더링 파이프라인과의 병합 및 테스트가 후속 과제로 남아 있습니다.