It is currently Fri May 31, 2024 6:16 am


uNCLEsAM098 wrote:Hello there. Sorry if I'm posting in the wrong area, I didn't see an area better suited for Mod Help.

Gary wrote:uNCLEsAM098 wrote:Hello there. Sorry if I'm posting in the wrong area, I didn't see an area better suited for Mod Help.
There is a programming subform: viewforum.php?f=25
Moved.

Well, in all honesty, if you have problems to follow tutorials to the letter (I didn't use 'exactly' the line provided (libc;libcd;libcmtd)) then yeah, programming is gonna be nearly impossible for you.uNCLEsAM098 wrote:Well, you won't believe this, but the problem lied within that I didn't use 'exactly' the line provided (libc;libcd;libcmtd). Once I changed that (trying things desperately), the problems went away. I dunno why, I had those three portions plus more... Anyway.
Is there some simpler form of doing this? I feel like I'm constantly hitting every error known to man. There's got to be something simple I'm screwing up.
Can you be any vaguer? What is the issue? Please dont tell me you dont know how to change directories in a link.uNCLEsAM098 wrote:Another problem came up. I installed Steam within a custom folder inside my D drive (I've always done this), but now it turns out that there's a problem with that location.
Because I did not have Steam installed in the Program Files (x86) location, I'm having issues here:
https://developer.valvesoftware.com/wik ... mmand_line
the sdk was written in 2005, most likely because when hl2 was made visual studio 2010 didn't exist. And yeah, compiling in 2005 probably enables you to run the code straight from the box, but 2008 and 2010 work fine as long as you follow the tutorials to fix the code.uNCLEsAM098 wrote:------------------------------
A second question. I saw another thread that seems to have a similar problem: viewtopic.php?f=25&t=36004
According to that thread, running Visual Studio 2010 is a problem. Is that true? Is 2005 the best to run for this? Is this why I'm having so many problems?
------------------------------

zombie@computer wrote:Well, in all honesty, if you have problems to follow tutorials to the letter (I didn't use 'exactly' the line provided (libc;libcd;libcmtd)) then yeah, programming is gonna be nearly impossible for you.uNCLEsAM098 wrote:Well, you won't believe this, but the problem lied within that I didn't use 'exactly' the line provided (libc;libcd;libcmtd). Once I changed that (trying things desperately), the problems went away. I dunno why, I had those three portions plus more... Anyway.
Is there some simpler form of doing this? I feel like I'm constantly hitting every error known to man. There's got to be something simple I'm screwing up.
zombie@computer wrote:Can you be any vaguer? What is the issue? Please dont tell me you dont know how to change directories in a link.uNCLEsAM098 wrote:Another problem came up. I installed Steam within a custom folder inside my D drive (I've always done this), but now it turns out that there's a problem with that location.
Because I did not have Steam installed in the Program Files (x86) location, I'm having issues here:
https://developer.valvesoftware.com/wik ... mmand_line


uNCLEsAM098 wrote:I did change the location, and properly changed it dependent on the location of my test modification. I'm not sure what else I'm missing, but if there's any information I can give to clarify the issue, let me know and I'll post it.






Gary wrote:Right click the mod in steam, goto advanced options and add -allowdebug to the command line.








stoopdapoop wrote:nice work.
I would reccomend compiling release builds over debug builds though. They're faster and almost as easily debugged.
Gary wrote:Asserts are always going to happen in debug. I recommend running the mod in windowed mode.

Users browsing this forum: No registered users