branchrust_reboot/main/projectile_jobscancel
113 Commits over 30 Days - 0.16cph!
Update: BaseRaidBench - set batched mode as default for scene
Update: BaseRaidBench - restore global state at the end of the benchmark
Tests: ran the scen
Update: BaseRaidBench - emulate timed explosive fuse
Not really important for now, but later once rockets fly upwards and have a chance to miss, this should make it match reality closer
Tests: ran the scene
Update: BaseRaidBenchmark - expose batching mode via component
Tests: none, trivial change
Update: BaseRaidBench - disable camera shake and hurt effects
Tests: ran the scene
Update: Add BaseRaidBench to build scene list and mark it for maps bundle
- Also removed the nuked Foliage scene - forgot to clean it up
Tests: none
Update: BaseRaidBench - unblock pooling
Takes the edge off halfway through the benchmark, but initial 5 seconds are still rough.
Tests: ran the scene
Update: BaseRaidBench - reposition camera to above the circle
Tests: ran scene
Bugfix: BaseRaidBench - fix NREs by loading game manifest on start
Tests: ran scene
Update: BaseRaidBench - players now animate and produce muzzle flashes
Tests: ran the scene
Bugfix: BaseRaidBench - track weapon cooldown properly
- also account for animation delay for weapons that have it
The benchmark is now much more tame.
Tests: ran the scene
Update: BaseRaidBench - stagger initial weapon cooldowns
More realistic, and avoids spiking specific frames
Tests: ran scene
Update: BaseRaid - emulate rockets and grenade movement
Tests: ran scene, player is blasted to high heaven
Update: BaseRaidBench - use projectile specific velocity
Tests: ran scene
Update: BaseRaidBench - weapons now use their respective projectiles instead of rifle bullets
- EffectLibrary can return GameObjects now
Tests: ran the scene. Server-side projectiles need further massaging (as there's no server)
Update: BaseRaidBench - implement firing cooldown
At least now frame time stabilizes around 150ms.
Tests: ran the scene.
Update: BaseRaidBEnch - wip shooting
Since there's no firing cooldown, 100 players shooting every frame lags a ton
Tests: ran scene
Bugfix: BaseRaidBench - this is no longer nude beach
Tests: built C+S and C-only, ran the scene
Update: BaseRaidBench - simulate client flow
- use a fake client backend and a dummy connection
Fixes players not facing the target, but breaks player clothing for what-ever reason.
Tests: ran scene
Update: BaseRaidBench - wip weapon aiming
- Weapon debug graphics confirm aiming direction
- Player model doesn't face the right way (need to run client updates, that's next)
- added benchmark-related safety checks in local client logic
This also hijacks main camera, I'll have to fix that later
Tests: ran the scene
Bugfix: BaseRaidBench - make sure weapon flags are synced with held state
Tests: ran the scene
Update: BaseRaidBench - give players projectile weapons on spawn
For what-ever reason, doesn't appear in hands(instead on back), despite being reported as "held". Still investigating
Tests: ran the bench scene
Update: BaseRaidBenchmark - adjust the camera positioning to get the full circle in view
Tests: ran the scene
Update: BaseRaidBenchmark - players are visible and dressed
Tests: ran the scene
New: BaseRaidBenchmark - stress test client via a raid scenario
- Doesn't do much, just ground framework
Tests: ran the scene - saw players spawn (but not their visuals)
Update: World Setup Benchmark -> BiomeBenchmark World Setup rename
- replaced default params on BiomeBEnchmark with placeholder to indicate they don't do anything
Tests: none, trivial changes
Clean: Refactor free-slot searching logic
Hope is to make it harder to mess up index calculation when writing more code of this style
Tests: GamePhys unit tests + projectile consistency unit test
Tests: GamePhysics.TraceRrays and TraceSpheres coverage
Wasn't covered previously which led a bug slip in. But has already been fixed.
Tests: ran it with bugfix revwerted - failed(as expected). Reapplied fix - passed
Clean: simplify previous bugfix
Tests: ran the unit test
Update: Projectile.TestConsistency now checks for number of phys commands issued
Tests: unit test passes
Bugfix: Projectile.TestConsistency - when substepping movement, use the right trace result
Tests: consistency unit test now passes
Bugfix: TestProjectileEntity now works in C+S
Tests: ran the previously failing unit test
Bugfix: Projectile.Batch - don't over-simulate prjectile when reacting to a hit/ricochet
Also noticed serial test vs entity is failing - will fix next
Tests: single-projectile-batch test passes, but the whole batch fails
Update: ProjectileTests.TestConsistency - debug code to isolate projectile
Still fails on 520, but now with different results(proj moves, but different height).
Tests: ran unit test - fails (expected)
Update: ProjectileTests.TestConsistency - rewrote logic to run both serial and batched in one test
- Removed old serial validation logic
- Renamed PerfSerial test to Performance (since it also runs batched variation)
Detects an issue currently, investigating.
Tests: ran the new test - fails (kind of expected, but still suspicious)
Update: TestLineOfSightBatched
A lil cheeky 44k raycasts test. Missing the actual batched query impl.
Tests: ran the test - failing as expected
Update: GamePhysics tests - move box grid creation to individual tests
Avoids polluting the world for other tests(problem for LineOfSightBatched)
Tests: ran the updated unit tests
Update: GamePhysics tests - spawn ignore volumes per tests
Tests: ran the 3 affected tests - they pass
Update: TestTraceAll - don't spawn Terrain boxes
We already have terrain at the bottom of the ocean
Tests: ran TestTraceAll
Tests: new GamePhysics tests - TestLineOfSight
- Also making craggy loading in unit test stable by applying same fixes from Test.Projectile
No batched variant as we haven't implemented it yet
Tests: ran the new unit tests
Tests: new GameTrace tests - TestsTraceAll and TestsTraceAllBatched
TestTraceAllBatched is currently failing, as it's wip
Tests: ran new unit tests
Update: projectile perf test
Tests: ran the perf test
Buildfix: rename UnitTests.WaterLevel to WaterLevelTests
It was colliding with a non-namespace WaterLevel and causing a headache
Tests: editor build in C+S
Update: refactor TestConsistency and make it cover a larger area
- increased proj velocity, as it was possible for proj to start inside the shield, breaking validation
Tests: ran unit test
Update: TestConsistency now validates repl projectiles as well
Test: ran the unit test
Update: TestConsistency now passes
- validates auth proj hit their players/shields
- added utility that helps revalidate projectile hit and get more info (auth only for now)
Need to expand to re-validate non-auth hits
Tests: ran projectile consistency test
Update: wip fixing the consistency test
- fix invalid tracking of on which frame a hit is expected
- extra validation code to confirm hits to expected players - revealed missmatches
Need to redo how I setup the players to avoid random overlapping
Tests: ran the test
Update(wip): new comprehensive projectile test on craggy
- spawns a bunch of players on craggy and drops projectiles on them
Currently fails as majority of hits miss (but expect 100% hit rate) - likely bad test setup. Will investigate tomorrow
Tests: ran unit tests
Update: projectile tests against players with shields
Test: ran new unit tests
Update: rewrite TestProjectileWater to attempt to hit a player in water
Tests: ran new TestProjectileWater - pass all
