Forum posts
- Forums
- Posts
- Posted by
Penguinboy
That's just a crash, the error about JIT would just be programmer stuff I think. Try updating to the latest free version (released only in the last week or two), it fixed a common crash in the entity properties window. If you're already using that version... just make sure you have enabled autosave in the options because you can't do anything about it crashing sometimes.
Posted 3 months ago2024-01-18 01:36:24 UTC
in Competition 42: Half-Life 25th Anniversary: Vanilla HLDM Post #348465
in Competition 42: Half-Life 25th Anniversary: Vanilla HLDM Post #348465
Yep, I'm working through the submission issues on Discord, all good.
Posted 4 months ago2023-12-18 09:28:46 UTC
in Competition 42: Half-Life 25th Anniversary: Vanilla HLDM Post #348262
in Competition 42: Half-Life 25th Anniversary: Vanilla HLDM Post #348262
Hi, where do I actually make a submission?At the bottom of the competition brief, use the 'submit entry' form.
Posted 4 months ago2023-11-29 04:37:51 UTC
in Best way to updating pre-existing entity guide pages Post #348109
in Best way to updating pre-existing entity guide pages Post #348109
We don't really have a standard way to do it - it would be best to keep all the games on the same page unless they are significantly different for some reason. So I would say...
- Same entity with only slightly different game-specific stuff -> add info box with the game-specific info
- Same entity with very different game-specific stuff -> create new page with the game-specific info (new page called "entity_name (Game Name)")
I might be able to do something like that, I'll investigate when I can.
B
I choose option C, and also that you don't do the podcast thing.
Tower 1 uses spirit 1.8, maybe you downloaded the wrong version? I have a Linux version of SOHL 1.8 with bug fixes here, but note that I do not test these builds on Linux.
For Tower 2, it uses a slightly customised version of SOHL 1.8, the changes are pretty minor so the same thing might work for that, otherwise you can compile it yourself from this branch.
It might be easiest to just use WINE/Proton though.
For Tower 2, it uses a slightly customised version of SOHL 1.8, the changes are pretty minor so the same thing might work for that, otherwise you can compile it yourself from this branch.
It might be easiest to just use WINE/Proton though.
Spirit has a setting to enable single-player gauss jumping for a map, which that level uses. But SOHL can also be a bit bad at times, so it might be glitched or something in your save game. I didn't have any issues with the jump when I played it, but if it's not working right you can always just noclip through.
Posted 1 year ago2022-12-15 23:21:29 UTC
in What is an other way to prevent leaks that isnt a giant box around the map? Post #347167
in What is an other way to prevent leaks that isnt a giant box around the map? Post #347167
Read through VERC: Leaks for methods on finding leaks.
Posted 1 year ago2022-11-14 00:40:22 UTC
in Done with Op4 map, do I just send the .bsp file or do people need additional files to run it? Post #347084
in Done with Op4 map, do I just send the .bsp file or do people need additional files to run it? Post #347084
Yes, just the .bsp file is fine. If you used custom content (you didn't in this case), you would include that too.
...don't do that.
As I've said in the past, I'm not interested in maintaining TWHL in alternate languages. But feel free to translate the content somewhere else, just be sure to provide credit and a link back to the TWHL page.
As I've said in the past, I'm not interested in maintaining TWHL in alternate languages. But feel free to translate the content somewhere else, just be sure to provide credit and a link back to the TWHL page.
Posted 1 year ago2022-10-27 12:42:11 UTC
in Was Goldsrc built off of WinQuake or QuakeWorld? Post #347012
in Was Goldsrc built off of WinQuake or QuakeWorld? Post #347012
The only difference between the HL and Quake BSP formats is that HL has RGB lighting and Quake only has monochrome lighting. That's why the lightmaps are wrong.
Hm, that would be a bit tricky to add, other pages will have categories and other stuff that shouldn't be included in the base page, also there's the challenge of what you do when the embedded page is updated... then you have to detect and re-render all the pages that embed it. I think I'd need more of a justification for a feature like that.
Yeah, I think those flag descriptions should probably just be in the relevant entity pages, doesn't make a whole lot of sense to have separate ones. I think these came from the old glossary section from before we had a wiki.
Posted 1 year ago2022-07-17 01:55:47 UTC
in Error: Exceeded MAX_MAP_VERTS on map with many prefabs Post #346722
in Error: Exceeded MAX_MAP_VERTS on map with many prefabs Post #346722
Yep - brush entities do count towards the brush limit, it's models that do not. The complexity of the map would explain why Hammer was running slowly as well, it's not designed to handle that many brushes.
Posted 1 year ago2022-06-10 02:05:37 UTC
in Tutorials on getting started on Half-Life programming? Post #346614
in Tutorials on getting started on Half-Life programming? Post #346614
No sorry I've never used cmake myself, but there's probably resources online that you can find.
Posted 1 year ago2022-06-10 00:54:32 UTC
in Tutorials on getting started on Half-Life programming? Post #346612
in Tutorials on getting started on Half-Life programming? Post #346612
Visual Studio is kind of important if you want to use the SDK properly. But there's some alternative options.
Tutorials will all reference VS because that's the normal way of doing things, so not using it will make it more difficult.
First of all, and this is not optional, you must install the C++ build tools. This means that you either install Visual Studio 2022 (no need to use it, just install it), or the standalone Build Tools for Visual Studio 2022.
Compile via the command line:
Cmake replaces the VS project system with its own. When adding a new source file, you can use cmake to build instead of VS.
Tutorials will all reference VS because that's the normal way of doing things, so not using it will make it more difficult.
First of all, and this is not optional, you must install the C++ build tools. This means that you either install Visual Studio 2022 (no need to use it, just install it), or the standalone Build Tools for Visual Studio 2022.
Option one: use halflife-updated:
You cannot add new files to the solution since this requires Visual Studio to update the project files.Compile via the command line:
path/to/MSBuild.exe path/to/projects/vs2019/projects.sln /p:Configuration=Release /p:Platform=Win32Option two: use halflife-updated-cmake:
Cmake is complicated and requires extra knowledge to use.Cmake replaces the VS project system with its own. When adding a new source file, you can use cmake to build instead of VS.
Here's one I found a while back 
https://ia800506.us.archive.org/tarview.php?tar=/5/items/AtomicGamer_gamedesign/AtomicGamer_gamedesign.tar
https://ia800506.us.archive.org/tarview.php?tar=/5/items/AtomicGamer_gamedesign/AtomicGamer_gamedesign.tar
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
Yep, there's a few ways to do it, but the quick and dirty way is to just never draw the battery HUD element. Comment out this one line so that this method always returns at the start of the method:
https://github.com/SamVanheer/halflife-updated/blob/master/cl_dll/battery.cpp#L87
https://github.com/SamVanheer/halflife-updated/blob/master/cl_dll/battery.cpp#L87
int CHudBattery::Draw(float flTime)
{
//if ( gHUD.m_iHideHUDDisplay & HIDEHUD_HEALTH )
return 1;
...
CHudBattery class and fix up any references to it.Go into the project settings for both the client & server projects and change the folder in the post-build step to wherever you want the dlls to be copied, the default is
C:\Program Files (x86)\Steam\steamapps\common\Half-Life\halflife_op4_updated\cl_dlls\ which doesn't exist on your PC and is causing the error.Hi, TWHL is an English community and there's no plans to support other languages officially on the site. Please feel free to attempt a translation yourself, but it sounds like a massive effort and I'm not sure how realistic it is. Please just be sure to provide credit to the original authors and link back to the page on TWHL.
Looks like a really good plan! I don't really have any suggestions, you've already nailed it pretty well. I do notice the "guard room" you have isn't part of the player's main journey - there's no reason you have to make it a mandatory visit, but at least put some stuff (ammo/health) in there for the player so they have a reason to go there if they want. You could even make the guard room have two entrances, one you could open from the other side (point 4) so you can backtrack to point 2 and get some item you need to progress through the shelter.
Posted 3 years ago2021-04-15 23:50:51 UTC
in Java as a programming language for anything Half Life (2) related? Post #345537
in Java as a programming language for anything Half Life (2) related? Post #345537
Aside from some edge cases such as developing tools for other modders to use, the only programming language that can be used for HL/2 modding is C++. Unfortunately there's no way to avoid it.
There is a link in the tutorial to the complete code, you can see it here: https://github.com/LogicAndTrick/halflife-updated/commit/tutorial-standard-weapons
For your last error, I think you are missing the
For your last error, I think you are missing the
EV_FireDesertEagle function in cl_dll/ev_hldm.cpp. The tutorial explains where changes need to be made, if you plan on adding any more weapons please read through it so you know which areas you need to update.We have a tutorial for a Desert Eagle weapon, try looking through it to see what you've missed.
"unresolved external symbol" linker errors are generally caused by a function being declared but not implemented. My guess is that you didn't add the
"unresolved external symbol" linker errors are generally caused by a function being declared but not implemented. My guess is that you didn't add the
deagle.cpp file (or whatever the file name actually is) to the client-side VS project. For new weapons, you need to include the file in both projects. (See the section in the tutorial under the heading "Basic class implementation" for details)And the account's deleted.
I don't usually delete accounts because it will remove forum posts and so on, which might help other people who are searching for an issue. But if you really want all the data deleted, please send me a private message from the account you want deleted (to prove you are the owner).
I've just increased the limit to 25, can you try now?
I don't think that was ever finished - Solokiller's version is a much better option to go with for OP4.
Use a multi_manager to trigger your sound, and then trigger it again after a 10 second delay. Be sure you don't have 'Not Toggled' set on your ambient_generic (it's off by default - leave it off). See Tutorial: Multi manager for more info on using multi_managers.
Just as an aside, the crowbar fix is in SOHL - it's just 1 new line to add:
https://github.com/LogicAndTrick/halflife-updated/blob/spirit/spirit-1.0/dlls/crowbar.cpp#L268
Before:
https://github.com/LogicAndTrick/halflife-updated/blob/spirit/spirit-1.0/dlls/crowbar.cpp#L268
Before:
if ( !pEntity->IsAlive() )
return TRUE;
else
flVol = 0.1;if ( !pEntity->IsAlive() ) {
m_flNextPrimaryAttack = UTIL_WeaponTimeBase() + 0.25; //LRC: corrected half-life bug
return TRUE;
} else
flVol = 0.1;
Stop creating duplicate threads please. You have one issue, please keep it in one thread. I've moved your other post into this thread.
Apparently Sven Co-op has func_vehicle too, can that be allowed?
Only the
If you're using SOHL 1.8 the functionality is disabled by default, you can simply delete glow.cpp from your project and then you can remove the references to cg.lib and cgGL.lib from your project and delete all the cg/gl stuff from your project and your mod won't need to include the cg/cgGL.dll files. For Spirit 1.4/1.5 it's the same, but you also need to remove or comment out these lines in cdll_int.cpp:
r_glow feature uses CG in SOHL, which you probably don't want or need.If you're using SOHL 1.8 the functionality is disabled by default, you can simply delete glow.cpp from your project and then you can remove the references to cg.lib and cgGL.lib from your project and delete all the cg/gl stuff from your project and your mod won't need to include the cg/cgGL.dll files. For Spirit 1.4/1.5 it's the same, but you also need to remove or comment out these lines in cdll_int.cpp:
// Remove these lines and then delete glow.cpp!
// Also remove cg.lib and cgGL.lib from your linker settings, and remove cg.dll and cgGL.dll from your mod install.
// At the top of the file...
extern void InitScreenGlow(); // FragBait0 - Glow Effect
extern void RenderScreenGlow(); // FragBait0 - Glow Effect
// In HUD_VidInit...
if (CVAR_GET_FLOAT("r_glow") != 0) //check the cvar for the glow is on.//AJH Modified to include glow mode (1&2)
InitScreenGlow(); // glow effect --FragBait0
// In HUD_Redraw...
if (CVAR_GET_FLOAT("r_glow") != 0) //check the cvar for the glow is on.//AJH Modified to include glow mode (1&2)
RenderScreenGlow(); // glow effect --FragBait0
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
Please don't advertise on the forums, this is not the appropriate place for it.
Yep, you should be able to handle this with globals:
https://developer.valvesoftware.com/wiki/Trigger_Events_Between_Levels
https://developer.valvesoftware.com/wiki/Env_global
https://developer.valvesoftware.com/wiki/Logic_auto
I don't know much about Source, so I don't know how flexible globals are - but at the very least they can store a yes/no value. So for every action that the player can take (or not take) throughout the mod, you store it as a yes/no value with a name against it. And then in the endings, you can load those values and use logic entities to lock/unlock the endings that you want to happen.
Oh- and also, if this is just for a single map (no level transitions) then you can just use math_counter, which can do the counting you described. You can then use logic_compare to fire events if the counter is less/greater/equal to a certain number.
https://developer.valvesoftware.com/wiki/Math_counter
https://developer.valvesoftware.com/wiki/Logic_compare
For multiple maps, you could use all of the above - globals to store the variables across level changes, a math_counter to count all the "yes" globals in the ending map(s), and the logic_compare to trigger the appropriate endings.
https://developer.valvesoftware.com/wiki/Trigger_Events_Between_Levels
https://developer.valvesoftware.com/wiki/Env_global
https://developer.valvesoftware.com/wiki/Logic_auto
I don't know much about Source, so I don't know how flexible globals are - but at the very least they can store a yes/no value. So for every action that the player can take (or not take) throughout the mod, you store it as a yes/no value with a name against it. And then in the endings, you can load those values and use logic entities to lock/unlock the endings that you want to happen.
Oh- and also, if this is just for a single map (no level transitions) then you can just use math_counter, which can do the counting you described. You can then use logic_compare to fire events if the counter is less/greater/equal to a certain number.
https://developer.valvesoftware.com/wiki/Math_counter
https://developer.valvesoftware.com/wiki/Logic_compare
For multiple maps, you could use all of the above - globals to store the variables across level changes, a math_counter to count all the "yes" globals in the ending map(s), and the logic_compare to trigger the appropriate endings.
Sure, I'll PM you the details. I don't think we plan on fixing any WON issues though, unless they're easy.
Posted 3 years ago2020-08-25 13:05:36 UTC
in Can items be counted through-out a set of maps? Post #344645
in Can items be counted through-out a set of maps? Post #344645
This is possible with globals, see env_global & Tutorial: Globals.
I've just played the entries, they were all really good! It should be obvious, but remember that using all your 3 votes won't be very useful, so be sure to only vote for 1 or 2 entries 
Maybe that error message is actually important? Instead of assuming the tool is broken and ignoring the message, you should read the error message and think about what it's saying. If it's about file lengths, then you might be trying to add a file with a very long path. PAK supports paths of 55 characters maximum (plus a null terminator). Take a look at the files you're trying to add and see if any are too long.
You're going to have to give us more info. Why can't you compile, and are you sure there's no errors? Post the latest compile log, and explain what's happening (or what's not happening).
zhlt.wad is probably in the same folder as the build tools, go into the game profiles > textures section, remove zhlt.wad, and then add it again. Re-save the map first (just in case) and then try the compile again.
Post your log file here (use pastebin if it is long) so we can see it. Also a screenshot of your compile setup window in JACK (preferences > game profiles > build programs).
I think the problem might be the spaces in the path, you can see it in this part:
** Executing...Try putting the VHLT tools in a directory without spaces in the path (e.g. D:\VHLT\hlcsg.exe), and then set up Hammer to use those new locations. I'm not 100% sure if it'll fix it, but it should help narrow down the cause a bit more at the very least.
** Command: D:\Program Files (x86)\Steam\steamapps\common\Half-Life SDK\Map Tools\hlcsg.exe
** Parameters: "D:\Program Files (x86)\Steam\steamapps\common\Half-Life\TimesEnd\maps\d_portal_hack2"
Unknown option "(x86)\Steam\steamapps\common\Half-Life"
Yes, looks like
So the revised command would be:
pcm_s16le, pcm_s24le, and pcm_s32le also work for the audio codec, instead of pcm_u8. The number in the codec gives you the bit depth of the audio. pcm_s64le does not work. For sampling rate, looks like 44khz audio works as well.So the revised command would be:
ffmpeg.exe -i source_video.mp4 -c:v cinepak -c:a pcm_s32le -vf scale=640:480 -ar 44100 sierra.avi