Comments on: getting ill? and working hard … http://www.bluthaupt.com/2006/09/21/getting-ill-and-working-hard/ running with scissors Sun, 01 Aug 2010 04:43:55 +0000 http://wordpress.org/?v=2.0.4 by: CAMERON http://www.bluthaupt.com/2006/09/21/getting-ill-and-working-hard/#comment-7691 Thu, 24 Jun 2010 13:18:02 +0000 http://www.bluthaupt.com/2006/09/21/getting-ill-and-working-hard/#comment-7691 <strong>Medicamentspot.com International Legal RX Medications. Special Internet Prices (up to 40% off average US price). NO PRIOR PRESCRIPTION REQUIRED!...</strong> <a href="http://medicamentspot.com/products/antiviral/combivir/order/ Combivir@buy.online" rel="nofollow">.</a>... Medicamentspot.com International Legal RX Medications. Special Internet Prices (up to 40% off average US price). NO PRIOR PRESCRIPTION REQUIRED!…

Combivir@buy.online" rel="nofollow">.…

]]> by: Titel auteur datum xanax medication bmnwbbuk. http://www.bluthaupt.com/2006/09/21/getting-ill-and-working-hard/#comment-4703 Mon, 01 Sep 2008 20:42:56 +0000 http://www.bluthaupt.com/2006/09/21/getting-ill-and-working-hard/#comment-4703 <strong>Xanax addiction....</strong> Order xanax online. Xanax. Titel auteur datum xanax medication bmnwbbuk.... Xanax addiction….

Order xanax online. Xanax. Titel auteur datum xanax medication bmnwbbuk….

]]> by: Xanax addiction. http://www.bluthaupt.com/2006/09/21/getting-ill-and-working-hard/#comment-4686 Fri, 29 Aug 2008 22:19:57 +0000 http://www.bluthaupt.com/2006/09/21/getting-ill-and-working-hard/#comment-4686 <strong>Generic xanax 2 mg no prescription....</strong> Xanax bars. Xanax 2 mg 180 pills. Xanax. Xanax online.... Generic xanax 2 mg no prescription….

Xanax bars. Xanax 2 mg 180 pills. Xanax. Xanax online….

]]> by: stefs http://www.bluthaupt.com/2006/09/21/getting-ill-and-working-hard/#comment-3 Tue, 03 Oct 2006 00:34:07 +0000 http://www.bluthaupt.com/2006/09/21/getting-ill-and-working-hard/#comment-3 ~ how i would have done it ~ assumed facts: 1. the textures are needed as soon as the player character (pc) "sees" them, meaning needing them to be rendered and this pre-rendered, as rendering on the fly is undesireable. currently needed are all the tiles that can be problably seen, lying circulary around the player, as pc turning time is close to instant. 2. you know, how far (how many tiles) the player can see. 3. you know how fast the player can move (i assume, turning takes no time, and the mode is first person). 4. you precompute the actual time needed for rendering every tile on a developement machine and store the results as factors. then you know the exact case relativley to the users computer speed, thus aproximatley in absolute terms after benchmarking the users computer (e.g. with the simplest tile). so you need to pre-render all the tiles in viewing distance from your character, when hes not moving. but of course if he moves, you'd need to instantly pre-render tiles. so you need to pre-render all the tiles in viewing distance PLUS a certain amount of tiles even further away. this "certain amount" can be computed, as you know pc moving speed, the pre-rendering cost and the prerendering capability of the users pc. so, if the player moves, you've got a time buffer for prerendering the next tiles. teleports from and to specific destinations can be included too, teleports from random to specific destinations need more cache/precomputing, altought teleports to random destinations are uncachable with this method alone. or is there anything i didn't get? ps: now that i look at it, it is even simpler. 1200mb of hard disc cache shouldn't be a problem nowadays. so pre-render a circular shape (viewing plus x% security based on benchmarks) around your character before entering the world, and then use the spare, unused processor time to render the rest, sorted by distance from your player character. ~ how i would have done it ~

assumed facts:

1. the textures are needed as soon as the player character (pc) “sees” them, meaning needing them to be rendered and this pre-rendered, as rendering on the fly is undesireable. currently needed are all the tiles that can be problably seen, lying circulary around the player, as pc turning time is close to instant.

2. you know, how far (how many tiles) the player can see.

3. you know how fast the player can move (i assume, turning takes no time, and the mode is first person).

4. you precompute the actual time needed for rendering every tile on a developement machine and store the results as factors. then you know the exact case relativley to the users computer speed, thus aproximatley in absolute terms after benchmarking the users computer (e.g. with the simplest tile).

so you need to pre-render all the tiles in viewing distance from your character, when hes not moving. but of course if he moves, you’d need to instantly pre-render tiles. so you need to pre-render all the tiles in viewing distance PLUS a certain amount of tiles even further away. this “certain amount” can be computed, as you know pc moving speed, the pre-rendering cost and the prerendering capability of the users pc. so, if the player moves, you’ve got a time buffer for prerendering the next tiles.

teleports from and to specific destinations can be included too, teleports from random to specific destinations need more cache/precomputing, altought teleports to random destinations are uncachable with this method alone.

or is there anything i didn’t get?

ps: now that i look at it, it is even simpler. 1200mb of hard disc cache shouldn’t be a problem nowadays. so pre-render a circular shape (viewing plus x% security based on benchmarks) around your character before entering the world, and then use the spare, unused processor time to render the rest, sorted by distance from your player character.

]]>