{"id":5093,"date":"2016-12-14T18:18:20","date_gmt":"2016-12-15T02:18:20","guid":{"rendered":"http:\/\/www.autodesk.com\/products\/fusion-360\/blog\/?p=5093"},"modified":"2021-04-07T12:19:54","modified_gmt":"2021-04-07T19:19:54","slug":"december-14-2016-update-whats-new","status":"publish","type":"post","link":"https:\/\/www.autodesk.com\/products\/fusion-360\/blog\/december-14-2016-update-whats-new\/","title":{"rendered":"December 14, 2016 Update – What’s New"},"content":{"rendered":"

\"Problem?\"<\/span><\/p>\n

What is a troll bug? It\u2019s a bug that taunts you and makes you repeat the same thing over and over until you want to rage quit. The best way to deal with them is to remove them from the source instead of feeding them with your precious keystrokes and mouse clicks. Lucky for you, we got rid off a bunch of them this time around, so you can channel your energy into more productive and harmonious tasks, like designing sweet products in Fusion 360 that do good for the world. Here are the notable fixes and improvements we made for this update.<\/span><\/p>\n

Modeling\u00a0<\/strong><\/h1>\n

Joint and joint origin now stay intact after edits<\/b><\/h2>\n

TrippyLighting<\/b><\/a> reported a <\/span>joint-related bug<\/span><\/a> where editing a joint and joint origin back and forth resulted in some really poltergeist-ish behavior with the joint origin jumping around for no reason. We called the software ghostbusters and were able to catch em all so that joints work as they should again. <\/span><\/p>\n

Component issues fixed<\/b><\/h2>\n

We fixed a weird component naming issue in the browser where the first time you double click a component, it didn\u2019t highlight the text. Pressing CTRL+A to select all didn\u2019t work either, and pressing delete with the intention to delete the name actually deleted the component itself. What a hot mess. We\u2019re glad that this is sorted out. <\/span><\/p>\n

Bold.stelvis<\/span><\/a> reported <\/span>an issue <\/span><\/a>where he was seeing x-ref\u2019d designs nested in other components becoming out-of-date, even though no changes have been made to them. Turns out the out-of-date messaging was falsely triggered by some wonky code. We came up with the fix in November, but spent some time testing it to make sure that it works. Now it\u2019s fixed \ud83d\ude42 <\/span><\/p>\n

Mesh to Brep conversion improved <\/b><\/h2>\n

Since the introduction of the mesh workspace, we\u2019ve been receiving a number of crash reports related converting mesh bodies to brep bodies. We\u2019ve been incrementally improving the conversion performance, and this update should make it a lot better. Let us know in the forum if this is working better for you. <\/span>
\nAlso related – previously it would take about 10+ minutes to file > export a design with very large mesh bodies as SPD file format. Now it takes about 4 minutes.<\/span><\/p>\n

Usability\u00a0<\/strong><\/h1>\n

The trackpad scrolling troll bug is gone<\/b><\/h2>\n

Cekuhnen<\/b><\/a> reported that if you were scrolling through your browser with your trackpad and let go of it to select the item you were looking for, the browser would jump up just enough for you to select the wrong item. At first you\u2019d think that it was your own fault, but no. It\u2019s the trackpad. Trolling you. The more you did it, the more you were feeding it. Don\u2019t worry, we took care of it.<\/span><\/p>\n

Proxy server improvements <\/b><\/h2>\n

We\u2019ve made a bunch of proxy server improvements, such as automatic proxy detection for Mac users so you can move between an office proxy to a home proxy without any issues, as well as <\/span><\/p>\n

better install performance for corporate environments with PAC scripts enabled.<\/span><\/p>\n

Python upgraded to 3.5.1<\/b><\/h2>\n

Previously we were running Python version 3.3.5, but now we\u2019ve upgraded to 3.5.1. Our code jockeys believe that it will reduce the number of SSL related issues during the installation process. We are actively tracking this and seeing if it does, so if you run into install issues, please let us know.<\/span><\/p>\n

Rendering &\u00a0Graphics\u00a0<\/strong><\/h1>\n

STLs are no longer black when rendered locally<\/b><\/h2>\n

\"screen-shot-2016-12-12-at-12-44-57-pm\"<\/p>\n

So remember that bug where your STL bodies turned into pitch black as soon as you kicked off the local rendering engine to do its thing? Yeah, that\u2019s fixed. Now all STLs will adopt your default appearance material (Steel Satin, or whatever you\u2019ve set it as in your preferences). Hooray! <\/span><\/p>\n

Model disappearing from workspace issue fixed<\/b><\/h2>\n

We got a design where when you tried to orbit around it, it would literally disappear from the workspace. Poof. Gone. No errors, no way of getting it back. Even the viewcube went away with it. We later learned that this was due to a graphics corruption issue and got it fixed. Spooky.<\/span><\/p>\n

2D Drawings\u00a0<\/strong><\/h1>\n

View scale drop-down menu now stays open<\/b><\/h2>\n

We fixed a wonky UI bug where if you tried to expand the the View Properties dialog and wanted to select a different base view scale, the drop-down list wouldn\u2019t stay expanded. It would drop down for a second and then collapse back up, taunting you, testing your ninja reflexes. This isn\u2019t a dojo. Now when you expand the list, it\u2019ll stay expanded like it should.<\/span><\/p>\n

HSM<\/strong><\/h1>\n

Open slots now works better<\/b><\/h2>\n

Good news! We fixed an issue where recalculating an open slot toolpath resulted in an an error where the toolpath did not fit the open slot anymore. The fix in HSM means that cutting open slots in Fusion should now work a lot smoother with much better performance.<\/span><\/p>\n

HSM Kernel updated<\/b><\/h2>\n

We\u2019ve also updated our HSM kernel, which fixes a number of outstanding issues we couldn\u2019t get to in previous product updates. It also fixed a series of nasty turning issues related to gouging parts due to invalid toolpaths, checking for gouges, and machine tool crash scenarios.<\/span><\/p>\n

The updated kernel also fixed a tool path trimming issue for 2D Contour, where the incorrect trimming occurs when stock contours were defined.<\/span><\/p>\n

Apparently there was a ramp taper angle setting threshold that causes the cutting Z level to not go to the correct final depth, which resulted in a tool crash. This is now also fixed.<\/span><\/p>\n

Euler\u2026.Euler\u2026.Euler…<\/b><\/h2>\n

Unlike <\/span>Bueller, who was skipping class<\/span><\/a>, Euler was present, but had the wrong answers. We fixed a post process issue where the <\/span>Euler angles<\/span><\/a> were not correct. Now they are.<\/span><\/p>\n

Data no longer disappears <\/b><\/h2>\n

jonathanZRMZM<\/span><\/a> reported \u00a0<\/span>a glaring issue<\/span><\/a> where <\/span>moving ANY operation directly after a folder or pattern causes the folder to empty, leaving its children attached to the operation. If the operation is regenerated, the toolpath for the operation is removed, a bunch of important data gets lost. What\u2019s worse is that the issue won\u2019t throw any errors until it\u2019s too late. Ouch. We quickly jumped on this and got it fixed.<\/span><\/p>\n

Swarf bugs fixed<\/b><\/h2>\n

We caught a Swarf bug where the direction of Face chain couldn\u2019t be changed. Oh and it gets worse. When a swarf operation chooses the wrong side of a part, you have to check “machine other side” and the cut will go from conventional milling to climb milling. There was no option to specify which you want to use, which was annoyingly frustrating. Now you can change direction and machine the other side.<\/span><\/p>\n

Fusion 360 freeze issues fixed<\/b><\/h2>\n

This issue was found on both El Capitan 10.11, 10.12 Sierra, and Windows 7. Regenerating an adaptive operation, then clicking \u201cYes\u201d to confirm the regeneration, but then right-clicking the operation and then aborting it will make Fusion 360 get all frazzled and crash. <\/span><\/p>\n

When testing on a Surface Pro 4, we ran into a freeze issue when <\/span>trying to move and edit a tool in the local folder of the Tool Library dialog using the touch screen. We dug into the code and saw some mutated code that apparently came in contact with the green ooze. Luckily we had an antigen to reverse the effect. Now it\u2019s fixed.<\/span><\/p>\n

UI wonkiness fixed<\/b><\/h2>\n

We found a weird Mac OS UI issue where the Tool Renumbering dialog appeared to be unnecessarily enormous for only 4 entry fields and a couple of checkboxes. Now it’s back to a more logical size.<\/span><\/p>\n

Simulation<\/strong><\/h1>\n

Metals with nonlinear behavior added to Materials Library<\/b><\/h2>\n

When you conduct a nonlinear study, you would typically use metal materials that have inherent nonlinear material behaviors. Problem was that we didn\u2019t have any of these materials in the Materials Library in Fusion 360. Now the update includes new metals with nonlinear behavior. You can access them via the physical material command. Under the library drop-down menu, select Fusion 360 \u00a0Nonlinear Material Library and you\u2019ll get an assortment of metals to choose from.<\/span><\/p>\n

\"nonlinear-materials\"<\/p>\n

This should be a solid foundation for doing nonlinear analysis. We have plans to expand this library to include other materials types such as rubber in the near future.<\/span><\/p>\n

UI weirdness fixed <\/b><\/h2>\n

We found some conflicting UI behavior where if the name of your study was very long and you went into the Compare environment to compare results, the study name would be cut off when it reaches the Navigation tools. As a compromise, we shortened the allowed space so that it doesn\u2019t clash with the Nav tools, and if you name is still cut off, hovering over it will show a tooltip with the full name displayed.<\/span><\/p>\n

Compare option no longer disappears<\/b><\/h2>\n

Speaking of the Compare environment, we fixed a bug where the Compare option would disappear from the workspace switcher after you closed and reopened a design with results are already solved. The Compare option is now available as soon as you open a design with solved results, ready to be compared. <\/span><\/p>\n

There were cases where if you went into your preferences and changed your Load Glyph Graphics from Screen Size to Model Size, continued to exit out of the design and then opened it back up, a giant load arrow would flash for a second, followed by an empty canvas and an invisible viewcube. These troll bugs really know how to mess things up. Luckily we got this sorted out as well.<\/span><\/p>\n

\"screen-shot-2016-12-05-at-5-13-11-pm\"<\/p>\n

Another weird UI bug had to do with the materials dialog growing bigger and bigger every time you open it. If you do it repeatedly, the dialog would take over your whole window. Another case of some voodoo magic going on. Luckily we broke the spell and now our UI works as it should.<\/span><\/p>\n

Apparently the Event Simulation Contact Manager forgot to include the instance number for your components. If you haven\u2019t renamed your components (which you really should be doing), it seemed like you only had one component to work with. Now the contacts manager will correctly show the number of instances.<\/span><\/p>\n

\"screen-shot-2016-12-13-at-4-24-01-pm\"<\/p>\n

Probe bugs squashed <\/b><\/h2>\n

There have been a number of Surface Probe issues reported in the previous version of Fusion 360. Issues like when you go into Surface Probe, change Displacement result type to something else in the legend bar, and then move your mouse, the result type would switch back to Displacement for no reason. <\/span><\/p>\n

And then there\u2019s this annoying bug. Say that you ran a study and the results show some deformation of your model. The undeformed state is shown as wireframe. When you tried to put a surface probe on an area of the model where the undeformed and deformed state were very close, Fusion 360 would think that you want to put it on the deformed one (which is wrong), and will plop it on the wrong state. We\u2019ve taught the software to play nicely with the two states so now you can place your surface probes correctly.<\/span><\/p>\n

Web viewer naming issue fixed <\/b><\/h2>\n

Apparently troll bugs weren\u2019t just messing with us in-product. They managed to get into the web browser as well. In the Design details of the browser model view, one troll bug managed to take one of your study names and replaced all of your folder names under that study with the same exact name. We decided to take the high road and quietly put an end to this nonsense. Hopefully this didn\u2019t get too many of you.<\/span><\/p>\n

X-ref modeling performance back to 100%<\/b><\/h2>\n

There were some cases where running a Simulation on a model that included x-ref designs made the modeling performance worse. Things got slower over time, which shouldn\u2019t happen. We untangled some knots in the backend and now modeling performance is back up to speed.<\/span><\/p>\n

Suppress\/Unsuppress issues fixed<\/b><\/h2>\n

We fixed a couple of suppress\/unsuppress body issues related to Simulation. One was an instance where suppressed bodies were somehow also included in Event Simulation\u2019s Contacts Manager. We called the Event Simulation bouncer and tossed them outta there. <\/span>
\n<\/span>The other one was the suppress\/unsuppress command not actually working for x-ref designs that were sub-assemblies in a component. Now it does.<\/span><\/p>\n

API<\/strong><\/h1>\n

New FindBrepUsingRay and FindBRepUsingPoint methods<\/b><\/h2>\n

We\u2019ve added FindBrepUsingRay and FindBRepUsingPoint methods on the Component class, allowing you to find B-Rep entities in a model. \u00a0These can come in real handy for certain workflows.<\/span><\/p>\n

New viewToModelSpace and modelToViewSpace methods<\/b><\/h2>\n

We\u2019ve also added a couple of new methods to the Viewport class to let you go between the 2D space of the view and the 3D space of the model. \u00a0I know most of you haven\u2019t been losing sleep over this but if you have needed it, this will be a welcome addition.<\/span><\/p>\n

Notable fixes<\/b><\/h2>\n