Hi, I haven't tried the CAVE functionality after it was finished, so there might be changes in Naali that makes the crashing as I never noticed such a problem myself. But the new cave view is created succesfully, the crash happens when the window goes to another physical screen, right? I would do as toni said, and experiment different screen extending setups to see if the problem persists.
On 1 February 2011 12:33, Toni Alatalo <[email protected]> wrote: > On Jan 31, 2011, at 12:29 PM, ilikia wrote: > > for my MSc thesis, I need to implement a multiple-screen realization > > with realXtend. The Cave functionality works initially just fine, but > > Sounds great. I'm coming to visit the uni this afternoon btw, from 13-> on > - might have time around 15 or so if you wanna show your crashes first hand > :) (call/sms 040 7198759 if want to meet, am curious to here about the > thesis if you want to tell what it is about). > > > as soon as I drag and drop the new viewer windows onto another screen, > > Naali freezes, creates a crash dump file and has to be stopped with > > Task Manager. This has happened five times now, a 100% failure rate. > > Mikko Alaluusua, who wrote the CAVE rendering module and has used it most, > is not at work today but can perhaps give hints later this week. > > Perhaps that is sensitive to how the multi screen setup is made, i.e. > whether the same desktop is streched over all or whether they are > independent etc. Perhaps someone who has used the CAVE stuff succesfully can > tell what they did, I've never tried it yet. > > > I've tried to make sense of the .dmp files, but they are in binary and > > even though I've opened them in a hex editor, I cannot figure out the > > reason of the crash. > > Those dumps are to be analyzed with microsoft visual studio. You can copy > the .dmp to where your viewer.exe lives, and if have msvc installed can just > click to open it there. Then press the play button to run it, and it shows > where the crash happened. > > Without the sources and a debug build or the PDB debug files you won't see > much -- but you might see in what dll the crash happens and what the error > type was, and sometimes a bit of a call stack, so it can be helpful. But > probably is required to add an issue to the google code tracker, attach the > dump, and we need to analyze it in a dev/debugging env. > > ~Toni > > -- Regards, -Mikko Alaluusua http://www.evocativi.com -- http://groups.google.com/group/realxtend-dev http://wiki.realxtend.org http://dev.realxtend.org -- http://groups.google.com/group/realxtend http://www.realxtend.org
