User:Alvin/Sandbox

Aperture Science is the mysterious research corporation behind the plot of Portal.

According to its website, Aperture was founded by Cave Johnson in 1953 as a manufacturer of shower curtains. 26 years later, Aperture began development of the 'man-sized ad hoc quantum tunnel through physical space with possible applications as a shower curtain,' also called the 'Portal.'

Aperture eventually created the Aperture Science Handheld Portal Device, and built the Aperture Science Enrichment Center to test it. They also created GLaDOS in response to the news that Black Mesa was working on a similar portal technology.

The game, Portal, is set mostly in the test chambers of the Aperture Science Enrichment Center. After escaping the test chambers (and near-death), the player finds that the Enrichment Center is deserted, with abandoned desks and disconnected phones. It is apparently run only by GLaDOS. The Company's Slogan: Aperture Science: We do what we must, because we can.

Using preset sounds

It's actually very easy to make GLaDOS talk, but which method to use may not be immediately obvious. You can play one of her lines using an ambient_generic, but this has an unfortunate downside: ambient_generic entities continue to play even when the game is paused (hence the "ambient" part of the entity name).

In Valve's maps, a logic_choreographed_scene is used instead. Here's how to make GLaDOS speak in your own maps with a logic_choreographed_scene entity:

1. Create a small room outside of your regular play area. Cover the walls with the "nodraw" texture.
2. Inside the room, create a generic_actor entity. Set the entity's model to models/props/metal_box.mdl or something similar. The model doesn't really matter, but Valve uses metal_box in their maps because the map already uses that model in most cases (thus saving memory).
3. Set the generic_actor's Name property to Aperture_AI (the name cannot be anything other than Aperture_AI, otherwise the scenes will not function).
4. Create a logic_choreographed_scene in your play area and set the Scene property to whatever scene you want to play.

Note:If you are making a scene for cameras, you might want to try the following scenes out.

There are also many scenes that can be made for special use, including things like weighted storage cubes, and cameras.

Cameras

Note:As soon as you put an Aperture_AI, GLaDOS will automatically play one of the following scenes when a camera gets detached.

Note:After all five scenes have been played, GLaDOS will cease to randomly play the scenes and only play the fifth one.

* scenes\general\generic_security_camera_destroyed-1.vcd
* scenes\general\generic_security_camera_destroyed-2.vcd
* scenes\general\generic_security_camera_destroyed-3.vcd
* scenes\general\generic_security_camera_destroyed-4.vcd
* scenes\general\generic_security_camera_destroyed-5.vcd

Storage Cubes

* general\ai_box_fried.vcd
* general\ai_box_lost.vcd

Now, just trigger the logic_choreographed_scene entity and listen to GLaDOS speak!

Custom sounds

You can put in your own sounds for GLaDOS's voice if you like - just follow these steps:

Note:You should know about making triggers, inputs and outputs already before trying this!

1. Create your sound and place it in "~/USERNAME/portal/portal/sound/MAPNAME/"
2. Place an ambient_generic anywhere in your map - preferably near the trigger that will activate it.
3. Open the "Sound Name" field in the ambient_generic's properties and browse for your sound name.
4. Make a name for your ambient_generic, trigger it with a PlaySound input from somewhere, and it should work.

Important notes

• Your audio file needs to be a .wav file, preferably 22050 Hz Sample Rate and Playback Rate.
• When distributing the map, you will need to either package the sound with the map or use bspzip to add the files to your .bsp if you want the sounds to be heard by recipients of your map.
  • If you use bspzip, make sure to use all lowercase letters on everything and to use the .bsp internal sound folder of "/sound/MAPNAME/sound.wav"
• If things don't work correctly, try to trigger the sound in-game, then look at the developer's console and see if it gives you an error; this can be a valuable troubleshooting tool.
• All scenes from the GLaDOS' chamber requires a generic_actor named tim_larkin.

See also

• Portal Level Creation

Chell

Chell is the player character in Portal and Portal 2. Little is known of her, other than that she is dressed in test-subject attire and wears heel-springs to protect her from fall damage.

Unlike Gordon Freeman, a Chell model exists and she is visible in-game. The mechanics of portals required the player character to be visible.

Stub

This article or section is a stub. You can help by expanding it.

Cube (Portal 2)

Cube types.

Cubes are portable objects in the Portal series. A cube can be placed on a button to activate it.

Various kinds of cubes exist in Portal 2. The standard cube changes color when it triggers a button. The edgeless cube acts the same, but is ball-shaped, and may be placed in a special button-receptacle. The pivot cube (also known as a redirection cube) can redirect a discouragement beam. The companion and underground cubes are themed, but functionally the same as the standard cube. Frakenturrets are also functionally the same, but under certain conditions will jump around.

Cube

prop_weighted_cube - The entity models/props/metal_box.mdl - The world model portal_weighted_cube - in game command line

There are also reflector cubes which can redirect env_portal_laser's

GLaDOS

GlaDOS.

The deceitful computer, GLaDOS (which stands for Genetic Lifeform and Disk Operating System), is the speaker and controller behind the Aperture Science Enrichment Center. She has an odd obsession with cakes.

Origin

GLaDOS was created in response to the news that Black Mesa was developing a portal technology similar to that of Aperture Science. Her original purpose was to be an artificially intelligent research assistant (and disk operating system). Work on GLaDOS started in 1986, and was under development for more than ten years before she was finally completed several years after 1996. GLaDOS was activated for the first time, untested, during one of the events on Aperture Science's first annual "bring-your-daughter-to-work" day.

In many ways, the initial test went well...

GLaDOS is made up of several "personality cores" in the form of strange spheres that apparently control the AI's behavior. Chell encounters a morality core, curiosity core, cake core, and anger core (in that order) while destroying GLaDOS.

Spoiler Warning!

What follows is from Portal 2. If you have not played the game yet and do not wish to ruin the experience, do not read any further.

Updated Origin

Cave Johnson, founder of Aperture Science Center, in his wild pursuit of better portal technology, managed to contract cancer from the powdered dust of moon rocks. Over the years, he became more and more irrational until one day, in a fit of "genius", he decided to put his assistant Caroline in his new computer core. This was in the late 1970's. The final "version" of GLaDOS was not completed until 1996. The ten years it took to actually develop GLaDOS were mostly the OS portion.

The stresses of running the Enrichment Center were apparently too much for Caroline to handle. Her mind was simply not able to deal with the amount of testing the Enrichment Center needed to have completed on a daily basis. This may have been the reason for the addition of the OS to the computer core. It is unclear what drove the combined Human/AI mind to the point it is at when we first meet GLaDOS, but one thing is clear: the compulsion to test constantly certainly was a contributing factor. It is unfortunate that Caroline was the sane, stable part of GLaDOS. Caroline was also the only thing keeping Johnson from going completely insane.