I cannot understand why Valve doesen´t release an upgraded HL.exeThey did. WON users still whine about it.
And now for the alternative joke:
I cannot understand why Valve doesen´t release an upgraded HL.exeThey did. It's called HL2.exe.
Forum posts
And now for the alternative joke:
monster_scientist
model field: [mr. valve.mdl]
model field: [mr. valve.mdl]
The Source 2 tools are available already, and Dota 2 runs on Source 2.
No, they'll be in the hub map. Take a few into your level if you want, but they're not going through every rift with the player.
As opposed to all the free mods which, what, don't have a huge time commitment invested?
Looks a bit crap, tbh.
It's average-at-best mapping and looks worse than HL2 which came out in 2004. Come ahhhn. Demanding money for that is nonsense. It looks like myfirstmap.bsp.
It's average-at-best mapping and looks worse than HL2 which came out in 2004. Come ahhhn. Demanding money for that is nonsense. It looks like myfirstmap.bsp.
Black Mesa surviving the nuke seems unlikely. How about a small intro map set during the events of Half-Life wherein a portal experiment is damaged and teleports the player and a gaggle of his or her colleagues (and a couple of Barneys for good measure) to a hitherto unknown alien border world. This border world forms the hub as the story sees the scientists urging the player to travel through various rifts in the hopes of finding a way home.
?
?
And The Core is released, right? :3
Yes, and it's just Sledge 
Pebs is also busy on TWHL4 and The Core at the moment, so production has slowed a little.
Pebs is also busy on TWHL4 and The Core at the moment, so production has slowed a little.
Post a journal
It absolutely does count as a version. Also the subscription model is fine & makes a lot of pro software a lot more accessible. Be less cynical 
CC 2015.1.1 is the latest version of Photoshop & is the 16th major version. CS6 was the 13th, so it's pretty out-of-date.
CC 2015.1.1 is the latest version of Photoshop & is the 16th major version. CS6 was the 13th, so it's pretty out-of-date.
Add a gradient. I don't want flat colors slapped on there and then be called a railing.
In seriousness, though, Rendermode: Solid and Render Amount: 255.
This is covered in tutorials.
In seriousness, though, Rendermode: Solid and Render Amount: 255.
This is covered in tutorials.
I can't recommend this enough.
The current roster is Ant, Scoots, Urby, Jessie, Penguinboy & myself. Joebama and Livewire have bought it today, but haven't joined us yet. Honestly guys, this is something special. Grab it while it's on sale right now!
The current roster is Ant, Scoots, Urby, Jessie, Penguinboy & myself. Joebama and Livewire have bought it today, but haven't joined us yet. Honestly guys, this is something special. Grab it while it's on sale right now!
There's unfamiliar and there's objectively bad. Win8 tried to implement a bizarre hybrid of a touch interface with a traditional desktop and it just clashed at every single point.
It'll be forgotten to time along with ME and Vista.
It'll be forgotten to time along with ME and Vista.
Suggesting 8 is better than 10 is mindblowing to me. That said, I've not had any of the problems with 10 I've seen reported - although neither has anyone else I know who uses it, which is most people by now.
10 is, for the most part, exactly what we wanted - Win7, but far faster under the bonnet. I stand by my original review in the desktops thread:
10 is, for the most part, exactly what we wanted - Win7, but far faster under the bonnet. I stand by my original review in the desktops thread:
Well I'm just about a week into my Windows 10 experience and so far it's performed great! I've had no compatability issues whatsoever, and my niggles are so minor that they're barely worth mentioning - and will almost certainly be addressed in the first Service Pack, if not in smaller patches.For comparison, it's always fun to read about my Windows 8 experience.
Firstly, the aforementioned inability to rename items in my Quick Access list.
Second, after finally adding an easily-accessed New Folder button in W7, it's been hidden away again behind another menu. Mildly irritating.
Thirdly, programs don't automatically come to the front when they start up. This is good in some ways - dialogue boxes no longer reduce games to the taskbar, for example. However, I use a lot of keyboard G-key binds as shortcuts to my browser, my email and media players and it's a little annoying that they don't start in the foreground. I've caught myself waiting for a program to start for quite a while before noticing it's just sitting behind whatever else is running.
These are all barely even problems. Overall, I think W10 is a winner. It's exactly what we wanted - Windows 7 with all the performance advantages of Windows 8 and none of the horrendous design choices.
The Core is like 90% 256 & 512+ sized textures and I've only hit the engine's texture memory limit once or twice.
You're not limited to 512 x 512, incidentally. You're limited to 262144 pixels per texture, so 256 x 1024, for example, is totally fine.
You're not limited to 512 x 512, incidentally. You're limited to 262144 pixels per texture, so 256 x 1024, for example, is totally fine.
I was right with you with visuals until I played the previous build of The Core. Holy hell is it better now that the offices and cendark have been rebuilt with gameplay at the forefront.
The lower your texture scale, the sharper your shadows. I use 0.50 texture scale and get pretty decent results.
A more directional environment light would help as well.
Make sure you're not compiling with too many light bounces - 3 or 4 is plenty and also compile with -extra.
Avoid the light entity - it's garbage. Use textlights for subtle ambient tones, and use light_spot for the majority of your lighting. Ideally, your spots should contrast the textlights for a more stylised look.
Finally, don't ignore your skybox tones. Grab some RGB values from the sky texture and use them to properly blend your geometry with the skybox. Look at ravenholm - the moonlight is almost completely white, allowing a stark contrast with the extremely blue/green spotlights and orange tungsten interior lighting.
A more directional environment light would help as well.
Make sure you're not compiling with too many light bounces - 3 or 4 is plenty and also compile with -extra.
Avoid the light entity - it's garbage. Use textlights for subtle ambient tones, and use light_spot for the majority of your lighting. Ideally, your spots should contrast the textlights for a more stylised look.
Finally, don't ignore your skybox tones. Grab some RGB values from the sky texture and use them to properly blend your geometry with the skybox. Look at ravenholm - the moonlight is almost completely white, allowing a stark contrast with the extremely blue/green spotlights and orange tungsten interior lighting.
How different is this TWHL4 to the TWHL4 I got to play with a couple years back?
As for suggestions, have you considered adding a random texture spread feature to the face editor and also adding a tile-to-fit option? I PM'd you about this years ago and it's a shame it was never implemented to TWHL3.
As for suggestions, have you considered adding a random texture spread feature to the face editor and also adding a tile-to-fit option? I PM'd you about this years ago and it's a shame it was never implemented to TWHL3.
Dude! That is stunning, great work!
So after infinite badgering from Dimbark, me and Urby had a go of this last night.
It's exactly what you'd expect, if not worse. The graphics are a complete mess across the board, with the interface as messy and unreadable as the spritesheet. A large part of the game involves paying attention to a server-wide chat screen which is moving at the pace you'd expect of a Habbo Hotel room with 60 occupants.
It's a neat idea that everything can be tinkered with by players, but with everyone following their own personal objectives and the absolutely pitiful way the game conveys information, it's simply chaos at all times. Chaos can be great in a game - but it's only effective when it's a disruption of the norm, not the entire game.
You might be able to get some enjoyment out of it if you're the sort of person who has time to dedicate to reading hours of vague wiki documentation to understand just the basics.
I understand why people get into these games, but I'm just so not interested in putting in hours of work to maybe get some enjoyment out of it, and the horrific mess of a UI removes any chance of me touching this shit again.
TL;DR:
Look at the screenshots. It's exactly what you think it is from looking at those.
It's exactly what you'd expect, if not worse. The graphics are a complete mess across the board, with the interface as messy and unreadable as the spritesheet. A large part of the game involves paying attention to a server-wide chat screen which is moving at the pace you'd expect of a Habbo Hotel room with 60 occupants.
It's a neat idea that everything can be tinkered with by players, but with everyone following their own personal objectives and the absolutely pitiful way the game conveys information, it's simply chaos at all times. Chaos can be great in a game - but it's only effective when it's a disruption of the norm, not the entire game.
You might be able to get some enjoyment out of it if you're the sort of person who has time to dedicate to reading hours of vague wiki documentation to understand just the basics.
I understand why people get into these games, but I'm just so not interested in putting in hours of work to maybe get some enjoyment out of it, and the horrific mess of a UI removes any chance of me touching this shit again.
TL;DR:
Look at the screenshots. It's exactly what you think it is from looking at those.
I've never actually monitored my framerate in Fallout 4, but I have Vsync on and I've not noticed any dips, so a constant 60 is likely - maybe occasionally slightly lower, but not noticeably.
Show your devious creations!
Life is good at Fort Fuckity-Bye.
No mods for my first playthrough, although it was daaamn tempting to remove the settlement size limit. Next time!
Life is good at Fort Fuckity-Bye.
Deus Ex isn't super ugly, but this sure is. What a mess!
You've been trying to get me to play this for ages, but I just can't get into this sort of roleplay in games. I know you play RP on gmod as well, and I just find the whole thing a bit unfulfilling.
You've been trying to get me to play this for ages, but I just can't get into this sort of roleplay in games. I know you play RP on gmod as well, and I just find the whole thing a bit unfulfilling.
Post the compile log, please. You might have missed something
*bitter
Bitter context.
Bitter context.
I have it on good authority that Archie has no trouble getting drunk in the morning, so you don't even have worry about having to listen to him sober.Did that goddamn slimy spy Ant tell you that? He's such a fucking spy.
No, it's clearly Goldsource ¬_¬
Not too shabby, Dimbark. Glad to see you working on this again!
Good that you're detailing a bit more with brushwork as well. Earlier iterations were very much just props being the only details.
It doesn't look like your static props are casting shadows, and that would instantly improve the map by 4000%. Check your compile settings!
Not too shabby, Dimbark. Glad to see you working on this again!
Good that you're detailing a bit more with brushwork as well. Earlier iterations were very much just props being the only details.
It doesn't look like your static props are casting shadows, and that would instantly improve the map by 4000%. Check your compile settings!
$light_exe -both -final -TextureShadows -StaticPropPolys -game $gamedir $path$fileI'm amazed that Urby doesn't know about this since I use it extensively in The Core.
I use info_targets
I use info_targets
Rocket League? :3
The server has 12 slots. Any more than that and nobody would get a word in anyway amidst Dimbark's yelling, my drunken rambling and Urby's MC'ing
I guess it was implemented in Source!
Well they're clearly related.
Try deselecting everything then hitting shift + c (camera tool) and then hit del.
Also try tapping '2' which should increase your back clipping plane if you're not at the max already.
Why either of these would be affecting your compile, i have no idea.
Try deselecting everything then hitting shift + c (camera tool) and then hit del.
Also try tapping '2' which should increase your back clipping plane if you're not at the max already.
Why either of these would be affecting your compile, i have no idea.
Whatever that red circle is, delete it.
> Compiling question
> Doesn't post compile logWhy are you scared of wpolies?
Exactly the same as a corridor level change, just make the second map something completely different! Use env effects (fades and... Well, pretty much just fades) to hide the transition.
info_landmarks simply tell the engine which part of each map in a changelevel corresponds to the opposing map. They don't need to be anywhere near the changelevel and serve only to provide a point of reference in each map. The landmark must be in both maps.
The player will not 'spawn' anywhere in a standard changelevel. They will simply transition between maps in exactly the same place they leave the previous map - this is what the landmark entity exists to accomplish.
Wherever the player is relative to the info_landmark is where they will appear relative to the info_landmark in the next map, basically. This is the case no matter how you trigger the changelevel entity (it can be triggered like any other entity, or used as a walk-into trigger itself).
Here are two examples:
The yellow box is the landmark, the green box is the player and the orange rectangle is a trigger_changelevel.
Note that regardless of how the changelevel occurs, the player will always be in exactly the same position relative to the landmark.
In the second example, the trigger_changelevel has been triggered by something else - perhaps a button on the wall. The location of the trigger_changelevel has no bearing whatsoever on the location of the player in the next map.
info_landmarks simply tell the engine which part of each map in a changelevel corresponds to the opposing map. They don't need to be anywhere near the changelevel and serve only to provide a point of reference in each map. The landmark must be in both maps.
The player will not 'spawn' anywhere in a standard changelevel. They will simply transition between maps in exactly the same place they leave the previous map - this is what the landmark entity exists to accomplish.
Wherever the player is relative to the info_landmark is where they will appear relative to the info_landmark in the next map, basically. This is the case no matter how you trigger the changelevel entity (it can be triggered like any other entity, or used as a walk-into trigger itself).
Here are two examples:
Note that regardless of how the changelevel occurs, the player will always be in exactly the same position relative to the landmark.
In the second example, the trigger_changelevel has been triggered by something else - perhaps a button on the wall. The location of the trigger_changelevel has no bearing whatsoever on the location of the player in the next map.
Well I'm just about a week into my Windows 10 experience and so far it's performed great! I've had no compatability issues whatsoever, and my niggles are so minor that they're barely worth mentioning - and will almost certainly be addressed in the first Service Pack, if not in smaller patches.
Firstly, the aforementioned inability to rename items in my Quick Access list.
Second, after finally adding an easily-accessed New Folder button in W7, it's been hidden away again behind another menu. Mildly irritating.
Thirdly, programs don't automatically come to the front when they start up. This is good in some ways - dialogue boxes no longer reduce games to the taskbar, for example. However, I use a lot of keyboard G-key binds as shortcuts to my browser, my email and media players and it's a little annoying that they don't start in the foreground. I've caught myself waiting for a program to start for quite a while before noticing it's just sitting behind whatever else is running.
These are all barely even problems. Overall, I think W10 is a winner. It's exactly what we wanted - Windows 7 with all the performance advantages of Windows 8 and none of the horrendous design choices.
Firstly, the aforementioned inability to rename items in my Quick Access list.
Second, after finally adding an easily-accessed New Folder button in W7, it's been hidden away again behind another menu. Mildly irritating.
Thirdly, programs don't automatically come to the front when they start up. This is good in some ways - dialogue boxes no longer reduce games to the taskbar, for example. However, I use a lot of keyboard G-key binds as shortcuts to my browser, my email and media players and it's a little annoying that they don't start in the foreground. I've caught myself waiting for a program to start for quite a while before noticing it's just sitting behind whatever else is running.
These are all barely even problems. Overall, I think W10 is a winner. It's exactly what we wanted - Windows 7 with all the performance advantages of Windows 8 and none of the horrendous design choices.
drops microphone
Would any of you guys be up for putting together a championship table in Rocket League? Mibbe teams of 2 or 3 members so that games can keep coming thick and fast regardless of timezones.
Team SnC look forward to annihilating you all!
(although none of us have ever actually played before)
Team SnC look forward to annihilating you all!
(although none of us have ever actually played before)
The question is simple:
How can you set it up in Source to have an entity (let's say for the sake of argument a func_button) fire output A until a specific event makes it fire output B.
In other words, to have the behaviour of a trigger_changetarget in Goldsource.
I know I've done this before and I don't believe it was particularly complicated, but I haven't touched Source in so damn long I can't remember.
How can you set it up in Source to have an entity (let's say for the sake of argument a func_button) fire output A until a specific event makes it fire output B.
In other words, to have the behaviour of a trigger_changetarget in Goldsource.
I know I've done this before and I don't believe it was particularly complicated, but I haven't touched Source in so damn long I can't remember.
Regardless,
As a general rule, make your basic geometry at gridsize 16 or above. You can go much smaller when it comes to specific detailing, but for the majority of your brushwork, stay as tidy as possible to avoid exactly this situation.Use the square bracket keys to adjust it.
It looks like you built this either not snapped to the grid, or with your grid set to 1.
All of these sections, as well as giving other mappers nightmares, are liable to be full of microleaks that are damn near impossible to lock down.
Keep your wall widths consistent and your geometry neat. I can't imagine how tiring it must be to work with such disorganised brushwork. As a general rule, make your basic geometry at gridsize 16 or above. You can go much smaller when it comes to specific detailing, but for the majority of your brushwork, stay as tidy as possible to avoid exactly this situation.
All of these sections, as well as giving other mappers nightmares, are liable to be full of microleaks that are damn near impossible to lock down.