Hi Niels,
There are a couple of bugs right now and I wonder if they are affecting you. I meant to mention them in my post last week, but forgot.
Apparently the vertical anchor (fmear_anchor_z) value is currently ignored by the app. Right now the app uses z=0 when loading the model. For example, if your elevation was 50m, the app would still use 0, meaning the model is likely to appear above you, rather than below. Obviously we'll need to fix that one.
The second issue is that the AR Writer "adjusts" the model vertically, i.e. it moves the model along Z so that the model centre is at z=0. That's a writer bug that will be fixed as well.
So I'm thinking one of these might be the cause of this. Does that make sense to you? I'm not sure if you are using a z value for your anchor (if you're not, then the first issue won't apply) or whether your data has z values (again, if not, the second issue won't apply).
Either way I hope we'll get fixes for them as soon as possible.
Hi Niels,
We should have fixed the vertical issue in 1.4.0+. Version 1.5.0 is available now. Thanks for your feedback.
Angus Lau
Safe Software Inc.
Hi Niels,
We should have fixed the vertical issue in 1.4.0+. Version 1.5.0 is available now. Thanks for your feedback.
Angus Lau
Safe Software Inc.
Thanks! Will test this anytime soon.
Hi Niels,
There are a couple of bugs right now and I wonder if they are affecting you. I meant to mention them in my post last week, but forgot.
Apparently the vertical anchor (fmear_anchor_z) value is currently ignored by the app. Right now the app uses z=0 when loading the model. For example, if your elevation was 50m, the app would still use 0, meaning the model is likely to appear above you, rather than below. Obviously we'll need to fix that one.
The second issue is that the AR Writer "adjusts" the model vertically, i.e. it moves the model along Z so that the model centre is at z=0. That's a writer bug that will be fixed as well.
So I'm thinking one of these might be the cause of this. Does that make sense to you? I'm not sure if you are using a z value for your anchor (if you're not, then the first issue won't apply) or whether your data has z values (again, if not, the second issue won't apply).
Either way I hope we'll get fixes for them as soon as possible.
@mark2atsafe I really hope you will provide some nice tutorials, blog posts, articles or webinars when you get this working. What I can see from this and Dmitris demos look very interesting indeed, and I look forward to be able to pick up my smartphone and watch a virtual building in the correct georeferenced position!