Bug report: Monitor enumeration

[jo.stu]

Posted this to the Autodesk Fusion Account on Twitter a long time ago, no reaction, and it‘s still happening.

Copying the tweet contents here now, maybe someone will see it here:

@adskFusion360

Heya! I've got Fusion freeze during launch, even after reinstall. A quick glance at the callstack shows it might be connected to monitor enumeration? I uploaded a dump file at https://drive.google.com/file/d/1pI_PzgTLoUsZEluqEJBgrXc-ekIwCm8n/view?usp=sharing…—your devs should be able to find the source for the freeze w/ it.

No reinstall (reboot or no) helped, but with the assumed screen problem in mind, I dug through the logs and options a bit, and resetting MainWindowRectangle in ~/AppData/Roaming/Autodesk/Neutron Platform/Options/NMachineSpecificOptions.xml to "0,0,500,1000" fixed it for me.

[Phil.E]

Hi,

Thanks for posting here on the Fusion Support Forum. I don't know who monitors the twitter feed, but I can guarantee nobody from development or QA is watching that. There is definitely zero customer support activity on that feed.

As for your issue. I don't know what you mean by monitor enumeration. Do you mean which monitor is considered "primary" by the OS?

Thanks,

[jo.stu]

Heya Phil,

no, enumeration as in querying the connected display devices and getting back a list of them from Windows. Sorry, bad lingo habit of being a software dev myself. When I close Fusion after having it had fullscreen on my secondary display (the one without the task bar tray), with two 4k displays being connected, the config looks like 

<MainWindowRectangle UserName="MainWindowRectangle" Value="3071,-8,6144,1688"/>

But on startup, that seems to cause errors. I don't remember it 100% (I debugged into the posted dump file ages ago), but it looked like Fusion has a problem matching those coordinates to the second monitor correctly and then starting up the UI, and it gets stuck somewhere. Someone with access to your code should be able to pinpoint it, without it it's unfortunately hard to find the exact point it fails.

[Phil.E · Accepted solution]

Do either of these articles describe your setup or the findings you are getting?

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

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

[jo.stu]

I neither have „Nahimic and/or Asus Sonic Suite“ installed, nor some USB dock running (the Displays are connected to the graphics card directly via DisplayPort), and the card is a GTX960, not an RTX card, so no, those don‘t describe it.

Also, those both describe *workarounds* („disconnect the second monitor“), not fixes, and frankly, since the problem can be solved with editing the config file, like outlined in my initial post, it‘s a much more inconvenient workaround (a bit like suggesting to just call a taxi when someone‘s car runs out of fuel, instead of filling it up).
Plus, if I can edit the config manually to work around the problem, Fusion *should* be able to discard the values in the config automatically if they would lead to a freeze.

[Phil.E]

Thanks. The report is FUS-103334.

[jo.stu]

Sorry if I came across a bit brash in my last reply.

I‘m simply feeling a bit frustrated since this is such a similar problem to those I deal with at work daily (integrating a rendering plugin we make into CADs; not into Fusion, but Revit is among them) and it‘s irritating not being able to just step through the code myself and fix it in this case 😉 Not your fault tho of course.

[Phil.E]

No worries at all. Thanks for the helpful details. I have a few other bugs you can help sort out.... 🤣

JK. The report has plenty of detail, so thanks a bunch for posting all this.