MSDK 5.3 and Mini 3 Pro Obstacle Data Limitation
已完成
Any news about this incomplete MSDK 5.3 implementation?
DJI Mini have a perfect size for small places indoor missions.
Thank you
-
Testing the 5.6.0 Sample, I´m getting this warnings in this place in PerceptionFragment.kt (maybe could be something on the sample not SDK):
Lambda argument should be moved out of parentheses.
Tried apply the correction with no luck too.
private fun observerPerceptionInfo() {
perceptionVM.perceptionInfo.observe(viewLifecycleOwner, {
perceptionInfo = it
updatePerceptionInfo()
changeObstacleAvoidanceEnableSwitch()
changeOtherEnableSwitch(it)
})
perceptionVM.obstacleData.observe(viewLifecycleOwner, {
obstacleData = it
updatePerceptionInfo()
})
perceptionVM.obstacleDataForRadar.observe(viewLifecycleOwner, {
radarObstacleData = it
updatePerceptionInfo()
})
perceptionVM.radarInformation.observe(viewLifecycleOwner, {
radarInformation = it
changeObstacleAvoidanceEnableSwitch()
updatePerceptionInfo()
})
perceptionVM.radarConnect.observe(viewLifecycleOwner, {
isRadarConnected = it
if (it) {
rl_radar_obstacle_avoidance_switch.show()
} else {
rl_radar_obstacle_avoidance_switch.hide()
}
}) -
I apologize for any confusion caused by my previous response. Regrettably, the issue regarding the mini 3's inability to acquire obstacle avoidance information remains unresolved. At present, there is no specific timeline for when this matter will be addressed. It may be necessary to consider it as a potential feature requirement. We kindly request that you provide us with your feedback in the following format: - [Demand Scenario]: Could you please provide us with an analysis of the original demand scenario? It would be helpful to understand who the end user is and what the scenario requirements are. - [Scenario value]: We would appreciate it if you could describe the actual value, social value, and economic value for users. - [Priority]: It would be great if you could explain the importance of the requirement (high, medium, low). If it is high, please let us know why it is important. Additionally, if the degree of urgency (high, medium, low) is high, please explain why it is urgent. -
There is no logic have Virtual Sticks without Obstacle Data. As you move you have to know when to stop. This should be reason enough to get this implemented. Any virtual stick application potentially will lead to a crash if have any obstacle. At least 3 same requests from developers months ago.
This should not be addressed as a new feature, but a bug, because will lead to a crash.
-
I would like to inform you that I have already reported this issue to our Research and Development team as a bug. However, we are currently unable to determine the fixed time for this issue. Furthermore, I regret to inform you that the mini 4 device does not currently support the SDK. Nevertheless, I would like to assure you that we have plans to adapt the mini4 device to support the SDK in the future.
请先登录再写评论。
评论
15 条评论