Talk:Common L4D Mapping Problems: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
No edit summary
Line 4: Line 4:


:If you're sure it's not the stringtables issue, I'd start with removing all the new entities that came with L4D and see if that fixes it. I've scene some of them (func_simpleladder, beam_spotlight, etc) cause random crashes before. --[[User:Brandished|brandished]] 19:23, 23 February 2009 (UTC)
:If you're sure it's not the stringtables issue, I'd start with removing all the new entities that came with L4D and see if that fixes it. I've scene some of them (func_simpleladder, beam_spotlight, etc) cause random crashes before. --[[User:Brandished|brandished]] 19:23, 23 February 2009 (UTC)
::Wait, could this be the string tables crash? The map has already ran, and I didn't need to bother with it.  I'll have to try that out first. --[[User:CorporalAris|CorporalAris]] 12:27, 24 February 2009 (UTC)

Revision as of 05:27, 24 February 2009

crash to desktop

I'm getting a crash to desktop with my new map. I am trying to test it, and it starts loading, but before the loading bar moves, it's dead. Any suggestions? --CorporalAris 04:17, 23 February 2009 (UTC)

If you're sure it's not the stringtables issue, I'd start with removing all the new entities that came with L4D and see if that fixes it. I've scene some of them (func_simpleladder, beam_spotlight, etc) cause random crashes before. --brandished 19:23, 23 February 2009 (UTC)
Wait, could this be the string tables crash? The map has already ran, and I didn't need to bother with it. I'll have to try that out first. --CorporalAris 12:27, 24 February 2009 (UTC)