Helbreath In 800x600

[marleythe9]

well it depens

it wouldnt lag you if u have broadban internet.

128kbs internet you may see more lag.

anything under thats dial up.

sooooo.. it realy depens on your players.

i would just make an option of useing an 800by 600 or 640 by 480.

[Dax]

well it depens

it wouldnt lag you if u have broadban internet.

128kbs internet you may see more lag.

anything under thats dial up.

sooooo.. it realy depens on your players.

i would just make an option of useing an 800by 600 or 640 by 480.

Rofl? I thought you were smart...

[bone-you]

well it depens

it wouldnt lag you if u have broadban internet.

128kbs internet you may see more lag.

anything under thats dial up.

sooooo.. it realy depens on your players.

i would just make an option of useing an 800by 600 or 640 by 480.

Rofl? I thought you were smart...

That's what I thought when I read that.

Let me pull my 166mhz pentium out and run it off 16gbps. Yea, my comp won't lag. >.> so many people think internet speed defines your computer lag.

[marleythe9]

becouse anything under 400mhz is an old computer..

and probley dosnt work...

if u have a 166mhz you need to upgrade now!.


average person with a computer mostlikly will not be useing a 166mhz computer.

thats like a 10 -15 year on comp.

[Orkl]

becouse anything under 400mhz is an old computer..

and probley dosnt work...

if u have a 166mhz you need to upgrade now!.


average person with a computer mostlikly will not be useing a 166mhz computer.

thats like a 10 -15 year on comp.

I dont like to be mean.. but...

<span style='font-size:14pt;line-height:100%'>You my friend, are a FUCKING RETARD</span>

Your internet speed has nothing to do with your FPS, learn something about comps before posting you fucking moron.

[Orkl]

One thing that you could do to speed up performance is to use Triple Buffering.

You must understand how flipping works.

First off you must understand what happens when the backbuffer is flipped. Normally you're application is double buffered (only windowed mode can be single). Double buffering means that there are 2 surfaces. The primary, and backb uffer. Every time you flip, DDraw swaps their memory around, the backbuffer appears on the primary, and the primary appears on the backbuffer, got it?

Think of it like this:

Stage 1: A B
Stage 2: B A
Stage 3: A B

Think of (A) and (B] being two images; where A is blank, and B is a picture. In stage 1, primary buffer is A, and backbuffer is drawn to (therefore having an image in it ). Stage 2 shows the image on the backbuffer flipped onto the primary buffer, and we would now be seeing (B], and at the same time, the backbuffer would now be empty (A). Stage 3 is just the same again, this time the primary has what was just on backbuffer (stage 2) and the backbuffer has what was just on the screen.

So basically whilst the backbuffer is being flipped, you're program is busy. Basically idle, the messages have been sent to DirectDraw, and whilst it is rendering, your application is doing fuck all.

So rather than leaving the program to sit there and scratch its imaginary balls it'd be best to have it, so that when the current frame is flipping, you are already drawing the next frame. So when flipping is complete, you can just flip again immediately. Got it so far?

This method of rendering is called *drumroll* TRIPLE BUFFERING! *yay*

You may be stupid enough to think that if three buffers are faster than two, four buffers would be better again! Not true. Using more than 3 will -SLOW YOUR SHIT DOWN-. This is because of memory limitations, in a 640x480 program one buffer takes up about 350kb of memory. 2 buffers, about 700kb. 3 buffers, about 1050kb. The more memory you use, the slower shit gets.

So whilst you have 2 backbuffers working, things are obviously a lot faster, and your flipping chain ends up being like so.

Stage 1: A B C
Stage 2: B C A
Stage 3: C A B
and so on.

Now that you -should- understand triple buffering, i'll give you the secret on how to implement it.

You literally have to change 1 value in the code. You'll be amazed *drumroll*

IN:: DXC_DDraw.cpp

FIND::

Code: Select all

BOOL DXC_ddraw::bInit(HWND hWnd)

EDIT::

Code: Select all

ddsd.dwBackBufferCount = 1;

TO::

Code: Select all

ddsd.dwBackBufferCount = 2;

You're done, triple buffering..

In theory this should on average give you a significant FPS increase. But then, its all down to clean code at the end of the day at how fast something runs. But triple buffering is obviously faster than double.


If you dont feel like doing this, then do what marleythe9 suggests. Go pay more money for a faster internet connection. That will really speed your FPS up. :rolleyes::rolleyes:

PS: marleythe9 you're a fucking moron

[bone-you]

hahaha. For those who don't want to read Orkl's essay, triple buffering just makes the render thread work when it would otherwise be idle waiting for game logic to catch up (generally on multithreaded apps).

Don't see how it would make much of a difference on HB though.

[Orkl]

triple buffering has nothing to do with multithreaded apps.

Helbreath is NOT multithreaded.

[bone-you]

triple buffering has nothing to do with multithreaded apps.

Helbreath is NOT multithreaded.

Do tell me then, how does it write the back (2nd) buffer just by changing one value if there is only code to write a single back buffer? On top of that, how is there time to write to the 2nd back buffer if there is only one thread and that single thread only has to catch up with itself? Buffering is only good when there is something to write to the buffer and a single thread can only write one at a time.

Even if it writes ABC writing A, then B, then C, it's still only keeping up with itself.

Even if it somehow managed to be on C while displaying A, point being? A single thread would then display A, do everything it had to while writing the buffer, then display B. The code is only setup to write to the back buffer once then render. DrawSprite does all of that, then it flips it. You'd have to add deeper code to have it effectively use a 2nd buffer and even then, in HB it will be just about useless.

[Orkl]

Incorrect, DirectX automatically writes to the neccessary buffer. The functions that are used to write to the buffers do not matter, whilst there is more than 1 buffer, DirectDraw will keep writing while a buffer is free regardless. Multithreading isn't needed to write to more than 1 buffer at a time. DirectDraw is capable of writing to multiple buffers as long as their free.

Try it out. Make a simple tile engine, and display a 100x100 map. Use double buffering and check your FPS. Triple buffer it, and then try again, see your FPS increase.

[bone-you]

I got it I got it xD ignore my posts

[ADDKiD]

Wow. I learnt something!

[Drazz]

Wow. I learnt something!

me too!

[ADDKiD]

Wow. I learnt something! 

me too!

Grats to Juggalo2 on his 1000th post . Yeah Drazz, it's amazing you can actually still learn something here in Outpost.

[bone-you]

Wow. I learnt something! 

me too!

Grats to Juggalo2 on his 1000th post . Yeah Drazz, it's amazing you can actually still learn something here in Outpost.

It's amazing you can learn anything at all.