Difference between revisions of "Talk:Env projectedtexture/fixes"

From Valve Developer Community
Jump to: navigation, search
(Flashlight works fine if I run through VS, but not through steam)
(Flashlight works fine if I run through VS, but not through steam)
Line 28: Line 28:
 
When I run the game through VS I can turn on my flashlight it runs fine, both in debug and release builds, whether I'm debugging or not. But if I launch the game through steam, the game crashes as soon as I turn on my light.  My game appears to be running the newest versions of the DLLs, I'm not getting the copy glitch. I'm not sure what to do. --[[User:Stoopdapoop|Stoopdapoop]] 04:02, 26 July 2011 (PDT)
 
When I run the game through VS I can turn on my flashlight it runs fine, both in debug and release builds, whether I'm debugging or not. But if I launch the game through steam, the game crashes as soon as I turn on my light.  My game appears to be running the newest versions of the DLLs, I'm not getting the copy glitch. I'm not sure what to do. --[[User:Stoopdapoop|Stoopdapoop]] 04:02, 26 July 2011 (PDT)
 
: What happens if you run through Steam, then attach the VS debugger to the process? --[[User:Artfunkel|Artfunkel]] 04:16, 26 July 2011 (PDT)
 
: What happens if you run through Steam, then attach the VS debugger to the process? --[[User:Artfunkel|Artfunkel]] 04:16, 26 July 2011 (PDT)
::It still crashes when I turn on the flashlight when VS is attached to the process. then it says there's no code available when I break. hmm. Is there an easy/surefire way to make sure that the they're using the same DLL's? --[[User:Stoopdapoop|Stoopdapoop]] 04:59, 26 July 2011 (PDT)
+
::It still crashes when I turn on the flashlight when VS is attached to the process. then it says there's no code available when I break. hmm. Is there an easy/surefire way to make sure that the they're using the same DLL's? my output window has these lines (among many others) when I run it through VS.
 +
<syntaxhighlight>
 +
'hl2.exe': Loaded 'C:\Program Files (x86)\Steam\steamapps\sourcemods\tfdmod\bin\Client.dll', Symbols loaded.
 +
'hl2.exe': Loaded 'C:\Program Files (x86)\Steam\steamapps\sourcemods\tfdmod\bin\server.dll', Symbols loaded.</syntaxhighlight>
 +
This leaves me under the impression that it's using the same dll's as the one steam uses.
 +
--[[User:Stoopdapoop|Stoopdapoop]] 04:59, 26 July 2011 (PDT)

Revision as of 12:12, 26 July 2011

crash

after adding most of those fixes the game crashes after adding a env_projectedtexture. what could be the problem?--Pfannkuchen 21:24, 28 January 2010 (UTC)

crash as well

I am also getting a crash only on maps with an env_projectedtexture after making the changes to: targeting, parenting, and number of textures in the game at one time. when are the going to fix this?--uromastix87 13:16, 2 April 2010

Where?

Where can I find all these files to edit? I can't figure out where Clientshadowmgr.cpp is.--Markboydude 05:51, 8 January 2011 (UTC)

In source code from Source SDK. Here is a little tutorial how to get and compile source code http://developer.valvesoftware.com/wiki/My_First_Mod --Kave 10:25, 8 January 2011 (UTC)
Well what if I wanted to fix it for a game that already exists e.g. Counter-Strike: Source? --Markboydude 18:52, 12 July 2011 (PDT)
That's not possible. --Artfunkel 07:42, 13 July 2011 (PDT)

Crash

After adding code from Fixing targeting.

Crash happens on maps only with Env_projectedtexture.

Other stuff is work.

Flashlight works fine if I run through VS, but not through steam

When I run the game through VS I can turn on my flashlight it runs fine, both in debug and release builds, whether I'm debugging or not. But if I launch the game through steam, the game crashes as soon as I turn on my light. My game appears to be running the newest versions of the DLLs, I'm not getting the copy glitch. I'm not sure what to do. --Stoopdapoop 04:02, 26 July 2011 (PDT)

What happens if you run through Steam, then attach the VS debugger to the process? --Artfunkel 04:16, 26 July 2011 (PDT)
It still crashes when I turn on the flashlight when VS is attached to the process. then it says there's no code available when I break. hmm. Is there an easy/surefire way to make sure that the they're using the same DLL's? my output window has these lines (among many others) when I run it through VS.
'hl2.exe': Loaded 'C:\Program Files (x86)\Steam\steamapps\sourcemods\tfdmod\bin\Client.dll', Symbols loaded.
'hl2.exe': Loaded 'C:\Program Files (x86)\Steam\steamapps\sourcemods\tfdmod\bin\server.dll', Symbols loaded.

This leaves me under the impression that it's using the same dll's as the one steam uses. --Stoopdapoop 04:59, 26 July 2011 (PDT)