Cool VL Viewer forum

Pity, the newest Version dont work on my laptop..

I did install.
I try a TP and i crash.
relog: I see myself at the targeted location, but a second later the viewer crashes.
relog again 2 times: world is loading but then crashing after a second or so.

btw: When the viewer started the first time, and crashed during the TP it did not created dmp file. But after or during the follwing sessions.

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

Cool VL Viewer 1.26.8 (9) Jun 1 2013 11:05:40 (Cool VL Viewer)
Release Notes

CPU: Intel(R) Core(TM) i3 CPU M 380 @ 2.53GHz (2527.5 MHz)
Memory: 3958 MB
OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: ATI Mobility Radeon HD 5400 Series
Windows Graphics Driver Version: 8.17.0010.1132
OpenGL Version: 4.2.11733 Compatibility Profile Context

libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
J2C Decoder Version: KDU
Audio Driver Version: FMOD version 3.750000
Qt Webkit Version: 4.7.1 (version number hard-coded)

Built with MSVC version 1600

Compile flags used for this build:
-DNDEBUG -DLL_RELEASE=1 -DLL_RELEASE_FOR_DOWNLOAD=1 /O2 /Oi /arch:SSE2 /MD /MP /D_SECURE_SCL=0 /D_HAS_ITERATOR_DEBUGGING=0 /DWIN32 /D_WINDOWS /W3 /EHsc /GR /Oy- /GS /arch:SSE2 /fp:fast /TP /W2 /Zc:forScope /Zc:wchar_t- /c /nologo /DLL_WINDOWS=1 /DDOM_DYNAMIC /DUNICODE /D_UNICODE /DWINVER=0x0501 /D_WIN32_WINNT=0x0501 /DLL_USE_OLDFILESTREAMS=1 /DCARES_STATICLIB /DCARES_STATICLIB /DLIB_NDOF=1

It looks like an object in your avatar's environment is crashing the viewer: at what exact position in SL are you getting this crash ?

I found potential (though very unlikely) crash bugs in the code, but they should affect any viewer and need to confirm I squashed yours.

My exact position should have been my homepoint which is:
http://slurl.com/secondlife/Sondraman/166/219/79

update:
I changed location with the older 1264 to http://slurl.com/secondlife/Mexico%20Sonora/144/14/70. Then logged in with 1268. I walked around and all was good. Then i teleported to some other location at http://slurl.com/secondlife/COCO%20DESIGNS/97/218/22 and crashed. I logged in again, world loaded at the new, targeted point fine, I walked around. After a while I tepelorted again to another location. And crashed again.

Been there... No issue at all, and no, the crash log shown that you were in region Pak, but I don't know where exactly... Please, also try clearing your cache (especially the object cache) and see if it solves the issue...

Err... The current ATI graphics driver for your graphics card is v13.4, and you are running an hyper-old v8.17... Please, update !!!

Thanks, Henry,

btw.. my litte programm GPU-Z says i am running Driver version ATI Calalyst 12.6. ok, 1 year old...
(I tried to update, but after that the viewer showed a somehow weird slighlty destroyed image and even no tp-possibilty as usual so I went back to old version.)

However, I also cleard cache. Took no effect.

Now:
With the official viewer of linden from april this year I can teleport.
with Singularity Viewer 1.8 I can make snapshots and teleport.
Shall I try something else or wait for other updates?

The problem is that I cannot happen to reproduce your crash...

Note that running an up to date (and non-beta) graphics driver is of utmost importance with v1.26.8 (that uses the newest renderer, with modern OpenGL calls that only recent drivers can cope with properly): the viewer should not show "Compatibility Profile Context" in the About floater like it did, for example (this is the sign of missing OpenGL calls in your driver).

Also, make sure your graphics driver is not configured system-wide to override the applications' settings (such settings as ATI's "AI" can do that), since this cripples thing very badly: always choose "let the application decide" for all system-wide settings in your drivers control panel.

Try today's v1.26.8.10 release and post the log and crash dump if it still crashes for you. Also join your settings_coolvlviewer_1268.xml file (it could be a settings-dependent crash).

Henry, know what? That's COOL!
The bug is'nt no more in the 1.268.10.

Even with Compatibility Profile Context. (And of course I already always had let the applications decide the settings)

Thanks!