iClone freezes on startup if laptop not primary display while connected to monitor
On a Windows 10 ASUS ROG Strix Hero II laptop connected to a monitor, using "Multiple displays > Extend these displays" and setting the monitor as the primary display causes iClone 7.41.2525.1 to freeze on startup ("Not Responding"). If I connect the monitor AFTER starting iClone it causes no issues. If I set the laptop screen to be the primary display and the monitor the secondary iClone starts without problems. The problem seems to be entirely connected to the laptop screen not being the primary display during start up.
The monitor is an iiyama PROLITE XUB2792QSU-B1.
It would be good if you could look into this issue.
A similar crash happens if you try to reset layout using the Window > Workspace menu. The only way to reset the layout without crashing is to unplug my secondary (monitor) display and reset the layout on my laptop screen.
DialogueTrainer
Related to this bug: If I open the Transition Curve Presets window, move that window from my primary display (laptop) to my secondary display (monitor), close the window, then re-open it, iClone crashes in the same way (Not Responding). It then crashes every time I open this window until I unplug the monitor and re-open the Transition window, whereupon it appears on the primary display again without problems.
It appears iClone *really* doesn't like opening windows on anything other than the primary display. It may be that this only occurs with laptops connected to a monitor, or it could be this occurs with any multi-screen setup.
DialogueTrainer
I should note also, I first saw this when I dragged the iClone window from the laptop screen to the monitor during iClone start up, but cannot remember for certain whether I had previously successfully started iClone with the monitor already connected, or if I had always started iClone first and simply not encountered the problem for this reason. It could be this dragging the window between displays action triggered the (now consistent) issue, but I am not a 100% sure. Either way, now it happens on startup under the conditions described above regardless of further actions from the user.
