bevy/.gitignore

/target
crates/*/target
**/*.rs.bk
Cargo.lock
.cargo/config
.cargo/config.toml
/.idea
/.vscode
/benches/target
dxcompiler.dll
dxil.dll

# Generated by "examples/scene/scene.rs"
assets/scenes/load_scene_example-new.scn.ron
initial commit 2019-11-12 19:36:02 -08:00			`/target`
Add target directory for sub-crates to gitignore (#372) 2020-08-27 15:26:00 -04:00			`crates/*/target`
initial commit 2019-11-12 19:36:02 -08:00			`*/.rs.bk`
Expand README 2020-01-21 03:11:38 -08:00			`Cargo.lock`
Ignore CLion/intellij project files 2020-08-11 20:41:37 -07:00			`.cargo/config`
add .cargo/config.toml to .gitignore 2020-12-12 17:17:35 -08:00			`.cargo/config.toml`
Add .vscode to gitignore file (#347) 2020-08-26 00:48:21 +01:00			`/.idea`
Add target directory for sub-crates to gitignore (#372) 2020-08-27 15:26:00 -04:00			`/.vscode`
add .cargo/config.toml to .gitignore 2020-12-12 17:17:35 -08:00			`/benches/target`
Wgpu 0.15 (#7356) # Objective Update Bevy to wgpu 0.15. ## Changelog - Update to wgpu 0.15, wgpu-hal 0.15.1, and naga 0.11 - Users can now use the [DirectX Shader Compiler](https://github.com/microsoft/DirectXShaderCompiler) (DXC) on Windows with DX12 for faster shader compilation and ShaderModel 6.0+ support (requires `dxcompiler.dll` and `dxil.dll`, which are included in DXC downloads from [here](https://github.com/microsoft/DirectXShaderCompiler/releases/latest)) ## Migration Guide ### WGSL Top-Level `let` is now `const` All top level constants are now declared with `const`, catching up with the wgsl spec. `let` is no longer allowed at the global scope, only within functions. ```diff -let SOME_CONSTANT = 12.0; +const SOME_CONSTANT = 12.0; ``` #### `TextureDescriptor` and `SurfaceConfiguration` now requires a `view_formats` field The new `view_formats` field in the `TextureDescriptor` is used to specify a list of formats the texture can be re-interpreted to in a texture view. Currently only changing srgb-ness is allowed (ex. `Rgba8Unorm` <=> `Rgba8UnormSrgb`). You should set `view_formats` to `&[]` (empty) unless you have a specific reason not to. #### The DirectX Shader Compiler (DXC) is now supported on DX12 DXC is now the default shader compiler when using the DX12 backend. DXC is Microsoft's replacement for their legacy FXC compiler, and is faster, less buggy, and allows for modern shader features to be used (ShaderModel 6.0+). DXC requires `dxcompiler.dll` and `dxil.dll` to be available, otherwise it will log a warning and fall back to FXC. You can get `dxcompiler.dll` and `dxil.dll` by downloading the latest release from [Microsoft's DirectXShaderCompiler github repo](https://github.com/microsoft/DirectXShaderCompiler/releases/latest) and copying them into your project's root directory. These must be included when you distribute your Bevy game/app/etc if you plan on supporting the DX12 backend and are using DXC. `WgpuSettings` now has a `dx12_shader_compiler` field which can be used to choose between either FXC or DXC (if you pass None for the paths for DXC, it will check for the .dlls in the working directory). 2023-01-29 20:27:30 +00:00			`dxcompiler.dll`
			`dxil.dll`
Add writing of scene data to Scene example (#5949) # Objective Alice says to make this PR: https://discord.com/channels/691052431525675048/745805740274614303/1018554340841107477 - The "scene" example in the examples folder has a TODO comment about writing the serialized data to a file. This PR implements that. ## Solution The `AssetIo` trait in the `AssetServer` only supports reading data, not writing it. So, I used `std::io::File` for the implementation. This way, every time you run the example, it will mutate the file in-place. I had thought about adding a UUID string to the example Component, so that every time you run the example, the file will be guaranteed to change (currently, it just writes the same numbers over and over). However, I didn't bother because it was beyond the scope of the TODO comment. One thing to note is that the logic for serializing the scene into RON data has changed since the existing RON file was created, and so even though the data is the same, it's rendered in a different order for whatever reason. I left the changed output to the example file, because it's presumably trivial. I can remove it and force-push if you don't want that included in here. 2022-09-11 20:18:57 +00:00
			`# Generated by "examples/scene/scene.rs"`
			`assets/scenes/load_scene_example-new.scn.ron`