Fullscreen bug

[Anonymous]

When I try to go full screen on my laptop with Windows 10,

for some reason Fusion uses the space up to the Windows task bar.

The bottom part either remains gray or it duplicates the timeline.

Similarly on the right side it doesn't use all the screen space

it seems that the full screen dimensions are calculated from the

window (minus the width of the windows borders and the task bar)

[eellenburg]

Try maximizing the window before changing to full screen.

I see the same problems under Windows 7 if not maximized first.

[Anonymous]

I always have it maximized, I just wanted to go to full screen to gain a
bit of extra space in the small laptop screen

V.

[Anonymous]

For me it's even worse... The gray non-used field in the bottom. Some ghost garbage above timeline. Bottom toolbar overlaps the timeline.

 

UPD

Even funny... I have 2 timelines: the bottom one reacts to mouse hovering, but corresponding feature is highlighted on the top timeline. 🙂  (I drew where my mouse cursor actually was)

[paul.clauss]

Hi @Anonymous, @Anonymous, @eellenburg

Thanks for posting! It looks like you are experiencing a known issue in which there are graphics glitches in the design timeline and edges of the screen when Fusion 360 is used in fullscreen mode. This issue has been logged as FUS-28304, and I will update you when I have more information from our development team to share!

In the meantime, I did find that you can usually eliminate the repeated timelines by toggling out of and then back into full screen mode. Please let me know if you have any questions - I'm happy to help!

[haevyrie]

I'm still experiencing this bug and am unable to find a workaround that works. Maximizing or restoring the window before fullscreen does not fix the issue. I've also changed the location of my taskbar to no avail.

[paul.clauss]

Hi @haevyrie

Thanks for posting! Are you working on a high resolution monitor? If so, does the behavior still occur if you open Fusion in a lower resolution? 

As I have been unable to trigger the problem you described on my system, would you recording a screencast illustrating the issue? I'm happy to have a look and investigate further.

[haevyrie]

@paul.clauss

I'm using a pretty standard 1920x1080 monitor. This bug has persisted for months through countless updates. I've tried resetting my settings and reinstalling f360. If this bug is reported as fixed, I'm happy to reinstall again, though it would help to know any locations that will need data caches cleared to ensure I'm starting from a clean slate. I can try to record a screencast when I'm back at my computer, but all I'm doing is pressing the fullscreen command or using the hotkey. Same thing happens from a maximized window or a restored window.

[paul.clauss]

Hi @haevyrie

Thanks for the response - I am sorry to hear that this problem has continued. Fusion 360 should update automatically (which will include bug fixes), but it is possible that there was an error during an update that is contributing to this issue. You can use the clean uninstall utility tool at this link to ensure you are starting from a clean slate with a fresh install - I hope this will help! Please let me know if you have any questions.

[Anonymous]

@paul.claussfor the record, the problem is still there also on my computer. With a fresh installation of f360

[paul.clauss]

Hi @Anonymous

Thanks for the response - I am sorry to hear this behavior persisted through the uninstall/reinstall. I looked further into this issue and believe you may be experiencing a different known issue than I initially thought (logged internally as FUS-34389). I have made a note of this forum thread on the ticket for this behavior - we appreciate the input all of you have provided.

Does this issue occur if you manually size the Fusion window to slightly smaller than full screen? Or does it occur even when Fusion is not in full screen mode? I have noticed that I have not been able to trigger the problem when Fusion is not in full screen mode - this may be the best way to avoid this issue as it is addressed by development.

I apologize for any inconveniences this has caused - the ticket logged with our development team is still being investigated and I hope for a speedy resolution as well. 

[haevyrie]

@paul.clauss

This  issue only occurs in fullscreen, and only in the modelling environments (anything that shows the timeline). If I maximize the window, or resize it smaller, there are no issues, only when using fullscreen mode.

The bug only seems to affect the timeline itself being incorrectly positioned higher than it should be, and failing to update the screen where it would be if it was in the correct position down lower. What you end up with is the timeline, which you can still interact with, being about 100px above a stale image of the timeline at the bottom of the screen (in the former and correct position) which cannot be clicked on.

Based on the way the application behaves, when you go into fullscreen mode it looks like the UI is recalculating the correct positions of toolbar elements, and for whatever reason it seems like the coordinate position of the timeline is being miscalculated in fullscreen. As soon as you go into the rendering environment, which hides the timeline, the bug disappears with it.

Thanks for your help Paul.

[Anonymous]

@paul.claussI have exactly the same behavior like @haevyrie described

[baton2030]

The problem is still here, and with lateset design update (where tabs is redesigned) screenspace loss becomes much worse. Switching into mode w/o timeline and back do not solve this problem.

Also, on a Mac fullscreen mode is working fine, but it is not a solution

 
UPD: forgot to say — i'm working on a Win7 x64

[Anonymous]

Hello,

Still having this issue in Windows 10...

In fullscreen, the timeline gets hidden behind the display settings. 

Please fix!

[HughesTooling]

@paul.clauss This problem has been around for ages and reported in several posts. It's a problem on Win7,8 and 10. I'm not sure you're understanding as you mention resizing the screen, the whole idea of pressing Ctrl+Shift+F is to put Fusion into full screen. In full screen the title bar is removed but then the timeline is moved up and you get a grey line at the bottom of the screen and the display toolbar covers the timeline. It looks like the bar that contains the timeline is not getting the message the available screen height has increased when the title bar is removed by the Full Screen command, Ctrl+Shift+F.

On my Windows 7 and 8.1 systems it makes no difference if the window is maximised first or any other size. If you work in direct mode Full screen works great and you get more working area also good in all the other workspaces.

Mark

[D-NGK]

I'm still having these issues in the 2020 update.

I'm using a high-resolution display (4k).

Is there meanwhile any workaround?

[Anonymous]

(My display- 14inch) Laptop

I am using the latest version of Fusion360 and the bug in fullscreen for design history is still there.

There is still no work around to this? I mean its been 3 years since this was first reported.

Note.

1. Normal in maximised window. No issue.
2. Design history is not clearly visible in Fullscreen. Clearly Unusable.

I also have a dedicated MX110 Graphic-2GB Installed.

[mgabriellm]

I have the same issue as the original poster: when in full screen mode, a grey bar appears at the bottom blocking the feature timeline.   Apparently it's been almost 4 years, and this issue has yet to be addressed.  This is not the only thread that brings up this faulty behavior either.  One would think that an issue that causes the loss of potential screen real estate in a CAD application would merit more attention.  I assume this problem is a non-issue for those who work on large monitors, but for those of us working on smaller displays —let's say, laptops— this is not trivial.  We're loosing up to 5% of potential screen space, which can certainly make a difference when it comes to maximizing workflow.  Any efforts towards having this issue resolved will certainly be appreciated.  Thank you.

[Anonymous]

It is 2021 and I still see this problem, please fix...