Verve Bug Report 1.0
by Joseph W. · in Verve · 05/19/2010 (11:37 am) · 2 replies
Just got Verve yesterday so still trying to figure everything out but I have found a few possible bugs / improvements. Some of these may be fixed but after doing a Diff it didn't appear as though any of these were any different.
1)
Keep getting warnings about mounting and VPath::unmountObject and VPath::mountObject and that detachObject and attachObject should be used instead. Only thing is, I am not calling any of these functions, after poking inside of VPath.cpp I have noticed that in the functions onDetachObject and onAttachObject you are calling unmountObject and mountObject internally, should these instead be referencing your detachObject and attachObject functions or is this just a warning that has to be lived with when isServerObject is true for single player?
2)
When enabling the Editor Window and then going back to Torque window and using the X to close the game crashes inside of engine/source/gfx/d3d9/pc/gfxpcd3d9target.cpp @ line 369. I believe this has to do with your window being destroyed but not being properly removed somehow and thus the engine references it again before exiting completely.
3)
When adding in a StaticShape (this one happen to be a DTS with embedded animation sequences) into the Editor as a Scene Object Group and then adding a Animation Track Event I do not see any of the animation sequences from the pull down. What I found however was that if I select the StaticShape file and go to Shape Editor and then back to Verve the animations are present finally.
4)
When adding a Motion track I am unable to keyframe a third node to move to. I am able to do the first and second nodes without a problem but then the object becomes locked and I am unable to move it in order to progress the path to a third point, is there a crucial step that I am not seeing?
I am sure I will find others, but these are some that are happening regularly enough that I wanted to make you aware.
1)
Keep getting warnings about mounting and VPath::unmountObject and VPath::mountObject and that detachObject and attachObject should be used instead. Only thing is, I am not calling any of these functions, after poking inside of VPath.cpp I have noticed that in the functions onDetachObject and onAttachObject you are calling unmountObject and mountObject internally, should these instead be referencing your detachObject and attachObject functions or is this just a warning that has to be lived with when isServerObject is true for single player?
2)
When enabling the Editor Window and then going back to Torque window and using the X to close the game crashes inside of engine/source/gfx/d3d9/pc/gfxpcd3d9target.cpp @ line 369. I believe this has to do with your window being destroyed but not being properly removed somehow and thus the engine references it again before exiting completely.
3)
When adding in a StaticShape (this one happen to be a DTS with embedded animation sequences) into the Editor as a Scene Object Group and then adding a Animation Track Event I do not see any of the animation sequences from the pull down. What I found however was that if I select the StaticShape file and go to Shape Editor and then back to Verve the animations are present finally.
4)
When adding a Motion track I am unable to keyframe a third node to move to. I am able to do the first and second nodes without a problem but then the object becomes locked and I am unable to move it in order to progress the path to a third point, is there a crucial step that I am not seeing?
I am sure I will find others, but these are some that are happening regularly enough that I wanted to make you aware.
#2
1) This appears to be fixed as the code was very different for these functions.
2) This is still an issue, in fact I believe there is a major bug/issue with using the X to close Verve windows and possible just how Verve Editor window is closing in general. I have found that when using the X on the Verve Editor window and then reopening while in the Editor and trying to open up a new sequence file the Open File Dialog window will pop open once for each time I've closed the verve Editor window with the X.
Potentially related to this I have found that after multiple openings and closings that the Verve Editor window can become non-responsive for the normal inputs on the right where you can manually edit the duration and other general attributes of the sequence.
3) This continues to happen with animations not showing up, I'm curious now if it is because your code is looking for a scripted sequence file for collada maybe while DTS embed the animations with generic objects? Not a huge issue as we are trying to force all models into Collada for future development but it is a bug.
4) This seems to be fixed as well.
Thanks for all your hard work and hopefully I can help keep you informed of any fixes or issues I see down the road.
06/03/2010 (5:51 am)
As an update since we moved to 1.1 B1 for T3D and Verve to see if some of these issues would be resolved:1) This appears to be fixed as the code was very different for these functions.
2) This is still an issue, in fact I believe there is a major bug/issue with using the X to close Verve windows and possible just how Verve Editor window is closing in general. I have found that when using the X on the Verve Editor window and then reopening while in the Editor and trying to open up a new sequence file the Open File Dialog window will pop open once for each time I've closed the verve Editor window with the X.
Potentially related to this I have found that after multiple openings and closings that the Verve Editor window can become non-responsive for the normal inputs on the right where you can manually edit the duration and other general attributes of the sequence.
3) This continues to happen with animations not showing up, I'm curious now if it is because your code is looking for a scripted sequence file for collada maybe while DTS embed the animations with generic objects? Not a huge issue as we are trying to force all models into Collada for future development but it is a bug.
4) This seems to be fixed as well.
Thanks for all your hard work and hopefully I can help keep you informed of any fixes or issues I see down the road.
Associate Phillip O'Shea
Violent Tulip
Thanks Joseph!