Matterport SDK: Quest for SDK pose rosetta-stone?18822
Pages:
1
|
DouglasRhiner private msg quote post Address this user | |
| I'm wondering of anyone can give me a hint to how to map the date/parameters returned by: mpSdk.Camera.pose.subscribe to the various methods like: mpSdk.Camera.pan({ x: pose.param(?), z: pose.param(?) }) or mpSdk.Camera.setRotation({ x: pose.param(?), y: pose.param(?) }) Trying to programmatically manipulate the Camera view in Dollhouse and FloorPlan mode. I can't seem to get this right.... |
||
| Post 1 • IP flag post | ||
 WGAN ForumFounder & WGAN-TV Podcast Host Atlanta, Georgia |
DanSmigrod private msg quote post Address this user | |
| @DouglasRhiner Is this Matterport SDK documentation regardin pan helpful? Dan |
||
| Post 2 • IP flag post | ||
|
WGAN Forum Founder & WGAN-TV Podcast Host Atlanta, Georgia |
DanSmigrod private msg quote post Address this user | |
| @DouglasRhiner Also: 1. Please see this additional Matterport link 2. If you solve the puzzle, can you let us know how? 3. If you still need help, this may be an option: developer@matterport.com (and, please share Matterport's reply) Best, Dan P.S. I am stepping away from my computer for a while. If you reply to me, I may be slow to read/reply. |
||
| Post 3 • IP flag post | ||
|
|
DouglasRhiner private msg quote post Address this user | |
| Dan, I've been referencing the SDK docks heavily but I can't seem to get it right. So lets say a call to mpSdk.Camera.pose.subscribe returns... mode : "mode.transitioning" position : {x: 8.062565346450599, y: 1.5346455992403065, z: 10.123346514105743} projection : Float32Array(16) [0.6127381920814514, 0, 0, 0, 0, 1.3018981218338013, 0, 0, 0, 0, -0.9990093111991882, -0.2008531242609024, 0, 0, -0.9989420175552368, 0.0010580000234767795, buffer: ArrayBuffer(64), byteLength: 64, byteOffset: 0, length: 16, Symbol(Symbol.toStringTag): 'Float32Array'] rotation : {x: -0.38088000000000105, y: 89.99999999999999} sweep : "38402824149b4cc9ad4eb7c717aa828a" From this data I use position.x & position.z as illustrated below. mpSdk.Camera.pan({x: position.x, z: position.z}; However, the resulting movement is way-off-axis. |
||
| Post 4 • IP flag post | ||
|
WGAN Forum Founder & WGAN-TV Podcast Host Atlanta, Georgia |
DanSmigrod private msg quote post Address this user | |
| @DouglasRhiner Perhaps someone else here can answer your question. (I am not a coder: just referring you to the Matterport Support API/SDK documentation. While waiting for a WGAN Forum Member to reply (hopefully), I suggest that you also reach out to the Matterport SDK/API support email address: developer@matterport.com Please let us know how they reply. Best, Dan |
||
| Post 5 • IP flag post | ||
|
|
DouglasRhiner private msg quote post Address this user | |
| As a follow up to this... I contacted Matterport Dev support explaining the issue and providing some examples of the conundrum I am facing. Well, they got back to me and it appears I have made some headway. Here is the content of the email that I got back that gets to the heart of the matter. Hi Douglas, Thanks for writing back! I've come to the same conclusion as you. There needs to be a Camera.setPose() method. I've decided to tackle the problem alongside you and am a bit exasperated. https://goshow.me/showcase-sync/ In my demo, I'm pairing the Camera.pose() observable with Mode.setMode -- which is creating all sorts of nonsense in the developer tools console. I've recognized that Camera.setRotation works -- but has a tweening effect -- therefore, you cannot immediately use it to set the rotation -- and that there's no way to sync the camera in dollhouse or floorplan modes without using Mode.setMode. I've forwarded my complaint to the Development Team. This shouldn't be so hard, right?italic text[/i] Hopefully they will expose a new method soon. It would make sense, to me, that for every "getter" there should be a "setter". |
||
| Post 6 • IP flag post | ||
Pages:
1This topic is archived. Start new topic?