Forum posts
- Forums
- Posts
- Posted by
The Mad Carrot
Webspace is temporary offline, so downloads don't work. :/
SpockNax - Summerice
Haaaaaahahaha......... 
No really, im lmao.
Hehehe...... Ok here is the secret: http://www.letterjames.de
No really, im lmao.
Yep. Blame Valve. 
OMFG NO! I don't model for HL2. I can't even get that XSI or whatever its called.
Also, i did not model anything, i only decompiled the models, to convert them to HL1. All the textures and model polygons remain intact.
I can do a little HL1 modelling, but im still a beginner.
So, sorry, can't help you with that.
Also, i did not model anything, i only decompiled the models, to convert them to HL1. All the textures and model polygons remain intact.
I can do a little HL1 modelling, but im still a beginner.
So, sorry, can't help you with that.
I know it looks a tad bit too long, but im not going to change that, that would screw things up.
Anyway, finished the w_ and p_ models:
Anyway, finished the w_ and p_ models:
Does this makes you laugh?
I remade the model with the HD HEV arms.
Check the screenshot in my other post.
Anyone want it? (Say yes please! :D)
Check the screenshot in my other post.
Anyone want it? (Say yes please! :D)
Thats right, it can now be used as a Satchel replacement.
Thanks, 38_98. Yeah, i know about the MAC-11, i made it too big. Aw well.
I just spend the whole afternoon making this:
:
Yeah, i know about the MAC-11, i made it too big. Aw well.I just spend the whole afternoon making this:
Wel, im still a beginner when it comes to modelling, but i made some custom weapon/item models the last couple of months. You're free to try them, and everyone else.
Note that they're not pretty, but i think i did a good job making them.
You might want to check these in HL Modelviewer first, maybe you don't like em at all.
Here's what you get: Enjoy!
Download: http://wdevries.demon.nl/MarkH/Atom_zooi/MuzzleFlash_models.zip
Note that they're not pretty, but i think i did a good job making them.
You might want to check these in HL Modelviewer first, maybe you don't like em at all.
Here's what you get:
- A Duplo/Lego pistol (9mmhandgun replacement, w_ v_ and p_ models and a custom barney armed with this gun)
- A Dutch choclate cookie (Handgrenade replacement, w_ v_ p_ models)
- A Hammer (Crowbar replacement, w_ v_ p_ models)
- An Ingram Mac-11 (9mmAR replacement, w_ v_ p_ models
- A cake/pie (Satchel replacement, w_ v_ p_ models)
- A custom gauss ammo model, (Only w_ model)
- A custom medkit model
Enjoy!Download: http://wdevries.demon.nl/MarkH/Atom_zooi/MuzzleFlash_models.zip
Make them yourself?
The Hunter, your msn is mr.jgamer AT ntlworld.com right?
I don't have modelling skills. 
Is this what was called Half-Life: Day One?
Ill put it in the vault.
Stand By!
Stand By!
In case someone is interested, i made an "alien teleportation" prefab some time ago, identical to those alien teleportation in the original HL singleplayer story, with green flash, some green beams, 2 sounds, etc. I'll tell ya, its identical!
And best of all: my prefab gives you exactly the same effect as in Spirit.
And best of all: my prefab gives you exactly the same effect as in Spirit.
Yer kiddin' right?
Yes, just cmd, the DOS prompt. Works fine.
POST IT OR I DIE! 
Wtf.
Try weapon_gauss.
And how are you triggering it?
Try weapon_gauss.
And how are you triggering it?
To ripent a bsp:
Assuming you have placed everything in a short folder, like C:ripent.
That includes: ripent.exe and a bsp, like level.bsp
Fire up CMD and point to the directory where ripent.exe and the bsp file are located, in this case: C:ripent.
You should see this:
C:ripent>
Nou enter this:
C:ripent>ripent -export level
This'll creates a file named level.ent.
Make your changes to that file and then import it back into the bsp by typing:
C:ripent>ripent -import level
Im not sure if its necsesary to include the file extenstion. For me, it works without the extension.
Assuming you have placed everything in a short folder, like C:ripent.
That includes: ripent.exe and a bsp, like level.bsp
Fire up CMD and point to the directory where ripent.exe and the bsp file are located, in this case: C:ripent.
You should see this:
C:ripent>
Nou enter this:
C:ripent>ripent -export level
This'll creates a file named level.ent.
Make your changes to that file and then import it back into the bsp by typing:
C:ripent>ripent -import level
Im not sure if its necsesary to include the file extenstion. For me, it works without the extension.
No, you can make the suit play a short logon sound, but you can't disable it, unless you make an empty wav with the same name as the logon sound.
The game_player_equip entity is actually pretty easy to set up.
Simply place one and open its properties, then click the smart edit button. Now click add so you add a new keyvalue. The key is the weapon entity name, and the value is how many of this weapon the player will get. For example:
Key: weapon_9mmAR
value: 4
will give the player a mp5.
The game_player_equip entity is actually pretty easy to set up.
Simply place one and open its properties, then click the smart edit button. Now click add so you add a new keyvalue. The key is the weapon entity name, and the value is how many of this weapon the player will get. For example:
Key: weapon_9mmAR
value: 4
will give the player a mp5.
Looks better then your previous one. Go on!
Ah ok. Just want to be sure.
"I know It's almost nothing but I was trying to find how to make that screen a switchable texlight!!"
So does this mean you still didn't get it to work as in my example map?
So does this mean you still didn't get it to work as in my example map?
Nope, this only applies at custom texture lights.
Rowleybob, thats an example that uses a different way of making switchable texture lights.
I got the example at work, so ill upload it at the vault tomorrow.
I got the example at work, so ill upload it at the vault tomorrow.
Just ignore the unused key. Its because Styles are not in your fgd file.
And you must set the Style to Grouped (-3) or else ?t won't work.
And you must set the Style to Grouped (-3) or else ?t won't work.
Well there you go, you NEED the light entity.
And again:
The Grouped setting is essentially a hack to allow your texlights to be switchable. To use it, create a brush entity with texlights on it, and set its style to Grouped; then create a light entity with the same name as the brush entity. Hlrad will now pretend that the light emitted by the texlight is "really" being emitted by your light entity. In other words, turning the light on and off will now turn the texlights on and off, too.
And again:
The Grouped setting is essentially a hack to allow your texlights to be switchable. To use it, create a brush entity with texlights on it, and set its style to Grouped; then create a light entity with the same name as the brush entity. Hlrad will now pretend that the light emitted by the texlight is "really" being emitted by your light entity. In other words, turning the light on and off will now turn the texlights on and off, too.
?
Does it still work without the light entity?
Does it still work without the light entity?
Just finished my test on switchable texture lights for Elon Yariv. Then i logged into TWHL to explain how it works.
Then i logged into TWHL to explain how it works.Ok, i did some testing and i got it. Here you go, elon:
First, rename your "on" texture to +0~SCREEN_EY and the "off" texture to +A~SCREEN_EY. Then add these in a new or existing wad file.
Then openup your lights.rad/valve.rad file and add this line:
+0~SCREEN_EY 230 85 0 1200
Now go into Hammer and make a brush with your "on" texture on it. Turn this brush into a func_wall and name it screen_light. Then go the Style option and select Grouped. If you don't see the Style option, turn off smart-edit and add a new key and value:
key: style
value: -3
Next, place a light entity anywhere near and name it the same as your brush, in this case: screen_light. Set its color and brightness to 255 255 255 0.01, so that it won't emit any light of its own.
Now make a func_button and let it target the brush (screen_light). Goto its flags and check Don't move and Toggled.
Thats it, save and compile this map with the ZHLT 3.0 or higher. 3.2 is out, so use that one. Don't use older tools.
If you use the button ingame, the screen texture goes to its off version and the orange light dissapears. If you use button again, the screen texture goes back to its on version and the orange light reappears.
If you can't figure this out, i got an example map and everything ready for you.
First, rename your "on" texture to +0~SCREEN_EY and the "off" texture to +A~SCREEN_EY. Then add these in a new or existing wad file.
Then openup your lights.rad/valve.rad file and add this line:
+0~SCREEN_EY 230 85 0 1200
Now go into Hammer and make a brush with your "on" texture on it. Turn this brush into a func_wall and name it screen_light. Then go the Style option and select Grouped. If you don't see the Style option, turn off smart-edit and add a new key and value:
key: style
value: -3
Next, place a light entity anywhere near and name it the same as your brush, in this case: screen_light. Set its color and brightness to 255 255 255 0.01, so that it won't emit any light of its own.
Now make a func_button and let it target the brush (screen_light). Goto its flags and check Don't move and Toggled.
Thats it, save and compile this map with the ZHLT 3.0 or higher. 3.2 is out, so use that one. Don't use older tools.
If you use the button ingame, the screen texture goes to its off version and the orange light dissapears. If you use button again, the screen texture goes back to its on version and the orange light reappears.
If you can't figure this out, i got an example map and everything ready for you.
Whatever it is, im not touching Spirit anymore. YAY @ normal HL.
YAY @ normal HL. But you're right.
Rofl.
Anyway: add
Just place a light entity in front of the orange screen and trigger both the brush (func_wall) and the light goes off when switched to the grey screen.
Anyway: add
Just place a light entity in front of the orange screen and trigger both the brush (func_wall) and the light goes off when switched to the grey screen.
Do you want those textures to emit light?
+0~SCREEN orange-ish color
+A~SCREEN light grey-ish color
And when those texture switch, you also want the light to switch? From grey to orange and vice versa?
+0~SCREEN orange-ish color
+A~SCREEN light grey-ish color
And when those texture switch, you also want the light to switch? From grey to orange and vice versa?
Read my post and try that.
The new ZHLT (http://www.zhlt.tk allow you to add a style to any brush based entity with a texture light on any side(s)
Here's how it works:
Set a style of lighting for the texlight. Can be applied to any brush based entity.
Available styles are:
0 : "Normal"
-3 : "Grouped"
10 : "Fluorescent flicker"
2 : "Slow, strong pulse"
11 : "Slow pulse, noblack"
5 : "Gentle pulse"
1 : "Flicker A"
6 : "Flicker B"
3 : "Candle A"
7 : "Candle B"
8 : "Candle C"
4 : "Fast strobe"
9 : "Slow strobe"
12 : "Underwater"
The Grouped setting is essentially a hack to allow your texlights to be switchable. To use it, create a brush entity with texlights on it, and set its style to Grouped; then create a light entity with the same name as the brush entity. Hlrad will now pretend that the light emitted by the texlight is "really" being emitted by your light entity. In other words, turning the light on and off will now turn the texlights on and off, too.
You'll probably want to set the brightness of the light entity to 0.01, so that it emits no light of its own (this trick is unnecessary if you're using Spirit of Half-Life, which supports switchable texlights directly).
Here's how it works:
Set a style of lighting for the texlight. Can be applied to any brush based entity.
Available styles are:
0 : "Normal"
-3 : "Grouped"
10 : "Fluorescent flicker"
2 : "Slow, strong pulse"
11 : "Slow pulse, noblack"
5 : "Gentle pulse"
1 : "Flicker A"
6 : "Flicker B"
3 : "Candle A"
7 : "Candle B"
8 : "Candle C"
4 : "Fast strobe"
9 : "Slow strobe"
12 : "Underwater"
The Grouped setting is essentially a hack to allow your texlights to be switchable. To use it, create a brush entity with texlights on it, and set its style to Grouped; then create a light entity with the same name as the brush entity. Hlrad will now pretend that the light emitted by the texlight is "really" being emitted by your light entity. In other words, turning the light on and off will now turn the texlights on and off, too.
You'll probably want to set the brightness of the light entity to 0.01, so that it emits no light of its own (this trick is unnecessary if you're using Spirit of Half-Life, which supports switchable texlights directly).
<quote>:/ i stay far away from spirit. it scares me</quote>
Yay, im glad you said that.
So ill switch back to my original source code for the mod, with NO spirit, and ill see what i can make of it.
As for the bumpmapping, you people might want to see it with your own eyes first before i decide whether or not to include it in the mod.
Download and install this in your Half-Life folder, to see bump mapping in action: http://collective.valve-erc.com/data/docs/1091469531-97736200/files/HLbump.zip
Yay, im glad you said that.
So ill switch back to my original source code for the mod, with NO spirit, and ill see what i can make of it.
As for the bumpmapping, you people might want to see it with your own eyes first before i decide whether or not to include it in the mod.
Download and install this in your Half-Life folder, to see bump mapping in action: http://collective.valve-erc.com/data/docs/1091469531-97736200/files/HLbump.zip
Lol, nevermind bumpmapping, its a stupid idea. 
And so it my idea of using spirit code, that was a big mistake!
And so it my idea of using spirit code, that was a big mistake!
The Spirit code is somehow bugged, im getting lots of errors!!! Shit! Don't know whats wrong!