Re: [CsMain] Issues with Walktest Application

There are some more issues that I am facing again with the walktest
application. I am able to get the walktest application work with the default
castle map, but it doesnt seems to be working with the cornell map (with or
without the lightmaps).

When I try to run the walktest application with the cornell map, it just
shows a black screen with the crystalspace logo. There isn't any error
message produced on command line, too.

Any method to debug it, or any known issue with the cornell map, I am using
the cornell map in the data folder of trunk.

Regards,
Mohit Taneja


On Sat, May 29, 2010 at 11:43 PM, Mohit Taneja <[email protected]> wrote:

> Hi,
>
> I shifted onto windows with visual studio 2008, and the build procedure was
> pretty simple, and walktest with most of the other things is working.
>
> As for Ubuntu , it is still in the aftermath of mesa crisis, I think I
> would have to probably reinstall it.
>
> And as of now I am back to work, thanks for the help.
>
> Regards,
> Mohit Taneja
>
>
>
> On Sat, May 29, 2010 at 12:50 AM, Mohit Taneja <[email protected]>wrote:
>
>> Hi,
>>
>> I downloaded the source of mesa 7.8 (it contains the library i915_dri.so)
>> , earlier version which I was using was mesa 7.4. I compiled it from source
>> and installed but but still no success, and sadly after a restart my Xorg
>> environment isnt working :(  ( which means no desktop environment available
>> on Ubuntu).
>>
>> I will try to fix that out by reverting it to previous version and would
>> keep you updated of any progress.
>>
>> Regards,
>> Mohit Taneja
>>
>>
>> On Fri, May 28, 2010 at 4:29 AM, res <[email protected]> wrote:
>>
>>>  On 28.05.2010 12:08, Mohit Taneja wrote:
>>> > I am attaching the logs of the error I got after debugging it in gdb.
>>> > Any help would be great.
>>>
>>> Uhm. It crashes in i915, the graphics driver. Basically, that's not that
>>> good, as it's hard for us to debug/fixing the drivers as well...
>>>
>>> _Maybe_ there's some kind of workaround... but can't say yet. Anyhow,
>>> more information would be worthwhile; you can use the command line
>>> parameter “-verbose=-scf” to make CS more “talkative”. The output just
>>> before the crash may or may not give a clue on what happens.
>>>
>>> Besides that, look if there is a newer driver version or such available.
>>> Look if there is a “debug symbols” package or so available for the
>>> driver - that will make the backtrace more useful and may help to
>>> identify the issue. Maybe it's already fixed, so consider compiling a
>>> newer version from source.
>>>
>>> -f.r.
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>>
>>> _______________________________________________
>>> Crystal-main mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/crystal-main
>>> Unsubscribe: mailto:[email protected]
>>> ?subject=unsubscribe
>>>
>>>
>>
>

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo

_______________________________________________
Crystal-main mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crystal-main
Unsubscribe: mailto:[email protected]?subject=unsubscribe