 |
Rev 9109 Add new script event "getSecurityCameraState" to allow scripts to check the current status of a security camera. 1 = unalerted, 2 = partially alerted, 3 = fully alerted, 4 = switched off, 5 = destroyed, implicitly 0 = not a security camera. Rev 9110 Skin names are no longer hard-coded. Use "skin" as "skin_on", as described in entityDef tooltip, for backwards compatibility. ----- Rev 16139 Make Epifire's security camera entity useable in SVN. Set up new, full-featured camera entities in a new AI/Machines/Security Camera folder, using both the original and Epifire models. Maintain the original func_security_camera entity in the Func folder for backwards compatibility, but also make it act as a base class for other security cameras. Rev 16140 Tweaks to security camera entities, mostly for backwards compatibility. |
|
|
Rev 9111 Spotlight properties no longer hardcoded: code reads "spotlight_range", "spotlight_radius" and "spotlight_texture" spawnargs. If not found, uses old values (scanDist and lights/biground1). My initial idea was to just use the same spawnargs as projected lights (light_up, light_target, light_right), but this was very unintuitive for a mapper, especially because the code rotates the light and it more or less becomes mandatory to copy spawnargs from an existing light in order to get the axis right. Rev 16141 Add new spotlight spawnargs to new camera entityDefs for rev 9111. Scriptobject no longer needs to override the spotlight texture. |
|
|
Rev 9112 Rev 16144 Change spotlight_radius to spotlight_diameter to match how the spawnargs work for projected lights. ---- Rev 9113 Rev 16145 Colour changes now handled by the code whenever the state changes, rather than by the scriptobject continuously checking the alert state. |
|
|
Rev 9114 Spawnarg "start_on" now works. Also, initial colour is applied sooner at map start. |
|
|
Rev 9115 Use powerOn instead of STATE_PAUSED for getSecurityCameraState(). Set initial shaderParm value regardless of whether powerOn is true. |
|
|
Rev 9116 Rev 16147 Add "alarm_interval" spawnarg. Move handling of "skin_broken" from the scriptobject to the code, where the other skins are handled. Switch new spotlight material to use the new projection image. |
|
|
Rev 9117 Refactor sparks system in order to resolve sync/visibility issues: Stop spawning and deleting a func_emitter. Instead, create the func_emitter once, then refresh it by using the cycleTrigger property. No longer trigger the sparks effect in the same frame the camera is destroyed. Rev 16149 Create a new single-cycle version of the sparks particle. |
|
|
Rev 9120 Don't play fx_destroyed if camera has already been destroyed. Rev 16150 More work on entity setup: - Play spark fx when the camera is damaged or destroyed. - Document fx spawnargs in the entityDefs. - Adjust health: direct hit from fire arrow or 4-5 broadheads required. - Assign descriptions and folders to sub-entities. - Changed "snd_death" from "glass_bullethole" to "sizzle. - Gear scriptobjects shutdown if their camera is destroyed. |
|
|
Rev 9121 Rev 16152 Post-destruction sparks particle system has been made customisable. Most important new spawnargs: "sparks_periodic" and "sparks_power_dependent", which can be combined in various ways to achieve various behaviours. |
|
|
Rev 9125 Rev 16156 Rename the spawnarg "sweepSpeed" to "sweepTime" to match what is done with it in the code. Include a compatibility check for old cameras that still have "sweepSpeed" spawnargs. |
|
|
Rev 9126 Make sure all new variables are saved. Stop storing skins as variables because of problems loading them from saves. Rev 16157 Commit modified .exe for up to rev 9126. |
|
|
Rev 16160 Make sure the old security camera assets are compatible with all features of the security camera code. Use Blender to make the old camera's shapes more circular. Make a clipmodel for the old camera model. Only assign it to the new entity. Let DR automatically recognise clipmodel spawnargs as spawnargs of type "model". Rename the falloff gradient image to avoid conflict with Volta's version. Rev 9128 Rev 16161 Introduce spawnarg "skin_on" for the on skin. "skin" is now only for in-editor display, like with lamps. |
|
|
Rev 16162 Make prefabs of cameras using display screens and buttons to toggle power and individual functions. Follow wiki instructions to make 9 new camera materials so mappers can have up to 10 display screens in a map without having to figure out the map keyword. Reexport wall mount model without caulk surfaces. Flip camera GUI editor images horizontally to help mappers apply them correctly. Rev 16163 Moveable versions of security cameras. |
|
|
Rev 9130 Rev 16166 Add cameraFovX and cameraFovY spawnargs to entity.cpp, next to the existing cameraTarget spawnarg. Let security cameras modify these properties on their cameraTarget. This sets the fov of camera GUIs that are showing that entity's view. Rev 16167 Update security camera prefabs with better understanding of cameraTarget and the addition of cameraFovX and cameraFovY spawnargs. Rev 16168 Move all security camera and automaton prefabs to ai/machines. Also add a prefab for an automaton linked to a display screen. |
|
|
Rev 9132 Rev 16170 Allow mappers to use an existing spotlight with new spawnarg "spotlight_custom". Only accepts valid idLight entities. Otherwise spawns a spotlight. Rename new spawnarg "start_on" to "start_off" to match how it works with light entities. Move initial SetAngles(0, 0, 0) on spawned spotlights from scriptobject to code. Rev 16171 Let Epifire's camera use solid materials, just like grayman's camera. The code makes them all nonsolid anyway, so they rely on their clipmodels. |
|
|
Rev 9133 Rev 16172 If spotlight_diameter is set to 0, automatically calculate it to match spotlight_range and scanFov. Limited to scanFov up to 90°, since any wider starts getting ridiculous. Default value for spotlight_diameter is now 0. Rev 9134 Rev 16173 Add spawnarg "sight_threshold" to allow mappers to specify how lit up the lightgem has to be for the security camera to detect him. |
|
|
Rev 9135 Add new spawnargs to play a spark-free version of the fx when power is off. Add new snd_death_nopower spawnarg for when camera is destroyed while power is off. Make camera invincible when health is 0, as originally intended. Rev 16174 Add new "metal_damage" fx for better damage/destruction effects. Slightly increase default health to require 4 broadhead shots to destroy. |
|
|
Rev 9136 Rev 16175 Security camera can now follow the player when sighted, using spawnargs "follow" and "follow_tolerance". Currently this is silent. Switch sweep time variables from int to float to get enough precision. Initial skins were not set correctly after renaming "skin" to "skin_on". |
|
|
Rev 9143 Rev 16176 Camera can now also track the player in the vertical axis (pitch), in addition to the horizontal axis (yaw). The main new spawnarg is "follow_incline", which is enabled for the ceiling-mounted camera. The two rotation types occur independently of each other. Ceiling pivot has received a scriptobject so that it follows the camera's horizontal, but not vertical rotations Rotation speed can be increased while tracking the player with spawnarg "follow_speed_mult". |
|
|
Rev 9145 Rev 16178 Alarm no longer expires if the camera sees or recently saw the player (1/2 * alarm_duration seconds ago). Rename spawnarg "wait" to "alarm_duration". Simplify the Think() method a little. Rev 9146 When returning to regular activity, synchronise the sweep and incline times to whichever is longer. |
|
|
Rev 9149 Rev 16179 Ability to limit how far the camera can incline upwards or downwards from its starting orientation with "follow_incline_max_up" and "follow_incline_max_down" when tracking the player. Thus enable "follow_incline" for Epifire's wall-mounted camera. Old security camera's glass is no longer coloured when destroyed Added an editor image for Epifire's security camera material. |
|
|
Rev 9150 Rev 16180 Allow control over when the camera triggers its targets with spawnargs "trigger_alarm_start" and "trigger_alarm_end". Also allow to set "break_up_target" in addition to "break_up_script", to be triggered when destroyed. |
|
|
Rev 9151 Add new script event for toggling player detection. Add new script events for getting and setting health of the camera. Setting health to <= 0 will destroy it with fx. Add new script event for setting the sight threshold of the camera. Script event toggle_sweep() can now be called multiple times in one sweep without breaking sweep parameters. Script event toggle_sweep() can now also disable following. Rename alarm_duration to alertDuration internally. Rev 16181 The scriptobject now calls the script event for toggling player detection, rather than setting the spawnarg "canSee". Internally the code still monitors the "canSee" spawnarg. Remove empty ::init() and ::break_up() members from the scriptobject. Add light effect to metal damage fx. Remove broken light effect from existing sparks fx. Committed .exe since the scriptobject requires a new script event. |
|
|
Rev 16182 Add a wallplate for the wall-mounted Epifire camera. Add spawnarg "gear_speed" to ceiling mount for Epifire camera. Remove a protrusion from the wall pivot model that was clipping with the head. Add missing faces to the Epifire gear so that it can be better used as a standalone model. Document "cameraTarget" spawnarg in the base entityDef. |
|
|
Rev 16194 Add pivot mounts for the old security camera for walls and ceilings, allowing to rotate both horizontally and vertically. Add a compact version of the old security camera with a different origin, designed to fit into these pivot mounts. Rev 16195 Make new gear and pivot scriptobjects compatible with custom versions. Rev 9168 Rev 16196 Groundwork for constraining horizontal and vertical rotation. |
 |
Probably out of scope, but I'll mention it in case you feel like investigating: https://github.com/TTimo/doom3.gpl/blob/master/neo/game/SecurityCamera.cpp#L516 apparently has code to turn the destroyed camera into a moveable and drop it to the ground. This was removed at some point and I've no idea why; maybe it didn't even work. But if it could be trivially brought back it might be nice as an optional feature for camera designs that suited it. |
|
|
Yep this works as is, thanks for sharing that. The camera kind of pops out - should probably position it so that its collisionmodel is completely clear of anything else. Would be especially good for something like an eyeball plant, to have it pop out of its socket. Maybe it just didn't make it into the official release? Your link does say this is TImo's branch. |
|
|
According to https://ttimo.github.io/doom3.gpl/ it's in the source as id released it, so unless the change came after the D3 SDK release (I don't fancy installing a .exe just to check some code), I've no idea. Cheers for that, anyway. |
|
|
Ah right, this segment was actually in the TDM code until grayman redesigned the whole security camera in rev 7195, where this was dropped. I assume this is because it didn’t fit too well to the original camera models. This could be quite good if the models are designed with this in mind. Especially for something like an eyeball plant. |
|
|
Rev 9171, 9172 Security camera can now sweep 360° or more. |
|
|
Rev 9173 Rev 16199 - Reinstate code from pre-rev 7195 to “dislodge” the security camera when destroyed (turn into a moveable) and expand on it: -- Dislodge occurs when a specified amount of negative health is surpassed. Either a) only on a large hit (fire arrow) or b) after taking enough cumulative damage. -- Add more physics parameters and control them with spawnargs. -- Integrate dislodging with the sparks system so sparks particle can be set not to appear if dislodged - Adjust models & clipmodels such that the cameras have enough space to eject reliably. - Dislodging is enabled for Epifire’s cameras by default. Could also be enabled for pivot-mounted old cameras, but not a good idea for the original old cameras. - Pivots and gears are no longer solid, no longer absorbing projectiles like fire arrows. - Pivots check their camera’s status more frequently to react faster in case it’s dislodged. - Damaging the camera will now also trigger fx when it has already been destroyed. Weaknesses currently: - Not a true moveable. Makes no bounce sounds, can’t KO AIs, can’t be frobbed even after calling Set_Frobable(1). - Seeing this should alert AIs. |
|
|
Rev 9174 Rev 16200 AIs become alerted if they see a destroyed security camera. Rev 9175 Security cameras with sweepAngle over 180° properly resume their sweep after an interruption (power toggled or saw player without following him). |
|
|
Rev 9176. TDM no longer crashes at map load when a Response has been set on the security camera. idSecurityCamera::spawn contained the following: // SR CONTENTS_RESPONSE FIX if( m_StimResponseColl->HasResponse() ) physicsObj.SetContents( physicsObj.GetContents() | CONTENTS_RESPONSE ); physicsObj seems not to be initialised, so according to debug mode TDM crashes at GetContents() when a security camera with a Response is spawned. Replacing physicsObj. with GetPhysics()-> fixes the crash and allows the security camera to Respond to stims. physicsObj is only used in idSecurityCamera::Killed when the camera is dislodged from its mount, so it can probably be made into a local variable. A similar problem might exist with other spawnclasses, too, since the code block above is quite common. Rev 9177 Security camera is able to Respond to trigger stims and trigger signals. Don't need to activate the physics object after being dislodged. Rev 9178 Rev 16203 Now possible to frob the security camera. Also allow to make dislodged security cameras frobable/unfrobable. Rev 9179 Player is able to pick up a dislodged security camera. Move "dislodge" code into its own method. |
|
|
Rev 9180 Rev 16204 Transplant idMoveable::Collide to idSecurityCamera so that dislodged security cameras make sounds when colliding. In theory they should also damage / knockout AIs, but I wasn't able to reproduce this behaviour even with existing heavy moveables. Align physics spawnargs of security camera moveables with those of dislodged security cameras. |
|
|
Does it have a damage def? These spawnargs are in atdm:damage_moveable: "damage" "1" // scaled by mass & velocity at time of impact "scale_damage" "1" // scale damage before applying it "knockout" "1" // can cause a knockout, but mass and velocity also play a part "knockout_power" "0" // powered-up knockout, not used "push" "6" "kill_all" "0" // if = 1, allow the moveable to kill what it strikes |
|
|
Yeah it was missing a damage def, as well as a lot of other things that a TDM moveable requires to function, such as other code being able to recognise not only idMoveable, but also idSecurityCamera. I got it to work on my end (knocking out AIs, bounce sounds, etc.), but decided to revert it because there was simply too much non-security camera code to modify or replicate. It would be better to be replaced by a moveable and/or generate flinders. Rev 9181 Rev 16205 Revert most of the recent dislodge-related changes, but keep the logic for when the camera decides to dislodge. |
|
|
Rev 9182 Rev 16206 Rework damage system: - Add idSecurityCamera::Damage method for more control over what can damage the security camera: - Add "damage_mult_" spawnargs to allow mappers to control how much swords, broadheads, fire arrows etc. can damage the security camera. Mappers can change these ingame and also specify their own damage_mult_ spawnargs for custom damage defs. By default only fire arrows can damage the camera now. - Camera now flinderizes instead of dislodging upon taking a sufficiently large hit. Controlled by the "damage_flinderize" spawnarg. Flinders are yet to be made. - Allow to specify a separate model and skin for when the camera is flinderized. Spawnargs: "broken_flinderized" and "skin_flinderized". The idea is to leave behind a static stump. In idEntity: - Add new bool m_bFlinderize (default true) to idEntity to control whether an entity flinderizes during idEntity::BecomeBroken. - Hide broken models with "hideModelOnBreak" "1" even if a valid "broken" model has been specified. No .map or .def in core TDM or released FMs has used this spawnarg yet. |
|
|
Rev 9184 Rev 16210 Finetune damage system: - also allow to specify custom damage_mult spawnargs for entityDefs of the inflictor - custom damage_mult spawnargs take priority over standard damage_mult spawnargs - let fire arrow splash damage attenuate faster - clean up the logic Also some tweaks to the tooltips of the security camera entityDefs in general. Rev 9185 Add script events to set, rather than toggle, the state of the security camera as a whole ("power") and its subcomponents: - On() and Off(), as with idLight - state_light(boolean set) - state_sweep(boolean set) - state_see_player(boolean set) The existing toggle events now call these new events to avoid code duplication. Rev 9186 - Automatically detect whether the mapper has specified a looping sparks particle, thereby getting rid of the spawnarg "sparks_periodic". This is important for how the security camera will trigger the sparks particle (toggle on/off or cycleTrigger). - Move the creation of the sparks particle into its own method, AddSparks, just like AddLight. Rev 9187 Rev 16211 - Simplify the ::Damage method with some better usage of idStr/const char. - Add new spawnarg "damage_splash_falloff" to allow mappers to modify (exponentially) how quickly splash damage decreases with distance. |
|
|
Rev 9188 Rev 16212 Spawnarg "sweepSpeed" now sets speed rather than time. Get rid of redundant spawnarg "sweepTime". Introduce spawnarg "legacy" to mark old versions of the security camera that should still use sweepSpeed as if it was sweepTime. Merge clipmodels with models. Old original security camera still uses a separate clipmodel. |
|
|
Rev 9187 Fix use of const char and idStr in the ::Damage method, pertaining to custom spawnargs for specific damage sources. |
|
|
Rev 9647 AlertDuration of security camera wasn't being determined at init. Rev 16388 No longer possible to have multiple camera screens show different video feeds in parallel: eliminate additional camera GUI materials and update prefabs that used them. See rev 9232 and 0005676. |
 |
What does the last paragraph mean though? We can no longer have multiple security cameras on a map at the same time? That sounds like a huge limitation, hopefully I just misunderstood or if so that can be fixed soon. |
|
|
Revs 9749, 9754 Add script event getEnemy to security cameras. Gets the entity that most recently caused or refreshed the security camera's suspicious or alert state. Rev 9755 Add script event canSee() to security cameras. Tests whether the security camera is able to see a specific entity. Currently only player1 is supported. ----- Rev 16414 Spawn Epifire's new flinder pieces upon destruction of security cameras. |
|
|
@MirceaKitsune the problem was only with having multiple camera screens in view simultaneously, for a short while that was broken but it has meanwhile been fixed again. Security cameras themselves were never affected. |
 |
r9832 renderLight.suppressInSubview: persist in save games ( duzenko ) Setting to fixed. It can be re-opened if any further issues are found in the final beta release(s) |
|
|
Setting to resolved as I don't plan more work on security cameras before 2.10's release. Any further possible changes are for 2.11. All that remains is to update the Wiki documentation with the more recent revs. |
|
|
Setting to assigned again as Ive seen that some more documentation is still needed. |
|
|
Wiki is now fully up to date for TDM 2.10. |
- Anonymous
