stride3d / stride3d/stride

[RFC] Stride multithreading | Separate logic and windowing

Open
#1,488 7 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C#
Stars
7.8k
Forks
1.2k
Avg merge
2d 17h
Merged PRs (30d)
49

Description

Is your feature request related to a problem? Please describe.
Game core must be independet with window. If it will be independent its easy to beals windowless game. I.e. game server.
So you can write once use as you want. You dont need to write same logic again. Also with this feature will help in #1485.
If core will be separated it's easy to made concurency collections / pipes in places where window send events in core and core renders to window.

Describe the solution you'd like
Made core independent. Add RunCoreAsync() which will configure and run core without renderers / window. Add RunAsync() which will configure window / rendering and create em after start.

In fact, it would be cool to create a HostBuilder for Stride. #1487

Here are some questions that can aid in the description of the feature request:

What are the usecases?

  • Run raw game login without any rendering. Calculate physics process or game server

What kind of options/settings are expected/wanted?

  • separate loginc and rendering with input system. suggested methods

What would the (pseudo) code look like?

  • idk. there can be large work. First need to define all places where logic and window acting. separate em.

Is the feature affecting behaviour in the editor?

  • No. But game with this can be run in editor directly. Just bind editor scene and run game logic. Editor view will be renderer for us (game window)

Is there a component or datastructure?

  • architecture

what kind of documentation is needed or needs to be updated?

  • write new docs about how to build windowles and run just core

Should there be an example project?

  • one project will be enough. But when networking comes to Stride

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by mapping where core logic, windowing, rendering, and input currently interact, then review the related discussions in #1485 and #1487. Define the scope for RunCoreAsync() and RunAsync(); done should include a windowless core/server path, a separate rendering path, and documentation or an example showing how to build a windowless game.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.