Sparks problem

For all the help you need with Armagetron!
Post Reply
User avatar
Kijutsu
Match Winner
Posts: 676
Joined: Mon Jan 11, 2010 6:37 pm

Sparks problem

Post by Kijutsu »

When I turn sparks on, this happens:
Image

Yes, I'm aware of the fact that if you turn alpha blending on, you wont see it. But I want alpha blending off. How do I get normal sparks, like in 2.8?
epsy
Adjust Outside Corner Grinder
Posts: 2003
Joined: Tue Nov 07, 2006 6:02 pm
Location: paris
Contact:

Re: Sparks problem

Post by epsy »

Is vsync off? Turn it on.
User avatar
Kijutsu
Match Winner
Posts: 676
Joined: Mon Jan 11, 2010 6:37 pm

Re: Sparks problem

Post by Kijutsu »

If that fixes it then I'd love to do that, but I'm on a mac and I have no idea where to turn vsync on. (I have an ATI Radeon 2600 Pro if that helps)
epsy
Adjust Outside Corner Grinder
Posts: 2003
Joined: Tue Nov 07, 2006 6:02 pm
Location: paris
Contact:

Re: Sparks problem

Post by epsy »

You can force vsync from armagetronad itself: System Setup -> Display Settings -> Screen Mode -> VSync ("wait" means enabling)
User avatar
Kijutsu
Match Winner
Posts: 676
Joined: Mon Jan 11, 2010 6:37 pm

Re: Sparks problem

Post by Kijutsu »

Ive tried that already, it doesn't fix the sparks problem.
epsy
Adjust Outside Corner Grinder
Posts: 2003
Joined: Tue Nov 07, 2006 6:02 pm
Location: paris
Contact:

Re: Sparks problem

Post by epsy »

By "sparks problem" you mean the distortion? Or you mean the "never-dieing sparks" bug? If you mean the latter, it's a known bug that has been there since the inclusion of the new particles engine. Sure, that needs fixing, but no need for duplicate threads :)
User avatar
Kijutsu
Match Winner
Posts: 676
Joined: Mon Jan 11, 2010 6:37 pm

Re: Sparks problem

Post by Kijutsu »

The never-dying* sparks, the distortion was just a screenshot freeze or something.. but yeah the sparks-shower has got to go. I didn't know this bug wasn't fixed yet. :(
User avatar
Jonathan
A Brave Victim
Posts: 3391
Joined: Thu Feb 03, 2005 12:50 am
Location: Not really lurking anymore

Re: Sparks problem

Post by Jonathan »

vogue wrote:the distortion was just a screenshot freeze or something.
⇧⌘3 has done that to me countless times on SMP machines running ≤10.5. Either it freezes the screen while taking the screenshot or the screenshot becomes rather fragmented. It seems 10.6 finally switched to a proper technique, which neither freezes nor fragments.
ˌɑrməˈɡɛˌtrɑn
User avatar
Lucifer
Project Developer
Posts: 8756
Joined: Sun Aug 15, 2004 3:32 pm
Location: Republic of Texas

Re: Sparks problem

Post by Lucifer »

Epsy: Did someone take the new particle engine and actually rewrite sparks using it?
Check out my YouTube channel: https://youtube.com/@davefancella?si=H--oCK3k_dQ1laDN

Be the devil's own, Lucifer's my name.
- Iron Maiden
Luke-Jr
Dr Z Level
Posts: 2246
Joined: Sun Mar 20, 2005 4:03 pm
Location: IM: luke@dashjr.org

Re: Sparks problem

Post by Luke-Jr »

Added to Launchpad bug tracker: https://bugs.launchpad.net/armagetronad/+bug/566924
Fix in progress :)
Luke-Jr
Dr Z Level
Posts: 2246
Joined: Sun Mar 20, 2005 4:03 pm
Location: IM: luke@dashjr.org

Re: Sparks problem

Post by Luke-Jr »

And fixed! Blame goes to z-man ;)
User avatar
Z-Man
God & Project Admin
Posts: 11736
Joined: Sun Jan 23, 2005 6:01 pm
Location: Cologne
Contact:

Re: Sparks problem

Post by Z-Man »

Hmm? I don't remember touching the new particle stuff, ever. Was it in a merge? 'cause my work avoidance policy for those is 'compiles, runs, plays, check in'.
Luke-Jr
Dr Z Level
Posts: 2246
Joined: Sun Mar 20, 2005 4:03 pm
Location: IM: luke@dashjr.org

Re: Sparks problem

Post by Luke-Jr »

Z-Man wrote:Hmm? I don't remember touching the new particle stuff, ever.
This bug is with particles disabled.
svn r4679 wrote:revno: 31
svn revno: 4679 (on /armagetronad/trunk/armagetronad)
committer: z-man
timestamp: Wed 2006-05-31 19:57:05 +0000
message:
Fixed warning with particles enabled.
Disabled particle code on the server to avoid linker errors if the stupid
builder builds the server with --enable-particles.
You removed the updating of the lastTime variable for some reason...
Post Reply