Modcraft - The community dedicated to quality WoW modding!
Featured => Noggit => Topic started by: detonatorss on January 11, 2013, 09:15:04 pm
-
56716 - (MapView.cpp:419): [Debug] 165-Import.txt
57938 - (errorHandling.h:64): [Error] There was an exception of type "SIGSEGV"
"Invalid storage access; most frequently caused by attempting to store some value in an object pointed to by a bad pointer. (Segment violation.)".
Please excuse the inconvenience. You may want to report this error including the log to the developers.
57950 - (StackWalker.cpp:1133): [Error] OS-Version: 5.1.2600 (Service Pack 2) 0x100-0x1
58683 - (StackWalker.cpp:1133): [Error] 0113721C (noggit): (filename not available): (function-name not available)
58683 - (StackWalker.cpp:1133): [Error] 01108CA7 (noggit): (filename not available): (function-name not available)
58684 - (StackWalker.cpp:1133): [Error] 676EB9DF (MSVCR100): (filename not available): XcptFilter
58685 - (StackWalker.cpp:1133): [Error] 01168B6B (noggit): (filename not available): (function-name not available)
58685 - (StackWalker.cpp:1133): [Error] 768933CA (KERNEL32): (filename not available): BaseThreadInitThunk
58686 - (StackWalker.cpp:1133): [Error] 774A9ED2 (ntdll): (filename not available): RtlInitializeExceptionChain
58687 - (StackWalker.cpp:1133): [Error] 774A9EA5 (ntdll): (filename not available): RtlInitializeExceptionChain
it's strange becuase it's a ported WMO from MoP, in noggit sdl 1.1 works corretcly but however the bug for save wmo shit my life in noggit sdl 1.2 i have this error i don't know why, because in noggit sdl 1.1 works correctly
-
Everything under errorHandling.h is useless to us. We need the part over it, the actual log.
And I don't even get what your problem is. Something about a ported WMO that works in 1.1, but not in 1.2, while we don't even know what your problem is. Noggit crashing ? Noggit not saving WMOs ? Noggit not loading WMO up ?
-
when i import the WMO the noggit crashes
sorry for my bad explanation
-
Why is this even here ? Moved into the noggit area. Also, MoP WMOs were not concepted to be loadable into Noggit. The differences, or rather, the required changes to make them work for WoW are not even known.
-
but i have the same problem of one WMO of 4.0.6a and i don't know why
-
Because noggit only load WMOs of 335a.
But if we had rep you would get now +2 for the cool title of the topic ;)
-
but it's the true steff XDDD, i dont know how to load ported wmo from cata or mop XDD, i am idiot i know it but i am trying it XD
-
but it's the true steff XDDD, i dont know how to load ported wmo from cata or mop XDD, i am idiot i know it but i am trying it XD
Because we have no "safe" way of porting WMOs from Cata+ to WotLK. This area is yet to be disclosed.