Cube Dropper Help
Quote from JoeyGuy917 on October 27, 2013, 2:31 pmI made a custom cube dropper which spawns a portable laser, [spoiler]a laser parented to a cube[/spoiler] and when I put it through a fizzler, it emancipates, but it doesnt respawn. I have the button set to enable respawning of the cube (after the button is triggered). Come to think of it, it doesnt respawn after I push the button either. I am becoming more confused every second i type now...
I made a custom cube dropper which spawns a portable laser,
MLIA
Thanks in advance

Quote from JoeyGuy917 on October 27, 2013, 7:07 pmhttp://www.mediafire.com/?w43i5bb8limye3v This is my instance for it, and if anyone uses it in thier maps, please just give credit for it in the desc. please.
http://www.mediafire.com/?w43i5bb8limye3v This is my instance for it, and if anyone uses it in thier maps, please just give credit for it in the desc. please.
MLIA
Thanks in advance

Quote from Skotty on October 29, 2013, 10:19 amYou are funny. Inside that instance are just a few brushes and another func_instance I don't have.
You are funny. Inside that instance are just a few brushes and another func_instance I don't have.
Quote from piripiago on October 30, 2013, 4:52 amIt appears like you are trying to start with one of the existing dropper instances. Those instances have a lot of extra logic and triggers that might be interfering with spawning the laser. I created a cube and a parented a laser to it and threw them into a point_template. I think the problem you are experiencing is happening because there is not enough time between the cube being fizzled and the next cube being spawned. Maybe there is some confusion with which cube it is supposed to be parented to, in which case it is getting dissolved along with the previous cube. With an excruciatingly long delay of 2 seconds before the ForceSpawn, the previous cube is able to completely finish dissolving before the next cube and its laser are spawned, and the new laser is accurately created parented to the new cube.
see also: http://www.tophattwaffle.com/hammer-tutorial-12-spawing-props-and-other-things/
It appears like you are trying to start with one of the existing dropper instances. Those instances have a lot of extra logic and triggers that might be interfering with spawning the laser. I created a cube and a parented a laser to it and threw them into a point_template. I think the problem you are experiencing is happening because there is not enough time between the cube being fizzled and the next cube being spawned. Maybe there is some confusion with which cube it is supposed to be parented to, in which case it is getting dissolved along with the previous cube. With an excruciatingly long delay of 2 seconds before the ForceSpawn, the previous cube is able to completely finish dissolving before the next cube and its laser are spawned, and the new laser is accurately created parented to the new cube.
see also: http://www.tophattwaffle.com/hammer-tutorial-12-spawing-props-and-other-things/