Version 1.02[or3] VS. version 1.4:: Trigger Data
by Rex · in Artist Corner · 11/30/2007 (1:37 pm) · 9 replies
I do not see the latest version of STP showing trigger data in a .dsq sequence?? I open the same file in version 1.02 and I see it, use version 1.4 and I get an ERR in that column of Sequence Info?? I recently noticed the latest version and downloaded it...I still maintain an earlier version that came with my 1.4.2 license. Is that enough backStory??? LOL.
Has anyone noticed this?? Can it be looked into, please, if I'm correct or incorrect!???! Hard to tell if it's there without entering engine.... Have a nice day everyone!
This is the 'standAlone' version that installed in ProgramFiles....more backStory.
Has anyone noticed this?? Can it be looked into, please, if I'm correct or incorrect!???! Hard to tell if it's there without entering engine.... Have a nice day everyone!
This is the 'standAlone' version that installed in ProgramFiles....more backStory.
About the author
Rex does all his 3D graphics through BrokeAssGames and is currently working on DSQTweaker, Ecstasy Motion, and other interesting projects yet to be revealed. Just ask him about anything DTS/DSQ related, he's happy to help.
#3
12/01/2007 (6:03 am)
Thanks, Joseph, I thought so, wonder how this made it past QA??? Pretty major malfunction! I like the fact that version 1.4 allows for decent loading of a Constructor script, finally, but I've got to regress back a version or two...trigger data is too important not to be able to see in finished prototypes. 
#4
I can confirm the same problem with MilkShape models. Triggers work fine in v1.02 but just show err in v1.04.
Rex, at least you have another version to fall back on. I had to send my model halfway round the world to get this confirmed.
Dale
02/19/2008 (2:51 pm)
Hi all,I can confirm the same problem with MilkShape models. Triggers work fine in v1.02 but just show err in v1.04.
Rex, at least you have another version to fall back on. I had to send my model halfway round the world to get this confirmed.
Dale
#5
02/20/2008 (3:07 am)
Yet posted for a bugs into support? Maybe receiving a bit of request someone will take a look into it...
#7
03/13/2008 (5:08 am)
I don't believe so, I've never had my triggers 'not work' inside the engine before...only in ShowToolPro. I can take the same sequence and view it in both versions of program. I do believe that the groundTransform data is being parsed, otherwise they would not work in game? I see footprints and footpuffs in game, I see the ERR in the tool.......
#8
03/16/2008 (11:18 am)
I can confirm Rex's statement. Triggers exported from MS work fine in game but not the show tool.
#9
If you are only working with one DSQ, with triggers, simply load it twice. The top listing will have accurate trigger info.
If you are working with a list of DSQ's, reload one that has triggers as the last one you load. All trigger info will be reported accurately except the last one.
If you are working with a list of DSQ's and none of them have triggers you will still get Err under Trigs. I don't know how to get around this one.
If you are using Load DTS and CS you can temporally modify your CS to load a duplicate of a triggered DSQ at the end of the list. For example: I added ( sequence30 = "./player_side.dsq side2";) to the player.cs file for the default player. Without this line the Root seq. trigger = No, run = Yes, Back = Yes, Side = Err and everything below Side = Err. With the new line added all trigger info seems to be accurate except the last, duplicated, one.
It seems quite obvious by now that this is a STP problem and has nothing to do with the Blender or MS3D exporters.
08/22/2008 (12:54 pm)
I've came up with a work around for this problem. I noticed that sometimes the trigger data is displayed in STP 1.4. After a bit of experimenting it seems that the last DSQ loaded into STP has the Err. If you load a DTS then load one DSQ, STP will display Err under Trigs. It does not matter if the DSQ has triggers or not, Err is reported. If you load a second DSQ, one with triggers, the STP report for the first DSQ will be updated to display accurate trigger info. If neither of the DSQ's have triggers you still get Err under Trigs.If you are only working with one DSQ, with triggers, simply load it twice. The top listing will have accurate trigger info.
If you are working with a list of DSQ's, reload one that has triggers as the last one you load. All trigger info will be reported accurately except the last one.
If you are working with a list of DSQ's and none of them have triggers you will still get Err under Trigs. I don't know how to get around this one.
If you are using Load DTS and CS you can temporally modify your CS to load a duplicate of a triggered DSQ at the end of the list. For example: I added ( sequence30 = "./player_side.dsq side2";) to the player.cs file for the default player. Without this line the Root seq. trigger = No, run = Yes, Back = Yes, Side = Err and everything below Side = Err. With the new line added all trigger info seems to be accurate except the last, duplicated, one.
It seems quite obvious by now that this is a STP problem and has nothing to do with the Blender or MS3D exporters.
Torque Owner Rex
BrokeAss Games