You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Migration.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ release will remove the deprecated code.
74
74
*Note*: Calling instead `Camera::Update` for each camera is a waste of CPU resources.
75
75
+ It is invalid to modify the scene between `Scene::PreRender` and `Scene::PostRender` (e.g. add/remove objects, lights, etc)
76
76
+ Added `Scene::SetCameraPassCountPerGpuFlush`. Setting this value to 0 forces legacy behavior which eases porting.
77
-
+ Systems that rely on Graphics components like particle FXs and postprocessing are explicitly affected by Scene's Pre/PostRender. Once `Scene::PostRender` is called, the particle FXs' simulation is moved forward, as well as time values sent to postprocessing shaders. In previous ign-rendering versions each `Camera::Render` call would move the particle simulation forward, which could cause subtle bugs or inconsistencies when Cameras were rendering the same frame from different angles. Setting SetCameraPassCountPerGpuFlush to 0 will also cause these subtle bugs to reappear.
77
+
+ Systems that rely on Graphics components like particle FXs and postprocessing are explicitly affected by Scene's Pre/PostRender. Once `Scene::PostRender` is called, the particle FXs' simulation is moved forward, as well as time values sent to postprocessing shaders. In previous gz-rendering versions each `Camera::Render` call would move the particle simulation forward, which could cause subtle bugs or inconsistencies when Cameras were rendering the same frame from different angles. Setting SetCameraPassCountPerGpuFlush to 0 will also cause these subtle bugs to reappear.
78
78
79
79
1. **Visual.hh** and **Node.hh**
80
80
+ `*UserData` methods and the `Variant` type alias have been moved from the `Visual` class to the `Node` class.
on how to build the documentation files using Doxygen.
57
57
58
58
You can also take a look at the sample applications in the `examples` folder.
59
59
60
60
# Folder Structure
61
61
62
-
*`include/ignition/rendering`: Contains all the public header files which will be installed
62
+
*`include/gz/rendering`: Contains all the public header files which will be installed
63
63
64
64
*`src`: Contains all the C++ source code which are not installed.
65
65
66
66
*`test`: All integration, performance and regression tests go here, under their
67
67
specific folders.
68
68
69
-
*`examples`: Sample programs to demonstrate different features of ign-rendering
69
+
*`examples`: Sample programs to demonstrate different features of gz-rendering
70
70
71
71
*`doc`: Files used by Doxygen when generating documentation.
72
72
@@ -95,4 +95,3 @@ This library uses [Semantic Versioning](https://semver.org/). Additionally, this
95
95
# License
96
96
97
97
This library is licensed under [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0). See also the [LICENSE](https://github.com/gazebosim/gz-rendering/blob/main/LICENSE) file.
0 commit comments