Saving a mission file leads to duplicates?!?
by Tobias B. · in Torque Game Engine Advanced · 01/28/2009 (11:48 am) · 6 replies
Hi,
sometimes, in TGEA 1.8 we noticed a strange behaviour: After playing around with our missions and saving the resulting world, the mission file contains two object lists like this
//--- OBJECT WRITE BEGIN ---
...
...
//--- OBJECT WRITE END ---
//--- OBJECT WRITE BEGIN ---
...
...
//--- OBJECT WRITE END ---
where the first list seems te be the old one and the second is the "new" world. This is quite bad because most objects (items, terrain sky etc.) are renderes twice which drops the frame rate.
Is this a bug or a back-up feature? How can we disable this?
Thanks and best regards,
Tobias
sometimes, in TGEA 1.8 we noticed a strange behaviour: After playing around with our missions and saving the resulting world, the mission file contains two object lists like this
//--- OBJECT WRITE BEGIN ---
...
...
//--- OBJECT WRITE END ---
//--- OBJECT WRITE BEGIN ---
...
...
//--- OBJECT WRITE END ---
where the first list seems te be the old one and the second is the "new" world. This is quite bad because most objects (items, terrain sky etc.) are renderes twice which drops the frame rate.
Is this a bug or a back-up feature? How can we disable this?
Thanks and best regards,
Tobias
#2
The SimGroups are called like this
new SimGroup(MissionGroup) {
...
}
in both cases, i.e. they are identical. The only difference are some objects in these groups added between two mission savings.
I think that's strange, isn't it?
02/10/2009 (3:16 am)
Sorry for the delay... I was a bit in trouble ;-)The SimGroups are called like this
new SimGroup(MissionGroup) {
...
}
in both cases, i.e. they are identical. The only difference are some objects in these groups added between two mission savings.
I think that's strange, isn't it?
#3
02/23/2009 (3:08 am)
Does anyone have the same effect?
#4
02/23/2009 (4:51 am)
I had that happen in 1.8.0 a couple of times. I haven't seen it in 1.8.1 yet tho.
#5
02/23/2009 (6:33 am)
We've seen it a couple of times I think that was on 1.7.1 although could have been 1.8, not seen on 1.8.1 yet but we've only migrated to that engine in the past week.
#6
02/24/2009 (1:02 am)
We use v1.8.1, and it happens from time to time - don't know why...
Associate Scott Burns
GG Alumni