Ah, i see where you're coming from. I need to explain however that that the analysis for change is necessary. You see, in order to actually have things be decently fast in OpenGL, i compile the contents of one 16x16 block into one display list, that can be called as one single line in perl and gets drawn directly from gfx card ram. Without those this would be pretty much impossible.

However the act of actually constructing those is pretty costly timewise. To give a comparison, the following is from one refresh cycle where ALL display lists (98 in this instance) get generated:
the code took: 0.467388 wallclock secs ( 0.47 usr +  0.06 sys =  0.53 CPU)
And this one is from when NO display lists are generated:
the code took: 0.025486 wallclock secs ( 0.03 usr +  0.00 sys =  0.03 CPU)
As such, making the assignments would shave time off of an "idle refresh", but greatly increase the general costs by increasing the number of "rebuild refreshes".

The increases i'm looking for right now are necessary to ensure the ability to refresh at a constant rate while no game changes are occuring, without having any skipping in the operation. This goal is pretty much reached, as i can now fix the FPS at 30 and updates should fit inbetween frame generation.

In reply to Re^4: How to speed up a nested loop? by Xenofur
in thread How to speed up a nested loop? by Xenofur

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.