func_portal_orientation
... 
func_portal_orientation is a brush entity available in the 
Portal games. It adjusts a portal's rotation to match a specified angle. The "front" of the portal points in the specified direction.
Bug:
Broken in Portal 2. It will rotate existing portals to the specified direction when first enabled, but will not affect newly-placed ones.
Workaround: Since it still works when first enabled, a logic_playerproxycan be used to fire anEnableinput to the entity every time a portal is placed, which will orient the portals correctly. This can result in some odd behavior when placing portals near the edge of surfaces within the volume,func_portal_bumpers should be used to prevent this.
Keyvalues
{{KV|Angles to face|intn=AnglesToFace|angle|The angles to rotate portals to.
Tip:An easy way to figure out what to set this to is to place a prop_portal, rotate it to the desired orientation, then look at its angles.{{KV|Match linked angles.|intn=MatchLinkedAngles|boolean|If set, portals placed in this volume will have their angles match their linked portals. This only works for floor or ceiling portals with a currently linked partner that is on a surface with the same orientation.
Todo: Seems to be broken in P1? It does work in P2 if the workaround is used.
Base:
- Collisions
(solid)<choices> - Method of collision for this entity.
Values:
- 0: None
- 1: BSP (QPhysics) !FGD Bug:In , if an entity using QPhysics collisions is hit by Gel, the game will crash!
- 2: Bounding Box
- 3: Oriented Bounding Box (Use for runtime spawned brush entities meant to be rotated) !FGD
- 4: Oriented Bounding Box but constrained to Yaw only !FGD
- 5: Custom/Test (Usually no collision with anything) !FGD
- 6: VPhysics
- Parent
(parentname)<targetname> - Maintain the same initial offset to this entity. An attachment point can also be used if separated by a comma at the end. (
parentname [targetname],[attachment])Tip:Entities transition to the next map with their parentsTip:phys_constraintcan be used as a workaround if parenting fails.
- Origin (X Y Z)
(origin)<coordinates> - The position of this entity's center in the world. Rotating entities typically rotate around their origin.
Note:Hammer does not move the entities accordingly only in the editor.
- Pitch Yaw Roll (X Y Z)
(angles)<angle> - This entity's orientation in the world. Pitch is rotation around the Y axis, yaw is the rotation around the Z axis, roll is the rotation around the X axis.Note:This works on brush entities, although Hammer doesn't show the new angles.
- Classname
(classname)<string> !FGD - Determines the characteristics of the entity before it spawns. Tip:Changing this on runtime still has use, like making matching an entry in S_PreserveEnts will persist the entity on new rounds!
- Spawnflags
(spawnflags)<flags> !FGD - Toggles exclusive features of an entity, its specific number is determined by the combination of flags added.
- Effects
(effects)<flags> !FGD - Combination of effect flags to use.
- Entity Scripts
(vscripts)<scriptlist> (in all games since
) (also in 
) - Space delimited list of VScript files (without file extension) that are executed after all entities have spawned. The scripts are all executed in the same script scope, later ones overwriting any identical variables and functions. Scripts executed on the worldspawn entity will be placed in root scope.
- Think function
(thinkfunction)<string> (in all games since) (also in ) - Name of the function within this entity's script that'll be called automatically every 100 milliseconds, or a user-defined interval if the function returns a number. Avoid expensive operations in this function, as it may cause performance problems.
- Lag Compensation
(LagCompensate)<boolean> (in all games since) !FGD - Set to Yes to lag compensate this entity. Should be used very sparingly!
EnableDisable:
- Start Disabled
(StartDisabled)<boolean> - Stay dormant until activated (with the
Enableinput).
Inputs
Base:
AddContext<string>- Adds to the entity's list of response contexts. See Context.
AddOutput<string>- Assigns a new keyvalue/output on this entity. For keyvalues, some rely on extra necessary code to be ran and won't work if its simply just changed through this input. There is a strict format that must be followed:
// Format of changing KeyValues: "AddOutput [key] [value]"
//// Raw text:
"OnUser1" "!self,AddOutput,targetname new_name"
// Format of adding an Output: "AddOutput {targetname}:{inputname}:{parameter}:{delay}:{max times to fire, -1 means infinite}"
//// Raw text:
"OnUser1" "!self,AddOutput,OnUser1:SetParent:!activator:0.0:-1"
// Arguments can be left blank, but the empty blank should still be contained.
//// Raw text:
"OnUser1" "!self,AddOutput,OnUser1:ClearParent::0.0:-1"
|
ClearContext- Removes all contexts from this entity's list.
ClearParent- Removes this entity from the the movement hierarchy, leaving it free to move independently.
FireUser1toFireUser4- Fires the respective
OnUseroutputs; see User Inputs and Outputs.
Kill- Removes this entity and any entities parented to it from the world.
KillHierarchy- Functions the same as
Kill, although this entity and any entities parented to it are killed on the same frame, being marginally faster thanKillinput.
RemoveContext<string>- Remove a context from this entity's list. The name should match the key of an existing context.
SetParent<string>- Move with this entity. See Entity Hierarchy (parenting).
SetParentAttachment<string>- Change this entity to attach to a specific attachment point on its parent. The entity will teleport so that the position of its root bone matches that of the attachment. Entities must be parented before being sent this input.
SetParentAttachmentMaintainOffset<string>- As above, but without teleporting. The entity retains its position relative to the attachment at the time of the input being received.
RunScriptFile<script> (in all games since)- Execute a VScript file from disk, without file extension. The script contents are merged with the script scope of the receiving entity.
RunScriptCode<string> (in all games since)- Execute a string of VScript source code in the scope of the entity receiving the input. String quotation may be needed when fired via console. Bug:In Hammer, using string arguments will corrupt the VMF file's structure, making the file unviewable for the next Hammer session.
- Fix: Remove the string argument manually with a text editor.
EnableDisable:
Enable
Disable- Enable/disable this entity from performing its task. It might also disappear from view.
Outputs
Base:
OnUser1toOnUser4- These outputs each fire in response to the firing of the like-numbered
FireUser1toFireUser4Input; see User Inputs and Outputs.
