I tested Tango SDK Ikariotikos Version on Asus Zen Fone AR.
AreaLearning After running the New Area Description in the Scene, the ADF was saved and switched back to AreaLearning Scene.
However, when you run the New Area Description again, you will get the error message
"Failed to connect to Tango Service."
There is no problem with Phab2 pro.
Do you know this problem?
Please let me know how to fix it.
Related
I'm trying to see why our DJI-enabled app isn't working correctly with the Mavic Air 2 on iOS or Android. Here I'm debugging with iOS but I've seen the same failures when briefly testing on our Android app.
When calling setMode:completion: on the single camera belonging to the Mavic Air 2, I consistently get "Current product does not support this feature.(code:-1013)"
isMediaDownloadModeSupported returns true for the camera, and yet I can't set the camera mode to media download mode at all (or any other mode).
I've found that setFlatMode:completion: seems to work ok to set photo and video modes as a sort of alternative, however this is only for photo/video modes, and won't help me with downloading media from the SD card. (right?)
Any help out there?
From my DJI Developer Support ticket for the same issue:
For the Mavic Air 2 drone, should use the setFlatMode to switch the photo, video mode, and use the enterPlayback, exitPlayback to enter/ exit the download mode.
Has anyone used PanoramaMissionOperator on the mobile SDK for android or iOS? I can't see any example code online. Also it seems to be unclear which products support the use of PanoramaMissionOperator from the documentation. When I attempt to get the state of the PanoramaMissionOperator with a Mavic Pro and Phantom 4 Pro, I get a PanoramaMissionState of DISCONNECTED.
I know the DJI documentation describes how to achieve the same with a Waypoint Mission but some drones miss photos during waypoint missions.
PanoramaMissionOperator operator = MissionControl.getInstance().getPanoramaMissionOperator();
PanoramaMissionState missionState = operator.getCurrentState();
The PanoramaMissions are only supported for OSMO devices, source:
https://developer.dji.com/mobile-sdk/documentation/introduction/component-guide-missions.html -> scroll to the bottom.
Unfortunately the SDK documentation doesn't mention this and the only hint I got there is the description of the DISCONNECTED state: "The connection between the mobile device and Osmo is broken."
https://developer.dji.com/api-reference/android-api/Components/Missions/DJIPanoramaMissionState.html#djipanoramamissionstate_disconnected_inline
I am evaluating Unity3d 2017.4.2f2 with Vuforia and Xcode 9.3 for an AR App and have the problem, that the camera background works in the simulator but not on the iPad pro with iOS 11.3,1.
It seems to be a known problem and I checked nearly every solution including using XCode9.2 and copying the device config, deleting Metal from the Vuforia Settings, creating new AR Cameras, even the latest Unity3D beta and whatnot. The background does not show up and I get the following error:
2018-05-03 14:53:33.396112+0200 ProductName[2340:1694266] ERROR/AR(2340) 2018-05-04 14:53:33: CameraDevice::getCameraCalibration(): Failed to get camera calibration because the camera is not initialized.
and
cameraDeviceStartCamera
2018-05-03 14:53:33.460389+0200 ProductName[2340:1694266] ERROR/AR(2340) 2018-05-04 14:53:33: VideoBackgroundConfig with screen size of zero received, skipping config step
If there is anything else I can do or that points me into the right direction is appreciated. many thanks in advance
Just to be sure check if you did all of this:
In player settings enable Vuforia's support
Go to player settings >> Other Settings and check Camera Usage Description field
Then you can try one of the following suggestions:
change the Target resolution to native (default device resolution)
set the graphics to be OpenGLES2.0 instead of automatic
If this doesn't work you can also try to delete the meta data of the camera controller script.
Removing Unity3D completely and reinstalling the latest Unity3D version and the VuforiaSupportInstaller-Mac-7-1-35 solved it. Both accessible via the Vuforia Download page
After a new tango core update (version 1.48:2016.....:unstable) that my Lenovo Phab2Pro auto updated today, the Tango3DR_textureMeshFromDataset function is not working anymore, with an error code of -3 (It worked fine with the last tango core version)
In the logcat output I get the following message:
mesh_painter_adapter.cc:85 Source camera not available; source_camera_=16 available_cameras_mask=4096
Anyone know how to fix this? Do I need to change some permissions or something?
So the solution was to change the config_dataset_recording_mode.
Previously, setting the mode to TANGO_RECORDING_MODE_SCENE_RECONSTRUCTION
was sufficient to do reconstruction with textured meshes. With the caporales update, it seems that it is required to set the mode to TANGO_RECORDING_MODE_ALL for getting the textured 3d reconstruction to work.
I am facing an interface freeze issue with Flash Projector running a flex state based application. A Flash Projector exe was generated from a standalone flash player ver 10.2. The target machine on which the problem occuresd has 10.3.
Basically "screen freeze" means that the user interface is running as usual on Flash Player, but it's not responding to any user input (like button presses). But if we alt-tab to another application, the state changes in the Flash player. There is display with buttons on the screen, but touching the buttons or doing anything else - it did not respond. Rebooting the computer fixes the problem.
Can you suggest why this is happening? Is there any known bug in Flash Player.
The problem is this is being hard to reproduce on the developer workstation as it doesn't happen always. But it happens quite often on the target machine running an Intel Atom N270. What debugging steps can you suggest?
Problem : http://www.youtube.com/watch?v=z25oV9QWRyk
Have you tried publishing the projector in 10.1 or a version of Flash newer than 10.2? If you are able to publish it as a SWF first, you can use the stand-alone projector exe (downloadable here) to load and create a projector from it.
According to this Adobe bug issue (registration required), version 10.1 was supposed to have resolved this, but it sounds like it may have reappeared in 10.2.