[shen.de]

EDIT BY MIHAI:

If you also experience the issue described below, please re-download the installer from the Customer Portal download area, and re-install Maxwell. There is no need to run the licensing process again, or also re-install the licensing server. Only re-install Maxwell.

-----------------------------------

hi,

my mxed exe seems to crash on a lot of occasions. when I save a material and reopen the manager, material previews are broken and mxed crashes, or the program crashes while loading the thumbnails, or mxed crashes when trying to open a material. then sometimes when starting mxed again it crashes immediatly.

so right now it's impossible to work with it in any way.

any ideas?


cheers

[Bubbaloo]

Maybe V3 didn't install correctly?

[Half Life]

I have had this happen today as well, I found the cause was trying to save out v3 changes made to old v2 MXM files that somehow got assigned the property of "read-only".

The solution was to the set my main materials folder properties so that "read-only" is disabled for all files and sub-folders (Right-click on the folder and go to "properties").

You may have to restart the computer first so that the never ending saving process gets shut down first... I actually had to repeat this process (changing the read-only setting) twice before it was resolved.

Best,
Jason.

[shen.de]

I can't get the folder to turn off "read only" ... it always switches back

the materials are broken now. whenever mw tries to read them no matter where they're lying mxed or even studio crashes.

[Half Life]

Make sure you have full security privileges for the folder.

Once I got it straightened out, it all works fine -- but it took me about an hour of poking around to figure out exactly what the problem was, and how to resolve it. But yeah, Studio and MXED both were freezing/crashing constantly until I got it sorted.

Best,
Jason.

[shen.de]

ok i applyed foldersettings but doesn't seem to fix it.

i alway get this error report:

C:\Users\xxxx\AppData\Local\Temp\WER4AE4.tmp.WERInternalMetadata.xml
C:\Users\xxxx\AppData\Local\Temp\WER6E0E.tmp.appcompat.txt
C:\Users\xxxx\AppData\Local\Temp\WER7495.tmp.mdmp

[Half Life]

I am unable to recreate the problem on my old Windows XP 32-bit system at home -- so I'll take a look again when I get into work. No matter what, the "browser" side of MXED is acting funky (both here and at work, showing wrong previews and such) so I gave up using it, and just started double-clicking the actual MXM files to launch them in MXED.

I haven't had any issue with newly created v3 materials, so it definitely seems to be related to something in the process of opening and saving changes to old v2 MXMs. Is this what you were doing when the problem hit you too?

One thing that I implied, but didn't state outright, was that on my system the MXED process was still hung up (even when closed) -- so I had to stop the process. It wouldn't even let me delete some bad MXM's because it said they were still open in MXED. There are other ways to stop a process, but (to be absolutely sure all the crud is cleaned out) I always restart the system before making these types of changes.

Best,
Jason.

[shen.de]

I haven't had any issue with newly created v3 materials, so it definitely seems to be related to something in the process of opening and saving changes to old v2 MXMs. Is this what you were doing when the problem hit you too?

yeah. first i just pasted mw 1.7. materials to the v3 material folder in order to tweak them for v3 and save 'em.
but after the crashes I also tried to delete all 1.7 materials and folders and made clean new folder with new setup materials.

but what I recognized the crashing seems to occure only on materials with textures. hadn't had a crash with a new setup plastic.

furthermore although the previews are broken and the mxed crashen on them, the materials seem to render just fine. no problems on renderings so far.

One thing that I implied, but didn't state outright, was that on my system the MXED process was still hung up (even when closed) -- so I had to stop the process.

hadn't had this problem.


thanks for your help.

[Half Life]

I tried to recreate the initial bug by copying old v2 MXM files over to v3 and editing them in MXED -- but whatever permisions/file association errors that got me yesterday were not reproduced.

So the bad news is I can't offer any new advice... but the good news is it seems once the issue is sorted out you'll never need to worry about it again.

Best,
Jason.

[Half Life]

I spoke too soon... so I tried something else, and the problem reappeared.

I opened the default and default97 MXM's in the root MXM folder... made edits to them, and saved them back out. Then I started opening some materials that have textures and did nothing but render new larger previews. After I did six I tried to close MXED and I got the crash again...

When I re-opened MXED the browser thumbnail for default97 appears corrupted. If I navigate the browser to the folder containing the six re-rendered MXM's I get a crash... if I attempted to open any MXM I got the locked up MXED and a crash. I checked the file permisssions and there was nothing amiss...

I restart the system, and everything seemed to work normally again.

Hopefully the devs can figure this one out, because it seems pretty weird to me.

Best,
Jason.

[Half Life]

So I broke it a few more times to get to the place where both MXED and Studio were completely unuseable. Then I reset my permisions for the materials database folder ( both security and disable read only) , restart the system and all is good again... except the browser is still buggy.

Actually I suspect this is where the problem lies, as long as I don't use the browser everything seems fine... I wonder if there is some issue occuring when the browser thumbnails are being rendered.

Best,
Jason.

[shen.de]

yup. I think the problem is mxed browser/preview based.

maybe a dev can have a look into it. I mailed the tech support this morning via user comtrol panel but no answer yet whatsoever.

[Half Life]

I'll post the latest example of an MXM with corrupted preview which causes freezing/crashes -- perhaps something special about it can be identified by the devs.

Best,
Jason.

[JDHill]

We have been looking into it. It definitely appears to be an issue specific to the Studio/MXED browser. I think it's a threading problem, and that your MXM files are not actually corrupted -- you should be able to confirm that by noticing that the Maxwell thumbnails plugin has no problem reading previews from your MXM files, when viewed in Explorer.

[Half Life]

Actually it appears corrupted in Explorer, which is why I sent it along.

Best,
Jason.