Milkshape 3D 1.8.4 error report.

Try *.ms3d import-export trough Khed (http://khed.glsl.ru/)

the newest is not necessarily the best. the exporters were designed long before 1.8.4 was there. with 1.8.3 though there are exporters for all cmp, sur, mat, that work fine.

@Freestalker.fr

You have done your model in Milkshape, and trying to export cmp, sur and mat, and Milkshape crashes - right?

1. Take Khed, import milkshape model into it and then save as new file with name anticrashmodel.ms3d

2. Take Milkshape, open anticrashmodel.ms3d and Try to export it again into cmp, sur and mat.

Well… just for some clarification…

I run 1.8.2, keep my PC fully upto date and am using Vista

no worries… and i dare say everyone else has fired up there own version on there PC after reading this.

Have you tried reinstalling it? & more so… WHATS THE ERROR… cant help if we dont know more sry… just telling us you get an error tells us nothing about your problem… & to be honest… you really should be asking Chumbalum soft what there product is doing as well.

I see lots of detours here…

I am using the latest version 1.8.5 beta with these plugins:-

SUR Importer v1,
SUR Exporter v1.1, (do NOT use v1.2 unless you know what happens),
adoxa’s CMP Importer 1.1.3,
CMP/3db Importer v1,
CMP Exporter v0.3,
3db Exporter v1.0.0.1
MAT Exporter v1.0

and all are working. (Windows XP).

First - it may be a bad plugin.

Uninstall MilkShape, delete the folder that it was in.

Install MilkShape again and start MilkShape. If it is OK, the problem is in one of the plugins you were using.

Add them only one by one to find the bad one.

If MilkShape does NOT start OK before adding the plugins, then it is a Windows problem with your system or a problem with your install file.

Get 1.8.5 beta and try again.

A trick i learnt modding stalker (and chasing specific module crashes)

Go into your control pannel (for your OS) goto Administrative Tools & open the Event Viewer. Do this just after Ms3d fails… and look for the most recent critical error… with some luck you’ll be presented with a readout of what just went wrong… and maybe what caused it.

for instance… at this moment in time… my WMA is crashing on exit (silly MS… grr) here’s what i get…

Faulting application wmplayer.exe, version 11.0.6002.18111, time stamp 0x4aa91411, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000374, fault offset 0x000afaf8, process id 0x13cc, application start time 0x01cb28964b51ab40

now i know i just installed MTX to try and play Mechwarrior4 Mercenarys (Failed by the way) and it played with my .net… obviously it screwed my ntdll.dll… and i now have a solution to my problem… reload my last current update for my .net framework.

That’s just an example… your problem could range from many things but you wont know untill you find out what (via the above instructions)

If I’ve interpreted it correctly, it should not be crashing there. Can you tell me the actual address? When it crashes again, click “click here” twice (at least, that’s what you do in XP) and tell me what the Address is (on the third line).

Sorry, that doesn’t help. I’ve attached a screenshot. The top window is the intial crash; click “click here” and you get the middle window; click “click here” and you get the bottom window. In the bottom window, tell me what’s after Address:. If it’s 0x00000000004E78A7, then I did interpret it right, but I don’t see how it would crash there.

Hm, maybe you have to disable error reporting to get the display I see. That can be done by bring up System Properties (Win+Break), clicking Error Reporting and disabling it. As ST says, another approach is to move *.dll from the milkshape folder (it’ll tell you which ones it needs to actually start), so you can eliminate a plugin problem. I also installed MilkShape as standard, not trial, so there could be something with that, too.