2022-05-16 13:53:20 +00:00
|
|
|
//! Demonstrates how shadow biases affect shadows in a 3d scene.
|
|
|
|
|
2022-08-30 19:52:11 +00:00
|
|
|
use std::f32::consts::PI;
|
|
|
|
|
2021-12-14 03:58:23 +00:00
|
|
|
use bevy::{input::mouse::MouseMotion, prelude::*};
|
2021-07-19 19:20:59 +00:00
|
|
|
|
|
|
|
fn main() {
|
|
|
|
println!(
|
|
|
|
"Controls:
|
|
|
|
WSAD - forward/back/strafe left/right
|
|
|
|
LShift - 'run'
|
|
|
|
E - up
|
|
|
|
Q - down
|
|
|
|
L - switch between directional and point lights
|
|
|
|
1/2 - decrease/increase point light depth bias
|
|
|
|
3/4 - decrease/increase point light normal bias
|
|
|
|
5/6 - decrease/increase direction light depth bias
|
|
|
|
7/8 - decrease/increase direction light normal bias"
|
|
|
|
);
|
|
|
|
App::new()
|
2021-12-14 03:58:23 +00:00
|
|
|
.add_plugins(DefaultPlugins)
|
2021-07-26 23:44:23 +00:00
|
|
|
.add_startup_system(setup)
|
|
|
|
.add_system(adjust_point_light_biases)
|
|
|
|
.add_system(toggle_light)
|
|
|
|
.add_system(adjust_directional_light_biases)
|
|
|
|
.add_system(camera_controller)
|
2021-07-19 19:20:59 +00:00
|
|
|
.run();
|
|
|
|
}
|
|
|
|
|
|
|
|
/// set up a 3D scene to test shadow biases and perspective projections
|
|
|
|
fn setup(
|
|
|
|
mut commands: Commands,
|
|
|
|
mut meshes: ResMut<Assets<Mesh>>,
|
|
|
|
mut materials: ResMut<Assets<StandardMaterial>>,
|
|
|
|
) {
|
|
|
|
let spawn_plane_depth = 500.0f32;
|
|
|
|
let spawn_height = 2.0;
|
|
|
|
let sphere_radius = 0.25;
|
|
|
|
|
|
|
|
let white_handle = materials.add(StandardMaterial {
|
|
|
|
base_color: Color::WHITE,
|
|
|
|
perceptual_roughness: 1.0,
|
2022-03-01 20:52:09 +00:00
|
|
|
..default()
|
2021-07-19 19:20:59 +00:00
|
|
|
});
|
2022-11-14 22:34:27 +00:00
|
|
|
let sphere_handle = meshes.add(
|
|
|
|
Mesh::try_from(shape::Icosphere {
|
|
|
|
radius: sphere_radius,
|
|
|
|
..default()
|
|
|
|
})
|
|
|
|
.unwrap(),
|
|
|
|
);
|
2021-07-19 19:20:59 +00:00
|
|
|
|
|
|
|
println!("Using DirectionalLight");
|
|
|
|
|
Spawn now takes a Bundle (#6054)
# Objective
Now that we can consolidate Bundles and Components under a single insert (thanks to #2975 and #6039), almost 100% of world spawns now look like `world.spawn().insert((Some, Tuple, Here))`. Spawning an entity without any components is an extremely uncommon pattern, so it makes sense to give spawn the "first class" ergonomic api. This consolidated api should be made consistent across all spawn apis (such as World and Commands).
## Solution
All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input:
```rust
// before:
commands
.spawn()
.insert((A, B, C));
world
.spawn()
.insert((A, B, C);
// after
commands.spawn((A, B, C));
world.spawn((A, B, C));
```
All existing instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api. A new `spawn_empty` has been added, replacing the old `spawn` api.
By allowing `world.spawn(some_bundle)` to replace `world.spawn().insert(some_bundle)`, this opened the door to removing the initial entity allocation in the "empty" archetype / table done in `spawn()` (and subsequent move to the actual archetype in `.insert(some_bundle)`).
This improves spawn performance by over 10%:
![image](https://user-images.githubusercontent.com/2694663/191627587-4ab2f949-4ccd-4231-80eb-80dd4d9ad6b9.png)
To take this measurement, I added a new `world_spawn` benchmark.
Unfortunately, optimizing `Commands::spawn` is slightly less trivial, as Commands expose the Entity id of spawned entities prior to actually spawning. Doing the optimization would (naively) require assurances that the `spawn(some_bundle)` command is applied before all other commands involving the entity (which would not necessarily be true, if memory serves). Optimizing `Commands::spawn` this way does feel possible, but it will require careful thought (and maybe some additional checks), which deserves its own PR. For now, it has the same performance characteristics of the current `Commands::spawn_bundle` on main.
**Note that 99% of this PR is simple renames and refactors. The only code that needs careful scrutiny is the new `World::spawn()` impl, which is relatively straightforward, but it has some new unsafe code (which re-uses battle tested BundlerSpawner code path).**
---
## Changelog
- All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input
- All instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api
- World and Commands now have `spawn_empty()`, which is equivalent to the old `spawn()` behavior.
## Migration Guide
```rust
// Old (0.8):
commands
.spawn()
.insert_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
commands.spawn_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
let entity = commands.spawn().id();
// New (0.9)
let entity = commands.spawn_empty().id();
// Old (0.8)
let entity = world.spawn().id();
// New (0.9)
let entity = world.spawn_empty();
```
2022-09-23 19:55:54 +00:00
|
|
|
commands.spawn(PointLightBundle {
|
2021-07-19 19:20:59 +00:00
|
|
|
transform: Transform::from_xyz(5.0, 5.0, 0.0),
|
|
|
|
point_light: PointLight {
|
|
|
|
intensity: 0.0,
|
|
|
|
range: spawn_plane_depth,
|
|
|
|
color: Color::WHITE,
|
|
|
|
shadow_depth_bias: 0.0,
|
|
|
|
shadow_normal_bias: 0.0,
|
2021-11-27 10:12:47 +00:00
|
|
|
shadows_enabled: true,
|
2022-03-01 20:52:09 +00:00
|
|
|
..default()
|
2021-07-19 19:20:59 +00:00
|
|
|
},
|
2022-03-01 20:52:09 +00:00
|
|
|
..default()
|
2021-07-19 19:20:59 +00:00
|
|
|
});
|
|
|
|
|
Spawn now takes a Bundle (#6054)
# Objective
Now that we can consolidate Bundles and Components under a single insert (thanks to #2975 and #6039), almost 100% of world spawns now look like `world.spawn().insert((Some, Tuple, Here))`. Spawning an entity without any components is an extremely uncommon pattern, so it makes sense to give spawn the "first class" ergonomic api. This consolidated api should be made consistent across all spawn apis (such as World and Commands).
## Solution
All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input:
```rust
// before:
commands
.spawn()
.insert((A, B, C));
world
.spawn()
.insert((A, B, C);
// after
commands.spawn((A, B, C));
world.spawn((A, B, C));
```
All existing instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api. A new `spawn_empty` has been added, replacing the old `spawn` api.
By allowing `world.spawn(some_bundle)` to replace `world.spawn().insert(some_bundle)`, this opened the door to removing the initial entity allocation in the "empty" archetype / table done in `spawn()` (and subsequent move to the actual archetype in `.insert(some_bundle)`).
This improves spawn performance by over 10%:
![image](https://user-images.githubusercontent.com/2694663/191627587-4ab2f949-4ccd-4231-80eb-80dd4d9ad6b9.png)
To take this measurement, I added a new `world_spawn` benchmark.
Unfortunately, optimizing `Commands::spawn` is slightly less trivial, as Commands expose the Entity id of spawned entities prior to actually spawning. Doing the optimization would (naively) require assurances that the `spawn(some_bundle)` command is applied before all other commands involving the entity (which would not necessarily be true, if memory serves). Optimizing `Commands::spawn` this way does feel possible, but it will require careful thought (and maybe some additional checks), which deserves its own PR. For now, it has the same performance characteristics of the current `Commands::spawn_bundle` on main.
**Note that 99% of this PR is simple renames and refactors. The only code that needs careful scrutiny is the new `World::spawn()` impl, which is relatively straightforward, but it has some new unsafe code (which re-uses battle tested BundlerSpawner code path).**
---
## Changelog
- All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input
- All instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api
- World and Commands now have `spawn_empty()`, which is equivalent to the old `spawn()` behavior.
## Migration Guide
```rust
// Old (0.8):
commands
.spawn()
.insert_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
commands.spawn_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
let entity = commands.spawn().id();
// New (0.9)
let entity = commands.spawn_empty().id();
// Old (0.8)
let entity = world.spawn().id();
// New (0.9)
let entity = world.spawn_empty();
```
2022-09-23 19:55:54 +00:00
|
|
|
commands.spawn(DirectionalLightBundle {
|
2021-07-19 19:20:59 +00:00
|
|
|
directional_light: DirectionalLight {
|
|
|
|
illuminance: 100000.0,
|
|
|
|
shadow_projection: OrthographicProjection {
|
|
|
|
left: -0.35,
|
|
|
|
right: 500.35,
|
|
|
|
bottom: -0.1,
|
|
|
|
top: 5.0,
|
|
|
|
near: -5.0,
|
|
|
|
far: 5.0,
|
2022-03-01 20:52:09 +00:00
|
|
|
..default()
|
2021-07-19 19:20:59 +00:00
|
|
|
},
|
|
|
|
shadow_depth_bias: 0.0,
|
|
|
|
shadow_normal_bias: 0.0,
|
2021-11-27 10:12:47 +00:00
|
|
|
shadows_enabled: true,
|
2022-03-01 20:52:09 +00:00
|
|
|
..default()
|
2021-07-19 19:20:59 +00:00
|
|
|
},
|
2022-08-30 19:52:11 +00:00
|
|
|
transform: Transform::from_rotation(Quat::from_euler(
|
|
|
|
EulerRot::ZYX,
|
|
|
|
0.0,
|
|
|
|
PI / 2.,
|
|
|
|
-PI / 4.,
|
|
|
|
)),
|
2022-03-01 20:52:09 +00:00
|
|
|
..default()
|
2021-07-19 19:20:59 +00:00
|
|
|
});
|
|
|
|
|
|
|
|
// camera
|
Spawn now takes a Bundle (#6054)
# Objective
Now that we can consolidate Bundles and Components under a single insert (thanks to #2975 and #6039), almost 100% of world spawns now look like `world.spawn().insert((Some, Tuple, Here))`. Spawning an entity without any components is an extremely uncommon pattern, so it makes sense to give spawn the "first class" ergonomic api. This consolidated api should be made consistent across all spawn apis (such as World and Commands).
## Solution
All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input:
```rust
// before:
commands
.spawn()
.insert((A, B, C));
world
.spawn()
.insert((A, B, C);
// after
commands.spawn((A, B, C));
world.spawn((A, B, C));
```
All existing instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api. A new `spawn_empty` has been added, replacing the old `spawn` api.
By allowing `world.spawn(some_bundle)` to replace `world.spawn().insert(some_bundle)`, this opened the door to removing the initial entity allocation in the "empty" archetype / table done in `spawn()` (and subsequent move to the actual archetype in `.insert(some_bundle)`).
This improves spawn performance by over 10%:
![image](https://user-images.githubusercontent.com/2694663/191627587-4ab2f949-4ccd-4231-80eb-80dd4d9ad6b9.png)
To take this measurement, I added a new `world_spawn` benchmark.
Unfortunately, optimizing `Commands::spawn` is slightly less trivial, as Commands expose the Entity id of spawned entities prior to actually spawning. Doing the optimization would (naively) require assurances that the `spawn(some_bundle)` command is applied before all other commands involving the entity (which would not necessarily be true, if memory serves). Optimizing `Commands::spawn` this way does feel possible, but it will require careful thought (and maybe some additional checks), which deserves its own PR. For now, it has the same performance characteristics of the current `Commands::spawn_bundle` on main.
**Note that 99% of this PR is simple renames and refactors. The only code that needs careful scrutiny is the new `World::spawn()` impl, which is relatively straightforward, but it has some new unsafe code (which re-uses battle tested BundlerSpawner code path).**
---
## Changelog
- All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input
- All instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api
- World and Commands now have `spawn_empty()`, which is equivalent to the old `spawn()` behavior.
## Migration Guide
```rust
// Old (0.8):
commands
.spawn()
.insert_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
commands.spawn_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
let entity = commands.spawn().id();
// New (0.9)
let entity = commands.spawn_empty().id();
// Old (0.8)
let entity = world.spawn().id();
// New (0.9)
let entity = world.spawn_empty();
```
2022-09-23 19:55:54 +00:00
|
|
|
commands.spawn((
|
|
|
|
Camera3dBundle {
|
2021-07-19 19:20:59 +00:00
|
|
|
transform: Transform::from_xyz(-1.0, 1.0, 1.0)
|
|
|
|
.looking_at(Vec3::new(-1.0, 1.0, 0.0), Vec3::Y),
|
2022-03-01 20:52:09 +00:00
|
|
|
..default()
|
Spawn now takes a Bundle (#6054)
# Objective
Now that we can consolidate Bundles and Components under a single insert (thanks to #2975 and #6039), almost 100% of world spawns now look like `world.spawn().insert((Some, Tuple, Here))`. Spawning an entity without any components is an extremely uncommon pattern, so it makes sense to give spawn the "first class" ergonomic api. This consolidated api should be made consistent across all spawn apis (such as World and Commands).
## Solution
All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input:
```rust
// before:
commands
.spawn()
.insert((A, B, C));
world
.spawn()
.insert((A, B, C);
// after
commands.spawn((A, B, C));
world.spawn((A, B, C));
```
All existing instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api. A new `spawn_empty` has been added, replacing the old `spawn` api.
By allowing `world.spawn(some_bundle)` to replace `world.spawn().insert(some_bundle)`, this opened the door to removing the initial entity allocation in the "empty" archetype / table done in `spawn()` (and subsequent move to the actual archetype in `.insert(some_bundle)`).
This improves spawn performance by over 10%:
![image](https://user-images.githubusercontent.com/2694663/191627587-4ab2f949-4ccd-4231-80eb-80dd4d9ad6b9.png)
To take this measurement, I added a new `world_spawn` benchmark.
Unfortunately, optimizing `Commands::spawn` is slightly less trivial, as Commands expose the Entity id of spawned entities prior to actually spawning. Doing the optimization would (naively) require assurances that the `spawn(some_bundle)` command is applied before all other commands involving the entity (which would not necessarily be true, if memory serves). Optimizing `Commands::spawn` this way does feel possible, but it will require careful thought (and maybe some additional checks), which deserves its own PR. For now, it has the same performance characteristics of the current `Commands::spawn_bundle` on main.
**Note that 99% of this PR is simple renames and refactors. The only code that needs careful scrutiny is the new `World::spawn()` impl, which is relatively straightforward, but it has some new unsafe code (which re-uses battle tested BundlerSpawner code path).**
---
## Changelog
- All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input
- All instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api
- World and Commands now have `spawn_empty()`, which is equivalent to the old `spawn()` behavior.
## Migration Guide
```rust
// Old (0.8):
commands
.spawn()
.insert_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
commands.spawn_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
let entity = commands.spawn().id();
// New (0.9)
let entity = commands.spawn_empty().id();
// Old (0.8)
let entity = world.spawn().id();
// New (0.9)
let entity = world.spawn_empty();
```
2022-09-23 19:55:54 +00:00
|
|
|
},
|
|
|
|
CameraController::default(),
|
|
|
|
));
|
2021-07-19 19:20:59 +00:00
|
|
|
|
|
|
|
for z_i32 in -spawn_plane_depth as i32..=0 {
|
Spawn now takes a Bundle (#6054)
# Objective
Now that we can consolidate Bundles and Components under a single insert (thanks to #2975 and #6039), almost 100% of world spawns now look like `world.spawn().insert((Some, Tuple, Here))`. Spawning an entity without any components is an extremely uncommon pattern, so it makes sense to give spawn the "first class" ergonomic api. This consolidated api should be made consistent across all spawn apis (such as World and Commands).
## Solution
All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input:
```rust
// before:
commands
.spawn()
.insert((A, B, C));
world
.spawn()
.insert((A, B, C);
// after
commands.spawn((A, B, C));
world.spawn((A, B, C));
```
All existing instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api. A new `spawn_empty` has been added, replacing the old `spawn` api.
By allowing `world.spawn(some_bundle)` to replace `world.spawn().insert(some_bundle)`, this opened the door to removing the initial entity allocation in the "empty" archetype / table done in `spawn()` (and subsequent move to the actual archetype in `.insert(some_bundle)`).
This improves spawn performance by over 10%:
![image](https://user-images.githubusercontent.com/2694663/191627587-4ab2f949-4ccd-4231-80eb-80dd4d9ad6b9.png)
To take this measurement, I added a new `world_spawn` benchmark.
Unfortunately, optimizing `Commands::spawn` is slightly less trivial, as Commands expose the Entity id of spawned entities prior to actually spawning. Doing the optimization would (naively) require assurances that the `spawn(some_bundle)` command is applied before all other commands involving the entity (which would not necessarily be true, if memory serves). Optimizing `Commands::spawn` this way does feel possible, but it will require careful thought (and maybe some additional checks), which deserves its own PR. For now, it has the same performance characteristics of the current `Commands::spawn_bundle` on main.
**Note that 99% of this PR is simple renames and refactors. The only code that needs careful scrutiny is the new `World::spawn()` impl, which is relatively straightforward, but it has some new unsafe code (which re-uses battle tested BundlerSpawner code path).**
---
## Changelog
- All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input
- All instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api
- World and Commands now have `spawn_empty()`, which is equivalent to the old `spawn()` behavior.
## Migration Guide
```rust
// Old (0.8):
commands
.spawn()
.insert_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
commands.spawn_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
let entity = commands.spawn().id();
// New (0.9)
let entity = commands.spawn_empty().id();
// Old (0.8)
let entity = world.spawn().id();
// New (0.9)
let entity = world.spawn_empty();
```
2022-09-23 19:55:54 +00:00
|
|
|
commands.spawn(PbrBundle {
|
2021-07-19 19:20:59 +00:00
|
|
|
mesh: sphere_handle.clone(),
|
|
|
|
material: white_handle.clone(),
|
|
|
|
transform: Transform::from_xyz(0.0, spawn_height, z_i32 as f32),
|
2022-03-01 20:52:09 +00:00
|
|
|
..default()
|
2021-07-19 19:20:59 +00:00
|
|
|
});
|
|
|
|
}
|
|
|
|
|
|
|
|
// ground plane
|
Spawn now takes a Bundle (#6054)
# Objective
Now that we can consolidate Bundles and Components under a single insert (thanks to #2975 and #6039), almost 100% of world spawns now look like `world.spawn().insert((Some, Tuple, Here))`. Spawning an entity without any components is an extremely uncommon pattern, so it makes sense to give spawn the "first class" ergonomic api. This consolidated api should be made consistent across all spawn apis (such as World and Commands).
## Solution
All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input:
```rust
// before:
commands
.spawn()
.insert((A, B, C));
world
.spawn()
.insert((A, B, C);
// after
commands.spawn((A, B, C));
world.spawn((A, B, C));
```
All existing instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api. A new `spawn_empty` has been added, replacing the old `spawn` api.
By allowing `world.spawn(some_bundle)` to replace `world.spawn().insert(some_bundle)`, this opened the door to removing the initial entity allocation in the "empty" archetype / table done in `spawn()` (and subsequent move to the actual archetype in `.insert(some_bundle)`).
This improves spawn performance by over 10%:
![image](https://user-images.githubusercontent.com/2694663/191627587-4ab2f949-4ccd-4231-80eb-80dd4d9ad6b9.png)
To take this measurement, I added a new `world_spawn` benchmark.
Unfortunately, optimizing `Commands::spawn` is slightly less trivial, as Commands expose the Entity id of spawned entities prior to actually spawning. Doing the optimization would (naively) require assurances that the `spawn(some_bundle)` command is applied before all other commands involving the entity (which would not necessarily be true, if memory serves). Optimizing `Commands::spawn` this way does feel possible, but it will require careful thought (and maybe some additional checks), which deserves its own PR. For now, it has the same performance characteristics of the current `Commands::spawn_bundle` on main.
**Note that 99% of this PR is simple renames and refactors. The only code that needs careful scrutiny is the new `World::spawn()` impl, which is relatively straightforward, but it has some new unsafe code (which re-uses battle tested BundlerSpawner code path).**
---
## Changelog
- All `spawn` apis (`World::spawn`, `Commands:;spawn`, `ChildBuilder::spawn`, and `WorldChildBuilder::spawn`) now accept a bundle as input
- All instances of `spawn_bundle` have been deprecated in favor of the new `spawn` api
- World and Commands now have `spawn_empty()`, which is equivalent to the old `spawn()` behavior.
## Migration Guide
```rust
// Old (0.8):
commands
.spawn()
.insert_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
commands.spawn_bundle((A, B, C));
// New (0.9)
commands.spawn((A, B, C));
// Old (0.8):
let entity = commands.spawn().id();
// New (0.9)
let entity = commands.spawn_empty().id();
// Old (0.8)
let entity = world.spawn().id();
// New (0.9)
let entity = world.spawn_empty();
```
2022-09-23 19:55:54 +00:00
|
|
|
commands.spawn(PbrBundle {
|
2021-07-19 19:20:59 +00:00
|
|
|
mesh: meshes.add(Mesh::from(shape::Plane {
|
|
|
|
size: 2.0 * spawn_plane_depth,
|
|
|
|
})),
|
2021-07-26 23:44:23 +00:00
|
|
|
material: white_handle,
|
2022-03-01 20:52:09 +00:00
|
|
|
..default()
|
2021-07-19 19:20:59 +00:00
|
|
|
});
|
|
|
|
}
|
|
|
|
|
|
|
|
fn toggle_light(
|
|
|
|
input: Res<Input<KeyCode>>,
|
|
|
|
mut point_lights: Query<&mut PointLight>,
|
|
|
|
mut directional_lights: Query<&mut DirectionalLight>,
|
|
|
|
) {
|
|
|
|
if input.just_pressed(KeyCode::L) {
|
2022-07-11 15:28:50 +00:00
|
|
|
for mut light in &mut point_lights {
|
2021-07-19 19:20:59 +00:00
|
|
|
light.intensity = if light.intensity == 0.0 {
|
|
|
|
println!("Using PointLight");
|
|
|
|
100000000.0
|
|
|
|
} else {
|
|
|
|
0.0
|
|
|
|
};
|
|
|
|
}
|
2022-07-11 15:28:50 +00:00
|
|
|
for mut light in &mut directional_lights {
|
2021-07-19 19:20:59 +00:00
|
|
|
light.illuminance = if light.illuminance == 0.0 {
|
|
|
|
println!("Using DirectionalLight");
|
|
|
|
100000.0
|
|
|
|
} else {
|
|
|
|
0.0
|
|
|
|
};
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
fn adjust_point_light_biases(input: Res<Input<KeyCode>>, mut query: Query<&mut PointLight>) {
|
|
|
|
let depth_bias_step_size = 0.01;
|
|
|
|
let normal_bias_step_size = 0.1;
|
2022-07-11 15:28:50 +00:00
|
|
|
for mut light in &mut query {
|
2021-07-19 19:20:59 +00:00
|
|
|
if input.just_pressed(KeyCode::Key1) {
|
|
|
|
light.shadow_depth_bias -= depth_bias_step_size;
|
|
|
|
println!("PointLight shadow_depth_bias: {}", light.shadow_depth_bias);
|
|
|
|
}
|
|
|
|
if input.just_pressed(KeyCode::Key2) {
|
|
|
|
light.shadow_depth_bias += depth_bias_step_size;
|
|
|
|
println!("PointLight shadow_depth_bias: {}", light.shadow_depth_bias);
|
|
|
|
}
|
|
|
|
if input.just_pressed(KeyCode::Key3) {
|
|
|
|
light.shadow_normal_bias -= normal_bias_step_size;
|
|
|
|
println!(
|
|
|
|
"PointLight shadow_normal_bias: {}",
|
|
|
|
light.shadow_normal_bias
|
|
|
|
);
|
|
|
|
}
|
|
|
|
if input.just_pressed(KeyCode::Key4) {
|
|
|
|
light.shadow_normal_bias += normal_bias_step_size;
|
|
|
|
println!(
|
|
|
|
"PointLight shadow_normal_bias: {}",
|
|
|
|
light.shadow_normal_bias
|
|
|
|
);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
fn adjust_directional_light_biases(
|
|
|
|
input: Res<Input<KeyCode>>,
|
|
|
|
mut query: Query<&mut DirectionalLight>,
|
|
|
|
) {
|
|
|
|
let depth_bias_step_size = 0.01;
|
|
|
|
let normal_bias_step_size = 0.1;
|
2022-07-11 15:28:50 +00:00
|
|
|
for mut light in &mut query {
|
2021-07-19 19:20:59 +00:00
|
|
|
if input.just_pressed(KeyCode::Key5) {
|
|
|
|
light.shadow_depth_bias -= depth_bias_step_size;
|
|
|
|
println!(
|
|
|
|
"DirectionalLight shadow_depth_bias: {}",
|
|
|
|
light.shadow_depth_bias
|
|
|
|
);
|
|
|
|
}
|
|
|
|
if input.just_pressed(KeyCode::Key6) {
|
|
|
|
light.shadow_depth_bias += depth_bias_step_size;
|
|
|
|
println!(
|
|
|
|
"DirectionalLight shadow_depth_bias: {}",
|
|
|
|
light.shadow_depth_bias
|
|
|
|
);
|
|
|
|
}
|
|
|
|
if input.just_pressed(KeyCode::Key7) {
|
|
|
|
light.shadow_normal_bias -= normal_bias_step_size;
|
|
|
|
println!(
|
|
|
|
"DirectionalLight shadow_normal_bias: {}",
|
|
|
|
light.shadow_normal_bias
|
|
|
|
);
|
|
|
|
}
|
|
|
|
if input.just_pressed(KeyCode::Key8) {
|
|
|
|
light.shadow_normal_bias += normal_bias_step_size;
|
|
|
|
println!(
|
|
|
|
"DirectionalLight shadow_normal_bias: {}",
|
|
|
|
light.shadow_normal_bias
|
|
|
|
);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-11-22 23:16:36 +00:00
|
|
|
#[derive(Component)]
|
2021-07-19 19:20:59 +00:00
|
|
|
struct CameraController {
|
|
|
|
pub enabled: bool,
|
|
|
|
pub sensitivity: f32,
|
|
|
|
pub key_forward: KeyCode,
|
|
|
|
pub key_back: KeyCode,
|
|
|
|
pub key_left: KeyCode,
|
|
|
|
pub key_right: KeyCode,
|
|
|
|
pub key_up: KeyCode,
|
|
|
|
pub key_down: KeyCode,
|
|
|
|
pub key_run: KeyCode,
|
|
|
|
pub walk_speed: f32,
|
|
|
|
pub run_speed: f32,
|
|
|
|
pub friction: f32,
|
|
|
|
pub pitch: f32,
|
|
|
|
pub yaw: f32,
|
|
|
|
pub velocity: Vec3,
|
|
|
|
}
|
|
|
|
|
|
|
|
impl Default for CameraController {
|
|
|
|
fn default() -> Self {
|
|
|
|
Self {
|
|
|
|
enabled: true,
|
|
|
|
sensitivity: 0.5,
|
|
|
|
key_forward: KeyCode::W,
|
|
|
|
key_back: KeyCode::S,
|
|
|
|
key_left: KeyCode::A,
|
|
|
|
key_right: KeyCode::D,
|
|
|
|
key_up: KeyCode::E,
|
|
|
|
key_down: KeyCode::Q,
|
|
|
|
key_run: KeyCode::LShift,
|
|
|
|
walk_speed: 10.0,
|
|
|
|
run_speed: 30.0,
|
|
|
|
friction: 0.5,
|
|
|
|
pitch: 0.0,
|
|
|
|
yaw: 0.0,
|
|
|
|
velocity: Vec3::ZERO,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
fn camera_controller(
|
|
|
|
time: Res<Time>,
|
|
|
|
mut mouse_events: EventReader<MouseMotion>,
|
|
|
|
key_input: Res<Input<KeyCode>>,
|
|
|
|
mut query: Query<(&mut Transform, &mut CameraController), With<Camera>>,
|
|
|
|
) {
|
|
|
|
let dt = time.delta_seconds();
|
|
|
|
|
|
|
|
// Handle mouse input
|
|
|
|
let mut mouse_delta = Vec2::ZERO;
|
|
|
|
for mouse_event in mouse_events.iter() {
|
|
|
|
mouse_delta += mouse_event.delta;
|
|
|
|
}
|
|
|
|
|
2022-07-11 15:28:50 +00:00
|
|
|
for (mut transform, mut options) in &mut query {
|
2021-07-19 19:20:59 +00:00
|
|
|
if !options.enabled {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Handle key input
|
|
|
|
let mut axis_input = Vec3::ZERO;
|
|
|
|
if key_input.pressed(options.key_forward) {
|
|
|
|
axis_input.z += 1.0;
|
|
|
|
}
|
|
|
|
if key_input.pressed(options.key_back) {
|
|
|
|
axis_input.z -= 1.0;
|
|
|
|
}
|
|
|
|
if key_input.pressed(options.key_right) {
|
|
|
|
axis_input.x += 1.0;
|
|
|
|
}
|
|
|
|
if key_input.pressed(options.key_left) {
|
|
|
|
axis_input.x -= 1.0;
|
|
|
|
}
|
|
|
|
if key_input.pressed(options.key_up) {
|
|
|
|
axis_input.y += 1.0;
|
|
|
|
}
|
|
|
|
if key_input.pressed(options.key_down) {
|
|
|
|
axis_input.y -= 1.0;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Apply movement update
|
|
|
|
if axis_input != Vec3::ZERO {
|
|
|
|
let max_speed = if key_input.pressed(options.key_run) {
|
|
|
|
options.run_speed
|
|
|
|
} else {
|
|
|
|
options.walk_speed
|
|
|
|
};
|
|
|
|
options.velocity = axis_input.normalize() * max_speed;
|
|
|
|
} else {
|
|
|
|
let friction = options.friction.clamp(0.0, 1.0);
|
|
|
|
options.velocity *= 1.0 - friction;
|
|
|
|
if options.velocity.length_squared() < 1e-6 {
|
|
|
|
options.velocity = Vec3::ZERO;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
let forward = transform.forward();
|
|
|
|
let right = transform.right();
|
|
|
|
transform.translation += options.velocity.x * dt * right
|
|
|
|
+ options.velocity.y * dt * Vec3::Y
|
|
|
|
+ options.velocity.z * dt * forward;
|
|
|
|
|
|
|
|
if mouse_delta != Vec2::ZERO {
|
|
|
|
// Apply look update
|
2022-08-30 19:52:11 +00:00
|
|
|
options.pitch = (options.pitch - mouse_delta.y * 0.5 * options.sensitivity * dt)
|
|
|
|
.clamp(-PI / 2., PI / 2.);
|
|
|
|
options.yaw -= mouse_delta.x * options.sensitivity * dt;
|
|
|
|
transform.rotation = Quat::from_euler(EulerRot::ZYX, 0.0, options.yaw, options.pitch);
|
2021-07-19 19:20:59 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|