[Linux] Loading Shaders stuck

cojack

Hello,
I just bought the game and could not run tutorial during those errors in log file, it says:

[ 25.342] Worker 07 : Error: shaders/GorgeTunnel.screenfx:24 : Parameter 'noiseMap' doesn't exist in shader
[ 25.342] Worker 07 : Error: shaders/GorgeTunnel.screenfx:24 : Parameter 'baseTexture' doesn't exist in shader
[ 25.342] Worker 07 : Error: shaders/GorgeTunnel.screenfx:24 : Parameter 'amount' doesn't exist in shader

And It sometimes crash, sometimes freeze without crash. In annex I append also a few information about fglrx that I have

My kernel is:

Linux cojack-desktop 3.16.0-28-generic #38-Ubuntu SMP Fri Dec 12 17:37:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Could you help guys?

GhoulofGSG9

I get the same errors on windows. So i guess that's not really the reason you crash. Could you attach gdb to ns2 and get us a full backtrace?

cojack

GhoulofGSG9 wrote: »

I get the same errors on windows. So i guess that#s not really the reason you crash. Could you attach gdb to ns2 and get us a full backtrace?

I will try, give me a sec.

cojack

Sorry, but I have no idea how to run game in dbg mode, I just found an option to run a steam in dgb, but game runs it's own space out of the dbg, any tips?

devel

Freeze-loading bug is back. Looks similar to the problem in the 269 build:
http://forums.unknownworlds.com/discussion/comment/2220883

But I can't reproduce it.

cojack

I could not attach gdb to the ns2 process, an errors is in an annex, or Im doing it wrong.

cojack

Im newbie so forgive me, after attach an gdb to tthe process I forgot to continue the process, so in annex there you are an output from gdb with steam and ns2. What can I do to help more?

GhoulofGSG9

So far you figured out how to use gdb All you need to do now is to wait for ns2 to crash with a segfault and then run bt full.

SamusDroid

I've heard of this error before with the same shaders but I don't know what causes it.

cojack

In annex there is a file with full gdb program runs, what did I do? I just modifiy the file run.sh in

~/.local/share/Steam/ubuntu12_32/steam-runtime/run.sh

to exec a program in gdb:

exec gdb "$@"

After this you will have a full list of what happend step by step, around 182 line, gdb crash by him self (strange situation, kind of bug) and I run it once again as you can see in 200 line number after this game crash and you have bt full from lines 357

What can I improve in this stack is that I can install an -dev packages for debugger symbols but it will be only an libc and fglrx, and I don't think so it will help you guys

I'm also an programmer

Tell me how can I help you, to fix this error.
Regards.

cojack

Any progress?

SamusDroid

I can't see anything that would cause that error in the log. Though it seemed to not happen the second time you loaded the map

cojack

How can I improve those stack trace from gdb?

GhoulofGSG9

cojack wrote: »

How can I improve those stack trace from gdb?

Those are totally fine but your issue seems to be related to awesomium which is a third part lib so nothing we can fix directly.

cojack

Maybe I will compile new libawesomium v1.7.5.0 and try to replace the old one? Any tips?

devel

That malloc part looks like gperftools compiled statically into awesomium. You can override some of its functions through LD_PRELOAD and suppress the assert. Maybe it won't crash afterwards.