The glitching around thing might be a performance issue.
[editline].[/editline]
Can you tell me which sound is looping? Is it always the same?
Like, if it's only the touch-ground sound, it may actually be my fault.
I let my mom try it since she's a tetris fan, and she rage quit :v:
One comment: Can you give a second or two delay after one block touches another for the next block to spawn? It's annoying to try to place a block precicely only to find I lose control of it immediately after making the slightest bit of contact with another block.
[QUOTE=Itszutak;23554838]One comment: Can you give a second or two delay after one block touches another for the next block to spawn? It's annoying to try to place a block precicely only to find I lose control of it immediately after making the slightest bit of contact with another block.[/QUOTE]
I actually had it so you could touch other blocks if you still had a certain vertical speed, but it didn't work for some.
[QUOTE=Upgrade123;23553434]Pieces are still glitching around and getting stuck inside shit. Also, sound bug's still there.[/QUOTE]
This happens mostly when performance is too low, the general solution is a 'dt cap', like this:
[code]
function love.update(dt)
local dt2 = dt
local dt3
repeat
dt3 = math.min(dt2, 0.1)
world:update(dt3)
dt2 = dt2 - dt3
until dt2 <= 0
--your other code
end
[/code]
Though you can probably write a cleaner version. (btw, the 0.1 here is a guess, but one that seems to work in most cases)
Function parameters can be reassigned like any local variable or upvalue:
[lua]function love.update(dt)
repeat
local cap = math.min(dt, 0.1)
world:update(cap)
dt = dt - cap
until dt <= 0
end[/lua]
[QUOTE=jA_cOp;23559939]Function parameters can be reassigned like any local variable or upvalue:
[lua]function love.update(dt)
repeat
local cap = math.min(dt, 0.1)
world:update(cap)
dt = dt - cap
until dt <= 0
end[/lua][/QUOTE]
I know, of course I do, but you most likely want to use the dt value for other things as well.
Played a couple of games and then my whole computer crashed, the screen had a blue glow over everything and I had to restart my computer twice before everything was gone :(
[QUOTE=quincy18;23563509]Played a couple of games and then my whole computer crashed, the screen had a blue glow over everything and I had to restart my computer twice before everything was gone :([/QUOTE]
Uh.. I really doubt that was the game's fault.
Sounds more like overheating or something.
Yea lol, my video card broke down today :(
[IMG]http://i25.tinypic.com/df82mp.jpg[/IMG]
Well fuck... I had the best pieces, but not the skills to guide them...
I am pleased to announce that this game works on steam, and fully supports the in-game browser and chat. Not sure what use it is, but it's still neat.
Hey, I am new here, I only got here because I saw this on TheAwesomer.com. Imagine my surprise when I saw that the game was created with Löve. I just had to register. Also, I saw this post...
[QUOTE=DeadBarney;23516609]This is kinda strange...
It worked on my other computer, but there, i only get a white screen (but the music works perfectly).
If i press enter twice, to start a game, i can see this:
[img]http://img829.imageshack.us/img829/6632/scrsht.jpg[/img]
Only some sprite are showing.
Btw, i'm on XP sp2, with a good computer, and a working graphic card.[/QUOTE]
I know why this is happening. Maurice, I need to talk to you. You forgot to use Power of 2 image sizes. Some video cards can only work with images that have a power of 2 size. The only two images in your whole project that are power of 2 is the bar and the square. None of the rest are power of 2. You should really use Quads and put all the images in one big image with the image size being a power of 2. Any non power of 2 images will show up as white, like the screenshot above. Out of all the computers I have, only one (A G4 Mac mini) has problems with non power of 2 images. So it's really one of those problems you can't predict.
Power of 2 means the image width or height is power of 2, meaning 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, and so on. Where each subsequent number is the previous number times 2.
Maurice, you should come to the [url=http://love2d.org/forums/index.php]Löve forums[/url] and we'll help you figure out how to make the project work on computers with video cards that require power of 2.
[QUOTE=Jasoco;23581845]*bunch of stuff*[/QUOTE]
Goddamn you're probably one of the most helpful new-joiners ever
[QUOTE=Jasoco;23581845]Text[/QUOTE]
He already fixed it a few days ago: [url]http://www.facepunch.com/showpost.php?p=23525235&postcount=96[/url]
I'm not entirely sure what happened, but I was up to about 30 pieces, all nicely stacked and such when suddenly the game froze, the music stopped, and the next thing I knew everything was bouncing around so fast the game logic couldn't keep up
then it crashed. I wish I could have taken a screenshot, it was absolutely spectacular.
[QUOTE=Jasoco;23581845]Stuff I already told him[/QUOTE]
I think I was a little faster Jasoco, read up to my first post.
Congrats, your game got blogged on a somewhat big Dutch blog :)
[url]http://www.flabber.nl/linkdump/game/not-tetris-5703[/url]
Uuugh, I'm so used to Tetris being so perfect and symmetrical, you're a bastard for making it so clunky :C
Great update, the sound isn't buggy anymore for me.
Keep the good work !
Even though the game is simple and the time to play is limited by how many pieces you can fit in the screen, the game is addicting as fuck and is super fun.
Glad you like it.
Version 1.8 is out!
There's now a sexy highscore board.
You can reset the highscores by pressing "backspace" in the music menu. (the one shown below)
[img]http://filesmelt.com/dl/scores.png[/img]No you can't select "NORMAL".
Also uses the Not Tetris 2 code, which won't change anything but might cause some bugs. (It's because I wrote this into NT2, and this is basically a version without gameA)
Didn't have the sound problem til version 1.8 :(
Oh shit you're right I forgot that do what I did in 1.7 to "fix" it.
[editline].[/editline]
Oh shit I forgot what I did to fix the sound bug.
[editline].[/editline]
Nevermind (I just reload all sounds)
I'm now also including what bartbes wrote earlier, which is supposed to fix the stuttering some people have.
[editline].[/editline]
Okay uploading 1.9..(what am I gonna call the next version..?) Done!
Why, 1.A of course.
1.9.1?
It goes 1.10
So uh, is 1.9 working for everyone?
I'm always scared that it doesn't work for people and they just don't report it.
[QUOTE=ZeekyHBomb;23612480]Why, 1.A of course.[/QUOTE]
Definitely. Then 1.B, and so forth till he gets to 1.F and then 2.0. Hurray! Hexadecimal versioning!
Sorry, you need to Log In to post a reply to this thread.
