UDN - Content - ExampleMapsFluorescentLights

Content Creation

Content Creation home

Documents listed below, but not hyperlinked, are restricted to engine licensees only.

As certain texts become relevant, due to released games using that technology, new documents will be made available. Check back often!

Getting Started
   - WhatToReadFirst
   Support
   - UnEdit (mailing list)
   - UnEditTraffic (summaries)
   - UnDevIRC (chat)
   - UnDevIRCTraffic (summaries)
   - UnrealEdSux0rs (bug list)
   Engine Prerequisites
   - TextureSpecifications
   - TextureComparison
   - Etc.

General Editor
   Basics
   - IntroToUnrealEd
   - UnrealEdInterface
   - RotationGizmo
   - UnrealEdKeys
   - BrushClipping
   - VertexEditing
   - BoxSelection
   - ShapeEditor
   - ExampleMaps
   - TriggersTutorial
   - WorkflowAndModularity
   Primitives < br>    - BspBrush
   - MirrorsAndWarpZones
   - Hardwarebrush
   - MoversTutorial
   - UKXPackagesTutorial
   - TerrainTutorial
   - VolumesTutorial
   - LightingTutorial
   - ProjectiveTutorial
   - MaterialTutorial
   - CollisionTutorial
   - FluidSurfaceTutorial
   Animation
   - AnimNotifies
   - AnimBrowserTutorial
   - AnimBrowserReference
   Particles
   - EmittersTutorial
   - EmittersExamples
   New Particle Editor
   - ParticleSystems
   - ExampleParticleSystems
   Matinee
   - MatineeTutorial
   - MatineeExample
   - MatineeDemoOpening
   - MatineeDemoDropship
   - SampleMatineeTips
   Scripted Sequences
   - ScriptedSequenceTutorial
   - ScriptedSequenceActions
   - AIControllers
   Techniques
   - LevelTransitions
   - Leveloptimization
   - GroupsBrowser
   - NavigationAI
   - VertexBlendingTutorial
   - ConvertingContent739To829

Tools
   - ActorX
   - UmodWizard< br>    - ModelingTableOfContents
   - CADtoUnreal

Karma Physics
   - IntroToKarma
   - Karmareference
   - ImportingKarmaActors
   - UsingKarmaActors
   - KarmaAuthoringTool
   - RagdollsInUT2003
   - KarmaExampleUT2003
   - ExampleMapskarmaColosseum

PlayStation2 and GameCube
   - ConsoleDevelopment

Contribute!
You can create a new page, and then you can edit this list to add it to the categories, as well as edit the Content Creation homepage to tell everyone about it!
Make Requests!
You can also stop by the UdnStaff page to see what we're working on, and edit it to add your own document requests.

Please take note! For mod developers working with Unreal Tournament 2003, this documentation is meant to be a starting point for your own explorations into UT2003, not a definitive guide. There will be differences between the documentation here and the product in your hands, and you may have to figure out quite a bit for yourself. Check out the Unreal Tournament 2003 page in the Unreal Powered area for links to community sites if you're having problems. UDN is a licensee support site, and cannot provide technical support or game-specific assistance to end users.

ExampleMapsFluorescentLights

Licensees can log in.

Interested in the Unreal engine? Check out the licensing page.

Questions about UDN itself? Contact the UDN Staff.

Fluorescent Lights Example Map

Last updated by Jason Lentz (DemiurgeStudios), to separate from the main ExampleMaps doc. Original author was Lode Vandevenne (UdnStaff).

Fluorescent Lights Example Map
Introduction

Introduction

This map, for the 927 build, has 8 realistic TL lights: if you turn them on, they'll first blink for a while before eventually going on.
http://udn.epicgames.com/pub/Content/ExampleMapsFluorescentLights/TL.zip
If you give it a sound, the sound will go on and off too. You may have to increase your volume to hear the sound. You can adjust a lot:
bInitiallyOff: choose if the TL light will be on or off in the beginning.

FlickerTime: how long it will flicker before it goes on.

OnChance: while it flickers, how often the light will be on or off, 0.5 means 50/50.

Period: the length of 1 flicker.

TriggerAction: if the light should ignore events, go on after an event, go off after an event, or toggle on/off after an event.

NOTE: if you use TriggerToggle, please set the ReTriggerDelay of the trigger to 0.5, otherwise the light may go out again if the trigger touch accidently gets detected twice. This seems to happen quite often.
This TL light is just an example of a scripted light: to make a scripted light, the light must have bStatic = False and bDynamicLight = True in its properties, otherwise it'll ignore its script. Once you did that, you can change almost anything, including the radius, color, corona, lighttype, sound... with a script.
This is UNTESTED in multiplayer, the TL lights should have bStatic = False in the Default Properties (but the setting is hidden), and the behavior on the clients and the server is untested.

Attachment: sort Action: Size: Date: Who: Comment:

TL.zip action 332499 04 Dec 2002 - 21:09 DemiurgeStudios Demo map: flickering fluorescent lights.