Please or Register to create posts and topics.

Player constraint

Page 1 of 2Next

I need a way to make the player not move at all, not even their feild of vision, but still have use of their USE button so they can properly activate a controllable tank. Apparantly the trigger volume needed for the tank cannot be parented to anything or move around, otherwise the tank misbehaves. So the player must be forced to activate it by remaining completely stationery

Just when I think I understand the system, it changes on me.

Point_viewcontrol freezing the player. They can't move and their FoV is controlled by the camera.

Falsi sumus crusto!
Fracture wrote:
Apparantly the trigger volume needed for the tank cannot be parented to anything or move around, otherwise the tank misbehaves. So the player must be forced to activate it by remaining completely stationery

Isn't there a way to force the player to use the tank? - Some sort of output.

?????????????????????????????TWP Releases | My Workshop

yes actually i just find out about +use and -use.

Just when I think I understand the system, it changes on me.

Make the player start for a few split seconds inside a dark black room, make a logic_auto and servercommand make the player +use, then teleport them back and make the player -use. I have an instance made of a portal 1 elevator in a room that I'm using for my gravity gun maps, and it already has it built in.

My YouTube Channel: https://www.youtube.com/user/Camben24
Aperture Science: We do our science asbestos we can!

If they need control of items, but need their view constrained. You should be able to use a point_viewcontrol to prevent their view from moving. Then so they have control of things, you can use a game_UI. They then can use WASD M1 M2 (And I think some other keys) to control various things in your level.

Happy Mapping

http://www.tophattwaffle.com/ - My site for Source Engine Level Design
http://therewillbescience.com/ - Portal 2, Lab Rat
http://www.moddb.com/mods/portal-2-lab-rat - Portal 2, Lab Rat (MODDB)

Game_ui gives you WASD, M1, M2, a gamepad joystick and some sort of analogue attack button I don't really understand. A func_button in front of them gives you E, which you can route through a user input of the game_ui, and a logic_playerproxy gives you SPACE, CTRL, and whether a portal shot succeeded or not. That's almost everything the game's code itself uses, and keybindings can get you anything else you want.

Falsi sumus crusto!

sweet, good to know, thanks

Just when I think I understand the system, it changes on me.

I see that the playerproxy doesn't support enabling and disabling to itself. Is there a way around this? I also am guessing the CTRL button is supposed to be the flashlight?

Just when I think I understand the system, it changes on me.

No, CTRL is Duck (or cancel gel effects). And you can route the inputs through relays with similar names and use a wildcard to enable/disable them all.

Falsi sumus crusto!
Page 1 of 2Next