AssetUsageRender MAIN_WORLD and RENDER_WORLD is confusing and not explicit and overlapping with MainWorld Resource

[FcGod]

Greetings, dear reader!

Was looking at CPU rendering example and the line:
RenderAssetUsages::MAIN_WORLD | RenderAssetUsages::RENDER_WORLD

is confusing. MAIN_WORLD feels so weird to say "this is loaded on CPU and RAM" and "RENDER_WORLD" is "loaded on GPU and VRAM" as per: DOCS: struct.RenderAssetUsage

It gives me the feeling MAIN_WORLD is just..logic? processing? and no rendering yet it can also do rendering..so main and render world both..render? not just render_world as per its name?

And when a friend told me "do it in main world" I was given this the resource on google over the bit flag. Which made me confused "why does state of application help me render?" as per: DOCS: struct.MainWorld

I propose a rename for the constants to something more intuitive, perhaps CPU_PROCESSING AND GPU_PROCESSING for example. So its more intutive as "i want this cpu and ram or GPU and VRAM"

Thank you!

[laundmo]

I talked @FcGod into making this after he told menon discord how RenderAssetUsages confused him.

To reiterate: Theres a duplication of terminology which makes it unclear what RenderAssetUsages refers to.

does RenderAssetUsages::MAIN_WORLD mean just the ECS Main App/World, does RenderAssetUsages::RENDER_WORLD then refer to the ECS Render Subapp/World? The docs state otherwise: MAIN_WORLD means CPU/Ram, and RENDER_WORLD means GPU/VRam - so does that mean a asset with RenderAssetUsages::RENDER_WORLD is or isn't available in Render Subapp?

Even though the docs are relatively comprehensive, i can fully understand the confusion (and this isn't the first time the naming needs explaining)

[JMS55]

Also see this PR for past discussion about this topic: #11399