fusion360 not launching and how i got around it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
cross posted from reddit r/fusion360
i was having some issues launching fusion on a particular pc that has been fine til recently (Still am) and during debugging it i noticed events.launchdarkly.com and mobile.launchdarkly.com being blocked since it is on https://github.com/StevenBlack/hosts which is fine in itself, this is an expected function of these lists/pihole.
but i noticed the fusion360 network diagnostics does a go/no go tests on the various urls fusion360 uses, which turns out it actually really doesn't, at least not comprehensively
it only checks the status of some the services, not the actual url list which fusion uses.
you can find the list here, this is a much more useful list than what is in the fusion360 diagnostic check.
so status.launchdarkly.com is not on the block list and the diagnostics only check that for reachability they might be of the mind that if it is not actually required to launch, it doesn't show up in the network diagnostics tool which is fair enough. but i figured it might be worth a mention.
also i think fusion360 windows proxy settings are still broken, though i can't test it yet 🙂
just in case anyone has issues launching fusion360 on windows and can't find a resolution after uninstalling and reinstalling, at least for me.
Locks up on the splash screen. Wait chains are stuck on a network request ( ldclientapi.dll seems to be stuck in a select failing loop)
for me disabling my vmware/hyperv network adapters did the trick, left wsl2 virtual on but otherwise just left just my physical connections enabled and fusion popped right up.
even though i bypassed my pihole and whitelisted the launchdarkly domains in pihole it is possible maybe it was going via a virtual adapter because ldclientapi.dll is all about launchdarkly so it seems like its related, even disabling my pihole temporarily didn't fix it though) especially since it was stuck on a select (which could be a red herring and/or confirmation bias)
public and insider same results, started just over a week ago.