Autodesk-Forge configurator live sample with geometry change - autodesk-forge

I want to build enterprise solution for configurator base on Autodesk Inventor models and drawings. I want to have ability to change dimension of assembly (witdh, depth, length and another). I want to see changes on model in real time (something like here but with changes dimensions in custom values: https://tylko.com/shelf/bookcases/1429438/?cv=0&board=cat_all__type_all__id_4267)
As a result I want to have fully documented model with drawings.
Can Forge do that? Is there any demo?

Yes, here's a sample application that does something similar.
https://forge-rimconfigurator-inventor.herokuapp.com/
You can find the source code of the above application here:
https://github.com/sajith-subramanian/forge-rimconfigurator-inventor
There also is another intricate sample available. You can find it here:
http://inventor-config-demo.autodesk.io/
The source code of the above sample is available here:
https://github.com/Autodesk-Forge/forge-configurator-inventor

Thank you for response. Provided samples are different than:
https://tylko.com/shelf/bookcases/1429438/?cv=0&board=cat_all__type_all__id_4267
My sample is dynamic. Is there a possibility to not wait for change update. Same as you can see change directly in Inventor.

Related

RUN iLogic rule on drawing (old C360_OnPublish)

when we used configurator 360 we could start a rule on the Inventor Drawing (idw) simply by calling it "C360_OnPublish".
Now with Forge it doesn't work anymore.
Run Rule is essential to be able to do a quick scaling of the view after a configuration update the drawing, and before the PDF is published.
Is there a quick method that allows you to do the same thing?
we also tried to insert the rule in the Inventor EventTriggers ('Before save document' or 'Drawing view change') but without success.
thank you
Configurator 360 is available in Design Automation. You would need to trigger the rule yourself using Inventor API, depending on your code logic.
You can run directly iLogic macro from your FDA AppBundle. You need to obtain the iLogic Addin first and then start a method from this Addin.
ApplicationAddIn iLogicAddIn = inventorApplication.ApplicationAddIns.ItemById["{3BDD8D79-2179-4B11-8A5A-257B1C0263AC}"];
dynamic iLogicAutomation = iLogicAddIn.Automation;
iLogicAutomation.RunRule(doc, "Your_iLogic_script");
Another option is to run the iLogic script directly from your activity without the AppBundle, but there are some caveats related to that, mainly long operations without any output and with missing heart beating can cause the processing timeouts. This video demonstrates how to do that:
https://youtu.be/kA82e_XcMrY?t=100

Missing custom Inventor materials in SVF/SVF2 models using Autodesk FORGE Model Derivative

A customer has created a custom Inventor Material Library: all his parts are defined to use these custom materials in order to obtain a very realistic representation of model.
When I try to convert his assembly files (exported with Pack & Go) with Autodesk FORGE Model Derivative, the output models (no different between SVF and SVF2 format) contains some white surfaces associated to the parts defined with custom materials.
Interessant: in developer console of browser I've found an error HTTP 400 related to the Galvinized_2_svf_tex_mod.png.
What can I do in order to obtain a better SVF model?
I've found the cause: see Appearances with enabled Self-Illumination are translated to white when creating a shared view from Inventor
The Material Library of customer has the "Self Illumination" active!
I just had a similar issue. I removed the "Self Illumination" and the color came through. I then added "Self Illumination" back to the color, but added the assembly file to my zip with copy and paste in leu of Pack and Go. And the color still works in the viewer.
Don't know if that always works, but if anyone else needs SI, it might be worth a try.
P.S. Good to know that shared views can be a quick test of the Viewer. Hadn't thought of that before.

Convert custom tiny-YOLOv3 to a tensorflow format

After having tried all solutions I have found on every github, I couldn't find a way to convert a customly trained YOLOv3 from darknet to a tensorflow format (keras, tensorflow, tflite)
By custom I mean:
I changed the number of class to 1
I set the image size to 576x576
I set the number of channels to 1 (grayscale images)
So far I am happy with the results on darknet, but for my application I need TFlite and I can't find working method for conversion that suits my case.
Anyone have succeed in doing something similar?
Thank you.
Do you have the resulting .weights file for your custom model?
If so, the following project by peace195 may help:
https://github.com/peace195/tensorflow-lite-YOLOv3
EDIT:
In the above link, use convert_weights_pb.py file to convert your .weights file to a .pb file.
Then use the .pb file as a saved model and convert it to a .tflite model using the following command.
tflite_convert --saved_model_dir=saved_model/ --output_file yolo_v3.tflite --saved_model_signature_key='predict'
Thanks Anton Menshov for your suggestion on improving the answer.
This is the most simplest and easy repo. Author has done a wonderful job and it works well with yolov3, yolv3-tiny and yolov-4. Please don't forget to change the coco.names under classes if you are training on custom classes.
Git link for the code

Custom property (Identity Data) in Revit model got translated wrong

We are experiencing troubles when using the model derivative API to translate and extract properties from a Revit Model.
As the screenshot implies, we have a custom property under Identity Data. But after translation its under Mark (the property on top of it).
It's a model created in Revit 2018.
Is this a bug?
kind regards
This issue has been logged as RVTLMV-4 in our internal case system to our engineering team to allocate time to investigate what happened yesterday and they're working on it. We will get back to you A.S.A.P. once there is any update. Apologizing for any inconvenience had caused to you.
I am seeing this issue too - custom properties appear to be coming through with "Cost" as the PropertyName. The ModelDerivative translation process seems to be the source of the bug. Happens on Revit 2018 or Revit 2019 model.
Is there any chance this issue can be escalated?
Our (live) Forge application relies on custom properties being correctly named and this current API release has broken our application when new models are uploaded.
Image of Model Derivative JSON
Image of Properties in Revit
#Eason Kang: FYI
I met this issue too. However, this issue happened when the translated field was not in the top of the Properties list. When this field was in the top, translation succeeded.
Hope this could give more information to your team.
I attached the image as below. First screenshot, it translated correctly. The 3 following screenshots, it translated wrong

Can the AS3 API reference be accessed trough code

I am making a code completion system for a code editor, and i would like to show a tooltip for every parameter containing its reference data. I would like to emulate the code completion from Eclipse, so i was wondering if the API reference is available in code, or if i have to manually import it using the file system or something like that.
You could reflect the current class in question with flash.utils.describeType
This will return a xml with informations about methods, properties and so on.
This can be very heavy. If you use it all the time, try to use a caching system. The Flex framework has a class for it mx.utils.DescribeTypeCache