Check if you accidentally turned off the instructor hints convar.

How do i check that?, Sorry for the noobish question =P

gameinstructor_enable is the cvar you want. The "find" command is very useful.

Thanks for the help FelixGriffin and TeamSpen210 =D it was disabled, also didn't knew about the "find" command.. will be very useful. just one final question: When i post the map on workshop, is there any chance that the players will have this problem by default?

Quite probably. Use a point_clientcommand to turn it on for them.

Ok, thx again =D

Dr.Toaster Waffles wrote:

What compile are you using? Looks like VRAD is trying to do it's job, but is still goofing it up. Do a full compile and see if anything changes. Also, what type of lights are you using?

Do you have any models on/close to those walls (vines, frames)? Try setting Disable Shadows to true so they don't black out the walls behind.

Dr.Toaster Waffles wrote:
Arachnaphob wrote:

Try compiling without RAD. If it's still dark, I don't know what to do. If not, you may have 'disable shadows' off. Enable that and see what happens.

I agree with srs bsnss, it really looks Default compiled =/

No, it's HDR compiled. I even tried a full compile to no avail. I have also tried disabling shadows already.

It's no matter though, I don't really like the geometry of the map so I'm restarting it...hopefully it doesn't happpen again. Although an answer to why this is happening would be nice.

@srs bsnss: Just a light spot and a projected texture.

Dr.Toaster Waffles wrote:
No, it's HDR compiled. I even tried a full compile to no avail. I have also tried disabling shadows already.

It's no matter though, I don't really like the geometry of the map so I'm restarting it...hopefully it doesn't happpen again. Although an answer to why this is happening would be nice.

@srs bsnss: Just a light spot and a projected texture.

Try compiling with LDR only, see if you get any different results.

Can I somehow limit the distance from where I can activate a button? I have func_button in my level and it has a ridiculous range. I can even activate it if I'm not really looking at it. I would prefer if the player had to be right next to it to press it.

You could use a trigger that Locks and Unlocks the button when players are close to it. If you use two trigger_look s (one pointing at it, one pointing the opposite direction with the activation angle turned up you could control how accurate the player must be.

Alternatively, you could put down a regular prop_button with the extra keyvalues "RenderMode 10" and "Solid 0" to make it invisible and non-solid.

I have a func_door_rotating on the wrong axis. How do I set the axis to make it move up instead of sideways?

Set the spawn flags for the correct orientation. Note that func_rotating/func_door_rotating don't rotate correctly inside instances

I have a point_viewcontroll set up on a set of path_corners. (I'm very new to viewcontrolls so this may be a nooby question.) When the hold time on the first path_corner runs out, the camera moves very slowly, and then just stops not even halfway to the second path_corner. Any ideas?

Don't use path_corners, use a tracktrain and parent the viewcontrol to it. The old path_corner system is rather messy and outdated.

I haven't experienced with env_entity_makers before, but can someone tell me why it's spawning objects at a different location?

yishbarr wrote:
I haven't experienced with env_entity_makers before, but can someone tell me why it's spawning objects at a different location?

What does that even have to do with this thread?

Env_entity makers spawn a template relative to themselves, with the location of the point_template basically the origin. (If you put the two in the same place, it will spawn at the original location, if the env_entity_maker is 64 units left of the point_template the object will spawn 64 units left of its original location.) There are also properties and inputs which change what happens after it spawns, so you might want to check that.

The thread's for lots of small problems, so we don't have lots of small threads cluttering everything.