3 ms·

It's not a BSP, it's volumetric data (this is in the actual article). Just off the bat I get aerial navigation "for free" without having to hand-place regions,

It's not a BSP, it's volumetric data (this is in the actual article). Just off the bat I get aerial navigation "for free" without having to hand-place regions, and a secondary collision-query for bullet-hell that's much faster than Chaos, which was a huge perf regression in UE5 from PhysX (which already wasn't great). Additionally, there's productivity + rapid iteratoin. Trying to build interiors with Unreal's built in drag-out-an-actor-at-time interface is too laborious, and the built-in automations (Construction Scripts, Blutilities, PCG) are impedance-mismatched for constructing interiors quickly.

LarsDu88 2y ago
How is it that you are running into cpu limitations for raycasts in a bullet hell game with UE5 to the extent you built this? I wrote a VR game that has hundreds of bullets running at 72 fps on Quest 2. Never went multithreaded and never actually encountered FPS drops due to CPU limitations
- mwkaufma 2y ago
  Can't tell you wo a profile, but I assume your content was as complex as a full byzantine shooter map. I've also got large enemy squads, so there's an M×N issue.
LarsDu88 2y ago
I don't think I quite understood what you are trying to accomplish that is distinct from what 90s BSP engines like Unreal 1, Quake 2, and Source were doing? Are you trying to do convex spatial partitions for 3d pathfinding in the air? I did an indie VR starfighter game Rogue Stargun (https://roguestargun.com https://roguestargun.com) and quite honestly intermittent navigation raycasts from the enemy ship AI is sufficient for this sort of stuff. The bullets all run on the main thread on mobile hardware and so does all the AI. It's not optimized and I have yet to witness CPU bottlenecks being the main cause of frame drops. Your game looks simple enough and is on the PC platform... I suspect you may be optimizing for the wrong thing.
- mwkaufma 2y ago
  Target is switch/steam deck, and I have hard profiling numbers on fully decked scenes, so your suspicions are inaccurate.

LarsDu88 2y ago

How is it that you are running into cpu limitations for raycasts in a bullet hell game with UE5 to the extent you built this? I wrote a VR game that has hundreds of bullets running at 72 fps on Quest 2. Never went multithreaded and never actually encountered FPS drops due to CPU limitations

mwkaufma 2y ago
Can't tell you wo a profile, but I assume your content was as complex as a full byzantine shooter map. I've also got large enemy squads, so there's an M×N issue.

LarsDu88 2y ago

I don't think I quite understood what you are trying to accomplish that is distinct from what 90s BSP engines like Unreal 1, Quake 2, and Source were doing? Are you trying to do convex spatial partitions for 3d pathfinding in the air? I did an indie VR starfighter game Rogue Stargun (https://roguestargun.com https://roguestargun.com) and quite honestly intermittent navigation raycasts from the enemy ship AI is sufficient for this sort of stuff. The bullets all run on the main thread on mobile hardware and so does all the AI. It's not optimized and I have yet to witness CPU bottlenecks being the main cause of frame drops. Your game looks simple enough and is on the PC platform... I suspect you may be optimizing for the wrong thing.

mwkaufma 2y ago
Target is switch/steam deck, and I have hard profiling numbers on fully decked scenes, so your suspicions are inaccurate.