47 replies to this topic

[kucalc]

From grayscales, to calc-to-calc gaming, now say hello to Revolution-FX v1.0. (Yeah, I did some number skipping... This might be the last version of Revolution-FX)

Download here: http://sourceforge.n...group_id=199425

Here's a rundown of the new features:
* Tired of lame and boring fonts? Revolution-FX introduces some new ones with the CoolText() function
* All those DrawSprite functions in previous versions of Revolution-FX have now been replaced with one single faster, more versatile and powerful drawing function that can handle many types of sprite sizes
* InvertArea() and ClearArea()
* Faster keyboard detection routines. Some keycodes overlap, but for gaming Revolution-FX's functions are fast for the purpose
* Some bug fixes

Some silly doodle:


Here's the code for the doodle to help you get started with the new Revolution-FX functions: http://revolution-fx...e.c?revision=66

If you have any questions on usage and syntax of the new functions, go ahead and ask.

[k3v]

Hey thats awesome, nice work kucalc.

Ill probably have to wait until my uni mid semester break before i do some programming, no time at the moment.

[kucalc]

Thanks. What would be nice, is to see some new programs with this.

Fez suggested this, I don't know whether to post it here or the other thread... Anyways I found this awesome team collaborative site and signed up for a space there. Here's the link: http://www.assembla..../show/casio_dev.

It's got a wiki, chat (with history and logging!), SVN, image uploading (could be useful for sprites and images for games) and scrum section where people report what they did.

Here's the repository: http://svn.assembla.com/svn/casio_dev. Maybe we could start out by collaborating together and work on a chess game or a 2D racer.

If anyone is interested in joining the team, PM me your email address so I can invite you. Practically anyone can join in: prog testers, artists, programmers, support, etc.

[Fez]

Cool Text FTW
XD
Good to see that this has been continued, even if it is a last release. XD

Also geat find with that assembla.

[PierrotLL]

It's interesting, I'll trie it.
But why do you close the sources?

[Andreas B]

The source code is also here: http://revolution-fx...olution-fx-1.0/

[PierrotLL]

Oh, sorry. Thank you Andreas.

[kucalc]

Well I added some new pages to the wiki at the CASIO Dev Team site. If you're a new team member, please get comfortable with the site (check out Flow, Scrum and Chat) and the SVN. I wrote some SVN tutorials for Windows users who are new to it.

As for Revolution-FX, yeah, the source code has always been available.

[djrose]

Great! We have confirmation. I've heard someone say they have problems running MLC fx-9860 on a Slim. But that shouldn't be a problem if you don't plan on using it.

Sorry if here is not the right area to put this, but not sure where else to go.

I've been experimenting more with the FX-9860 Slim, SDK and Revolution-Fx.

General SDK functionality still looks great ... But ...

Found a few things which may not be specific to the Slim (since I don't have any other [yet]), but I noticed that changing the speed using the Revolution-Fx library calls CPUSpeedXXXX occasionally cause the calculator to lock. Worst appeared to be going from Quadruple back to Normal where it seems to fail every time.

I have investigated, looked at datasheets etc and slightly modified the functions. They appear to work more reliably; i.e., I have not yet seen a lock-up with them.

Here is one of the modified functions to show the basics of the change:

void CPUSpeedQuadruple()
{
WDT.WTCSR.WRITE = 0xA500;
WDT.WTCNT.WRITE = 0x5A00;
CPG.FRQCR.WORD = 0x0303;
}

Writing to the CPG as one operation seems to be the part that improves the operation most.

[kucalc]

Thanks, I'll take a look into it.

[ECE]

Dear admin,

Could you please move the post by “djrose” to the thread “Slim and SDK”, this could help others in there search.

Thanks.

[kucalc]

But it kinda fits here the most.

[CoDEmanX]

i hope someone reads this... forum looks pretty dead.

just wrote my first add-in using FX Revolution 1.0 (it's phenomenal, thanks!)
everything looked fine in the emulator, but when i transfered the g1a to my CASIO fx-9860g (Firmware 1.05) and ran it, this showed up:

(output wrapes for some reason)


it was supposed to look like this:


please, can you tell me why?

//edit:
never mind, i had to replace SDK_VRAM by VRAM - ouch xD

is the FX Revo lib still in development to add more nice features? and what about tutorials / a documentation? all i found was a v0.3 doc incl. 3 tutorials.

a few ideas:
+ utility functions like DrawBox (4 DrawLine calls)
+ DrawRect (filled, not just outlined like DrawBox)
+ optional arg for DrawBox and DrawRect to round the borders
+ DrawEllipse using an algorithm similar to the one for DrawLine?
+ a set of functions to add F1-F6 "buttons" (like "JUMP", "DEL", ">MAT" etc. in stock RUN MAT app, 2 styles)
+ framework for calc-to-calc games (using serial port)

not really something to add to RevoFX, but i saw a hex editor add-in with the ability to change the data in memory. any chance to replace the CASIO logo shutdown image?

Edited by CoDEmanX, 19 January 2009 - 01:05 AM.

[kucalc]

Revolution-FX is still in development. I will take your requests into consideration. If you think you could make some contributions (whether it be coding or writing up tutorials) you can join the team.

As for replacing the shutdown image, it's possible. If I remember correctly, the shutdown image appears in two places in the firmware (I have the locations written down somewhere...) The firmware could be modified so that the checksum at the end (the very end) of the firmware matches and can be easily downloaded back into the calculator using CASIO's own software. I'll take a look into it.

[CoDEmanX]

i'll try to do certain things and after that, i may write a tutorial and some code lines. but first off, i need to recharge my batteries
The "DEVO"-Greyscale demo was the culprit... btw: 5000 is an interesting timer value

i'm relieved that RevoFX is still under development. but what happened to the RevoFX Code-Editor?

thanks for the research on the logo!

[tuxianer]

Hi,
it's nice to see, that yoz have add a input function, like I have tried it some time before (http://www.casiocalc...wtopic=3807&hl=).

Very good work!

Edited by tuxianer, 18 March 2009 - 08:04 PM.

[Kelli]

Heh, I thought v.0.3 was the final version and I have been using it all the time.
Found this 1.0 version today and tested it couple of hours. It's awesome.


If this masterpiece is really still in development I have a few suggestions that could make it even better:

- Inverted transparency when drawing a sprite. See figure 1.
- Transparency maps. See figure 2.
- GetPixel(); that works at different sized buffers. Current command works only 1024byte buffer. (128x64)

[Kelli]

It looks like Revolution FX 1.0 command FastKeyDown(); is a little messed up. I investigated it a little and made my own keycode chart.

It seems you can't separate the top two key rows from each other. If you press for example F1 it triggers keycodes from 0x60 to 0x69 so if you use let's say number 4 in your app/game you have to add something that makes it separate from F1 and Shift. Like if(FastKeyDown(0x63)==1 && FastKeyDown(0x60)==0)



Hope this helps someone, it sure helped myself

[alias4399]

Wow Kelli... I havent authored my own programs in Rev-FX yet... though Im sure your hint about FastKeyDown() will come in handy. That pic took a fair bit of work, too Thank you!

PS No way at all to differentiate between top 2 rows with FastKeyDown() ? I see they have the same keycodes.. :S

[Paul94]

Hi!

I want to build an background-image for my AddIn. I generatet two buffers (4 colors) with SpriteStudio. My Question is how to draw the buffers to the screen.

I build the following code, but it doesn`t work:

// decleration of the buffers and the variable key
 
 GrayLinkBuffers(&buffer_1, &buffer_2);
   GrayInit(3661, 3661);	
   
   DrawSprite(1, 1, 128, 64, 16, buffer_1, VRAM, NO_TRANS);
   DrawSprite(1, 1, 128, 64, 16, buffer_2, VRAM, NO_TRANS);
   
   while (1) {
		 GetKey(&key);
   }

Paul

[kucalc]

Hello Paul94 and welcome to the UCF!

You can't use GetKey with Revolution-FX. Messes up with the interrupts. Use IsKeyDown() instead.

[Paul94]

Hi!

i deleted GetKey, but it still doesent work. Now I see many pixels, but not the picture...

I have the following code (this time complete):

//Declaration of the buffers
   
	   GrayLinkBuffers(&different_world_1, &different_world_2);
	   GrayInit(3661, 3661);	
   
	   DrawSprite(1, 1, 128, 64, 16, different_world_1, SDK_VRAM, NO_TRANS);
	   DrawSprite(1, 1, 128, 64, 16, different_world_2, SDK_VRAM, NO_TRANS);
   
	   while (!IsKeyDown(KEY_CTRL_MENU)) {
	   }
   
	   Reset_Calc();
	   return 1;
   }
   
   
   
   //****************************************************************************
   //**************											  ****************
   //**************				 Notice!					  ****************
   //**************											  ****************
   //**************  Please do not change the following source.  ****************
   //**************											  ****************
   //****************************************************************************
   
   
   #pragma section _BR_Size
   unsigned long BR_Size;
   #pragma section
   
   
   #pragma section _TOP
   
   //****************************************************************************
   //  InitializeSystem
   //
   //  param   :   isAppli   : 1 = Application / 0 = eActivity
   //			  OptionNum : Option Number (only eActivity)
   //
   //  retval  :   1 = No error / 0 = Error
   //
   //****************************************************************************
   int InitializeSystem(int isAppli, unsigned short OptionNum)
   {
	   return INIT_ADDIN_APPLICATION(isAppli, OptionNum);
   }
   
   #pragma section

It would be nice if you can help me finding my mistake.

But there is another problem:
After using MENU i get into the Main-menu but I can`t do anything. To continue I have to press the P-Button.

Paul

[kucalc]

Remove these two lines:

DrawSprite(1, 1, 128, 64, 16, different_world_1, SDK_VRAM, NO_TRANS);
DrawSprite(1, 1, 128, 64, 16, different_world_2, SDK_VRAM, NO_TRANS);

GrayLinkBuffers will draw different_world and different_world_2 for you.

And try using this to exit:

while (IsKeyDown(KEY_CTRL_EXIT) != 1) {
}

Reset_Calc();

[Paul94]

hi!

I removed the two DrawSprite-functions, but the image still isn`t correct. I can see one buffer, the other one seems to be at another position (only a few pixels).

The problem with the Main-Menu is now ok.

Paul

[kucalc]

Did you modify or shift the buffers? It seems like that's the problem since what you're describing sounds like it got shifted.

[Paul94]

I used the original SpriteStudio Code and used GrayLinkBuffers to display it.

Here is the complete code.

Paul

[kucalc]

I haven't tried running your code, but how did you draw the picture? (Black, white, light gray, dark gray) or 3 (black, white, gray)? Because the way GrayInit it set up in your code, it only has one shade of gray (3 color system).

[tuxianer]

Hi,
is there a referenc of all Rev-FX commands?

[kucalc]

Yes here: http://revolution-fx.../documents.html, but it's not up to date.

[kucalc]

Nope, there's nothing wrong with your code. The fx-9860G SDK emulator cannot do grayscales because it doesn't exactly simulate the fx-9860G perfectly. You'll just have to test your code by running it on your calc.

[kucalc]

No, because as I said before, it doesn't simulate the fx-9860G exactly.

[AlShikan]

does anyone know how the Serial_Transmit/Serial_Receive commands work? i always get an system error. on the official page of revolution-fx are only instructions for version 0.3 of revolution-fx... any help?

thanks

[Casimo]

You should try the system calls Serial_open, Serial_raedByte and Serial_write. They're explained.

[AlShikan]

can u post a link where? searched for about an hour and couldnt find anything... seems im blind ;D

ty anyways

Edited by AlShikan, 22 January 2013 - 07:02 PM.

[Casimo]

Look at Casiopeia.

Edited by Casimo, 23 January 2013 - 09:44 AM.