-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added documents for migration to URP/HDRP, and other improvements. #188
Added documents for migration to URP/HDRP, and other improvements. #188
Conversation
Bob-Eric
commented
Jan 30, 2025
•
edited
Loading
edited
- Rewrote the Depth Camera Shader by Shader Graph to better support URP/HDRP. And added documents for migration. However, versions prior to Unity 2022 with built-in render pipeline need to use the legacy depth material.
- The depth value of the depth camera means the perpendicular distance from the camera plane, not a straight line from the object to the camera lens. So it is corrected.
- Changed asmdef to exclude Editor scripts when building.
- Loaded the shader via a material reference and create the corresponding material. This means there is no longer need to add custom shaders to the Always Included Shaders when building.
- Merged branch beta/v2.x.x. It is now possible to encode colour images in RGB8, depth images in 32FC1 and 16UC1 formats.
- Added raycast layermask option for raycast-based lidar sensors.
- Fixed a bug in TF sensor. Added TF and Clock example scene.
- Updated to Unity 2023.2.
* Switch compressed image to raw image * Remove 'compressed' from camera topic name in camera prefab
…cs-Japan#182) * Update to test unity2020.3.x to 2022.3.x * Delete unnecessary files * Fix to delete unnecessary file copy
…pth camera support UPR/HDRP; load the shader via a material reference and create the corresponding material; rename the Color2Depth shader to DepthBufferLidar shader and use it for DepthBufferLidar; Change asmdef to exclude Editor scripts when packaging
… null references in RGBDCamera_ros prefab; adjusted texture format in RGBCameraSensor; updated ImageMsgSerializer to support raw texture data serialization .
…scripts; added GPU read error logging to DepthCameraSensor; updated RaycastCommand API in IUpdateRaycastCommandsJob; added UnitySensorsROS to Some sensor prefabs; added Raycast LayerMask in RaycastLiDARSensor.
…laces the PointUtilities class and updates the associated prefabs; remove redundant Usings
…chCount in Job to improve performance; added logging of GPU read errors; removed unsafe code in PointCloud2MsgSerializer.
…re data into a single array; disabled HUD display for ROS TCP Connector to avoid lag caused by frequent GC at high frame rates; removed redundant AlwaysIncludedShaders
…mera frame_id format; fixed TFMessageMsgSerializer multiple TransformStampedMsg references to the same HeaderMsg
@Bob-Eric I will check your update step by step. |
Check list
|
I found those problems. Environment
Depth Buffer Lidar has incorrect images.As following, this PR still has a problem on Depth Buffer Lidars. Depth Camera Color mistakeI found that with Legacy Shader, the blue and red colors are replaced as showing on following. @Bob-Eric |
@Bob-Eric |
If you want to use URP or HDRP, 2022, 2023 are okay, but if you want to use built in pileline in unity 2022, you need to use the legacy depth material. |
Depth Buffer Lidar has incorrect imagesI didn't change the logic of the Depth Buffer lidar shader, so it should behave the same as before! Also, I think it's possible to get the coordinates of the pixel point in the camera system directly in the ShaderGraph via the Depth Camera Color mistakeAs for the Depth Camera Color mistake, I think there was an error in the ROS message serialization part, I published the red point cloud directly and it showed blue in rviz... The easiest way to do this is to flip the R and B channels in Assets/UnitySensors/Runtime/Scripts/Sensors/Camera/RGBDCamera/ITextureToColorPointsJob.cs |
@Bob-Eric Depth Buffer Lidar has incorrect imagesI see the modification is not changed, and this PR should be accepted, I think. But we still need to fix this bending problem in other development. Depth Camera Color mistakeI understand that the ROS software has mistake... So, I will accept all of this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part, I will create Issue and we should deal with those FIXME topics.
#166
5bd4a0d
into
Field-Robotics-Japan:master
Update PR #188 example codes