Portal 2 (Other files)
Miscellaneous Portal 2 mods, assets, tools, and non-map downloads.
Scene Voice Script Package
These are a number of files which you can use to play Valve's scene files for voice lines. You can create your own custom order for the scenes like the way Valve has done it. This example mainly covers coop GLaDOS. If you really want to use a custom scene this is the only way to do it if the Scene Table is personalised for a certain map. I highly suggest you don't go all out unless you are making a mod or a larger map-pack. Check out: https://developer.valvesoftware.com/wiki/Portal_2_VCDs for references of each scene.
Credits
A Credit script that works with an instance to display your credits
Want You Gone Music and Lyrics
This will play "Want You Gone" (Portal 2 credits) and display the lyrics at the same time. Extract the zip folder and run "Want_You_Gone.bat" to start. See the ReadMe document for more info. Note: This will only work with a Windows computer.
Gel Dropper instance
Instance of a gel dropper that comes from a standard cube dropper. ============================================== = GEL DROPPER INSTANCE MADE BY CHICKENMOBILE = ============================================== This instance covers every available, working gel in Portal2. It has presets for each gel when you specify the type. Please note: Options are CASE SENSITIVE therefore you will need to type 'Bounce' instead of bounce and 'BigBlob' instead of bigblob etc. Instructions: 1. Place an func_instance inside your map and point towards your gel dropper instance. 2. Name this instance 3. Select your Gel type for $PaintType. Options: 1. Bounce 2. Speed 3. Erase 4. Portal 4. Select if it will spawn as a BigBlob or a constant stream of gel for $BigBlobOrConstant Options: 1. BigBlob 2. Constant 5. If it is 'BigBlob', set $TimeBetweenBigBlobs as a number for time BigBlobs spawn after each other (2 seconds is a good time) Notes: 1. BigBlobs are treated like physics objects which can be catapulted by faith plates and explodes when in contact with other BigBlobs 2. BigBlobs cannot press buttons 6. If you set $DropperInitiallyDisabled to 1, you will need to manually turn the gel spawner on using an output. Create an output from your activator (i.e. a button etc.) and then point it towards your gel spawner, then select from the 'Target Input' drop down menu: 'instance:StartGel;Trigger'. If you want to stop the gel from spawning choose: 'instance:StopGel;Trigger' 7. Profit?!?! P.S. I cbf uploading a thumbnail its nearly 4am. Good day
Light Beam Platform (from Portal 1)
Just because Portal 2 is a newer game there is no reason to waste old testing elements. A good example besides the Energy Balls (Working Energy Balls + Clean models + Instances) are the Light Beam Platforms. They can be used everywhere because they don't need any fixed points with walls like Portal 2's moving platforms. In this pack you have 5 instances: BeamPlatform_Beam: Here you have a preset env_beam where you have to set the start and endpoint of its beam. BeamPlatform_Corner: Thats the corner for a Light Beam Platform track. BeamPlatform_End: Thats the end platform for a Light Beam Platform track. BeamPlatform_Wall: This is a wall emitter for the Light Beam. For the first two instances the func_instance center is the point where you have to put your path_tracks to. The wall emitter needs to have the path_track on the same layer but of course a bit futher from the wall. BeamPlatform_Platform: Thats the platform itself with some settings. It's moving from MapSpawn on. Make sure to give all instances/parts that belong to the same Light Beam the same fixup name! For multiple platforms per track you have to use of course different ones. This just causes that the toggle won't work. In this pack there are also the missing models and textures for all the parts of the Light Beam Track. I recompiled the corner model and made it to a static prop. Please make sure to use the light_rail_endcap2.mdl and not the light_rail_endcap.mdl. I hexed that model because Valve made some texture tries on the original one in Portal 2's VPKs and it looks unfinished.
Diversity Vent help V2
i NEED help to get it working now with hammer files
Underground giant door transition
My attempt at an underground transition seal, trying to re-create a4_end without copy-pasting. I was going to include it in my 'useful instances' - but it's too big and doesn't really fit into a category. Gaps have been left for you to plug doorways in to the North and South sides, as well as a gap for a descending elevator. Triggering the massive door to open is easy with just a few entities, but is beyond the scope of this text and will not be explained here. Check the forums!
Frames prefabs
This file contains two prefabs: one for a doorframe, one for a funnel frame. To use these, place them in steam/steamapps/common/portal 2/bin/Prefabs. In hammer, click the entity tool and then select prefabs, and choose the one you want to use.
Portals on Panels, Issue Clarification
I'm having an issue where portals placed on my rotating panels will only be oriented one specific way relative to the prop_dynamic (panel) inside of them. Here is a big, simple version of the problem I'm facing.
Co-op tube ride sequence
This is an instance that when triggered causes a sequence in which Blue, Orange or both go flying through a set of vents, like the one that leads to and from the 'DLC room' in the hub. To activate it you need a trigger_playerteam that will tell the instance what sequence to start (Blue/Orange; Long/Short) and to enable/disable the trigger_teleports. You should also place two trigger_teleports - one for Orange and one for Blue. these should be enabled when the corresponding bot arrives and disabled when he leave's the trigger_playerteam brush. There are four alternate remote destinations for these brushes: @orange_tuberide_long_teleport_trigger @orange_tuberide_short_teleport_trigger @blue_tuberide_long_teleport_trigger @blue_tuberide_short_teleport_trigger You can also have up to four point_teleport entities, from these the player will re-appear in the map after the sequence: @orange_tuberide_long_teleport_trigger2 @orange_tuberide_short_teleport_trigger2 @blue_tuberide_long_teleport_trigger2 @blue_tuberide_short_teleport_trigger2 YOU MUST NAME THESE ENTITIES APPROPRIATELY, otherwise the instance won't work properly. Hope you'll make the best out of it, I'm sure I will.
