Gamer125 / fofix

Automatically exported from code.google.com/p/fofix
0 stars 0 forks source link

Preload graphical menus before game. #515

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.The game starts.
2.You enter a grahpical menu, it lags 2-3 seconds before entering it.
3.You can't enter menus fast, and you're annoyed. :)

What is the expected output? What do you see instead?
Like GH3 and RB2, i think the game should preload grahpical menus.
You launch the game.
Then you get theme/menu/startingimage.png 
[http://i41.tinypic.com/2gtadug.png] This one is for RB2.
It displays "Loading..." text. Then you get "Press any key to continue" or 
"Press start to continue" and you enter the menus fast.

Please provide any additional information below.

This should be toggable by option, some users may not want it.

Original issue reported on code.google.com by kristija...@gmail.com on 1 Feb 2009 at 7:22

GoogleCodeExporter commented 9 years ago
I agree, this needs to be done. The game takes a few seconds to load the solo 
and 
settings menus.

Original comment by mrhappen...@gmail.com on 5 Mar 2009 at 3:48

GoogleCodeExporter commented 9 years ago
We could finally make some usage of the start image. We have two of them. One is
named startimage, second one is named startimage1. First one consist of a sign. 
For
instance It says ROCK BAND. The second one is a smaller image, on which says: 
press
enter to continue. The second image shows after the loading is complete. If my
english is bad, I can make some examples.

Original comment by slash_...@windowslive.com on 8 Jun 2009 at 8:50

GoogleCodeExporter commented 9 years ago
I've already said that?

Original comment by kristija...@gmail.com on 8 Jun 2009 at 11:25

GoogleCodeExporter commented 9 years ago
Hahahhahahahahahah. Didn't see that. 

Original comment by slash_...@windowslive.com on 9 Jun 2009 at 1:00

GoogleCodeExporter commented 9 years ago
Issue set to invalid due to one or more of the following reasons:
1) Age. This issue is considered abandoned.
2) Unrelated. The issue isn't related to FoFiX.
3) Fluke. The issue cannot be reproduced or was fixed long ago. (AKA: It's just 
you.)

Feel free to reply if you are certain the issue still exists and is relevant to 
FoFiX.

Original comment by fuzio...@gmail.com on 2 Sep 2010 at 2:01