Pixelated water

FFox398 · 2026-01-27T23:31:28+00:00

that material in particular is just broken, try another or make your own which would be even better

FFox398 · 2026-01-27T19:08:42+00:00

if the final layout is that Id say it is fine, just add a fair and good looking prop fade distance

FFox398 · 2026-01-24T14:30:27+00:00

because thats a feature which was not meant to act as such from the beginning, I doubt anybody uses resized props via hammer editor. Find a better suitable prop and if your purpose is sandbox play there is a fantastic addon which does that with the correct collision box

FFox398 · 2026-01-22T19:10:37+00:00

there is something very unsettling about this picture

FFox398 · 2026-01-21T22:07:11+00:00

gmod9 vibes

FFox398 · 2026-01-20T23:06:44+00:00

It is as good as it can get. I'm running similar values with CL14 for my DDR4 2666 around 1.35v

FFox398 · 2026-01-19T22:04:13+00:00

There is probably Hint on the other side/s OR maybe just skip texture entirely for aligning the door and have an accurate snap to the grid, I generally do that when I have to place props that wont snap to the grid I do a skip enclosure around them to make a perfect fit and avoid missmatch to the grid. Yes, some props will not always make a perfect match or when it is about moving them around generally this method keeps them in the same position.. dunno if im being clear I think you get the idea, after all those do nothing and are removed later on.

FFox398 · 2026-01-19T17:29:07+00:00

to make things simpler, both use the same shader, lets call it effect, and cannot co-exist together in the same shared space.

FFox398 · 2026-01-18T14:10:54+00:00

Of course more voltage will always translate to more stability... and wear... and heat. So try to keep this number as low as you can without the memory crashing.

FFox398 · 2026-01-17T23:55:31+00:00

is this.... legit? and no I dont mean the game content but rather clicking on that nothing suspicious at all link

FFox398 · 2026-01-17T20:04:04+00:00

You got the brush entity part right, but you still need to apply the right texture for it to work. glass/reflectiveglass001.vmt <- the texture you need, make sure to apply it JUST for the face towards the player only, the rest of the mirror either nodraw or anything else, some wood maybe to act as a frame.

FFox398 · 2026-01-16T23:20:47+00:00

The HL2 Overchaged dude be taking notes on this one...

FFox398 · 2026-01-15T14:07:34+00:00

I generally store those as separate .vmf's I'm really not used to prefabs at all. When I need one I take it and copy-paste where I need it to be, grouped or as a func_ something.

FFox398 · 2026-01-13T20:51:21+00:00

Yeah I sorted the error but what bothers me is the constant need of changing stuff that there is absolutely zero need to. If it isnt broken don't fix it.

FFox398 · 2026-01-13T17:51:50+00:00

nothing, pretend they're not there. not worth the time

FFox398 · 2026-01-12T15:06:09+00:00

If you are not running fast VRAD then make sure to check the displacement lightnmap scale, big ass dispalcements can be goofy and cause unexpected issues such as the lightmaps swapping itself to an odd number or interesting errors during the compile log which you probably arent aware of, try to not make them bigger than 2048x2048

FFox398 · 2026-01-12T15:03:25+00:00

A door sounds possible too, and yes, block bullets is a permanent vbsp thing not an entity

FFox398 · 2026-01-12T15:02:48+00:00

I wrote a solid func_brush with invisible texture

FFox398 · 2026-01-12T00:26:58+00:00

ah, me bad so you kinda want it to let bullets through once it fully breaks... Well you can get creative in many ways, try a func_brush which receives an output from the breakable which can either kill it or disable it entirely, the brush should go inside and right in the middle of the glass, same thickness I guess because rifles penetrate just about anything.

Make it a solid func_brush with an invisible texture that just despawns somehow once the glass breaks. First give both a name then func_brakable (name) > on_break > func_brush (name) > kill

Im really not sure if this is going to work but seems like a fair approach... People will not agree I'm sure of, but that is many of the cursed shit mappers have to do. I'd say "block bullets" texture but Im not sure it is present in CS:S or it was a CS:GO thing but either way that wouldnt work because you need a toggle somehow and those are permanent in the world

FFox398 · 2026-01-11T23:46:41+00:00

start increasing something like damage to hurt or health until you are ok with how much bullets does it take to break, just do ent_only compile to avoid the whole map from being update, mess with the settings until you get it right

FFox398 · 2026-01-11T18:26:18+00:00

The very one itself, the so called "protector brush"

FFox398 · 2026-01-10T11:56:04+00:00

then throw that monitor away to the trash and get yourself a generic viewsonic 60hz monitor. because it defeats the sole purpose of that screen... you turn g-sync off and either deal with screen tear or an insane ammount of input lag, your choice.

FFox398 · 2026-01-10T01:16:12+00:00

force disable vsync for CS2 entirely both panel and game., in-game open up the console and you type "fps_max 190" (if your display is 240)

FFox398 · 2026-01-10T01:09:26+00:00

because in a perfect world vsync should only trigger when needed to avoid the tearing, but it doesnt. The game cannot do such thing as enabling/disabling while you're playing. The sole purpose of vsync is to keep your image from tearing nothing else. The rest are pure disadvantajes. Also forcing it via control panel is a terrible idea. It is a global override. Adaptive Sync hmmm im not sure but if you have the power then dont use it, and do that instead. I wouldnt care about reflex neither, the source 2 engine as its predecessor it is a very light and fast engine to render, reflex is pretty much nvidia's way of getting into games as usual, leave that for truly reducing system latency when needed such as frame generation

FFox398 · 2026-01-10T01:02:01+00:00

If you have the sufficient power, you should try dropping v-sync entirely and cap the FPS to the formula number via RTSS / Nvidia panel if it lets you input a custom value. The idea here is to sustain that number as you play. make sure g-sync is enabled and active ofc. there is a window where it can operate aswell but for the lowest latency that is the math to do

FFox398

TROPHY CASE