0000108: Trigger a object with info_waypoint parented in a trigger_once_oc makes crash the mod

View Issue Details [ Jump to Notes ] [ Wiki ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000108

Obsidian Conflict

[All Projects] Bug-Report

public

25.01.2012 20:48

25.01.2012 23:20

Reporter

Maestro Fenix

Assigned To

TESLA-X4

Priority

immediate

Severity

crash

Reproducibility

always

Status

resolved

Resolution

duplicate

Projection

minor fix

ETA

none

Platform

OS Version

Product Version

0.1.3.5

Product Build

Target Version

0.1.3.6

Fixed in Version

0.1.3.6

Summary

0000108: Trigger a object with info_waypoint parented in a trigger_once_oc makes crash the mod

Description

If you parent a info_waypoint to a physic object (doesnt matter if is a normal prop_physics or a overrided one), and then, you make touch the object with a trigger_once_oc that makes an output of killing the object, the mod will crash.

No idea if this happens on the normal trigger_once, as well as the trigger_multiple.

The mod will crash anyway whether if you make an output to kill the object and the waypoint as if you only kill the object.

Steps To Reproduce

(In Hammer):

Parent a info_waypoint with a prop_physics

Make a trigger_once_oc and make an output that kills the object

(In the mod):

Pick up the object and carry it to the trigger to crash the mod.

Tags

No tags attached.

Attached Files

Relationships

Notes
(0000190) W0rf0x (manager) 25.01.2012 23:09	Workaround: disable the waypoint before killing it or the object its parented to.

(0000191) TESLA-X4 (developer) 25.01.2012 23:19	This is no longer an issue in 0.1.3.6, I'll see if any better workarounds exist that can be applied to the next server hotfix.

Time: 0.1055 seconds.
memory usage: 8,342 KB