11 replies to this topic

[k3v]

Latest rev-fx is great!

Now how do i clear and update buffers continuously without getting extra flicker?

My current setup is this, and it creates tons of extra flicker as each loop it draws the cleared screen... rather then clear it behind the scenes
[not actual code, just the general idea]

int AddIn_main(int isAppli, unsigned short OptionNum)
{

GrayInit(3270, 3270); 
GrayLinkBuffers(buffer1, buffer2);

while(1){		  //main loop

memset(buffer1, 0, 1024);
memset(buffer2, 0, 1024); //clear each buffer

DrawSprites(); //Draw what i want etc.

} //repeat!

return 1;

}

[kucalc]

To overcome flickering, you should use the double buffer technique. If you've looked at the source code for MLC fx-9860, it employs this technique to overcome flickering. The idea is to first draw your sprites onto separate buffers, then when finished, copy them to the screen.

[k3v]

Lol cmon help us out a bit more, haha i dont know were i can find the source to MLC-fx-9860 either...

[Andreas B]

You should search or ask what exactly kucalc meant with:

The idea is to first draw your sprites onto separate buffers, then when finished, copy them to the screen.

http://www.google.co...ouble buffering

[kucalc]

Lol cmon help us out a bit more, haha i dont know were i can find the source to MLC-fx-9860 either...

Lol, I don't know how to describe it in more detail. If you read what I posted, you could get the idea:

The idea is to first draw your sprites onto separate buffers, then when finished, copy them to the screen.

Now, that we got the idea let's implement it into some code.

unsigned char deck_buffer1[1024];

unsigned char deck_buffer2[1024];	  // We draw to these buffers



unsigned char screen_buffer1[1024];

unsigned char screen_buffer2[1024];   // These buffers are for the screen



GrayLinkBuffers(screen_buffer1, screen_buffer2);

GrayInit(3280, 3280);



while (1) {

	memset(deck_buffer1, 0, 1024);

	memset(deck_buffer2, 0, 1024);	// Only clear the deck buffers



	DrawSprites...();   // Draw only to deck_buffer1 and deck_buffer2

	

	// After finishing drawing to the deck buffers copy them to the screen buffers

	memcpy(screen_buffer1, deck_buffer1, 1024);

	memcpy(screen_buffer2, deck_buffer2, 1024);

}

[k3v]

lol i tried, i tried! But found nothing that could help me. The way i understood what you said kucalc sounded like what i was allready doing haha so i was like wtf?!?!?, i didnt think about two pairs of buffers. But thanks now i understand, i wasnt familiar with that buffer copying command either.

It reminds me of when i first asked about buffers, i completely missed the boat on that one haha... :roll:

EDIT: Ergh, with the four buffers now im getting a complile error:

The size of B and R section should be 0x2000 bytes or less.
Please refer to "C:Program FilesCASIOfx-9860G SDKk3v's gamesDD2 GreyscaleDebugFXADDINror.map".

Build was not successful.

How can i fix this?

[kucalc]

EDIT: Ergh, with the four buffers now im getting a complile error:

The size of B and R section should be 0x2000 bytes or less.
Please refer to "C:Program FilesCASIOfx-9860G SDKk3v's gamesDD2 GreyscaleDebugFXADDINror.map".

Build was not successful.

How can i fix this?

You need to trim down on how much working memory your using. The fx-9860 only allows you to use 8KB of working memory. Four buffers already consume 4KB (half of the working memory). My suggestion is to look over your code and try to replace as many large datatypes (like int - 4 bytes) with something smaller (like char - 1 byte) if possible or look for stuff you don't need that can be removed.

[k3v]

lol ok, will do.

Sorry for all the bitching/questions haha, its great your there for help though! Appreciated!

[kucalc]

lol ok, will do.

So, did you do it? We're you able to minimize the amount of memory you were using?

Sorry for all the bitching/questions haha, its great your there for help though! Appreciated!

No problem.

[k3v]

Yep i was, its all fine (for the moment )

[kucalc]

Yep i was, its all fine (for the moment )

Cool. If it's not too much to ask for since we did kind of help you out, could you perhaps put in some credit to the UCPF and Revolution-FX, maybe perhaps like a start up screen announcing the UCPF/Revolution-FX. Any amount of attention for the UCPF would be great.

[k3v]

Haha, well i was definately going to put some sort of thanks to your work kucalc since it wouldnt be possible without it. Sure.. why not

Offtopic: Are you entering the planet-casio competition? Im in a mad rush to try finish mine..