I start city engine, it loads, gets to open file and crashes before it finishes loading. Any ideas why?
thanks in advance
dave
all files? or just that one?
try to rule out, it opens, from it opens with X, it crashes with Y.
And can you test Y on another installation elsewhere or are you in an isolated environment (ie single machine, single install)
I tried a couple of files that were both working fine until this morning. SIngle seat, single machine unfortunately.
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffa28a24eba, pid=7140, tid=6472
#
# JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [com.esri.prt.core.dll+0x254eba]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Dave, the only thing remotely containing java, crash and city engine within the last year is
https://community.esri.com/message/573817
I would just file a support request, in case it is something new with your environment and updates.
Thanks so much. I had a look and didn't see any others. I got a service
ticket from esri and will try and reinstall monday when my IT admin get a
minute. I'll keep you posted. Regards
Dave
Here are some general fixes:
I think a corrupt .prtcache might be the cause, I had some troubles with broken images in version 2014 that caused loads of crashes when generating buildings. Try removing your resource folders as well.
Thanks for the advice. I'll be back in the office monday and will give it a
go.
Regards
Dave
This might actually help me with some of my experiences lately, but they seemed to have resolved without deleting the prtcache/metadata folders yet.
Renaming the the file did the trick. Thanks for the advice.
That let me get to the file and after regenerating the objects, one collada
file was triggering the grief.
Made changes and all is good.
Now I am waiting for my I.T. dept. to run the update and solve all my other
bugs.
Looking forward to it and thanks all for the response and advice.
Very much appreciated.
Dave