Forum posts
- Forums
- Posts
- Posted by
Solokiller
This post was made on a thread that has been deleted.
There's a hard limit of 256 visible entities, so even if you could bypass the other limits, that will always restrict you. You can try using models that have multiple trees in them to reduce the number of entities.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
The engine will always allow access to Half-Life content when running any other mod, you won't need the files in the cstrike directory.
You should ask him why he's asking for the files, it would help if we knew that.
You should ask him why he's asking for the files, it would help if we knew that.
There's a button labeled "ig" that turns off grouping of all kinds, including entities.
Note that you can only tie a brush to one entity, so you can't make it part of 2 or more entities.
Note that you can only tie a brush to one entity, so you can't make it part of 2 or more entities.
+mp_allowmonsters 1
Any cvar can be set using +, just as long as the game doesn't reset it later on.
Any cvar can be set using +, just as long as the game doesn't reset it later on.
Set the passable spawnflag, it turns off collisions for it.
Brushes with water textures on them are automatically considered as water volumes. You just can't set render modes or anything on them, you can do this by removing the entity that they're attached to using Tools->Move to world.
You can make doors non-solid with the passable flag.
Entity data is networked so the client can deal with entities locally, it will simulate physics on the client to help counteract lag. Entities aren't networked if they're set not to draw, so you need to be careful.
You can make doors non-solid with the passable flag.
Entity data is networked so the client can deal with entities locally, it will simulate physics on the client to help counteract lag. Entities aren't networked if they're set not to draw, so you need to be careful.
If you can set the EF_NODRAW flag then it won't network the entity's data: https://github.com/ValveSoftware/halflife/blob/master/dlls/client.cpp#L1100
You can manually set that by adding a keyvalue "effects" with value 128.
I've never tried it myself though, so use with caution. It may break client side water physics prediction.
You can manually set that by adding a keyvalue "effects" with value 128.
I've never tried it myself though, so use with caution. It may break client side water physics prediction.
Try splitting it up into separate entities, that should cut down on the number of visible polygons from any one location, provided your map isn't one large open area.
You can apply decals on trigger but you can't remove them.
If breakpad is pre-empting core dumps then i doubt it, otherwise you should consult the documentation for core dump generation to see if there's anything that can be done to force it.
Is there any particular reason why you can't build the tools yourself?
Is there any particular reason why you can't build the tools yourself?
This whole engine is a hack, this is just how they network the data to the client.
According to the breakpad documentation there's a tool to convert the minidumps to a human readable format:
[quote]
From https://github.com/google/breakpad/blob/master/docs/getting_started_with_breakpad.md
I suggest you try to use this processor tool to get the information you need.
[quote]
The client is a library that you include in your application. It can write minidump files capturing the current threads' state and the identities of the currently loaded executable and shared libraries. You can configure the client to write a minidump when a crash occurs, or when explicitly requested.The symbol dumper is a program that reads the debugging information produced by the compiler and produces a symbol file, in Breakpad's own format.The processor is a program that reads a minidump file, finds the appropriate symbol files for the versions of the executables and shared libraries the minidump mentions, and produces a human-readable C/C++ stack trace.From https://github.com/google/breakpad/blob/master/docs/getting_started_with_breakpad.md
I suggest you try to use this processor tool to get the information you need.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
By renaming the directory you're actually making it use the vanilla Half-Life client dll, that's not a solution.
What do you mean by "experimental isolated steam version"? I would assume that any modifications made to it would risk breaking anything relying on it.
What do you mean by "experimental isolated steam version"? I would assume that any modifications made to it would risk breaking anything relying on it.
The conveyor's scroll speed is stored in an entity's render color, so you could cheat and use env_render to change the color to 0 0 0 to make it stop.
X is whether to change scroll direction.
The speed value is broken up into the Y and Z values, Z contains 0-255, Y contains 256-32768.
I've never tried this myself though, and it won't affect the conveyor's actual speed. You'll need to use some tricks to prevent it from still pushing things, like a func_door that moves up to cover it, or a func_wall_toggle, if you can be sure that nothing will be touching it when toggled.
Note that triggering a func_conveyor will reset its scroll speed settings, so always apply that after triggering it.
X is whether to change scroll direction.
The speed value is broken up into the Y and Z values, Z contains 0-255, Y contains 256-32768.
I've never tried this myself though, and it won't affect the conveyor's actual speed. You'll need to use some tricks to prevent it from still pushing things, like a func_door that moves up to cover it, or a func_wall_toggle, if you can be sure that nothing will be touching it when toggled.
Note that triggering a func_conveyor will reset its scroll speed settings, so always apply that after triggering it.
This post was made on a thread that has been deleted.
Just to confirm: you installed the mod through Steam, right? It should be installed in common/Half-Rats - Parasomnia, not common/Half-Life.
Did you install the Steam version or did you install it as a mod? Based on your error message it's the latter. Right now only the Steam version is supported.
We just found a problem that was causing memory corruption issues and ultimately crashes, Shepard's preparing an update.
Yes, trigger_hurt can be toggled.
EDIT: you can also use game_player_hurt: http://twhl.info/wiki.php?id=31
EDIT: you can also use game_player_hurt: http://twhl.info/wiki.php?id=31
There's no entity that does this directly, but you can use trigger_hurt and doors to hurt/heal them. You can damage them just enough to get health down to what you want, and use negative damage to heal them.
Yeah that's one way to do it.
If you're willing to make extensive modifications you can do it like Source and use template entities to instantiate whenever and wherever you want, but that's tough to get right due to how entity data is handled.
If you're willing to make extensive modifications you can do it like Source and use template entities to instantiate whenever and wherever you want, but that's tough to get right due to how entity data is handled.
Unfortunately there is no way to do this in vanilla HL.
Try using Vluzacn's tools, Uncle Mike's tools are way more advanced and much newer, so there might be unknown issues there.
If it works with Vluzacn's then the problem is in the tools, if it still fails then you should post a couple logs so we can see if anything strange is showing up.
Also provide one of the map sources so we can see if you've got anything weird going on.
If it works with Vluzacn's then the problem is in the tools, if it still fails then you should post a couple logs so we can see if anything strange is showing up.
Also provide one of the map sources so we can see if you've got anything weird going on.
That's not quite enough to go on, could you post the compile log? Maybe show us how big your map is, that will also help.
IIRC that's done by having 2 func_tanks, one of which can only move in yaw, but not pitch. The actual tank is the one that can both pitch and yaw.
Those are used on the client side, so you'll need to use a config executed on the client side. You can add one yourself if you add an "exec <config_name>.cfg\n" console command somewhere in client code. Alternatively you could add it to the options screen to allow users to change it there.
There are 2 things to consider:
First, the global maximum speed setting, governed by sv_maxspeed. Can be changed in ServerActivate: https://github.com/ValveSoftware/halflife/blob/5d761709a31ce1e71488f2668321de05f791b405/ricochet/dlls/client.cpp#L657
Second, the per-player speed. Can be changed anytime, but usually in the player's Spawn method to set the initial speed, and anywhere else when it needs to be altered: https://github.com/ValveSoftware/halflife/blob/5d761709a31ce1e71488f2668321de05f791b405/dmc/dlls/player.cpp#L2886
I would advise against directly modifying pev->maxspeed, but you can read from it to get the player's current maximum speed.
First, the global maximum speed setting, governed by sv_maxspeed. Can be changed in ServerActivate: https://github.com/ValveSoftware/halflife/blob/5d761709a31ce1e71488f2668321de05f791b405/ricochet/dlls/client.cpp#L657
Second, the per-player speed. Can be changed anytime, but usually in the player's Spawn method to set the initial speed, and anywhere else when it needs to be altered: https://github.com/ValveSoftware/halflife/blob/5d761709a31ce1e71488f2668321de05f791b405/dmc/dlls/player.cpp#L2886
I would advise against directly modifying pev->maxspeed, but you can read from it to get the player's current maximum speed.
Deleting the entity won't fix the leak. To fix leaks you need to make sure your level is sealed by regular brushes, as in brushes that are not tied to an entity.
The point file should show where the leak enters your map, that's where the leak is.
The point file should show where the leak enters your map, that's where the leak is.
Warning: === LEAK in hull 0 ===Unless this is the leak you fixed (in which case you should provide the latest log), there is another leak.
Entity light @ (-440, -79, 238)
Learning to read and write a language can be much harder if you can't understand the verbal part of it.
http://onlinelibrary.wiley.com/doi/10.1111/0938-8982.00022/pdf
http://digitalcommons.wustl.edu/cgi/viewcontent.cgi?article=1185&context=pacs_capstones
https://www.quora.com/How-do-deaf-children-learn-to-read-and-write
http://onlinelibrary.wiley.com/doi/10.1111/0938-8982.00022/pdf
http://digitalcommons.wustl.edu/cgi/viewcontent.cgi?article=1185&context=pacs_capstones
https://www.quora.com/How-do-deaf-children-learn-to-read-and-write
[quote]
void CGameUI::ConnectToServer(const char *game, int IP, int port)
{
if ( TheCareerGame && (TheCareerGame->_vptr + 2)() )
{
else
{
//...
}
[/quote]
void CGameUI::ConnectToServer(const char *game, int IP, int port)
{
if ( TheCareerGame && (TheCareerGame->_vptr + 2)() )
{
//...else
{
if ( strcasecmp(game, "valve") )
engine->pfnClientCmd("mp3 stop\n");//...
}
[/quote]
This is an engine level issue, you can't fix it through the code. The GameUI library does this if the game isn't Half-Life, so unless you're mapping for vanilla HL or using a custom sound system you're out of luck.
The Sven Co-op map incoming has one if i'm not mistaken.
That means a brush model couldn't be found. As The Mad Carrot said, it may be caused by saving and then loading that save with a newer version of the map.
Saves aren't compatible with different versions of the same map.
Saves aren't compatible with different versions of the same map.
This engine never had much in the way of documentation, it's pretty sad that we have to reverse engineer the code to get some of that info.
That said, if there were a place to put documentation i'd contribute some, some people have asked for guides on working with the SDK and there are some pitfalls that can be avoided if you only have a way to know about them.
That said, if there were a place to put documentation i'd contribute some, some people have asked for guides on working with the SDK and there are some pitfalls that can be avoided if you only have a way to know about them.
Please use the edit button when adding more information, it avoids all the double posting.
Probably missing Op4's skill cfg file.
You can use the liblist.gam keyvalues fallback_dir and fallback_maps to allow your mod to use gearbox content: https://developer.valvesoftware.com/wiki/Liblist.gam#fallback_dir
This is easier than copy pasting everything. Remember to set it to use the gearbox dlls or you won't be able to use Op4 features.
This is easier than copy pasting everything. Remember to set it to use the gearbox dlls or you won't be able to use Op4 features.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
The problem you have is that you keep biting off more than you can chew. We keep telling you to start with the basics, and every time you come back saying you'll start by making an engine, because you know some of the language's syntax.
I didn't get to the point where i can spot vulnerabilities like these until years after i started programming. I started small, failed at what i was doing, learned why i failed and how to do better and succeeded.
Based on your responses here you can't handle failure very well, and your response is to bite off more than you can chew again a few days later.
You really need to start with the basics. Even if that means learning how to write if statements again, it's how you start with learning any programming language.
If you want to make an engine you should start by looking at and using existing engines, preferably in the language that you're intending to make your own with.
Once you have a strong grasp of the syntax of the language and experience with one or more engines you'll have enough knowledge to start making an engine. You'll still fail at first, but you'll be able to learn from your mistakes, instead of just throwing your arms up and saying "i can't even understand words like what you are spewing out".
It'll take time, but if you really want to do this you'll get there eventually. How long it takes depends on how much time you spend on it, as well as how motivated you are and how much you already know.
If you have a problem you just can't fix you can always ask for help, and if it's too stressful you can take a step back and come back later. Giving up at the first sign of trouble won't get you anywhere.
I didn't get to the point where i can spot vulnerabilities like these until years after i started programming. I started small, failed at what i was doing, learned why i failed and how to do better and succeeded.
Based on your responses here you can't handle failure very well, and your response is to bite off more than you can chew again a few days later.
You really need to start with the basics. Even if that means learning how to write if statements again, it's how you start with learning any programming language.
If you want to make an engine you should start by looking at and using existing engines, preferably in the language that you're intending to make your own with.
Once you have a strong grasp of the syntax of the language and experience with one or more engines you'll have enough knowledge to start making an engine. You'll still fail at first, but you'll be able to learn from your mistakes, instead of just throwing your arms up and saying "i can't even understand words like what you are spewing out".
It'll take time, but if you really want to do this you'll get there eventually. How long it takes depends on how much time you spend on it, as well as how motivated you are and how much you already know.
If you have a problem you just can't fix you can always ask for help, and if it's too stressful you can take a step back and come back later. Giving up at the first sign of trouble won't get you anywhere.