rosalila / flatshot Goto Github PK

They are still using TinyXML directly

You have to close the game and re open it in order to watch the replay

Flatshot currently has memory leak issues.
Probably the most problematic ones are:

• Leaking about 1.5MB per stage played
• Leaking all the old leaderboard data every time the new one it's requested

If you set a gamepad controller, close and rerun the game, it crashes on startup unless you "Configure input" again.

Or not?

It currently renders rectangles only

The steam controller configuration panel does not shows up.

• Notification ease animation
• Graphics feedback on winning/losing a game

It stores scores and I was able to watch replays, but then I hit a new high score, stored it but crashed everytime I tried to watch my replay. I was able to watch everybody else's replays though. This was the first stage of theTutorial

It's currently drawing the hitboxes as white rectangles

They are only getting written on the console

• Might checkout the hitbox collision process
• Might checkout the rendering process

I hope this is fixable. @ceteco found this

• When trying to play the game and choosing "Configure inputs" the following controllers' d-pad and left stick weren't recognised by the game:

1. X-Box 360 wireless controller
2. Logitech Gamepad F310 (neither X or D mode)
3. HORI PlayStation 3 Gem Pad 3

• However, when entering Big Picture mode in steam, the left stick could be used to navigate through the menus.

• Now, the following controller was perfectly usable: Radioshack 2603666.

• Setup: MacBook A1342 (Mid-2010) with Windows 8

• Stage clear feedback on menu: It would be nice to give feedback to the player if the stage:

  • Has not been cleared yet
  • Has been cleared
  • Has been cleared without getting damage

• Update stage names

• Setup colors

Might use the steam API

This is currently working on keyboard

Now that we have a glance at the final XML version before steam release. It looks like a good time to simplify and clean up the XML.

This might be due to the poor random seed handling:
https://github.com/Rosalila/RosalilaEngine/blob/master/RosalilaUtility/RosalilaUtility.cpp#L399

Might use rand() combined with srand() to fix this as @Immac suggested

• Display steam buttons in game
• Use the api
• Make a default controller setup
• Etc...

This happened after the bullets started being drawn by opengl shapes.
Before that, is needed to:

• Support geometric shapes inside the engine
• Find a way to handle this trough XML

Now that bullets are rendered using opengl rectangles we need some a new "on hit" animation

Or not?

The game crashes on the character selection screen when steam is on offline mode.

• I don't like the fact that the parry should always be used on the early game to get a better score
• Probably make more stages