forums.ps2dev.org

The PC version of Lua Player is not up to date yet. You'll need to modify some in your code before attempting to run it on your PSP.

I am hoping someone would be able to update the PC version soon.

Hi, folks! New release of LuaTut v0.3 is now available at LuaForge. It covers the first 5 chapters of OpenGL Programming Guide, 2nd Ed (known as Redbook). Download the book at www.gamedev.net/download/redbook.pdf if you don't have one. Next release will cover the next 5 chapters of the book. Enjoy. ...

table.foreach() function is now deprecated. Use for i,v in ipairs(t) do ..., instead. See Lua 5.1 ref manual. function CopyTable(old) local new = {} -- for i, item in ipairs(old) do table.insert(new, item) end for i, item in ipairs&am...

From the other thread, If you experiment with 3D, you could first start with coding OpenGL on PC, then move from there to PSPGL on PSP, and then move from there to sceGu (native gu calls) on PSP. I have developed OpenGL bindings to Lua for PC. The project is called LuaScene and now available at LuaF...

Sorry, dude. I tried to help. Perhaps, you could implement Windows version for Lua 5.1 with some additional features as needed in order to debug your thingy. You could get the source at lua.org. I know it is a nasty job to do. I do mine for Windows version but it is not for PSP. It is all written in...

Perhaps print() command writes somehting on the back buffer of the screen. If so, flip the screen to read the output. If no help, the screen should be turned off somehow in order to view the output on PSP. Of course, you can use Windows version to debug but the version is pretty old.

I don't know where print() should print but have you tried io.write("string\n")?

Some users might press either button first. Check each button if it is pressed or not. If so, check the other button as well.

I am sure somebody already did the coding somewhere. You might look up those codes.

youresam wrote:... a 480x272 image takes up exactly 1mb RAM.

Are you referring to the double buffer which occupies exactly 1 MB in the memory space, 4 bytes for the front and 4 for the back buffer?

That explains why the funny number of 272 for the height.

You need to do each in traditional expressions like BASIC or Pascal, that's, for instance:

a += b -> a = a + b
.

Aren't they all compressed before loading?

When loaded unto the memory, each image is uncompressed, that's, pixel by pixel, correct?

A single 1000x1000 image loaded would eat up about 4MB of VRAM, would it?

The VRAM is only 32MB in PSP, I believe.

PS Is it VRAM or just RAM?

All global non-nil variables can be left untouched in the namespace. It has been advised to declare all variables as locals if possible since they can be garbage-collected sooner or later automatically.

All parameters in every Lua function are locals.

Sorry, dude!

BTW, nice looking, indeed. :)

daurnimator wrote:Ack, you beat me too it. I had my post done with color coding and everything :(

Why don't you just post your colorful reply, anyway? We all are curious to see yours.

arrow = Image.load("arrow.png") grass = Image.load("grass.png") screenwidth = 480 - arrow:width() screenheight = 272 - arrow:width() arrow = {} arrow[1] = {...

Both function syntax work the same but the latter makes more sense if it is used as a variable.

I see you did alright but...

The function 'enemies' should be moved above in order to declare it sooner than using it.

For the two dimensional array, you need to create a table within a table. Did you do that?

Try this:

No need to unassign anything in Lua. Use the same variable name for a new value of *any* type. Lua has a built-in garbage collector to take care of cleaning up inside.

Take a look at my code in LED Timer which comes with Lua Player distribution. This should give you some ideas how to use a timer.

Have fun!

What is wrong with System.sleep(ms)? It should do the job.

Use your scissors. ;)

Can't resist.

PS Sorry...

More at http://en.wikipedia.org/wiki/Frame_rate

I am still learning in spite of my age. Sigh...

Movie theaters run at 60 fps if I am not mistaken. It was because of the very large screen for audience who sit closer. Smaller screen or deeper perspective would not make any difference with a lower fps rate. Does it make sense?

Yeah, but PSPgl or PSPgu is much faster, even with fractional arguments.

We have a function for OpenGL. It is called glScale(size). It works in both 2D and 3D scenes. Size can be any number like 1.23 or 0.73. If we have implementation for Lua Player, it would be gl.Scale(size). Too bad, we don't have the implementation yet. Anyone dare to implement? PS: I am switching ol...

Try http://en.wikipedia.org/wiki/Cellular_automaton It has a good stuff to read. Warning: lot of discussions involved. Since Lua is an interpreting language, all interpreters are intented to preform in slow motion, pixel by pixel. Best bet is to code some of them in C/C++ where the bottleneck occurs...

yes and no yes -- a table can act like an array as long as indices are used. Eg, x[1] = 1234, etc. no -- a table can act like a dictionary, that's, it contains pairs of key and value. It would be more helpful if you read/study a book called "Programming in Lua". It can be found at www.lua....