Thread history

From Talk:Neuromancer/Version History
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
09:04, 5 October 2017 Xor (talk | contribs) New reply created (Reply to Performance Enhancing Bugs)
07:51, 5 October 2017 Skilgannon (talk | contribs) New reply created (Reply to Performance Enhancing Bugs)
07:49, 5 October 2017 Skilgannon (talk | contribs) New reply created (Reply to Performance Enhancing Bugs)
02:44, 5 October 2017 Xor (talk | contribs) New reply created (Reply to Performance Enhancing Bugs)
02:33, 5 October 2017 Xor (talk | contribs) New reply created (Reply to Performance Enhancing Bugs)
19:47, 4 October 2017 Skilgannon (talk | contribs) New reply created (Reply to Performance Enhancing Bugs)
16:26, 29 June 2013 MN (talk | contribs) New reply created (Reply to Performance Enhancing Bugs)
18:44, 28 June 2013 Chase-san (talk | contribs) New reply created (Reply to Performance Enhancing Bugs)
16:41, 28 June 2013 Skilgannon (talk | contribs) New thread created  

Performance Enhancing Bugs

I just ran into a pretty strange one. The old prediction code I was using for my wave-intersections gave NaN hit points under certain conditions (reversing and turning a lot simultaneously). Fixing it raises my 1v1 score, but lowers my melee score a lot. The new method also also allows me to re-use my prediction paths, so I really want it because it means I might have a chance at multi-branch multi-wave surfing, but the score drop right now means that it isn't at all worth it. Crazy...

Skilgannon (talk)16:41, 28 June 2013

Figure out why it was raising your score and re-tune so that it has the same behavior for melee, but not for 1v1.

Chase18:44, 28 June 2013
 

Maybe it's because in melee there a lot more Play It Forward/Pattern matchers than in 1v1. And reversing/turning a lot functions as some kind of anti pattern-matching.

MN (talk)16:26, 29 June 2013
 

This old Performance Enhancing Bug just came back to bite me... I thought gunheat waves would fix it, but clearly not!

Skilgannon (talk)19:47, 4 October 2017

So is the bug fixed and re-tuned at that time? Or did u just leave it in, or branching on 1v1 and melee?

Xor (talk)02:33, 5 October 2017

I made a copy of the subset of the code that caused it, and branched to use it when more than one enemy is present.

Skilgannon (talk)07:49, 5 October 2017
 

IMO, there always lies another bug behind one performance enhancing bug. The bug behind scene maybe in code, or it is just the assumptions you made when writing the code. e.g. ScalarBot’s gun is using far smaller cluster size nearly randomly (actually, it depends on the structure of the tree, which is not consistent over battles) in the past, but that bug helps against surfers dramatically. That bug is performance enhancing because the assumptions I made before using kNN with huge cluster size breaks when facing surfers. And using smaller cluster size is generally a rule-of-thumb of Anti-Surfer Guns.

Xor (talk)02:44, 5 October 2017

Agreed. And from the rumble score, it seems that the rumble thinks re-introducing the bug didn't actually change anything, which means that it might be something else. Melee wavesuffering is so much worse than 1v1...

Skilgannon (talk)07:51, 5 October 2017

That sounds strange ;/ Maybe some combination of bugs introduced the performance enhancing. Or the way handling other stuffs is the condition of triggering the enhancing... Experiencing the same thing that melee wave surfing is much much harder...

Xor (talk)09:04, 5 October 2017