FoFiX v3.1xx development thread

[death_au]

You know if i could go in here and delete every post like this in this "DEVELOPMENT" thread, it would probably take it down to around 10 pages.

...Is that all?

[Qstick]

You know if i could go in here and delete every post like this in this "DEVELOPMENT" thread, it would probably take it down to around 10 pages.

...Is that all?

i meant his post not yours big guy, and maybe i could get it down to 8 but 11 max

[death_au]

lol, I misread. I thought you said "take it down 10 pages", not take it down to 10 pages. That makes more sense. [/offtopic]

[Blue Murder]

Hard to explain, but...

If you set your setlist to list/album it'll show a little CD case that revolves around. My question is what must you name the picture file in order to have that cover display and/or what does the size have to be?

[angellinus]

lol, I misread. I thought you said "take it down 10 pages", not take it down by 10 pages. That makes more sense. [/offtopic]

10 more pages? Hmm...........

[death_au]

there's an option to switch between displaying "labels" and "albums". If albums is selected, the image must be called "album.png" (in the song's folder), or "label.png" for labels.

[Juhaz]

I never noticed a jump in memory usage, but I never paid that much attention anyway. If someone else can test an corroborate this, it would be appreciated.

Also, between beta 4 and final, there was a release candidate (links are on the FoFiX wiki's Old News page). If you could test this one out also and see if the memory problem exists, it will narrow down the list of changes to investigate for the cause of the problem.

beta 4 was r960, and final was r1075. Only about 100 revisions to check... The RC falls in the middle of that at r1017.

Didn't test with the rc yet since there was no working binary release of it for Linux, and I have some issues with running from the source with the versions of dependencies included in Ubuntu (pyopengl or some other component seems to be fond of screwing up my display card/drivers when trying to run FoF, to the point where cutting the power to the machine is required to get it working), but I guess building a separate python environment is one way to spend a weekend

I'll see what I can do.

[BlackJack]

Talking about the setlist, with v3.100, on the GH3 theme(s), if it is set to "CD/List" mode, it doesn't scroll on locked songs (somewhat annoying when you just played a song in Quickplay, then go to Career).

[SystemFailure]

is there any way to fix the over sized multiplier, or is this a theme problem?

[death_au]

is there any way to fix the over sized multiplier, or is this a theme problem?

...probably a theme problem. What theme? And what does the multiplier look like (could you provide a screenshot)?

[SystemFailure]

it the rock band 2 theme, i will post a screeny later, i am just taking coding brake

[Super_Crazy_Dude]

why no new updates???

[holystoneH]

no free time = no updates

[slantyr]

why no new updates???

fingers enormously hugh optimization, rewriting how fof handles lists of notes

once that's done the floodgates might be reopened ;)

the fact the other devs are sort of in a holding pattern,(not commiting changes) could mean that he's getting close

good things come to those who wait.

[Juhaz]

Also, between beta 4 and final, there was a release candidate (links are on the FoFiX wiki's Old News page). If you could test this one out also and see if the memory problem exists, it will narrow down the list of changes to investigate for the cause of the problem.

beta 4 was r960, and final was r1075. Only about 100 revisions to check... The RC falls in the middle of that at r1017.

Didn't test with the rc yet since there was no working binary release of it for Linux

Ah, I remembered wrong, it was beta3 that did not have a working release, not the rc.

Tested now, the rc uses more memory than b4, but not as much as final, and the jump from rc to final is larger than from beta to rc.