+- Wings 3D Development Forum (https://www.wings3d.com/forum)
+-- Forum: Wings 3D (https://www.wings3d.com/forum/forumdisplay.php?fid=1)
+--- Forum: ManifoldLab Plug-ins Collection (https://www.wings3d.com/forum/forumdisplay.php?fid=14)
+--- Thread: mlab crash on startup "werl.exe has encountered a problem...." (/showthread.php?tid=257)
Pages:
1
2
mlab crash on startup "werl.exe has encountered a problem...." - ConfusedCam - 03-24-2013
Hi all,
A little background. I use Wings3d to generate parts for the electronic PCB layout software KiCAD. I struggle at best with Wings3d, but I have a fair bit of experience using parametric/solid modelling CAD type programs.
One thing I struggle at is drilling holes, so easy in CAD, confuses the hell out of me in Wings3D. Anyway long story short I found mlab, and love the CSG operations, they help me a lot.
But latest builds of mlab crash on launch. Giving the helpful error "werl.exe has encountered a problem and needs to close."
Error signature
AppName: werl.exe AppVer: 0.0.0.0 ModName: beam.smp.dll ModVer: 0.0.0.0 Offset: 0004bb10
I tied it down to the exact version the crashes started at:
wings-1.4.1.2012-01-28---19-33.mlab.exe This is the last version that works for me.
wings-1.4.1.2012-03-18---17-51.mlab.exe This version crashes and so does every version after.
Comparing the two installs the difference that sticks out is, the working one uses beam.dll, the none working one uses beam.smp.dll
I also tried wings-1.5.pre1.74.g2aee.exe out of interest, it runs fine.
I have tried turning "Hardware acceleration" down on my graphics card as suggested in a couple of places on the net, it made no difference.
OS is Windows XP SP3, it's an oldish machine, graphics card is an AGP Sapphire ATI Radeon HD 4650.
Also tried on another XP sp3 box, and latest mlab build (wings-1.5.0.2013-03-24---09-42.mlab.exe) failed with a different error: "failed to start wings3d error:14001"
Tried the same build on a win7 box and it worked.
I am totally lost as what to try next, any suggestions ?
Thanks.
Cam.
RE: mlab crash on startup "werl.exe has encountered a problem...." - ConfusedCam - 03-25-2013
Does mlab have minimum requirements I am missing ? Is Windows XP still a supported platform for mlab ?
RE: mlab crash on startup "werl.exe has encountered a problem...." - ggaliens - 03-25-2013
Requirements are supposed to be exactly those of the host application, Wings3D.
I did TWO things for you and other BOOLEAN users today.
Retest on XP SP3. Worked.
Also release Boolean as separate plugin tested on OSX and Win32 with good results.
RE: mlab crash on startup "werl.exe has encountered a problem...." - ConfusedCam - 03-25-2013
I have solved the error:14001 problem. Can't imagine I will be the only person that needs this fix, as I tried "wings-1.5.0.2013-03-24---09-42.mlab.exe" on a totally unrelated XP box and got the same error. Anyway.
I ran this program: http://www.dependencywalker.com/ on werl.exe
It told me 'The Side-by-Side configuration information for "werl.exe" contains errors.'
It also reported that "msvcr80.dll" couldn't be found while walking the dependencies.
I then found this post about the problem: http://buffered.io/posts/resolving-side-by-side-configuration-issues
It lead me to this tool "Mainifest view by Kenny Kerr": http://weblogs.asp.net/blogs/kennykerr/ManifestView.zip
It tells you exactly what version of a dll set you need by reading the manifest embedded in the executable.
Turns out werl.exe needs Microsoft.VC80.CRT V8.0.50727.4053 and you guessed it, it wasn't installed.
Download it here and install http://www.microsoft.com/en-gb/download/details.aspx?id=14431
It's listed as "Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update" should this link change.
Error 14001 is gone, and I have mlab running on one of my XP boxes.
Still no idea why I get the error "werl.exe has encountered a problem and needs to close." on my other XP box. Grrrr !!!!!
RE: mlab crash on startup "werl.exe has encountered a problem...." - ConfusedCam - 03-25-2013
This maybe a red herring for my original problem. If I run the command line "werl.exe -smp enable" and nothing else I still get the error message "werl.exe has encountered a problem and needs to close."
I know nothing of ERLang, but does this simple test remove wings3d from the cause of the problem ?
Turning on -init_debug gives "{progress,preloaded}" in the ERLang window before the crash and nothing else.
EDIT: No it doesn't remove Wings3d from the problem. Next step with -init_debug switched on should be "{progress,kernel_load_completed}" which it does from the directory ".../wings3d/lib/kernel-2.15.3" I am guessing.
RE: mlab crash on startup "werl.exe has encountered a problem...." - ConfusedCam - 03-25-2013
OK I have to conclude the error "werl.exe has encountered a problem and needs to close." is partly hardware based. On the same machine I am seeing the error on I have installed on a different partition a very small and clean install of XP for rescue purposes. Installing wings-1.5.0.2013-03-24---09-42.mlab.exe under this OS gives exactly the same error. (It also gave the error:14001 but I can fix that now
)Given my hardware used to work with previous versions of mlab and that it still works with wings-1.5.pre1.74.g2aee.exe I have to assume it's not beyond scope to fix this. But unless a long list of people add to this topic I can understand that this is unlikely
Want to try the new TARBALL versions ? - ggaliens - 03-25-2013
Want to try the new TARBALL versions ?
If you have the all-in-one snapshot working ... you don't need to .... but these tar balls are supposed to be more PORTABLE.
RE: mlab crash on startup "werl.exe has encountered a problem...." - ConfusedCam - 03-25-2013
OK, i'll try anything once
I still don't have an up to date mlab working on my main box and forgive the noobness but I presume "wings-1.5.0.2013-03-24---09-42.mlab.exe" is the all-in-one snapshot ?
RE: mlab crash on startup "werl.exe has encountered a problem...." - ggaliens - 03-26-2013
Yes ... that is a very new snapshot all-in-one.
You said you wanted CSG. If that's most all you want out of MLAB ... then you relly need to think about using the Boolean tarball. It is much much much more likely to work ... if you already have a working HOST app for it ... such as an "OFFICAL BUILD".
RE: mlab crash on startup "werl.exe has encountered a problem...." - ConfusedCam - 03-26-2013
Sounds good, so how do I get my hands on the tarball then ?