Fatal Crash DAZ3D PC 4.6.3.52 'Point At'
Fatal Crash Using 'Point At' with parented cameras - DAZ3D PC 4.6.3.52 64-Bit
Application crashes when attempting to delete a Genesis figure rigged to point at a null
object by another with attached cameras.
Scene:
1 Genesis
1 Null object
2 Cameras with default settings
Rig:
Genesis
.Hip
..Abdomen
...Abdomen 2
....Chest
..... Neck
......Head
.......Right Eye
........* Camera 1
.......Left Eye
........* Camera 2
......* Null 1
Instructions:
1. Parent Camera 1 > Right Eye, Camera 2 > Left Eye and Null 1 > Head.
2. Set 'Right Eye' and 'Left Eye' to point at 'Null 1' via [Parameters/General/Point At]
3. Delete the figure
Crash!
DAZStudio.exe caused ACCESS_VIOLATION in module "D:\Program Files\DAZ 3D
\DAZStudio4.6\DzCore.dll" at 0033:00000000642F2660, DzNode::getNodeParent()
The only workaround seems to unparent the related objects from the figure to be removed.
-------------------------------------------------------------
Is anyone else able to replicate this?

Comments
You know, in a way it kind of makes since, if you think of other parented items removed from a scene, all the children get deleted from the scene as well.
In this case it may be a dependance issue, the point at may be making something think the null and cams are removed, when there not, or something like that. Complex systems tend to have unexpected behavior at times, this is probably one of them. Sorry not much help, other then a thought as to why.
A question to help others that know more help you. What Operating system is this on? PC/Apple/mac? How much ram?
You should write a bug repport using zendesk or the devs will not notice the bugreport as they very seldom wade through the forums hunting for reports.
But the bug look very much like an "opps" something got deleted and something else is depending on it and was not unhooked correctly.
The bug was submitted. I did find a workaround to deleting the figure. One must unparent all related objects from the figure before it can be safely deleted. Save often!!! :)
UPDATE: This is fixed as of v4.8.x