I can’t fully determine why. This was on a child’s computer (Windows 10), so I originally thought it was file privileges, but the same thing happens on the Windows Admin profile or even with RunAs… It installed without error, and the redistributable also seemed to install. But we cannot seem to start the software at all. It has never started. We’ve uninstalled, deleted all cache, deleted the %APPDATA% folders, etc.
Now, it’s just an older desktop with integrated graphics… is 3D acceleration required? If so, a more descriptive error message would help.
No matter what it either behaves as though we never tried to start World Machine or gives us the error above. I also grabbed the crash reports and attached them.
Two assumptions I’m making. First, you sent a bug report using that dialog, with exact steps to reproduce in the “Additional details” box. Second, you’re on the latest stable or development build. The latest Stable build is 4046, and dev build is 4048. I have both of those installed on my machine, and both work as expected initially. 4048 does use more memory when using macros, but that’s a functionality issue and not a bug.
That said, did you install with the admin account or your child’s account? A guest account may have skipped some files silently during install, so make sure to do another clean install from the admin account. If not, I don’t know what else could be the issue. If you sent your bug report, just wait for a response.
World Machine does require a GPU to function, but an integrated one should be sufficient. One of the first things it does is checks for OpenGL >=3.2 on startup, which your system apparently indeed has.
I took a look at your crash file. It appears that OpenCL is crashing upon initialization on your system. The system reports that OpenCL is available (which is why WM is attempting to use it), but the platform code crashes somewhere deep in its own bowels. Unfortunately, these kinds of experiences are not uncommon on integrated graphics setups, particularly older ones!
If WM is able to get far enough to setup your user config file (world.ini) in %APPDATA%\World Machine Release, you can fix this there:
Search for the line ‘Compute_enabled=1’ within the INI file. That line may or may not exist yet.
If the line does exist, change the end to a 0 and save.
If it does not exist, add Compute_enabled=0 to anywhere within the INI file.
If there is no world.ini file in the above folder, there should be one under ‘Program Files\World Machine ’. You will need admin rights to change the file in that folder.
This should allow WM to start on your system. You will be unable to use the custom Code device but otherwise the impact should be pretty minimal.
