Hello, I have been using UE with no problems. After updating to UE 2.0 I get nothing but crashes. It may be my settings. Please take a look.
windows error log.
Application Name: UE.exe
Application Version: 2.0.0.0
Application Timestamp: 4837f180
Fault Module Name: kernel32.dll
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bd80
Exception Code: e06d7363
Exception Offset: 0001b09e
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Information 1: b5ae
Additional Information 2: 799a7cf9ff1b6fd2b2ab1f334dbec022
Additional Information 3: a42c
Additional Information 4: b1c22f34670e0d106b95998c9adb3806
Thank you
sid van
Exception Code: e06d7363 (AVAST)
E06D7363 is most likely file exception.
can you check what is in log.txt in the ue database directory?
it tracks a little more info than that, so i could see where the crash would origin from.
you also may well see a reason like "acess denied", sometimes firewall may cause it, also 6.0 is vista and it could be some executable permission issue because you changed the executable.
do you get UE error box at all or the system somehow intercepts the exception before UE? it tells you to check/email log.txt, not to refer to limited windows crash info.
Later: after further checking the matter through email, it was found out the problem was AVAST antivirus which appears not to handle replacing executables properly, maybe it tried to plug in into UE in the wrong place based on old executable. while turning AVAST off solved the problem - deleting and then readding UE into the antivirus definitions if there is such thing there could fix it as well.
can you check what is in log.txt in the ue database directory?
it tracks a little more info than that, so i could see where the crash would origin from.
you also may well see a reason like "acess denied", sometimes firewall may cause it, also 6.0 is vista and it could be some executable permission issue because you changed the executable.
do you get UE error box at all or the system somehow intercepts the exception before UE? it tells you to check/email log.txt, not to refer to limited windows crash info.
Later: after further checking the matter through email, it was found out the problem was AVAST antivirus which appears not to handle replacing executables properly, maybe it tried to plug in into UE in the wrong place based on old executable. while turning AVAST off solved the problem - deleting and then readding UE into the antivirus definitions if there is such thing there could fix it as well.