订阅以下载
Urik Crosshair Support (for non-urik huds, global)

Hello again Urik! Just wanted to drop by to let you know that I've made an improvement on my HUD from last time, and of course, I've given you credit for the custom crosshair support I integrated into it.

The new and improved HUD is here on the Steam Workshop if you wanna take a look.

Thank you again for your contributions!

@aldsTM Looks cool, thanks and you're welcome

Hello Urik! I don't know if you were the first one to figure out hudlayout.res and how to add elements to it such that they allow support for other UI elements like a custom crosshair, but as a newbie modder I wanted to thank you for the knowledge. I've used your idea to add Urik/SCHISM crosshair support to another existing HUD mod , and I wanted to give you credit for the idea.

Because of you, the mod that I've made contains a very small dot crosshair, but still allows support for an additional Urik/SCHISM crosshair, like SCHISM's Tri-Angled crosshair (therefore making it so that the Tri-Angled crosshair has a dot in the middle). It was an interesting discovery, so thank you for that.

Игра, временами, вылетает именно с модом. После отключении вылеты прекращаются.

гавно ебанное ссука!

Блять, я просто хочу нормальный прицел, сукаа...

Will this conflict with poM's No HUD mod?

There is file called hudlayout.res and it's like the main gui file. It defines areas and dimensions for most other elements (self panel, teammate panels, scoreboards, timer panels, etc ). And while the majority of these other elements have their own .res files so that they can be edited (to some degree) without touching hudlayout, weapon panel can be only modified in hudlayout.res since it doesn't have its own file.
Being a new custom element (image panel), the only way custom crosshair can be added is into the hudlayout.res (because it covers entire screen space and thus you can put xhair in the center). So that's why we have so many conflicts.
For example, "vertical" teampanels alignment usually requires modifying the hudlayout, because otherwise there just isn't enough space vertically (because hudlayout defines the area for teamdisplayhud.res) Which would again conflict if there's also weapon panel mod etc.
The drawback of the "global" method is that it shows always including ~

~ spectator screen and infected gameplay. The other way (survivor-only) which I used in my huds modifies additional files so it isn't possible to use with other
huds without re-editing those huds. You may have noticed my crosshair uses some weird material .vmt it's because it's the only files in default l4d2 which is a) unused (it's some hl2/cs leftover junk) b) is transparent/empty , so that you don't get pink
checkerboard without crosshair vpk. That way I could have crosshair supported in the my hud without too much complications.
I don't know about Neun weapon panel, it must've been written in description about differences.
There's a tool called BeyondCompare Pro (it's commercial, but there's *****ed versions on torrent trackers), I use it to compare files including text files like .res , makes it easier to see differences.
If you use some custom hud (not my), I could take some time to implement the crosshair support (survivor version) into that mod if you really need.

May I ask what's exactly special about NeunGUI weapon panel? I'm a NeunGUI user myself, but I don't use the weapon panel addon.

Just recenlty I've made a custom crosshair mod, using Urik's method to avoid conflicts, because the original custom crosshair-change method messes up the default weapon panel (exactly because of hudlayout.res).

You can see yourself how it looks from the screenshots here .