Forum posts
What are you planning, Kimilil? 😃
Awesome, fantastic work! 🥳
Posted 2 weeks ago2024-07-10 07:54:47 UTC
in Is there a way to make a toggleable looping circuit? Post #348973
in Is there a way to make a toggleable looping circuit? Post #348973
In your typical multi_manager loop, you set the Multi-threaded flag and have it target whatever is supposed to repeatedly trigger, and after some delay it'll trigger itself.
Triggering the multi_manager again will only create more loops, so instead of a button to start the loop we can use a trigger_auto to start it from the beginning of the map, and instead of triggering the target directly we can use a trigger_relay, but we'll leave the relay's target empty to begin with.
To connect the target to the loop, we let the button target a trigger_changetarget (we can name it turn_on) to change the relay's target to our env_blood. We can use another trigger_changetarget (sharing the same name as the first) that will change the button's target to turn_off.
Now we create another pair of trigger_changetarget, both named turn_off. One will change the relay's target back to empty, and the other will change the button's target to turn_on.
It might be a bit complicated, but here's an example map for such a toggled loop:
To connect the target to the loop, we let the button target a trigger_changetarget (we can name it turn_on) to change the relay's target to our env_blood. We can use another trigger_changetarget (sharing the same name as the first) that will change the button's target to turn_off.
Now we create another pair of trigger_changetarget, both named turn_off. One will change the relay's target back to empty, and the other will change the button's target to turn_on.
Posted 2 weeks ago2024-07-08 18:48:57 UTC
in Improving accuracy of collisions with pushables? Post #348967
in Improving accuracy of collisions with pushables? Post #348967
I'm sorry, I was wrong. My brain must have had a hiccup last night. Of course changing the
Maybe you could force it to use the pointhull, and do your own collision checks using its bounding box. The performance won't be as good as with cliphull-based collisions, of course.
pev->movetype to MOVETYPE_STEP won't help, and monsters uses the cliphulls as well for entity-to-world collisions.Maybe you could force it to use the pointhull, and do your own collision checks using its bounding box. The performance won't be as good as with cliphull-based collisions, of course.
There's no reason for hollowing out solid brushes for "performance" reasons.
If the hollow volume is big enough, it'll even produce more clipnodes as Urby says, just wasting away the clipnode budget for no good reason.
If those brushes are world brushes, it's even less reason to do so as any outside and unseen faces will be stripped out by the compilers automatically anyway.
Manually NULLing faces is an optimisation step you only should do if you need to. Otherwise you're just wasting time that could have gone to actually building the map.
If the hollow volume is big enough, it'll even produce more clipnodes as Urby says, just wasting away the clipnode budget for no good reason.
If those brushes are world brushes, it's even less reason to do so as any outside and unseen faces will be stripped out by the compilers automatically anyway.
Manually NULLing faces is an optimisation step you only should do if you need to. Otherwise you're just wasting time that could have gone to actually building the map.
You could take a look at the speaker entity. It plays a sentence from sentences.txt at a random interval between 3 and 10 minutes. Using a sentence group (sentences with the same name but different number suffix) will make it choose a random sentence from the group.
It's used a lot in the original Half-Life campaign where it adds random background noises. In these cases multiple
If you're mapping for HL, you can take a look at predefined sentence groups in sentences.txt and see if any fits your need. If you're making a mod, you could create a new custom sentence group that fits exactly your need.
It's used a lot in the original Half-Life campaign where it adds random background noises. In these cases multiple
speaker entities are used together to make the sounds play more often. An example would be c2a5c, where four speaker entities set to play the FAR_WAR sentence group to add an ambiance of distant combat.If you're mapping for HL, you can take a look at predefined sentence groups in sentences.txt and see if any fits your need. If you're making a mod, you could create a new custom sentence group that fits exactly your need.
Posted 2 weeks ago2024-07-07 21:36:58 UTC
in Improving accuracy of collisions with pushables? Post #348959
in Improving accuracy of collisions with pushables? Post #348959
Your guess of it having something to do with the HULL sizes is correct.
While player-on-pushable collisions uses the pushable's bounding box, the pushable's collisions with the level uses clipping hulls instead.
Clipping hulls date back to Quake. Essentially, instead of continuously testing mesh-on-mesh collisions (very expensive), the player and pushables are simulated as a single point, and collision hulls are pre-calculated by expanding the solid level geometry by an appropriate amount (e.g. 16 units horizontally and 36 units vertically for HULL1). This way collisions are tested using point-on-mesh instead, which is computationally very cheap. It performs better, and that's why the engine uses this instead of bounding boxes.
It might be possible to force it to use bounding box instead, I'm guessing changing the
While player-on-pushable collisions uses the pushable's bounding box, the pushable's collisions with the level uses clipping hulls instead.
Clipping hulls date back to Quake. Essentially, instead of continuously testing mesh-on-mesh collisions (very expensive), the player and pushables are simulated as a single point, and collision hulls are pre-calculated by expanding the solid level geometry by an appropriate amount (e.g. 16 units horizontally and 36 units vertically for HULL1). This way collisions are tested using point-on-mesh instead, which is computationally very cheap. It performs better, and that's why the engine uses this instead of bounding boxes.
It might be possible to force it to use bounding box instead, I'm guessing changing the
pev->movetype to MOVETYPE_STEP should get it to use similar collisions as monsters, though it's not guaranteed to be better.The process is exactly the same as any custom content for the mod: Place the custom assets in the corresponding folder in your mod's folder.
If you've already started working on your mod, you should have a folder at
Any custom models should then be placed in
This way when you launch the mod, it'll use the custom models instead of the vanilla models.
You can check out Tutorial: Setting up a Mod: Part 1 - Mod directory and liblist.gam (Steam) for more information about setting up a mod.
If you've already started working on your mod, you should have a folder at
.../Steam/steamapps/common/Half-Life/<your_mod>.Any custom models should then be placed in
.../Steam/steamapps/common/Half-Life/<your_mod>/models.This way when you launch the mod, it'll use the custom models instead of the vanilla models.
You can check out Tutorial: Setting up a Mod: Part 1 - Mod directory and liblist.gam (Steam) for more information about setting up a mod.
Posted 4 weeks ago2024-06-28 18:50:58 UTC
in trenchbroom asking for a non-existant .p0 file when compiling...? Post #348937
in trenchbroom asking for a non-existant .p0 file when compiling...? Post #348937
No problem! It's easy to miss things, sometimes all you need is another pair of eyes to take a look 🙂
Posted 4 weeks ago2024-06-28 15:13:46 UTC
in trenchbroom asking for a non-existant .p0 file when compiling...? Post #348934
in trenchbroom asking for a non-existant .p0 file when compiling...? Post #348934
I haven't tried TB yet, but I suspect that the CSG lacking a checkmark to the left of it, unlike the BSP just below it, in that screenshot might tell us that CSG is disabled.
Posted 4 weeks ago2024-06-28 08:18:01 UTC
in trenchbroom asking for a non-existant .p0 file when compiling...? Post #348932
in trenchbroom asking for a non-existant .p0 file when compiling...? Post #348932
The problem is that you're missing the CSG compiler at the start of the compilation process, you're only running BSP, VIS and RAD.
It should have been CSG -> BSP -> VIS -> RAD.
It should have been CSG -> BSP -> VIS -> RAD.
The Sven Co-op engine (AKA Svengine) is a modified version of GoldSrc.
Even if it had the same engine, it's still a standalone game with its own executable and settings separate from Half-Life.
So, did you try out the advice you got in the other thread for Sven Co-op specifically?
Even if it had the same engine, it's still a standalone game with its own executable and settings separate from Half-Life.
So, did you try out the advice you got in the other thread for Sven Co-op specifically?
Did you try out the advice you got in the last thread for Sven Co-op as well?
Sven Co-op and Half-Life are two different games using separate executables and settings, so fixing the problem in one game won't affect the other.
Sven Co-op and Half-Life are two different games using separate executables and settings, so fixing the problem in one game won't affect the other.
When you made the model replacement, did you shift the origin up to the center (36 units up from the bottom of the model)?
Most prop and monster models have the origin placed at the bottom/feet, but playermodels specifically has the origin at the center of the player bounds.
Most prop and monster models have the origin placed at the bottom/feet, but playermodels specifically has the origin at the center of the player bounds.
Posted 1 month ago2024-06-04 22:20:57 UTC
in I made a wad but some textures don't show up. Post #348851
in I made a wad but some textures don't show up. Post #348851
Is the valve/aleph.wad the same WAD package that has been updated, or is your Game Configuration in JACK pointing to a different WAD file?
Both the Apply Decals tool and the infodecal entity it creates can only use textures from
To create signs using textures from any other WAD, such as halflife.wad, you can instead create a very thin brush with the chosen texture and tie it to func_detail.
Set the Passable (zhlt_noclip) keyvalue to Yes (1) and then the player won't be able to collide with it.
decals.wad. Any other textures won't work.To create signs using textures from any other WAD, such as halflife.wad, you can instead create a very thin brush with the chosen texture and tie it to func_detail.
Congrats! 🥳
Keep it up!
Keep it up!
The compile tools are fine, the Run Dialogue are finding them and launching them without issue, as you can see from the compile log (again, you should read it).
The problem now, as you can easily find by reading the compile log, is that the WAD file
The problem now, as you can easily find by reading the compile log, is that the WAD file
/Users/marii/Documents/1compiletools/tools/sdhlt.wad is not found. You should change the entry for this WAD in the Game Configuration, to point to its location on the X:/ drive.Hi, and welcome to TWHL!
Please don't be intimidated by the compile log, it has a lot of useful information about the compile process and learning how to read it will be very helpful in the long run.
If you look near the end of the log, you will see the text
"There was a problem compiling the map."
When you see that, or a BSP was for some reason not produced, open the compile log in a text editor and search for the keyword "Error".
Compile logs like this will produce lines starting with "Error: " that will tell you what went wrong and oftentimes how to fix it.
Try it out yourself before continuing.
In this case the error is:
Error: Could not open wad file /Users/marii/Documents/1compiletools/tools/sdhlt.wad
Error: Could not find WAD file
Description: The compile tools could not locate a wad file that the map was referencing.
Howto Fix: Make sure the wad's listed in the level editor actually all exist
Unfortunately this one can be a bit cryptic. I noticed your compile tools and game directories are in two different drives (C:\ and X:\). The compile tools tend to have issues with finding files that are on a different drive, so I recommend moving the compile tools to the same drive as the game installation.
Please don't be intimidated by the compile log, it has a lot of useful information about the compile process and learning how to read it will be very helpful in the long run.
If you look near the end of the log, you will see the text
"There was a problem compiling the map."
When you see that, or a BSP was for some reason not produced, open the compile log in a text editor and search for the keyword "Error".
Compile logs like this will produce lines starting with "Error: " that will tell you what went wrong and oftentimes how to fix it.
Try it out yourself before continuing.
In this case the error is:
Error: Could not open wad file /Users/marii/Documents/1compiletools/tools/sdhlt.wad
Error: Could not find WAD file
Description: The compile tools could not locate a wad file that the map was referencing.
Howto Fix: Make sure the wad's listed in the level editor actually all exist
Unfortunately this one can be a bit cryptic. I noticed your compile tools and game directories are in two different drives (C:\ and X:\). The compile tools tend to have issues with finding files that are on a different drive, so I recommend moving the compile tools to the same drive as the game installation.
Most sprites in GoldSrc already automatically rotate on their own, to face the player camera. This is known as Parallel Orientation. It is one of 5 Orientation types:
What you might want to use is the Oriented type. In vanilla HL1 you're not able to set a sprite's Orientation type through mapping, it must be done by editing the sprite file itself. You can use Half-Life Texture Tools to do this, either when creating a new sprite or when editing an existing one.
After that the sprite will obey the Entity Attribute: Pitch Yaw Roll (angles) keyvalue.
After that the sprite will obey the Entity Attribute: Pitch Yaw Roll (angles) keyvalue.
By "particle" you likely mean sprite, which are 2D image objects in the game, and yes these can be attached to a playermodel and turned on/off based on various conditions such as when a flashlight is turned on/off.
Both making the sprite turn on/off, and limiting its use to only specific weapons, should be possible to code in
Both making the sprite turn on/off, and limiting its use to only specific weapons, should be possible to code in
CBasePlayer::FlashlightTurnOn() and CBasePlayer::FlashlightTurnOff() methods. Of course, you'll need to use programming for this using the SDK.By "repair men", do you mean Gus?
Gus (forklift.mdl)
If so the model name is forklift.mdl and it's one of Half-Life standard assets (so this version from
On the other hand, if you mean some player model then there's
As for using assets from the main games (such as Half-Life, Blue Shift and Opposing Force), it's generally fine to do so for a HL/BS/Op4 mod. So re-using a main game texture in your mod's WAD is all good.
It's only a problem if you lift these assets out of these games and put them in another non-Valve game.
Gus (forklift.mdl)Half-Life/valve/models can be used in your mod).On the other hand, if you mean some player model then there's
/models/player/HL_Construction/HL_Construction.mdl and /models/player/HL_Gus/HL_Gus.mdl from Sven Co-op and these are specific to SC, which means that you should ask for permission to use these in your mod, and possibly need to do some conversion as the player skeleton and/or sequences are different between HL and SC.
As for using assets from the main games (such as Half-Life, Blue Shift and Opposing Force), it's generally fine to do so for a HL/BS/Op4 mod. So re-using a main game texture in your mod's WAD is all good.
It's only a problem if you lift these assets out of these games and put them in another non-Valve game.
Posted 2 months ago2024-04-29 18:10:07 UTC
in How to change hand texture throughout maps Post #348761
in How to change hand texture throughout maps Post #348761
I remember seeing this being done in some mod, could it have been Azure Sheep?
If I recall correctly, there was basically a duplicated set of weapons, one that used the uniform-clothed hands and another with the hands wearing the HEV suit. Then at some point in the campaign you would be stripped of your weapons and find yourself a HEV suit before being given the HEV-variants of the weapons.
This is of course a game code change, not something that can be done purely through mapping.
If I recall correctly, there was basically a duplicated set of weapons, one that used the uniform-clothed hands and another with the hands wearing the HEV suit. Then at some point in the campaign you would be stripped of your weapons and find yourself a HEV suit before being given the HEV-variants of the weapons.
This is of course a game code change, not something that can be done purely through mapping.
If this is a singleplayer campaign, you can fake the elevator just like how it's done in the HL1 campaign (e.g. the transition from c1ac1 to c1a2, the end of Unforeseen Consequences and start of Office Complex). This is probably the easiest solution.
Basically there's no moving elevator whatsoever. Just a room that looks like an elevator, a set of doors, and a button inside to trigger a trigger_changelevel.
After the level transition you're taken to an identical "elevator" room. An env_shake creates a rumbling and various ambient_generics creates noise, together creating the illusion of movement. Do this for a few seconds, then trigger a ambient_generic with a "ding!" sound and trigger the doors to open.
Add other details/effects to taste.
If it has to be within one level, then as Urby says a trigger_teleport has no relative offset in vanilla GoldSrc which would be very obvious and immersion-breaking. Additionally, to "toggle" a trigger_teleport you need to use a multisource master as trigger_teleport cannot be triggered on/off directly.
Another solution, which is a lot more complex than the others, is instead of using func_door for the doors you use func_train. Essentially 3 trains moving together to create the elevator.
This sort of setup needs careful timing and path_corner's Fire on Pass key can be of great help with that.
Basically there's no moving elevator whatsoever. Just a room that looks like an elevator, a set of doors, and a button inside to trigger a trigger_changelevel.
After the level transition you're taken to an identical "elevator" room. An env_shake creates a rumbling and various ambient_generics creates noise, together creating the illusion of movement. Do this for a few seconds, then trigger a ambient_generic with a "ding!" sound and trigger the doors to open.
Add other details/effects to taste.
If it has to be within one level, then as Urby says a trigger_teleport has no relative offset in vanilla GoldSrc which would be very obvious and immersion-breaking. Additionally, to "toggle" a trigger_teleport you need to use a multisource master as trigger_teleport cannot be triggered on/off directly.
Another solution, which is a lot more complex than the others, is instead of using func_door for the doors you use func_train. Essentially 3 trains moving together to create the elevator.
This sort of setup needs careful timing and path_corner's Fire on Pass key can be of great help with that.
The Delay before close (wait) value of
What you likely want in this situation is a Delay before close value greater than zero, but with the Toggle (32) spawnflag set instead.
That way, the door will open the first time it's triggered, and then close on the next trigger.
-1 makes it never close.What you likely want in this situation is a Delay before close value greater than zero, but with the Toggle (32) spawnflag set instead.
That way, the door will open the first time it's triggered, and then close on the next trigger.
Posted 3 months ago2024-04-19 18:28:41 UTC
in BEGINNER TO RESKINNING HALF-LIFE 1 MODELS? Post #348729
in BEGINNER TO RESKINNING HALF-LIFE 1 MODELS? Post #348729
Hi and welcome to TWHL! It's nice to see someone with passion for learning to mod HL 🙂
Textures, whether for models or for maps, are very similar in requirements and how they're made. You can follow The303's map texture guide here.
For the image editor I can recommend Gimp. Alternatively there's also Paint.net, and for the final conversion to 8BPP BMP (AKA 256 colours indexed BMP) I recommend IrfanView as it does a really great job at preserving the colour quality. All three are free.
As for why the image loses quality when converting to 8BPP it's simply because you're reducing the amount of colour values that exists in the image, typically from 16,777,216 different colour values (24bit RGB) to only 256 colours!
For model viewers, these days it's recommended to use HLAM as it's far more up-to-date and have a lot of nice features.
Textures, whether for models or for maps, are very similar in requirements and how they're made. You can follow The303's map texture guide here.
For the image editor I can recommend Gimp. Alternatively there's also Paint.net, and for the final conversion to 8BPP BMP (AKA 256 colours indexed BMP) I recommend IrfanView as it does a really great job at preserving the colour quality. All three are free.
As for why the image loses quality when converting to 8BPP it's simply because you're reducing the amount of colour values that exists in the image, typically from 16,777,216 different colour values (24bit RGB) to only 256 colours!
For model viewers, these days it's recommended to use HLAM as it's far more up-to-date and have a lot of nice features.
Ah, I see. Thanks for the update, Solokiller!
Could you take a screenshot of your door's keyvalues with SmartEdit disabled?
Please post your solution, so that others that stumble upon this thread may learn from it. 🙂
I haven't messed around with GMod in quite some years, but could you give some more details?
When loading fails, is that only happening on a particular map?
And when you say loading works from a different map, is that any other map, or a specific map?
When loading fails, is that only happening on a particular map?
And when you say loading works from a different map, is that any other map, or a specific map?
Posted 3 months ago2024-03-29 21:32:43 UTC
in How to trigger a multi_manager when two trigger_multiple's are being touched? Post #348677
in How to trigger a multi_manager when two trigger_multiple's are being touched? Post #348677
You can use a multisource as a logic AND gate (i.e. all inputs must be ON at the same time).
Make sure it's only your two trigger_multiple entities that are targetting the multisource.
Make sure it's only your two trigger_multiple entities that are targetting the multisource.
That's not a bug but instead a common level design error known as a Leak. It means that the level isn't properly sealed (all entities must be contained within world geometry).
This guide can help you fixing those leaks.
This guide can help you fixing those leaks.
"
The coordinates you get is the lower bounds (-X, -Y, -Z) and upper bounds (X, Y, Z) and the problem brush is within that box.
If it's hard to visualise this bounding box, you could make a box brush with those bounds, or use the Cordon Tool to limit the map to those bounds, and look if there's any misshapen brushes in there (either world brush or func_detail).
model 0" is the worldspawn model, i.e. all world brushes (including func_detail).The coordinates you get is the lower bounds (-X, -Y, -Z) and upper bounds (X, Y, Z) and the problem brush is within that box.
If it's hard to visualise this bounding box, you could make a box brush with those bounds, or use the Cordon Tool to limit the map to those bounds, and look if there's any misshapen brushes in there (either world brush or func_detail).
Hm, at a first glace it looks fine to me. Nothing that seems out of place and it doesn't seem like there's any direct contact, geometric or trigger-wise, between the trigger_hurt and the trigger_gravity volumes.
I ended up working longer than I expected today and so I think I'll wait until tomorrow to set up a DoD config and compile and test this myself, sorry.
If you want to, you could compile it yourself with
I ended up working longer than I expected today and so I think I'll wait until tomorrow to set up a DoD config and compile and test this myself, sorry.
If you want to, you could compile it yourself with
-chart argument on the compile tools and check for warnings and any limits being reached, and run the map with developer 2 and check for any console messages when the trigger_hurt is triggered.If you want, you could upload your map in the vault and link it here and I can take a look at it after work tomorrow.
I don't think any of your other triggers are affecting the trigger_gravity entities, as trigger_gravity cannot be toggled.
trigger_gravity doesn't define a volume of a certain gravity but instead defines a volume where a new gravity is set, and stays at this new gravity value until a different trigger_gravity is entered.
Is it possible you didn't take this behaviour into account in your map?
trigger_gravity doesn't define a volume of a certain gravity but instead defines a volume where a new gravity is set, and stays at this new gravity value until a different trigger_gravity is entered.
Is it possible you didn't take this behaviour into account in your map?
Hey and welcome!
Compile logs are for the most part humanly readable and will contain a lot of useful information about the compilation process.
Near the end of the log you have the message:
The quickest way to find problems in the log is to open it in a text editor and search for "error" (serious problems preventing compilation) and then for "warning" (less serious problems that doesn't prevent compilation but can cause issues in the compiled map).
The messages you find tend to be very self-explanatory and often tell you how to fix them. In other cases when it's more unclear you can look up the error message at Tommy14's compile error page.
In your case you'll find the warning message: "Warning: === LEAK in hull 0 ==="
That means there's a leak in your map and you can use this guide to find and fix it: Tutorial: How to fix those leaks
As for why the map turns out fullbright when there's a leak, it's because leaks prevents VIS and RAD from running, and RAD is the compile tool that generates lightmaps. Without lightmaps, the map becomes fullbright.
Compile logs are for the most part humanly readable and will contain a lot of useful information about the compilation process.
Near the end of the log you have the message:
There was a problem compiling the map.which means you had one or more problems in the map which will be described further up in the log.
Check the file C:\Program Files (x86)\Steam\steamapps\common\Half-Life\valve\maps\Q3.log for the cause.
The quickest way to find problems in the log is to open it in a text editor and search for "error" (serious problems preventing compilation) and then for "warning" (less serious problems that doesn't prevent compilation but can cause issues in the compiled map).
The messages you find tend to be very self-explanatory and often tell you how to fix them. In other cases when it's more unclear you can look up the error message at Tommy14's compile error page.
In your case you'll find the warning message: "Warning: === LEAK in hull 0 ==="
That means there's a leak in your map and you can use this guide to find and fix it: Tutorial: How to fix those leaks
As for why the map turns out fullbright when there's a leak, it's because leaks prevents VIS and RAD from running, and RAD is the compile tool that generates lightmaps. Without lightmaps, the map becomes fullbright.
It does exist in GoldSrc, it's used to halt execution of the following commands until the next frame (often used complex binds to prevent multiple commands happening on the same frame).
I don't think the GoldSrc version takes any arguments though, only ever waiting a single frame.
I don't think the GoldSrc version takes any arguments though, only ever waiting a single frame.
Hi and welcome!
First of all it sounds like you're using very old compile tools (as it doesn't automatically add CLIP to the sky), I highly recommending switching to Vluzacn's ZHLT v34.
Secondly to make invisible walls and such it's better to use CLIP texture. It creates a collision mesh in the shape of the brush it's applied to.
As for the reason why the
First of all it sounds like you're using very old compile tools (as it doesn't automatically add CLIP to the sky), I highly recommending switching to Vluzacn's ZHLT v34.
Secondly to make invisible walls and such it's better to use CLIP texture. It creates a collision mesh in the shape of the brush it's applied to.
As for the reason why the
{invisible texture didn't turn invisible, it's because the brush covered in it must be tied to a solid entity such as func_wall with the render mode set to Solid (this render mode removes the masking colour from {-prefixed textures, most of the time this is the blue colour). In most cases it's better to use NULL texture instead (removes the face completely).When making signs you pretty much have to do it using brushes.
A common and easy technique is to make it a thin brush and tie it to func_detail and set Passable to Yes (zhlt_noclip 1). This prevents it from both chopping the walls it's placed on, as well as generating unnecessary clipnodes the player might collide with.
Another technique is to actually embed it in the wall and either use the Clipping Tool to cut out a hole for the sign:
or, a bit more advanced technique is a sort of mix of the two. Embed the sign in the wall as with the second technique, but instead of clipping a hole in the wall leave it as it is and tie the sign to a func_detail again. This time set the Detail level (zhlt_detaillevel) to 1 and the Priority when faces overlap (zhlt_coplanarpriority) to 1 as well.
It will do a lot of Z-fighting in the editor (flickering) but in-game it's the sign that will be visible without any Z-fighting (because of the zhlt_coplanarpriority keyvalue).
A common and easy technique is to make it a thin brush and tie it to func_detail and set Passable to Yes (zhlt_noclip 1). This prevents it from both chopping the walls it's placed on, as well as generating unnecessary clipnodes the player might collide with.
or, a bit more advanced technique is a sort of mix of the two. Embed the sign in the wall as with the second technique, but instead of clipping a hole in the wall leave it as it is and tie the sign to a func_detail again. This time set the Detail level (zhlt_detaillevel) to 1 and the Priority when faces overlap (zhlt_coplanarpriority) to 1 as well.
It will do a lot of Z-fighting in the editor (flickering) but in-game it's the sign that will be visible without any Z-fighting (because of the zhlt_coplanarpriority keyvalue).
The problem has nothing to do with the compilers (you'll likely find the infodecal entities in the entity lump of the compiled BSP).
What is actually happening here is that decals only work with the special textures from the game/mod's decals.wad file, and you've used normal textures from halflife.wad
What is actually happening here is that decals only work with the special textures from the game/mod's decals.wad file, and you've used normal textures from halflife.wad
Seems like efs didn't post an update here so I'll do it.
The problem was the landmark. I assume that particular issue was fixed then.
The problem was the landmark. I assume that particular issue was fixed then.
I got your DM.
So you're having trouble with level changes where the player spawns at map origin in the second level.
In that case you should check that
So you're having trouble with level changes where the player spawns at map origin in the second level.
In that case you should check that
- There is an info_landmark in both levels and named the same (without any special symbols or non-latin letters)
- Both levels have a trigger_changelevel pointing to the corresponding map of the level change (i.e. the first level pointing to the second, and the second pointing to the first). It must do this even for one-way level transitions (in this case the second level's trigger_changelevel can be placed outside the playable area to keep the player from going back).
There are plenty of people here that can help, depending on the problem/issue.
Start by telling us what problems you've been having, one at a time.
Tell us what you wanted to do, what you expected to happen, what you've tried, and what actually happened instead.
Start by telling us what problems you've been having, one at a time.
Tell us what you wanted to do, what you expected to happen, what you've tried, and what actually happened instead.
Yeah, it was around late 2010s, Discord really took off soon after its release.
Though he decline of forums have been going on for longer, alongside the growing popularity of social media platforms such as FB and Twitter. Unlike forums, these platforms are designed to bring tons of personalised content directly at the users.
Between the two, it's kind of like the choice between having a bag of candy handed to you or going to the kitchen and cook a healthy dinner. The latter has higher quality, but the former gets you instant gratification for no effort. It's no surprise which one is more popular, despite the downsides.
Though he decline of forums have been going on for longer, alongside the growing popularity of social media platforms such as FB and Twitter. Unlike forums, these platforms are designed to bring tons of personalised content directly at the users.
Between the two, it's kind of like the choice between having a bag of candy handed to you or going to the kitchen and cook a healthy dinner. The latter has higher quality, but the former gets you instant gratification for no effort. It's no surprise which one is more popular, despite the downsides.
Sledge is an open source level editor for Goldsrc.
Unfortunately not being developed anymore, and the Tools and Resources page says "Unfinished and rather unstable - use with caution"
Unfortunately not being developed anymore, and the Tools and Resources page says "Unfinished and rather unstable - use with caution"
It's very much not dead.
Just because it's not a spammy memedump, or has as much activity as a chat platform, it doesn't mean it's dead. It's just quiet and that tends to be the case for forums in this age where forums are not as popular as they used to be (which is a shame). People are still around and reading and posting, just might take some hours or days between posts.
Just because it's not a spammy memedump, or has as much activity as a chat platform, it doesn't mean it's dead. It's just quiet and that tends to be the case for forums in this age where forums are not as popular as they used to be (which is a shame). People are still around and reading and posting, just might take some hours or days between posts.
As far as I know Valve haven't given us an estimate yet
Posted 6 months ago2024-01-19 08:43:58 UTC
in Trouble regarding re-texture and compiling Post #348480
in Trouble regarding re-texture and compiling Post #348480
You're getting the "padev.wad not found" error message because you have some textures from that WAD in your map, but you don't have the WAD in your mod folder or haven't used the
To make things easier, use a game configuration in your editor that only uses the standard set of HL textures (and zhlt.wad):
Open the texture browser and enable the checkbox for Only used textures.
All textures with a black-purple checkerboard is an invalid texture, so click it and hit Replace... and for the replacement (right side) type in "C1A0_W1" for example.
Do this for all invalid textures until there are no more errors when you Check for problems (Alt+P).
After that, compile the map and make sure the BSP is placed in your mod's maps folder, launch your mod and start up the map.
-wadinclude padev argument on the CSG compiler.To make things easier, use a game configuration in your editor that only uses the standard set of HL textures (and zhlt.wad):
halflife.wad
decals.wad
liquids.wad
xeno.wad
zhlt.wadInvalid texture ('<texture name>') errors. These cannot be fixed by the editor so you have to fix it manually:Open the texture browser and enable the checkbox for Only used textures.
All textures with a black-purple checkerboard is an invalid texture, so click it and hit Replace... and for the replacement (right side) type in "C1A0_W1" for example.
Do this for all invalid textures until there are no more errors when you Check for problems (Alt+P).
After that, compile the map and make sure the BSP is placed in your mod's maps folder, launch your mod and start up the map.
Posted 6 months ago2024-01-18 09:30:38 UTC
in Trouble regarding re-texture and compiling Post #348469
in Trouble regarding re-texture and compiling Post #348469
I highly encourage keeping the valve folder free of any custom content. The valve_addon folder (enabled in Options -> Content -> Allow custom addon content), or even better your mod's directory, should be used instead.
Make sure you don't have a duplicate of your WAD in the valve folder, and make sure the one in your mod's folder is up-to-date with your changes.
As for the problem in hand, it's possible the textures in your WAD are named the same as textures from stock Half-Life WADs, such as halflife.wad.
This causes a naming conflict where (iirc) the texture of the first WAD to load will replace any subsequent textures of the same name.
If that's the case, you simply just have to rename your textures and fix the references in your map in the level editor.
Make sure you don't have a duplicate of your WAD in the valve folder, and make sure the one in your mod's folder is up-to-date with your changes.
As for the problem in hand, it's possible the textures in your WAD are named the same as textures from stock Half-Life WADs, such as halflife.wad.
This causes a naming conflict where (iirc) the texture of the first WAD to load will replace any subsequent textures of the same name.
If that's the case, you simply just have to rename your textures and fix the references in your map in the level editor.