[SOLVED] Fog and global_ents instance
Quote from Konke on May 5, 2014, 11:39 amIndeed it's a great tutorial. I just had a short conversation with him about the matter to keep the global_ents or not. He said that the global_ents instance contains base entities that most other instances call, like a client/server command. I take it it's good to keep then.
I think I've found a workaround for the fog and it seems to be working. I controll my own fog_controller with a fog volume, and the volume will just have to be over the most part of the map. I'm not sure how official this solution is but at least it's working and I guess that's all that matters.
Indeed it's a great tutorial. I just had a short conversation with him about the matter to keep the global_ents or not. He said that the global_ents instance contains base entities that most other instances call, like a client/server command. I take it it's good to keep then.
I think I've found a workaround for the fog and it seems to be working. I controll my own fog_controller with a fog volume, and the volume will just have to be over the most part of the map. I'm not sure how official this solution is but at least it's working and I guess that's all that matters.
Quote from srs bsnss on May 6, 2014, 12:01 pmGlobal ents will save you time down the track with other things. For example:
- It provides the '@autosave' entity, which is an easy way to save the game via entities (OnTrigger > @autosave > Save).
- You can change environments, which includes color correction, tonemapping, fog, etc, on the fly very easily.
- It provides the required entities for choreographed scenes, so that you only need to worry about a logic_choreo_scene entity, as opposed to involving generic_actors.Basically, it can save you time for other things, outside of fog triggers (although that's its main use). You can get rid of it if you want, though; nothing bad will happen if you don't have it.
Global ents will save you time down the track with other things. For example:
- It provides the '@autosave' entity, which is an easy way to save the game via entities (OnTrigger > @autosave > Save).
- You can change environments, which includes color correction, tonemapping, fog, etc, on the fly very easily.
- It provides the required entities for choreographed scenes, so that you only need to worry about a logic_choreo_scene entity, as opposed to involving generic_actors.
Basically, it can save you time for other things, outside of fog triggers (although that's its main use). You can get rid of it if you want, though; nothing bad will happen if you don't have it.
Quote from Konke on May 7, 2014, 2:56 pmsrs bsnss wrote:Global ents will save you time down the track with other things. For example:- It provides the '@autosave' entity, which is an easy way to save the game via entities (OnTrigger > @autosave > Save).
- You can change environments, which includes color correction, tonemapping, fog, etc, on the fly very easily.
- It provides the required entities for choreographed scenes, so that you only need to worry about a logic_choreo_scene entity, as opposed to involving generic_actors.Basically, it can save you time for other things, outside of fog triggers (although that's its main use). You can get rid of it if you want, though; nothing bad will happen if you don't have it.
Thanks for the great reply! As long as the instance doesn't slow the performance down I think I'll keep it around. I'll try to implement autosaves on a later notice aswell.
- It provides the '@autosave' entity, which is an easy way to save the game via entities (OnTrigger > @autosave > Save).
- You can change environments, which includes color correction, tonemapping, fog, etc, on the fly very easily.
- It provides the required entities for choreographed scenes, so that you only need to worry about a logic_choreo_scene entity, as opposed to involving generic_actors.
Basically, it can save you time for other things, outside of fog triggers (although that's its main use). You can get rid of it if you want, though; nothing bad will happen if you don't have it.
Thanks for the great reply! As long as the instance doesn't slow the performance down I think I'll keep it around. I'll try to implement autosaves on a later notice aswell.