MevLyshkin Leinnan

## main.rs
/// minimal example of adding a custom render pipeline in bevy 0.11.
///
/// When this example runs, you should only see a blue screen. There are no
/// vertex buffers, or anything else in this example.  Effectively it is
/// shader-toy written in bevy.
///
/// This revision adds a post-processing node to the RenderGraph to
/// execute the shader.  Thanks to @Jasmine on the bevy discord for
/// suggesting I take a second look at the bevy post-processing example
///

## custom_game_engines_small_study.md

      
              1 file
            
          
              60 forks
            
          
              142 comments
            
          
              1309 stars
            
          
                raysan5
                / custom_game_engines_small_study.md
            
            
              Last active
              May 28, 2024 15:33
            
              
                A small state-of-the-art study on custom engines
              
          
    CUSTOM GAME ENGINES: A Small Study


A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) because d

  
## index.html
<!DOCTYPE html>
<html prefix="og: http://ogp.me/ns#">

<head>
  <!-- content-type, which overrides http equivalent header. Because of charset, this meta should be set at first. -->
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
  <!--  Overrides http equivalent header. This tells IE to use the most updated engine.  -->
  <meta http-equiv="X-UA-Compatible" content="IE=Edge">
  <!--  Tells crawlers how to crawl this page, and the role of this page. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta -->
  <meta name="robots" content="index, follow">

## fill_tileset_scene.gd

tool

extends EditorScript

# ------------------HOW TO USE-------------------------
# CONFIGURE CONSTANTS TO AUTOGENERATE THE TILESET SCENE
# -----------------------------------------------------

# PATH TO TEXTURE FILE
	/// minimal example of adding a custom render pipeline in bevy 0.11.
	///
	/// When this example runs, you should only see a blue screen. There are no
	/// vertex buffers, or anything else in this example. Effectively it is
	/// shader-toy written in bevy.
	///
	/// This revision adds a post-processing node to the RenderGraph to
	/// execute the shader. Thanks to @Jasmine on the bevy discord for
	/// suggesting I take a second look at the bevy post-processing example
	///
	<!DOCTYPE html>
	<html prefix="og: http://ogp.me/ns#">

	<head>
	<!-- content-type, which overrides http equivalent header. Because of charset, this meta should be set at first. -->
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
	<!-- Overrides http equivalent header. This tells IE to use the most updated engine. -->
	<meta http-equiv="X-UA-Compatible" content="IE=Edge">
	<!-- Tells crawlers how to crawl this page, and the role of this page. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta -->
	<meta name="robots" content="index, follow">

	tool

	extends EditorScript

	# ------------------HOW TO USE-------------------------
	# CONFIGURE CONSTANTS TO AUTOGENERATE THE TILESET SCENE
	# -----------------------------------------------------

	# PATH TO TEXTURE FILE