Weekly problem log #1

Weekly problem log #1

fritter63
Collaborator Collaborator
1,249 Views
18 Replies
Message 1 of 19

Weekly problem log #1

fritter63
Collaborator
Collaborator

I decided to start keeping a quick log of problems and glitches I find while using F360. For me, faster to just take a quick note and then put in bulk here.

 

This is my first one:

 

CAVEAT: new release came out this week, so it could be some of these have been resolved. 

 

- crashes when selecting post processing
- on a crash, I now get the crash report popup window TWICE
- occasionally won’t respond to operations, i.e., “delete sketch”. Just does nothing. Have to try it several times.
- right click on timeline, get popup menu, “edit feature” not selectable. Dismiss menu, do it again, “edit feature” is now selectable. This happens a LOT.
- when editing a feature like “push/pull”, if you want to add or remove selections, you have to zero out the distance value. It will not let you change selections until you do this. Is this by design?
- sometimes when zooming by using touchpad gestures, it zooms WAY out (to where the model almost can’t be seen). Despite that fact that it was two finger spreading gesture. Also does this while just trying to scroll the drawing with two finger drag motion
- Tried to close a simulation, F360 quit responding. Just to the spinning beach ball, I left and came back after 1.5 hours, and it was still just spinning. Didn’t even crash. Had to kill the process.
- some help popup/“Tooltip” (in cam ops setups) windows won’t display. They flash quickly and then disappear (need to get a list of these)
- Froze during simulation of a vey simple (one cam op, 2d pocket) setup, small toolpath, etc. Spinning beach ball.
- Capture image: no way to ONLY save to local file (and not to cloud). “Save” button won’t always activate unless you deselect save to computer, then select it again, but always saves to both places
0 Likes
1,250 Views
18 Replies
Replies (18)
Message 2 of 19

innovatenate
Autodesk Support
Autodesk Support

 

Thanks for letting us know! It might be helpful to have more concentrated forum posts instead of putting everything into one post. It can get confusing if there are too many topics being discussed in a single thread. I'll take a swing at it though... 

 

I'm wondering if any of the issues are related to graphics. 

 

Can you paste a copy of the graphic diagnostics into this post?

Screen Shot 2016-05-02 at 3.44.07 PM.png

 

A couple of quick suggestions related to graphics that I would be curious to see if they have any impact on the behavior:

 

-Try checking the Limit Effects to Optimize Performance in the Graphics Diagnostics dialog.

 

-Another tip may be to switch from Auto-select to OpenGL for the graphics driver setting

Screen Shot 2016-06-24 at 5.36.56 PM.png

 

 

-Try enabling the Open in Low Resolution option in the below link: 

https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/Per...

 

 

Now one by one or by grouping:

- crashes when selecting post processing 
We are watching this issue via report CAM-4032. Thanks for submitting the error report. It's helpful to note what you were doing when the crash occurred. I or another member of the team may provide an update on this when it becomes available.
 
 
- on a crash, I now get the crash report popup window TWICE
Could there be more than one instance of Fusion 360 running when this occurs?
 
- occasionally won’t respond to operations, i.e., “delete sketch”. Just does nothing. Have to try it several times.
- right click on timeline, get popup menu, “edit feature” not selectable. Dismiss menu, do it again, “edit feature” is now selectable. This happens a LOT.
Do you have any peripheral devices plugged into the computer (e.g. space mouse or wacom tablet)? I'm wondering if a peripheral may be stealing focus or something... For the Edit Feature to not be grayed out in the context menu, you must first select the feature in the timeline (the feature should be highlighted before right clicking). We just made some updates to the timeline, so maybe these will help for this issue.
 
 
- when editing a feature like “push/pull”, if you want to add or remove selections, you have to zero out the distance value. It will not let you change selections until you do this. Is this by design?
Can you record a screencast of this issue, it will be helpful to know the exact picks and clicks.
 
 
 
- sometimes when zooming by using touchpad gestures, it zooms WAY out (to where the model almost can’t be seen). Despite that fact that it was two finger spreading gesture. Also does this while just trying to scroll the drawing with two finger drag motion
- Tried to close a simulation, F360 quit responding. Just to the spinning beach ball, I left and came back after 1.5 hours, and it was still just spinning. Didn’t even crash. Had to kill the process.
- Froze during simulation of a vey simple (one cam op, 2d pocket) setup, small toolpath, etc. Spinning beach ball.
 
Are any of these repeatable or do these things seem to occur intermittently? If you have reproducible steps I can pass along to the development team, it would be really helpful!
 
 
- some help popup/“Tooltip” (in cam ops setups) windows won’t display. They flash quickly and then disappear (need to get a list of these)
A screencast of this issue would be helpful as well. There's a discussion about this topic in the below post that may be helpful.
 
 
- Capture image: no way to ONLY save to local file (and not to cloud). “Save” button won’t always activate unless you deselect save to computer, then select it again, but always saves to both places
This is a known issue (reported ID FUS-23739). My understanding is that this is currently working as designed, but we are reviewing it for the future. It was originally reported via the below forum discussion.
 
I hope this helps! Have a great weekend!
 
 
 
 

 




Nathan Chandler
Principal Specialist
Message 3 of 19

fritter63
Collaborator
Collaborator

@innovatenate

 

Thanks for the late friday reply!

 

Will try to answer questions inline (no "quote" option on these forums?)

 

Diagnostics info:

 

[GPU Information]
GPU Device: Intel HD Graphics 4000
GPU RAM: 1536 MB (Integrated card)
GPU Driver API: OpenGL

[Graphics Effects Settings]
Use high-resolution graphics: Off
Anti Aliasing: Off
Ambient Occlusion: Off
Object Shadow: Off
Ground Shadow: On
Ground Reflection: Off
Selection Display Style: Normal
Transparency Effect: Better Performance

[Limit effects to optimize performance]
Off

 

 

Now one by one or by grouping:

- crashes when selecting post processing 
We are watching this issue via report CAM-4032. Thanks for submitting the error report. It's helpful to note what you were doing when the crash occurred. I or another member of the team may provide an update on this when it becomes available.
 
--- Awesome
 
 
- on a crash, I now get the crash report popup window TWICE
Could there be more than one instance of Fusion 360 running when this occurs?
 
--- Nope
 
- occasionally won’t respond to operations, i.e., “delete sketch”. Just does nothing. Have to try it several times.
- right click on timeline, get popup menu, “edit feature” not selectable. Dismiss menu, do it again, “edit feature” is now selectable. This happens a LOT.
Do you have any peripheral devices plugged into the computer (e.g. space mouse or wacom tablet)? I'm wondering if a peripheral may be stealing focus or something... For the Edit Feature to not be grayed out in the context menu, you must first select the feature in the timeline (the feature should be highlighted before right clicking). We just made some updates to the timeline, so maybe these will help for this issue.
 
 
--- Nope, just my macbook and using the touch pad
 
 
- when editing a feature like “push/pull”, if you want to add or remove selections, you have to zero out the distance value. It will not let you change selections until you do this. Is this by design?
Can you record a screencast of this issue, it will be helpful to know the exact picks and clicks.
 
--- Will do that next time I'm in CAM.
 
 
 
- sometimes when zooming by using touchpad gestures, it zooms WAY out (to where the model almost can’t be seen). Despite that fact that it was two finger spreading gesture. Also does this while just trying to scroll the drawing with two finger drag motion
- Tried to close a simulation, F360 quit responding. Just to the spinning beach ball, I left and came back after 1.5 hours, and it was still just spinning. Didn’t even crash. Had to kill the process.
- Froze during simulation of a vey simple (one cam op, 2d pocket) setup, small toolpath, etc. Spinning beach ball.
 
Are any of these repeatable or do these things seem to occur intermittently? If you have reproducible steps I can pass along to the development team, it would be really helpful!
 
--- It's regular, but not deterministically repeatable. Ie, I can't "make it happen" (like that weird shifting the my Dodge Ram for the last 17 years!). 
 
 
- some help popup/“Tooltip” (in cam ops setups) windows won’t display. They flash quickly and then disappear (need to get a list of these)
A screencast of this issue would be helpful as well. There's a discussion about this topic in the below post that may be helpful.
 
--- Will screencast the next time it is happening. it is repeatable and only on certain CAM option fields.
 
 
- Capture image: no way to ONLY save to local file (and not to cloud). “Save” button won’t always activate unless you deselect save to computer, then select it again, but always saves to both places
This is a known issue (reported ID FUS-23739). My understanding is that this is currently working as designed, but we are reviewing it for the future. It was originally reported via the below forum discussion.
 
--- Excellent!
 
I hope this helps! Have a great weekend!
 
--- Oh yeah, will be proof-of-concepting my first guitar rosette with Inlays (on the CNC with F360 programming), should be fun!

 

 

0 Likes
Message 4 of 19

TrippyLighting
Consultant
Consultant

When you click on reply there is a "Quote button' in the upper right corner.

 

Screen Shot 2016-06-24 at 10.55.01 PM.png


EESignature

0 Likes
Message 5 of 19

jeff_strater
Community Manager
Community Manager

Thanks @innovatenate, great set of responses, just a couple of clarifications:

 

    - right click on timeline, get popup menu, “edit feature” not selectable. Dismiss menu, do it again, “edit feature” is now selectable. This happens a LOT.

 

 

In general, in Fusion, you almost always have to left click first to select the item, then right click to get the context menu.  Most likely this is what is happening in your case:  You don't actually have the feature selected.

 

    - when editing a feature like “push/pull”, if you want to add or remove selections, you have to zero out the distance value. It will not let you change selections until you do this. Is this by design?

 

 

Yes, this is by design.  The reason is that Fusion needs to prevent you from being able to select faces which are part of the preview of the feature.  The preferred method of selecting additional items in Press/Pull or any other command is to hold down the CTRL key (CMD on Mac).  This will suspend the preview and allow you to select other items in any command.  Since CTRL/CMD is a common method for adding to selection in any computer applications, it seemed like a good way to allow you to add things in Fusion commands as well.

 

Jeff

 

 


Jeff Strater
Engineering Director
Message 6 of 19

HughesTooling
Consultant
Consultant

@jeff_strater wrote:

Thanks @innovatenate, great set of responses, just a couple of clarifications:

 

    - right click on timeline, get popup menu, “edit feature” not selectable. Dismiss menu, do it again, “edit feature” is now selectable. This happens a LOT.

 

 

In general, in Fusion, you almost always have to left click first to select the item, then right click to get the context menu.  Most likely this is what is happening in your case:  You don't actually have the feature selected.

 

 

Jeff

 

 


 

@jeff_strater 

 

Here's an example where Edit Feature is greyed out but other options like Rename and Delete are available. I admit I tend to just right click rather than the left then right click but surely if right clicking alone doesn't make the selection the menu should not pop up at all.

Clipboard01.png

 

Mark

 

Edit here's another one with a sketch.

Clipboard02.png

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


0 Likes
Message 7 of 19

fritter63
Collaborator
Collaborator

I have to agree with @HughesTooling, I'm not seeing it work like that and it also doesn't line up with my experience as a software engineer!

 

First off, I also am seeing where even if I have left clicked it, the menu doesn't build (highlight) correctly.

 

But in general, it shouldn't have to work that way (left click first). If you've recognized that a right click has been made, then it should be considered selected!

 

Are you using Cocoa to implement the Mac UI? Admittedly, I don't write user interface software anymore (I focus on server side enterprise apps), but usually the way it works that each "widget" on the screen (in this case those menu items) will have an event listener registered, and that will get notified/called whenever a mouse event occurs. Events such as "mouse enter" (the area of the widget) or "left click" or "right click" are all distinguishable events. It could be that you have one event listener handling all those events and deciding what to do, or maybe you have a different event listener for each type of event? In any event, the point is, you've been notified of a right mouse click on the widget, and are certainly able to build a menu to display, so why not make it all valid options? 

0 Likes
Message 8 of 19

kb9ydn
Advisor
Advisor

jeff.strater wrote:

 

In general, in Fusion, you almost always have to left click first to select the item, then right click to get the context menu.  Most likely this is what is happening in your case:  You don't actually have the feature selected.

 


 

 

 

That seems totally unnecessary and just slows you down.

 

 

C|

0 Likes
Message 9 of 19

jeff_strater
Community Manager
Community Manager

I really hesitate to wade into religious topics on a Friday afternoon, especially without a beer in hand...  But, I'm apparently going to do it anyway.  I don't expect to convince anyone of anything, and most likely we will end up changing this in the future.  But, I thought I'd offer some history, just for perspective, and to prove that we really have given serious thought to this, over a long period of time, and it's not just a snap decision made by one developer.  These types of decisions produce very long and sometimes heated discussions.  This one, in particular, we have been arguing about for years, no exaggeration.

 

The factors that went into this decision include:

  1. No clear common behavior across computer applications.  We looked at a very wide variety of tools, from a wide variety of software suppliers, inside and outside of Autodesk.  There really is not as much consistency as you might first think in this area.  When you factor in everything, such as behavior when one item is selected, when multiple items are selected, when the cursor is over something that is selected and other things are selected, how shift and ctrl modifiers affect selection, etc., you get a huge variety of behaviors.  Try it.  Some applications deselect all selections if you right click over something else.  Some applications leave the current selection intact, and perform the context menu action on the item your right clicked over, and do not apply it to the selection.  Some add the item to the selection, and apply the action to the selection + the new item.  And so on.
  2. Right click in Fusion is different than in many applications.  It is the way to invoke, not just a normal context menu, but the marking menu, of which the context menu is just a part of it.  The marking menu was (at least at one time) seen as the primary UI for accessing all commands.  Originally, Fusion was designed to run without a toolbar at all.  (those days are, of course, long past - Fusion was a much simpler application at that time).  So, we wanted to avoid surprising behavior such as right click clearing the selection, if all you were trying to do was find the Press/Pull command.  Add in the fact that you can use the marking menu to do OK and Cancel, if you are in a command (and undo/redo if not), and we had to be very careful with how right click affects selection.  Another small bit of trivia:  At one time (before any public availability), the marking menu in Fusion was not invoked with right click.  We used the "~" key instead.  Part of that was to get around this right-click problem.  A lot of people (myself included) hated this.  I use the marking menu a lot.  I use it for OK/Cancel, and I use it for repeat last command very frequently.  So, having to use a non-mouse key for me is very inefficient.
  3. In a CAD application, you often work zoomed into your model, so that it fills the entire screen.  That is, there is no blank space, your cursor is always over a selectable piece of geometry.   If, every time you right clicked, we selected the thing under the cursor, you would continually be selecting geometry that you might not have intended to select, just to do things like OK, or to repeat a command.

I do realize that the above was really designed around interaction in the graphics area, and the particular frustration here is over right click in the timeline (no marking menu there), but hopefully you can see that, having one behavior in the graphics area and another in the timeline might be confusing, so we decided to enforce consistency across the entire application.

 

Anyway, that's part of the reasons why this is the way it is.  I certainly understand the frustration, but the answer is not quite as obvious as it might seem at first glance.

 

Have a great weekend!

 

Jeff

 


Jeff Strater
Engineering Director
Message 10 of 19

fritter63
Collaborator
Collaborator

Thanks @jeff_strater

 

I'm not sure much religion is needed here! I'd just make it work differently in the context of the timeline, because it's actually what is more commonly expected.

 

So, how do we go about buying you a beer for a Friday?

0 Likes
Message 11 of 19

kb9ydn
Advisor
Advisor

jeff.strater wrote:

 

I do realize that the above was really designed around interaction in the graphics area, and the particular frustration here is over right click in the timeline (no marking menu there), but hopefully you can see that, having one behavior in the graphics area and another in the timeline might be confusing, so we decided to enforce consistency across the entire application.


 

 

 

@jeff_strater  The history lesson is quite interesting, so thanks for that.  I think where it maybe goes wrong is in enforcing the same behavior in the graphics area vs the timeline.  Consistency is usually a good thing but in some cases it doesn't make sense.  This I think is one of them.

 

But beyond that, I think there is more going on here than just not selecting the timeline entity first.  I've run into the grayed out edit option many times and I'm pretty sure it's not because I didn't select it first.  I can't pinpoint it but I suspect it has something to do with switching focus between Fusion and other applications.  I have two monitors and I frequently switch back and forth from Fusion to Solidworks to a web browser, and this seems to be when the problem occurs.

 

 

C|

Message 12 of 19

jeff_strater
Community Manager
Community Manager

I agree, @kb9ydn, sometimes better behavior should override consistency.  And, this is probably a good example.  In the timeline and in the browser, right click should do something different than today.  But, I'm interested in people's thoughts on what should happen in a few scenarios:

 

  1. Nothing is selected.  (OK, this one is obvious - just adding it for completeness - right click should select the thing under the cursor, and apply the command to it)
  2. One item is selected, right click over another item.  Should right click:
    a) de-select the currently selected item, select the item under the cursor, and apply the command chosen only to the item under the cursor
    b) add the item under the cursor to the one item that is selected, and apply the command to both
    c) apply the command only to the item under the cursor, without selecting it, and leave the other selected item as the one selected item
  3. multiple items are selected, right click over an item that is already selected.  Should right click:
    a) apply the command to everything selected
    b) apply the command only to the item under the cursor, leaving other items selected
  4. multiple items are selected, right click over an item that is not already selected.  Should right click:
    a) de-select the currently selected items, select the item under the cursor, and apply the command chosen only to the item under the cursor
    b) add the item under the cursor to the other items that are selected, and apply any commands to the entire set
    c) apply any commands only to the item under the cursor, without selecting it, and leave the other selected items selected

And, what should Shift/Ctrl do in these cases (let's leave that for now, but I bring it up only to show that there is more to consider)

 

For now, I'll withhold my opinions, to see what feedback we get.

 

thanks,

 

Jeff

 


Jeff Strater
Engineering Director
0 Likes
Message 13 of 19

kb9ydn
Advisor
Advisor

@jeff_strater wrote:

I agree, @kb9ydn, sometimes better behavior should override consistency.  And, this is probably a good example.  In the timeline and in the browser, right click should do something different than today.  But, I'm interested in people's thoughts on what should happen in a few scenarios:

 

  1. Nothing is selected.  (OK, this one is obvious - just adding it for completeness - right click should select the thing under the cursor, and apply the command to it)
  2. One item is selected, right click over another item.  Should right click:
    a) de-select the currently selected item, select the item under the cursor, and apply the command chosen only to the item under the cursor
    b) add the item under the cursor to the one item that is selected, and apply the command to both
    c) apply the command only to the item under the cursor, without selecting it, and leave the other selected item as the one selected item
  3. multiple items are selected, right click over an item that is already selected.  Should right click:
    a) apply the command to everything selected
    b) apply the command only to the item under the cursor, leaving other items selected
  4. multiple items are selected, right click over an item that is not already selected.  Should right click:
    a) de-select the currently selected items, select the item under the cursor, and apply the command chosen only to the item under the cursor
    b) add the item under the cursor to the other items that are selected, and apply any commands to the entire set
    c) apply any commands only to the item under the cursor, without selecting it, and leave the other selected items selected

And, what should Shift/Ctrl do in these cases (let's leave that for now, but I bring it up only to show that there is more to consider)

 

For now, I'll withhold my opinions, to see what feedback we get.

 

thanks,

 

Jeff

 


 

 

I would say:

 

1. I agree this one is obvious.

2. I would prefer option a.  Option b might be ok but I don't like it as much.  Option c doesn't make any sense at all because it shows you one thing and does another.

3. Option a for sure.  Option b is bad because again, it would be showing you one thing and doing another.

4. I would say option a.  Option b might be ok but I don't like it as much.  Option c is terrible.

 

 

When you hold down the <ctrl> key it says that you want to add the next item to the items already selected.  So here it would make sense to go with option 2b and 4b.

 

 

C|

0 Likes
Message 14 of 19

PhilProcarioJr
Mentor
Mentor

@jeff_strater

"

  1. Nothing is selected.  (OK, this one is obvious - just adding it for completeness - right click should select the thing under the cursor, and apply the command to it)
  2. One item is selected, right click over another item.  Should right click:
    a) de-select the currently selected item, select the item under the cursor, and apply the command chosen only to the item under the cursor
    b) add the item under the cursor to the one item that is selected, and apply the command to both
    c) apply the command only to the item under the cursor, without selecting it, and leave the other selected item as the one selected item
  3. multiple items are selected, right click over an item that is already selected.  Should right click:
    a) apply the command to everything selected
    b) apply the command only to the item under the cursor, leaving other items selected
  4. multiple items are selected, right click over an item that is not already selected.  Should right click:
    a) de-select the currently selected items, select the item under the cursor, and apply the command chosen only to the item under the cursor
    b) add the item under the cursor to the other items that are selected, and apply any commands to the entire set
    c) apply any commands only to the item under the cursor, without selecting it, and leave the other selected items selected

And, what should Shift/Ctrl do in these cases (let's leave that for now, but I bring it up only to show that there is more to consider)"

 

1. Agree

2. I would say (a) unless your holding control or shift then apply selected action to all selected objects

3. refer to 2.

4. I would say (c) unless your holding control or shift and (a) if your not 



Phil Procario Jr.
Owner, Laser & CNC Creations

0 Likes
Message 15 of 19

TrippyLighting
Consultant
Consultant

1. Agree

2. a

3. a

4. a or c


EESignature

0 Likes
Message 16 of 19

catot
Advocate
Advocate

Just my opinions:

2a

3a

4a

0 Likes
Message 17 of 19

jeff_strater
Community Manager
Community Manager

Thanks for all the great input.  OK, it is now time for me to be embarrassed.  It turns out that the project to fix right click behavior in the browser and the timeline was actually implemented way back in February!!  I had somehow lost track of that, and was explaining behavior that no longer exists.  I tried it, and it seemed to work for me.  So, if problems still exist for this, they are bugs, and we need to fix those.  If you can show a good workflow that shows right click not working correctly, please share it here.

 

BTW, for the record we do:

 

1

2a

3a

4a

 

screencast:

 


Jeff Strater
Engineering Director
0 Likes
Message 18 of 19

fritter63
Collaborator
Collaborator

Happens on a daily basis to me.

 

I've made to left click first, then right click ,and still don't get the "edit" option highlighted.

 

Will try to get a screen cast for you next time it's bugging me.

 

0 Likes
Message 19 of 19

kb9ydn
Advisor
Advisor

To reproduce the grayed out edit bug is actually quite simple.

 

1. Open a design with a timeline

2. With no items already selected; hover the mouse over an item in the timeline for 3-4 seconds and then right click it.

 

I discovered this the other day and was going to post about it, but apparently I got sidetracked.  Smiley Embarassed

 

 

 

C|