I am following the tutorial available here, in order to add Pushpins to a clicked location on the Forge viewer. My issue is that the pushpin is drawn on a different location to where I clicked on the viewer. I am using the exact same code that as available in the tutorial, although I have implemented it as a separate extension.
Following is a screenshot of where the Pushpin was drawn, and where the mouse pointer was at the time it was clicked.
I have been trying to play around with the code by even manually changing the location to get the correct position, but wasn't really successful. Any help on this regard would be appreciated.
Thanks in Advance!
I have this problem when my app was doing components size changes with css, and I solve this calling the method resize of the viewer, after the visual size changes, and before the pushpin creation, like above:
viewer.resize()
Link: https://forge.autodesk.com/en/docs/viewer/v7/reference/Viewing/Viewer3D/#resize
I hope this can help you!
Related
Description
Mirrored model has its materials flipped inside out when viewed in Autodesk Forge Viewer.
Adding a section plane reverts the mirrored model back to what it should look like.
We are using this sample viewer from Autodesk.
This weird behavior does not occur when looking at the model in BIM 360 Docs.
We've included screenshots and steps to reproduce this here.
EDIT: while writing this post, we came across Problems with forceDoubleSided setting. Has this been fixed?
Thanks.
Simply loading the 'Autodesk.AEC.LevelsExtension' might fix the problem.
See https://forge.autodesk.com/blog/bim-360-viewer-vs-forge-viewer
In viewer 7.35 a new setting was added:
Setting to turn section plane hatches on and off. This setting does not apply to the section box.
I am however not able to find this setting anywhere. Could anyone share some information and/or documentation on the use of this?
Does anyone know if we able to remove only hatches, but keep and outline and therefore be able to snap to the edges in the sectioned geometry?
Thank you all in advance for any help!
According to our engineering team, only Section planes support section hatches. Section box won't have that.
Although the viewer of BIM360 Docs built on top of Forge Viewer, it doesn't get updates as the new version of Forge Viewer released. It will take some time to merge the changes from the new Forge Viewer.
Is this not what you are looking for ?
Under settings -> Configuration -> Display section -> Display Section Hatches
I want to create 3d pushpin extension for Autodesk forge v7.*. I tried to use this article`
3D Markup with icons and Info-Card.
But some functions are not working correctly. How can i use it correctly?
I got this errors in console
Now all functions are working correctly, in data i got undefined for parent. Pushpins are not appeared yet.
Apparently there were a few issues with your code:
Since Viewer v7 and onwards overlay scenes are managed so you'd need to add custom geometry with:
this.viewer.overlays.addScene('custom-scene');
this.viewer.overlays.addMesh(this.line3d, 'custom-scene');
Use arrow functions or bind for your callbacks to window and document events such as mousemove or click otherwise they'd lose their contexts and throw errors
Necessary styling was not set for the markups to persist their relative positions ...
See here with corrections to all of the above:
I have a map with source and destination locations and a path is also drawn between the locations. I want to add an animated image of a flight that should move over the path. I have done the map in angular2. Please help me if anyone know the animation part in angular 2 or suggest me any link that i can refer.
Thanks in advance.
I used the below plugin for showing google map in angular 2
https://angular-maps.com/docs/api/latest/ts/core/SebmGoogleMap-directive.html
enter image description here
our initial focus within our 3d views needs tweaking. Currently it is zoomed out ~x2 too far.
Can anyone get me started in the right direction for the controls for this?
I've tried changing the cropregion/ section box etc in the original revit model, but that hasn't made a difference.
A simple way to handle that would be to position the camera as you wish then save the current state and restore it upon loading the model, see my blog post about managing viewer states: Managing viewer states from the API