Feedback thread

[GoogleCodeExporter]

What steps will reproduce the problem?
1. start program
2.
3.

What is the expected output? What do you see instead?
settings/help menus dont work

What version of the product are you using? On what operating system?
only android

Please provide any additional information below.
there is no way to add fof files at this point

Original issue reported on code.google.com by zaliman...@gmail.com on 30 Aug 2009 at 6:41

[GoogleCodeExporter]

Hi!

Yes, in this version settings/help do not work. I'm working on it right now.

As for fof files, this is strange, it should work, just put files to
/sdcard/TapsOfFire/songs.

Original comment by Dmitry.S...@gmail.com on 30 Aug 2009 at 9:16

[GoogleCodeExporter]

If it does not work, please post here or email me a link to FOF your song(s).

Original comment by Dmitry.S...@gmail.com on 30 Aug 2009 at 9:32

[GoogleCodeExporter]

well tried out a song and it works, but now the only problem that remains is 
songs 
that would require multi touch

Original comment by zaliman...@gmail.com on 31 Aug 2009 at 12:51

[GoogleCodeExporter]

If the creator would get ahold of a multitouch rom(any rom nowadays) that's 
rooted,he may be able to 
add multitouch.....

Original comment by all...@gmail.com on 31 Aug 2009 at 11:45

[GoogleCodeExporter]

I have an issue where 2 of my songs aren't being found. Here they are:
http://www.4shared.com/file/129988708/cd7c5aac/FOFSongs.html

Original comment by JDuverge...@gmail.com on 3 Sep 2009 at 8:48

[GoogleCodeExporter]

Yey, multitouch would make this a dream!

Original comment by I.Punish...@gmail.com on 4 Sep 2009 at 11:13

[GoogleCodeExporter]

JDuverge1020, thanks for the bug and the files! Unfortunately they revealed some
problems, which I can't fix fast. You'll have to wait one day more.

To all381, I.Punish.L3av0r: yes, I will certanly look into adding multitouch, 
but
only after I fix all obvious bugs :)

Original comment by Dmitry.S...@gmail.com on 4 Sep 2009 at 5:33

• Changed title: Feedback thread

[GoogleCodeExporter]

JDuverge1020, bugs that prevented you to play those two good songs are fixed! 
Try
version 1.0.3.

Original comment by Dmitry.S...@gmail.com on 5 Sep 2009 at 4:57

[GoogleCodeExporter]

It seems pretty hard to tap notes that are short after each other. Just like if 
the
buttons aren't responsible enough. (Hope you understood ;))

@Dmitry.Skiba: If you would like to help me a bit to find the correct classes, I
would be proud to help you adding multitouch

Original comment by till.ess...@googlemail.com on 5 Sep 2009 at 10:05

[GoogleCodeExporter]

@till.essers, yes, I understand :) In fact there is a setting called 'min notes
distance' which is 100ms by default. On game loading TOF will glue together 
notes
which are inside of that period. This setting is on Advanced settings page, to 
access
it press MENU in Settings.
Of course this solution is not quite satisfactory. This setting should be set to
appropriate value by default. But appropriate value is yet to be found :)

About multitouch: sorry, I don't know how to hack it. Yet.

Original comment by Dmitry.S...@gmail.com on 5 Sep 2009 at 3:22

[GoogleCodeExporter]

@Dmitry.Skiba: I just meant, that you should point me to the right direction in 
your
handling code.

Original comment by till.ess...@googlemail.com on 5 Sep 2009 at 5:14

[GoogleCodeExporter]

Ahh, ok :)
In the nutshell GameActivity remembers last touch coordinates in two variables 
(x and
y). Before rendering (which occurs in other thread) touch coordinates are put 
into
the engine, which analyzes them and sets internal flags. This process is very 
simple
and naive, there is even no up/down states; when not touched touch coordinates 
are
(-1,-1).
So, to work with multitouch we need to change number of touch coordinates. Also 
we
need to disable touch zones between keys and smart working of the middle key.
Let's do this: I will add new method to the engine that will accept N touch
coordinates. This method will simply match touches to keys, with all smartness
disabled. I will notify you when code is checked in, so you can start working.

BTW, I have few questions:
* How many simultaneous touches can there be?
* How hackery is that? Can we dynamically enable/disable multitouch support and 
have
one package for both cases?

Original comment by Dmitry.S...@gmail.com on 5 Sep 2009 at 6:13

[GoogleCodeExporter]

Afaik the G1 Multitouch-Hack (don't know about Galaxy, Magic and Hero [which 
should
have native Multitouch]) can handle 2 touch points.
It isn't that hackery, because it uses the same classes as the normal touch
interfaces, just a modified KeyInputManager is used to decode the multitouch 
points.
But there is a problem with the points snapping together, will have a look how 
far
the touch points have to be from each other.

Original comment by till.ess...@googlemail.com on 5 Sep 2009 at 7:56

[GoogleCodeExporter]

till.essers, source code is checked in, you can try to hack multitouch. I've 
added
Stage.onMultitouch method which accepts array or (x,y) pairs in screen 
coordinates (y
down, x right). You need to call it in GameActivity.onStageGLRender.

Original comment by Dmitry.S...@gmail.com on 7 Sep 2009 at 6:09

[GoogleCodeExporter]

Great, will have a look into it this week.

other topic:
- Make the songs being cached, so it doesn't scan the whole folder everytime 
you go
into the song list, instead having a "Scan" button in the menu or at the bottom 
of
the list. I'm having a lot of songs right now and I can't play until every song 
is in
the list, because if I try to hit it while scanning the list changes and I hit 
the
wrong song ;)
- The decoded songs aren't cached properly, it has to decode it every now and 
then.
When I add new songs (without touching the old ones) for example.
- The high scores of the songs aren't stored properly, after adding new songs 
for
example, the high scores of the old are gone.
(Trying to make a step by step instruction to reproduce the last 2 errors)

Original comment by till.ess...@googlemail.com on 9 Sep 2009 at 12:08

[GoogleCodeExporter]

Thanks for the feedback!

- Yes, song list is not behaving very good, and is somewhat slow. I'm fixing it 
right
now. I'm thinking of checking modification time of TapsOfFire/songs and 
rebuilding
song list when time changes. And adding explicit 'Scan' command of course.
- I will check that, but this is may be because of 'cache length'. There is a 
'cache
length' setting which controls number of entries in cache. When cache is full,
olderst cache entry is deleted. Default value is 5. Maybe I should mention this
setting (and its value) on 'decoding' screen...
- Yes, scores... I've got another report for this one. I don't know why it is
happening (though I have some guesses based on quality of code there), so steps 
to
reproduce would be very helpful!

Original comment by Dmitry.S...@gmail.com on 9 Sep 2009 at 3:40

[GoogleCodeExporter]

OK, I've reproduced bug with scores. Fixing...

Original comment by Dmitry.S...@gmail.com on 9 Sep 2009 at 4:04

[GoogleCodeExporter]

Fixed!
And also several other things too, see changelog.

Original comment by Dmitry.S...@gmail.com on 14 Sep 2009 at 5:26

[GoogleCodeExporter]

For the song loading thingy:
After you decoded a song the song list loads again when you hit play, without
changing anything by yourself. Don't know where the decoded songs are kept, but 
if it
is in the songs directory, you should consider moving it to another one.

Original comment by till.ess...@googlemail.com on 17 Sep 2009 at 11:58

[GoogleCodeExporter]

Hmm, this is really weird. Cache is under TapsOfFire/cache, and songs are in
TapsOfFire/songs, so there should not be any problem... 
Does it reload when you play songs undecoded (by tapping decoding progress)?
Algorihtm for detecting changes in songs is pretty simple: each time I multiply 
(yes,
multiply) modification time of TapsOfFire/songs by number of files inside it, 
and if
it changes then I reload songs. Can you please check whether modification time 
of
TapsOfFire/songs changes?

Original comment by Dmitry.S...@gmail.com on 17 Sep 2009 at 3:01

[GoogleCodeExporter]

Does not work on my Galaxy. It's very lagy and I can't see the things that you 
should
press to hit a note (the green, red and yellow tings)

Original comment by lille...@gmail.com on 29 Oct 2009 at 9:42

[GoogleCodeExporter]

:( this is bad news. I will take a look at it.

Original comment by Dmitry.S...@gmail.com on 30 Oct 2009 at 3:45

[GoogleCodeExporter]

lilleake, So you have Galaxy (i7500), not Galaxy Lite (i5700), right? I'm 
thinking of
getting me one.

Original comment by Dmitry.S...@gmail.com on 3 Nov 2009 at 3:47

[GoogleCodeExporter]

Dmitry.Skiba: Yes I have the i7500. It's a great phone I recommend it. It would 
be
nice if you got one so you can solve the bug because what I can see on videos 
of the
game it looks great.

Original comment by lille...@gmail.com on 3 Nov 2009 at 9:27

[GoogleCodeExporter]

The problem with i7500 aka Galaxy is not related to bug in Taps of Fire, it's 
bug in 
firmware that prevents playing ANY 3D games at decent speeds and I doubt if 
Taps of 
Fire could be made to work on Galaxy other way than making it two-dimensional. 
For 
example, SpeedForge, Armadillo Roll and Taps of Fire didn't work for me on my 
Galaxy. But when i used that hack: http://androidforums.com/samsung-i7500/14611-
opengl-working-galaxy-ii5.html [needs root and could be illegal, the trick 
depends 
on copying GL library from HTC recovery rom] all that games work as fast as 
they 
should, Taps of Fire is even too fast for my fingers but that's the fault of my 
poor 
skill ;).

Original comment by gsad...@gmail.com on 7 Nov 2009 at 11:49

[GoogleCodeExporter]

Yes, this issue feels like a bug in Galaxy's OpenGL.
But nevertheless here we developed a solution:
http://www.anddev.org/samsung_galaxy_odd_ogl_es_hardware_acceleration_resolved-t
8511.html
I will make special Galaxy build tomorrow.

Original comment by Dmitry.S...@gmail.com on 7 Nov 2009 at 1:52

[GoogleCodeExporter]

Dear Samsung Galaxy users, please try special build:
http://tapsoffire.googlecode.com/files/TapsOfFire104Galaxy.apk

Original comment by Dmitry.S...@gmail.com on 8 Nov 2009 at 4:41

[GoogleCodeExporter]

Will we be getting Multitouch support for the Hero? I have a few songs that 
require it.

Original comment by Supremes...@gmail.com on 24 Dec 2009 at 11:31

[GoogleCodeExporter]

Just one little thing: it is possible to have folders in the song list?

Original comment by fabio.ta...@gmail.com on 9 Jan 2010 at 7:29

[GoogleCodeExporter]

fabio.tacchelli: You mean in the 'TapsOfFire/songs' foldeR? Yes, absolutely.

Supremespeed: Hmm, all combinations of notes are doable without multioutch - 
you just
have to tap between the keys or use red key for green+yellow or green+red+yellow
combinations (and for red alone, of course). There can be difficulties with 
speed or
complexity of the song, though.

Original comment by Dmitry.S...@gmail.com on 9 Jan 2010 at 8:45

[GoogleCodeExporter]

i mean, i have something like songs/Album1 and songs/Album2, can i have this 2
folders ingame at the song list or it will be a future feature? (would be nice 
to
have songs organized by albums ingame:))

Original comment by fabio.ta...@gmail.com on 9 Jan 2010 at 8:53

[GoogleCodeExporter]

fabio.tacchelli: ok, I get it, and put it in the TODO list :)

Original comment by Dmitry.S...@gmail.com on 12 Jan 2010 at 10:21

[GoogleCodeExporter]

I don;t mind the way to get around having multi touch except when notes come on 
the 
green and yellow track at the same time.

Also, it seems that it doesn't register the note's location correctly in 
relation to 
the button. I have to hit the button a bit before it reaches to hit the note.

I'm on a Droid Eris

Original comment by adthrawn...@gmail.com on 24 Feb 2010 at 7:04

[GoogleCodeExporter]

This app is awesome. It plays good on Super Easy, but on the harder levels the 
only 
problem i see is that there is no way to hit the green and yellow chords.  
Other than 
that, i LOVE it.  Please continue to work on this.  :D

Original comment by CosmoKra...@gmail.com on 25 Mar 2010 at 7:31

[GoogleCodeExporter]

I play on my Samsung I5700 and got some performance problems. It runs on 10-15 
fps 
and has some graphics artifacts like white space in place of running lines 
(notes)
I think it's OpenGL problems or smth. Or maybe it needs some special 
optimization 
for Spica's processor. That would be great if you can fix these lags because 
the 
game is just awesome

Original comment by Element....@gmail.com on 26 Mar 2010 at 4:42

[GoogleCodeExporter]

Please try 'Galaxy' version.

Original comment by Dmitry.S...@gmail.com on 26 Mar 2010 at 4:44

[GoogleCodeExporter]

Still got the same problems

Original comment by Element....@gmail.com on 26 Mar 2010 at 4:50

[GoogleCodeExporter]

I play on 1.5 Cupcake, if that matters. Maybe that's the problem =\

Original comment by Element....@gmail.com on 26 Mar 2010 at 4:56

[GoogleCodeExporter]

So, will there be some optimized version for Spica's SC36410 processor?
FoF is my one of the most favourite games, and to know that this perfect 
adaptation 
for Android is unavailable for me... *sigh*

Original comment by Element....@gmail.com on 27 Mar 2010 at 7:26

[GoogleCodeExporter]

Ok, the fact is, Samsung made a little bit not so good OpenGL ES 1.0 support in 
Spica. Though, OpenGL ES 2.0 works just fine. That's all what i could find 
about 
Spica's 3D problem at the moment

Original comment by Element....@gmail.com on 27 Mar 2010 at 9:00

[GoogleCodeExporter]

Ok i realize now that you can hit Green + Yellow with the Red button but it's 
really 
tough to keep a streak up, especially when the chords change on harder 
difficulty.  If 
this game had multi-touch it would be the best mobile rhythm game out there.  
Isn't the 
Android 2.1 SDK out there, so you can add multi-touch?  

Original comment by Artie0...@gmail.com on 30 Mar 2010 at 4:11

[GoogleCodeExporter]

multi touch is the only thing what I miss in this game - with MT will be 
PERFECT :D

Original comment by zipiol...@gmail.com on 30 Mar 2010 at 11:15

[GoogleCodeExporter]

hi about gameplay i suggest having circles where the notes land for you to hit, 
cause 
now i feel that it is a bit counterintuitive to have to hit the notes right 
before they 
reach the solid boxes below. thanks for the great game!

Original comment by wenchon...@gmail.com on 8 May 2010 at 3:52

[GoogleCodeExporter]

I agree with WenChong15. I always take it that when the fret lands on the box, 
then i have to touch the box. So i always get super low scores. Change of the 
layout would make this game even better! :D
Also, keep up the awesome game! :D

Original comment by jerryk...@gmail.com on 13 Oct 2010 at 9:49

[GoogleCodeExporter]

Agreed with wenchong15 too. I also suggest moving the notes-hitting pictures 
alittle 'upwards' if you get what I meant because it is alittle out of sync. 
Notes have to be hit few moments before it touches the boxes. And of course, I 
edited my advance settings. There's another glitch. Notes CANNOT be hit when 
reaches the box. For holds, if you missed it, you can 're-touch' it again if 
your fast enuff (about 1 sec).

Samsung Galaxy Spica
- Android 2.1

Original comment by tanyik...@gmail.com on 12 Nov 2010 at 5:27

[GoogleCodeExporter]

Hi! Pls, make 4 string version, like an original frets on fire, that's would so 
great for big screen smartphones and tabs, also themes support will be great 
too. Thank u for your great work!

Original comment by ShinKrus...@gmail.com on 1 Jul 2011 at 4:05

[GoogleCodeExporter]

This app is spectacoular but isn't perfect.... I'd like to have a multitouch 
support
I have an Samsung galaxy s plus
Thank you for all!

Original comment by nosxs1...@gmail.com on 30 Jun 2012 at 1:46