Game Development Community

1.5.1 Particle Systems still don't save properly

by Oliver Rendelmann - DerR · in Torque Game Builder · 08/06/2007 (8:09 am) · 7 replies

I was working on a particle system with many emitters. It saved and loaded like a charm the whole time, until I deleted an emitter from the middle of the list... the whole particle system got destroyed. The emitters were there but they were given weird names and the settings had been resetted.

#1
08/08/2007 (5:34 am)
Same problem here. Is there going to be a fix? Will there be a 1.5.2? When will it be out?
#2
08/09/2007 (10:43 am)
Just got this same problem
#3
08/11/2007 (5:30 pm)
I also think that particle collision does not work in 1.5.1
#4
09/13/2007 (3:24 am)
Hm, does GG intend to release a patch for this? When is the next version/service pack planned?
#5
02/18/2008 (4:40 am)
I am still using TGB 1.5, so I don't know if the particle issues have been fixed, but I also have a problem with a particle whose mode is "kill" and with a lifetime of less than 0.5. The editor rounds the time down to 0.0 which makes the particle infinite. Definitely not what should happen.
#6
04/06/2008 (11:34 am)
Particle collision seems to work again (in 1.7.2). But sometimes it still happens that a particle system (.eff file) is destroyed. I just worked on an effect for quite some time and after I was happy with it I started to work on the next. After starting the level I noticed that the old particle effect does not work any more. In the editor I realized that the emitter was deleted from the effect :-(

Edit: See my next post. It is not really deleted but not shown any more since the file was not written correctly.
#7
04/06/2008 (12:45 pm)
I found out why this particle effect file is/was broken. I made a copy and compared it to working ones. In this case the values for spin_scale have not been written as shown in the screenshot. I was able to fix this by copying the missing bytes from a working effect file to the broken one.

www.codecoach.de/GG/particle_effect_error.png
I took a look in the code but was not able to see why this might happen.