0002101: Octree can end up with orphaned scene::Node

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0002101

DarkRadiant

Design/Coding

public

10.01.2010 15:40

20.06.2010 10:03

Reporter

greebo

Assigned To

greebo

Priority

normal

Severity

normal

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

1.1.0

Fixed in Version

1.1.0

Summary

0002101: Octree can end up with orphaned scene::Node

Description

It's possible to encounter orphaned scene::Nodes (a PicoModelNode in this case) when traversing the Octree. Steps to reproduce:

* Open a new map
* Create Entity
* Choose Lights > Switchable > Electric > Lampshade (the first one)

In debug builds, an assertion will fire due to the orphaned node evaluating its bounds during scenegraph traversal. The previous call to worldAABB() on the scene root has no effect on this node as the PicoModelNode has no parent.

Investigation needed, in which way 2 PicoModelNodes even get created during this process of adding a single entity and why the wrong one of them ends up in the Octree.

Tags

No tags attached.

Attached Files

Relationships

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
10.01.2010 15:40	greebo	New Issue
10.01.2010 15:40	greebo	Status	new => confirmed
11.01.2010 12:35	greebo	Status	confirmed => assigned
11.01.2010 12:35	greebo	Assigned To	=> greebo
11.01.2010 12:35	greebo	Status	assigned => resolved
11.01.2010 12:35	greebo	Fixed in Version	=> 1.1.0
11.01.2010 12:35	greebo	Resolution	open => fixed
11.01.2010 12:36	greebo	Projection	none => minor fix
11.01.2010 12:36	greebo	ETA	none => < 1 day
11.01.2010 12:36	greebo	Build	=> 5153
11.01.2010 12:36	greebo	Target Version	=> 1.1.0
20.06.2010 10:03	greebo	Status	resolved => closed