Houston we have a problem.
There are 2 scenarios.
Often WM will perpetually crash on start and it does not start to the default new file.
Sometimes it will start a new, but I am unable to load my saved file, which might work on another PC with WM, it will just crash. Even loading a much small file will not help. Recently, this other PC is having issues now.
It is very consistent. Even after reinstalling WM, it behaves exactly the same way.
The only solution was to reinstall Windows 11, only to have this same cycle happen again a few weeks later. This is my 3rd Windows now and it is not a good solution.
WM would start out working fast and gets slower and slower, before crashing forever.
There must be some issues between WM and Windows perhaps?
I have also encountered WM crashing when I drag in the multi file input device. Just this device would crash WM. But it was just working the day before…
I’ve attached the logs from both PC in the following replies
And it cannot possibly be that my hundred different saved files are corrupted when they were fine for months
“[Error ] A pair of ports failed to be connected on load. This is usually due to a load error…”
this seems to be the common error
I have a deadline in less than 3 weeks, so I am kinda stressed…
Some 3rd party “Macros” you have installed, are causing this crash on load. Multiple macros in your library are incompatible with your current WM build. Removing those legacy macros should fix this crash.
Your startup document is also from an older version, delete and recreate that. Best to uninstall, delete remaining files manually (including the world machine roaming folder). Then install fresh.
Uninstalled and deleted all the files you mentioned manually, including the roaming stuff, and did a fresh install.
The “macros” all came back after the install.
And the crash resumes.
Macros reside within your “documents” folder (by default: “User Documents\World Machine Documents”). Delete faulty ones from there too. I assume you updated from a very old version version of WM recently? You shouldn’t switch program versions between projects. Tends to break unknowns by the dozen…
In your documents folder, there’s a file called “Startup.tmd”. That’s your default world loaded on every startup.
Start WM as admin. After all errors okayed, delete everything from the graph, including groups. After your world is blank, save it as Startup.tmd in the default documents folder (Basically resave startup file without legacy devices). That file is a leftover from your previous version. Should fix those errors.
If your own project files are also giving errors, there are two destructive ways to fix them:
Update all devices to latest versions using device updater (project>update devices). This is going to break the look of your world, so tread carefully.
If you don’t want your look to change, better download the installer of your previous version of wm from update center (archived builds). Clear everything, install your old version of wm, your files should open without errors. Or not, worth a try…
This startup crash and those errors have been a recurring problem here on the forums. Too many unknowns with this one, so be patient, work carefully through above. This is one of those “human error” scenarios that the developer can’t solve in code. We have to work through it step by step.
The afore mentioned “documents” folder is empty, no macros there.
I’ve been using 4032 since early last year.
The alternate machine is 4031.2, but I only use that for Erosion.
I tried to Update All Devices but there was no devices listed.
I reverted to version 4031.2, as I’ve never used anything older than that. It still crashes as usual.
Another strange thing that happens; when I place a Tiled File Input, it causes an immediate crash.
Regardless of whether it is 4032 or 4031 after a totally clean install.
4032, is a development build, ahead of 4031. Files and nodes created in 4032, cannot be opened in 4031 due to there being additional stuff that did not exist during 4031.
Files created in 4032, cannot work properly in 4031, as simple as that. That ship has sailed.
Using 4032, across your pipeline, should work around that crashing problem then. Fresh installs, start over. Tell your project’s recipients as well. Like I said, should stick with one WM version mid project
That said…
That “tiled file input” crash is a new bug I discovered maybe last week, and developer has not been seen anywhere for an year+…
The Tiled File Input Bug have halted WM operations here. Reported the bug a month ago, got one response back and then radio silence. The support ticket are still listed as open so there are still hope it might be solved. Crossing fingers here…
I’m having the same issue. It was working before. I have a graph using Tile File Input node from last year and when I open that project it wm crashes. I tried to create the graph from scratch but same issue when I add the node to the graph.
Hoping to the team can fix it soon.
