But a 3500 GTX? What the hell is that?Exageration, plain simple ;), I mean that those guys are capable of buying a 600€ gpu and the next month buy another of 1000€ just because it gets "outdated" (those high end pcs ended in the second hand market).
Oh screw it, I'll call the entire town nearby to celebrate! Just kidding XDA girl did that kind invitation...
It will always be like that until I build an actual PC, so please, stop telling me to get newer programs, just stop, because I can't.The moto I did to you was made with the Athlon system. Go figure...
How could I shoot you from an empty gun?Even with a pan one could be lethal (ask Rapunzel)
Even if I could hit you with the stock, I wouldn't, because:Nothing more truth, I love to live...
1. It's insanely immoral and useless
2. Respect for the elderly (you're 1 of them)I don´t agree, I am THE ELDER...
3. I have no intention to damage/hurt/kill anyoneI know, only a bunch of targets, I love sharpshooting too
4. It's a terrible sin in my religionForget religion, read your own point 1.
5. I'd break the lawNot if we play a deathmatch game, on that case points 1,2,3,4 and 5 are pointless ;), one day we should do that, man!!
Seriously, do I look like I care? My avatar says it all.Your avatar says that you are near to blow my head off with that rifle just because of saying that Max is harder to learn!!, hahaha!!
Max needs plugins to export and import SMDs, while Milkshape supports it natively. Good idea =DKnew that!!, once upon a time I tried to do something with Max (1998 I think it was) and almost go nuts...
I can't get used to Milkshape's controls, too. So, I'll use 3ds Max.Cool!!
, you can do it savig the file as 3ds or obj, ages ago I have studied the 3ds files for the hgrunt included into the HLSDK v2.3. 
But on that case I remember that it uses also a roundereset entity to make the chicken re-appear. :/The last project I successfully finished only succeeded due to it's own sheer simplicity, and allowing myself to be satisfied with it's simplicity even though I wanted to push it much farther than what I had on paper.Beware!!, I said the same thing on 2004 and look at me now... The path of creativity and so the path of a project of this kind, on which many areas ar involved (2D and 3D art, sound editing, 3D environment design, coding, story writing, etc.) suffer a phenomenon that I call the "whirlwind effect", on which the center is tiny and expands as it gets bigger, all your efforts are concentrated in the beggining of the project, is when de deepest concept of it is done, then you can expand all the project towards infinite, the only way to stop it is, like in a real whirlwind, find obstacles in your way (lack of skills on one or more than one of those areas of the mod), but, no matter how much of them you find, if the center of the whirlwind is strong, it will continue to spin until it reaches its max power, that is, when your mod is finally released and then it will stops to spin...
), the effect just happened when ammo reached zero, so I deleted this feature from the SDK as it was stupid to see an overheat effect with no overheat behaviour at all. 
I said "don't be in a hurry", not "hurry up or I'll kill you" XD. I will implement all now and make some shots. 
If you need ANY files or even the full SDK of the Mod and te mod itself just tell me. 
int w = ScreenWidth;
int h = ScreenHeight;FillRGBA(w/2.46 , h/1.07, 240, 22, 0, 0, 0, 255);FillRGBA(w/2.46 , h/0.95, (2.4 * m_iHeat), 5, 255, 0, 0, 255);//ZWC OVERHEAT//-------------------------------------------------------------------code all over the weapon code with no luck... But, I did not add the variable on the multiplay_gamerules.cpp file... :/ (I know, it´s a desperate procedure...)
MESSAGE_BEGIN( MSG_ONE, gmsgOverheat, NULL, m_pPlayer->pev);
WRITE_BYTE( m_iHeat );
MESSAGE_END();
//--------------------------------------------------------------------
MESSAGE_BEGIN( MSG_ONE, gmsgOverheat, NULL, m_pPlayer->pev);All compiled fine this time!!, the function seem to not "swallow" well the ENT parameter, so I tested the code in three positions (I did searched as you told me) and...
WRITE_BYTE( m_iHeat );
MESSAGE_END();
,no coding skills involved.MESSAGE_BEGIN( MSG_ONE, gmsgOverheat, NULL, ENT( pPlayer );is telling me that gmsgOverheat... well, as usual this dog's day...
int gmsgOverheat = 0;//ZWC OVERHEAT (c) Shepard 62700FR
gmsgOverheat = REG_USER_MSG( "Overheat", 1);//ZWC OVERHEAT (c) Shepard 72700FRYes, they´re (c)you. Admit no complaints about this.
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\hud.h(650) : error C2146: syntax error : missing ';' before identifier 'm_Overheat'Points here:
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\hud.h(650) : error C2501: 'CHudOverheat' : missing storage-class or type specifiers
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\hud.h(650) : error C2501: 'm_Overheat' : missing storage-class or type specifiers
CHudAmmo m_Ammo;
CHudHealth m_Health;
CHudSpectator m_Spectator;
CHudGeiger m_Geiger;
CHudBattery m_Battery;G:\DevZWC20\Elementos\Single-Player Source\cl_dll\overheat.cpp(39) : error C2039: 'm_Overheat' : is not a member of 'CHud'And ppints here:
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\overheat.cpp(39) : error C2228: left of '.MsgFunc_Overheat' must have class/struct/union type
DECLARE_MESSAGE(m_Overheat,Overheat)Even if it is perfectly declared on overheat.h
int MsgFunc_Overheat(const char *pszName, int iSize, void *pbuf);The next is also extrange (at least for me):
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\overheat.cpp(45) : error C2653: 'CHudOverheat' : is not a class or namespace namePoints here:
int CHudOverheat::Init(void)But it is on Overheat.h !
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\overheat.cpp(48) : error C2065: 'm_iHeat' : undeclared identifierPoints here:
m_iHeat = 0;Into the function int CHudOverheat::Init(void)
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\overheat.cpp(49) : error C2673: 'Init' : global functions do not have 'this' pointersPointing to:
gHUD.AddHudElem(this);HOOK_MESSAGE(Radar);
gHUD.AddHudElem(this);
return 1;G:\DevZWC20\Elementos\Single-Player Source\cl_dll\overheat.cpp(55) : error C2065: 'm_hSprite' : undeclared identifierThat points to:
m_hSprite = 0;But in overheat.h...
private:
HSPRITE m_hSprite;G:\DevZWC20\Elementos\Single-Player Source\cl_dll\overheat.cpp(59) : error C2653: 'CHudOverheat' : is not a class or namespace nameHere I started to think that I am a totally moron because it points to:
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\overheat.cpp(60) : error C2373: 'MsgFunc_Overheat' : redefinition; different type modifiers
int CHudOverheat:: MsgFunc_Overheat(const char *pszName, int iSize, void *pbuf )That is the same function that CHudHealth...
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\overheat.cpp(69) : error C2653: 'CHudOverheat' : is not a class or namespace nameThat points to:
int CHudOverheat::Draw(float flTime)Believe me, I´m sure they all are on overheat.cpp
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\hud.cpp(354) : error C2065: 'm_Overheat' : undeclared identifierThat points to:
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\hud.cpp(354) : error C2228: left of '.Init' must have class/struct/union type
G:\DevZWC20\Elementos\Single-Player Source\cl_dll\hud.cpp(506) : error C2228: left of '.VidInit' must have class/struct/union type
m_Overheat.Init();//ZWC OVERHEAT (c) Shepard 62700FRand:
m_Overheat.VidInit();//ZWC OVERHEAT (c) Shepard 62700FRThat are already there, in overheat.h.
According to a reversed engineered version of Counter-Strike 1.6's source code...
MESSAGE_BEGIN is not related to sprites, it's related to "HUD messages".Oh, I said taht because I did see this part of the code always with the showing-sprites part of many elements of the SDK, like the apache´s explosion when dead, the houndeye shockwaves, the bullsquid´s spit, etc. Of course, It did not occur to me to relate MESSAGES with HUD messages (It´s true, sometimes the branches won´t let me see the forest).
Nothing to show (yet), sorry.Oh, c´mon!, there must be something!, anyway, if you need help making models or any gfx thing you only need to ask me, as you have seen I´m not bad at modelling, and I´m quite good making conceptual designs of any kind like buildings, weapons,vehicles, characters, monsters, etc. (apart of my real work I´m more a Comic drawer and designer).
did I hit the target? , haha!!, no, seriously, you gave me faaaar more help than I deserve, thanks, thanks, thanks. ), I have seen others freaking because they´ve done something similar without giving a clue to others, this works is perfect and will serve others to make better mods, well, it´s just a suggestion ;). ). Now it´s time for the hud bar. If I add:FillRGBA(w/2.46 , h/1.1, (2.4 * m_iHeat), 5, 255, 0, 0, 255);//ZWC OVERHEATin the weapon code under:
ALERT( at_console, "Heat = %d - Game time = %f - Cool down time = %2f\n", m_iHeat, gpGlobals->time, m_flCooldownTime );In the hl workspace... there are three errors appearing.
C:\DevZWC20\Elementos\Single-Player Source\dlls\mp5.cpp(411) : error C2065: 'FillRGBA' : undeclared identifierOn the cl_dll workspace I obtained the error:
C:\DevZWC20\Elementos\Single-Player Source\dlls\mp5.cpp(411) : error C2065: 'w' : undeclared identifier
C:\DevZWC20\Elementos\Single-Player Source\dlls\mp5.cpp(411) : error C2065: 'h' : undeclared identifier
C:\DevZWC20\Elementos\Single-Player Source\cl_dll\health.cpp(312) : error C2065: 'm_iHeat' : undeclared identifierI have declared it on hud.h, of course.
I have made a very basic overheating system for HL's 9mmAR, the only thing you have to do is to understand it and make the code that updates your HUD.For the understanding part, well, I think I will understand it (cross fingers again), but for the "making the code", expect some major disasters here, haha!!
To fix that, either you disable the client side prediction system (the CLIENT_WEAPONS define) or you perform all the animations/sounds on the server (this means removing the weapon event).Do you mean the void ev_firemp5(struct event_args_s *args); part?
BTW, author or not you are again on credits, and, finally, I can finish the credits video!! Weeeeeeeehaaa!!!! ( ahem!, sorry for being so enthusiastic).
KeyDown( &in_attack );
gHUD.m_Spectator.HandleButtonsDown( IN_ATTACK );KeyUp( &in_attack );
in_cancel = 0;if(gHUD.g_iHeat < 100)//Heat must be less than 100{//ZWC OVERHEAT
KeyDown(&in_attack);
gHUD.g_iHeat += gHUD.m_flTimeDelta * 300;
}//ZWC OVERHEAT
if (gHUD.g_iHeat > 100)
{
gHUD.g_iHeat = 100;// Avoid amounts over 100in_attack.state &= ~1;// Release ATTACK button}
gHUD.m_Spectator.HandleButtonsDown( IN_ATTACK );KeyUp( &in_attack );gHUD.g_iHeat -= gHUD.m_flTimeDelta * 100; //ZWC OVERHEAT.Cooldownif (gHUD.g_iHeat < 0 ) gHUD.g_iHeat = 0; //Heat not under 0in_cancel = 0;FillRGBA(x, y, iWidth, iHeight, 255, 160, 0, a);Put:
FillRGBA(w/2.46 , h/1.1,(2.4 * gHUD.g_iHeat),5,255,0,0,255);hud_redraw.cpp
#include "vgui_TeamFortressViewport.h"Put:
int g_iHeat;//ZWC OVERHEAThud.h
float GetSensitivity();int g_iHeat;//ZWC OVERHEATThat's still conditional, you shouldn't make it check that boolean. I'm not sure why that's there though. It should really be checking if the monster called DeathNotice before, but that requires the monstermaker to track the children.the if (m_fFadeChildren) etc. is original code, I did not know why it checks if monsters are fading or not to do the pevChild return NULL.
//=================================m_cLiveChildren--;
pevChild->owner = NULL;SUB_StartFadeOut();
//==========================// With this game does // not crash ARM: 26-1-2016//===========================
CBaseEntity *pOwner = CBaseEntity::Instance(pev->owner);
if ( pOwner )
{
pOwner->DeathNotice( pev );
}
UTIL_Remove( this );
UpdateOnRemove();//New. from GitHub 19-10-2016 (c)Solokiller
//========================if ( m_fFadeChildren )If so, you are on credits again!! (is like If I have you always on my developing team, haha!
{
pevChild->owner = NULL;
}
)Note that UTIL_Remove will call UpdateOnRemove already (unless your version doesn't) so you don't need to call it manually.Oh!, see?, I made a redundant code there, I hope it will not cause troube...
I will post also the full code of the turret and the FEMP.// ok, we've gotten the deathnotice from our child, now clear out its owner if we don't want it to fade.
m_cLiveChildren--;if ( !m_fFadeChildren )
{
pevChild->owner = NULL;
}CBaseMonster::Killed( pevAttacker, iGib );
pev->velocity = Vector( 0, 0, 0 );////////////////////////////////////////////// NEWCODE UNDER THIS COMMENT!!!//////
/////////////////////////////////////////Vector vecSplatDir;
TraceResult tr;CBaseEntity *pOwner = CBaseEntity::Instance(pev->owner);
if (pOwner)
pOwner->DeathNotice(pev);SetActivity( ACT_DIEVIOLENT );
pev->movetype = MOVETYPE_TOSS;
pev->takedamage = DAMAGE_NO;
pev->spawnflags = SF_MONSTER_FADECORPSE;
DeathSound( ) ;// Descomentado el 2-3-2016
UpdateOnRemove();//NUevo. Sacado de GitHub 19-10-2016 (c)Solokiller {
// this monster was created by a monstermaker... fade the corpse out.
SUB_StartFadeOut();
}//==================================================
//Intento de que no pete el sistema ARM: 26-1-2016
//==================================================
CBaseEntity *pOwner = CBaseEntity::Instance(pev->owner);
if ( pOwner )
{
pOwner->DeathNotice( pev );
}
UTIL_Remove( this );
UpdateOnRemove();//NUevo. Sacado de GitHub 19-10-2016 (c)Solokiller
//======================================================