forums.ps2dev.org

you could write a lua obfuscator...

"just add a little checkboxes here and there, so i can controll all those things"

ouch..

there's no way to do real transparency yet, unless you write your own blending routine, which would be very slow... Shine posted a demo how to access pspGL from Lua some time ago, maybe you want to take a look... that demo was for an experimental build of luaplayer. you can't do that with regular l...

sounds like you're going about things in the wrong way..

just make a loop that only checks for the buttons you want.

you can't concatenate variable names. something like this should work: cardImage = {} cardImage["2d"] = Image.load("cardspng/2d.png") cardImage["3d"] = Image.load("cardspng/3d.png") cardImage["4d"] = Image.load("cardspng/4d.png") cardImage[...

there's no way to do real transparency yet, unless you write your own blending routine, which would be very slow...

maximum texture/image size is 512x512, afaik.

60fps most of the time.. i've done a lot of optimizing.. things start to drop below that if i'm drawing more than about 80 16x16 tiles per refresh. You can blit the tiles to an offscreen image first, which is created on level start and then blit this to screen on every vsync (or multiple offscreen ...

60fps most of the time.. i've done a lot of optimizing..

things start to drop below that if i'm drawing more than about 80 16x16 tiles per refresh.

both are possible. currently i use the dofile method to load my levels.. i also have a level editor that uses the io library to create .lua files on the fly.. unfortunately, the documentation kind of sucks. http://www.lua.org/manual/5.0/manual.html#5.6 i suggest checking out the source code for one ...

thanks, that works.. but you're right, it's very slow :\

"Color image:pixel(x, y) --get" how can i manipulate the data from this object? for example, if i want to know what is the red value of the pixel at 3,9 on a image.. how do i find out? basically, i'm trying to create a fade function to fade parts of the screen, but i don't know any way to ...

a clever hacker would just modify the game to send a fake checksum ;) The checksum could be calculated by Lua Player and if it is MD5, the clever hacker has no chance to fake it. all you need to know is the correct checksum to send, no matter what hashing algorithm you use. capture the correct chec...

glad i could help.

You don't need encrypted luas, you only need a clever network protocol. (like checksumming the script file and refusing to start a multiplayer game if the checksum for the two games don't match) a clever hacker would just modify the game to send a fake checksum ;) ps: yes, i can not wait for intern...

if i had to make a guess, i'd say it was timezone related..

nice one. i made a lightsout clone in visual basic 1.0 (yes, this really existed) back in the windows 3.1 days... :)

-- a function to toggle usb mode function toggleUSB() if usb==0 then System.usbDiskModeActivate() screen:blit(1, 3, usba) usb = 1 else System.usbDiskModeDeactivate() usb = 0 end end -- the rest of this should be in your main lo...

Shine wrote:

chaos wrote:i'm not sure .tt is a valid tld..

It is a valid tld: http://nic.tt/ Trinidad and Tobago are some islands in the southern Caribbean Sea.

it seems you're right. i still can't access his site, though. :\

could you give us a list of what's going to change? i've currently got a couple thousand lines of code invested in a game i'm making, so i'm very interested in what's going to happen with the new version.

i'm not sure .tt is a valid tld..

well, maybe in a year from now, when luaplayer has taken advantage of all the nice things the psp has to offer.. sending it out as-is would be a wasted opportunity, imho.

Agoln wrote:LUA problems should be in the LUA forum...

Moved.

gotta love the moderation around here ;)

looks good

greetings fellow paint shop pro user ;)

wow, too bad qbasic doesn't run.. it could be the most powerful programming tool ever unleashed for psp ;)

so far i've used math and table without any problems.

very nice idea..

ok, the results are in. i rewrote my code, and the bug is gone. here's the code. i use it to move a 16x16 cursor around the screen in 16 pixel steps. i've left out the code for button presses, because it's handled the same way as movement, and the extra code would be redundant. the code has support ...

nevyn wrote:Chaos: Sounds to me like a bug in your code. Working /around/ the bug by disabling its sideeffects is a bad way of solving it :P

it does sound like a bug.. i'm rewritting all my control routines to make sure. i'll post the results when i'm done.