trouble with light gem in /dev/shm on Linux

[lost_soul]

I'm using Ubuntu 10.04, 64-bit. I have doom 3 installed in an unusual directory, but it is symlinked to /usr/local/games/doom3. When I play TDM, the light gem is totally black (except for during mantling). The guards cannot see me. The console is constantly flooded with "cannot open ../../../../dev/shm/tdm_lg.tga" or something like that. Any ideas?

I checked, and a file exists in /dev/shm, but it is blank. When I installed Doom 3, I just restored it from my external hard drive, rather than running the installer again. Could this be the problem? Doom 3 plays fine.

[aidakeeley]

the guards cannot see me.

 

That's weird...

 

The console is constantly flooded with "cannot open ../../../.. /dev/shm/tdm_lg.tga" or something like that

 

You probably oughta dump it (console command "conDump") and find out what it is saying; I imagine that the problem, the big weird one, described above is due to more than a missing tga.The dump file will end up in the directory of the mission you are playing.

Edited June 24, 2010 by aidakeeley

[nbohr1more]

Yeah, this reminds me of the following entry in our wiki:

 

Game exits to menu after mission load, with renderpipe error in console

Symptoms: Missions are installed properly and will load, but after they reach 100% you are returned to the main menu or objectives screen. If you open the console (Ctrl-Alt-~ on US keyboards), you see one/both of these errors:

 

ERROR: Failed to open \\.\pipe\dm_renderpipe

or

 

ERROR: idRenderSystemLocal::uncrop currentcrop <1

Solution: Some firewalls, notably Sunbelt Firewall (aka Kerio Firewall) are known to interfere with TDM's lightgem, even when "disabled". To fix this problem, completely uninstall the firewall, and get a different one instead.

 

[OrbWeaver]

I have doom 3 installed in an unusual directory, but it is symlinked to /usr/local/games/doom3.

 

Probably best not to do this. My guess would be that the symlink is causing Doom 3 (or perhaps the mod code) to get confused as to where /dev/shm can be found, although I'm not sure why a relative path would be used in this instance.

[Tels]

Probably best not to do this. My guess would be that the symlink is causing Doom 3 (or perhaps the mod code) to get confused as to where /dev/shm can be found, although I'm not sure why a relative path would be used in this instance.

 

/dev/shm ist shared memory, are you sure that you don't have a limit on this? (maybe not enough shared memory, or your user cannot write there?)

 

What does

 

dir /dev/shm/

 

or

 

ulimit

 

say?

 

I have doom also installed locally in my home dir and symlinked it to /usr/games/local, so it should work that way.

[lost_soul]

Nevermind. I fixed it! I just deleted Doom 3 and TDM and re-installed them. I've still got /usr/local/games/ (where doom 3 is) linked to another partition, because my slash is only 12 GB.

[Tels]

Nevermind. I fixed it! I just deleted Doom 3 and TDM and re-installed them. I've still got /usr/local/games/ (where doom 3 is) linked to another partition, because my slash is only 12 GB.

 

Ah that's good to know. I too have linked tons of directories away, beause I started with a 6Gb root some years back and every upgrade has left me struggling to find the needed space to start the update (tho the actual spaces like /tmp and /opt and whatnot used are in the giant /home partition but the stupid Kubuntu updater isn't able to figure this out... and everyyear the trick to convince it no longer works and you have to find a new one..*sigh*)

 

Anyway, glad you can play now!