🤑 Indie game store🙌 Free games😂 Fun games😨 Horror games
👷 Game development🎨 Assets📚 Comics
🎉 Sales🎁 Bundles

Bug Report Topic

A topic by Ammy created 1 year ago Views: 579 Replies: 14
Viewing posts 1 to 8
(Edited 2 times)

Guess who.'w' Thought it was a good idea to start this topic. I'll be giving the game a go and post again if I find anything.

Tips : How to write a good Bug Report

Anybody who has written software for public use will probably have received at least one bad bug report. Reports that say nothing ("It doesn't work!"); reports that make no sense; reports that don't give enough information; reports that give wrong information. Reports of problems that turn out to be user error; reports of problems that turn out to be the fault of somebody else's program; reports of problems that turn out to be network failures.

I'll try to state clearly what makes a good bug report. Ideally I would like everybody to read this before reporting any bugs. Hopefully that will make things easier :)

In a nutshell, the aim of a bug report is to enable the programmer to see the program failing in front of them! You can either show them in person, or give them careful and detailed instructions on how to make it fail. If they can make it fail, they will try to gather extra information until they know the cause. If they can't make it fail, they will have to ask you to gather that information for them.

  • In bug reports, try to make very clear what are actual facts ("I was at the computer and this happened") and what are speculations ("I think the problem might be this"). Leave out speculations if you want to, but don't leave out facts.
  • Tell them exactly what you did. Which buttons you pressed and what order you pressed them in. If it's a bug that happened after typing something, show them precisely what you typed.
  • Sometimes the fault doesn't show up on every computer; your system and theirs may differ in some way. Remember to give your specs if something still doesn't work.
  • If you saw error messages then tell the programmer, carefully and precisely, what they were. They are important! At this stage, the programmer is not trying to fix the problem: they're just trying to find it. They need to know what has gone wrong, and those error messages are the computer's best effort to tell you that.
  • In particular, if the error message has numbers in it, do let the programmer have those numbers.
  • Be specific. If you can do the same thing two different ways, state which one you used.
  • Be verbose. Give more information rather than less.
  • Be careful of pronouns. Don't use words like "it", or references like "the window", when it's unclear what they mean. Consider this: "I started FooApp. It put up a warning window. I tried to close it and it crashed." It isn't clear what the user tried to close. Did they try to close the warning window, or the whole of FooApp? It makes a difference.
  • As pointed out below, it would be nice of you to warn about typos too. ^_^

When an antelope is confronted with something unexpected or frightening, it freezes. It stays absolutely still and tries not to attract any attention, while it stops and thinks and works out the best thing to do. If you stumble upon a bug, keep calm and take note of what happened so far. If you close error messages too fast you may miss important information necessary to fix the bug...! x_x

Remember, if you're playing the beta safe often..! *chuckle*

Hope this was helpful...! Have fun playing! XD

(Edited 1 time)

First, I downloaded RockRobin as by itself from the website. After it was fully downloaded, I tried launching it and the game crashed immediately. After that, I downloaded the Itch.io desktop app, and decided to download the game on there too. After it was fully downloaded, I tried launching it once more and it still crashed. I then uninstalled it, and tested it one more time, and still nothing. Any ideas?


Update: Saw the FAQ in another post, and checked my video drivers. They're working properly, and are up-to-date.

(Edited 1 time)

Now this is odd. Which OS do you use? Windows? Linux? Mac? Are there any error messages before it crashes? And finally, are you able to visualize the splash image before the game window loads and crashes? That little detail is actually pretty important.

If you are able to see it and your game crashes right after that, it's possible that your graphics card has an issue to initialize OpenGL. If you're using Windows, note that you will need to install the newest version of DirectX 9 or superior to use the OpenGL renderer. Check more info on which DirectX you can install here. If it still doesn't work try this: Once you see the splash image, hold Shift. You'll be taken to a menu to pick your Graphics Acceleration settings. Tell it to use software renderer, then start the game again.

(Edited 1 time)

I use Windows, there aren't any error messages before it crashes. All I see is a little box that says RockRobin that's only on the screen for merely a second, which i'm going to assume isn't this "Splash" image you speak of.


I have just checked which DirectX I have, and it's DirectX11, I use windows 8. Is that any help? Not sure.

Developer (Edited 1 time)

That is the splash, actually.

Try holding SHIFT when booting up to try different modes.

Developer (Edited 2 times)

Things this may also be:

  • Your Anti-Virus program is blocking it.
  • Your computer username has non-ASCII characters in it.
  • You don't have enough memory.
  • Your drivers may be up-to-date, but your computer is using your on-board video card instead of your primary one (another tester had a similar issue and had to force their video card software to run the game).
(Edited 2 times)

So, this happened today:

Made a band including Joel, Natasha and Collin. Saved the game on default screen (with the playlist, and the list of buttons such as Manage Band, Band Meeting etc). Updated the game to the latest release today. Loaded saved file. Game went back to the Modify Band Screen with all characters exiting the band except Robin. Also I received an warning for a split second saying that Owen left the band. (?)

Possible update hiccup? I'll try a new game just to check.

PS: I had already finished a few events with Collin prior to saving.

Developer

There was a saving bug in the previous version of the game where if you fired someone, the game would never save again and would always load you out right after you fired them. This last update patched that.

(Edited 1 time)

Okay, here I go again. During Collin's route his event with Robin calming him down after they --- happened before her encounter with Grace. Those should go the other way around, no? *Blinks* Just wondering if I'm sleepy and missed something on the way.

And yeah, so far the update is working alright. Guess it was just an hiccup.

Developer

That is a mistake! Hehe. I'll fix that soon.

(Edited 1 time)

Hello.

I'm new in the community but I've been playing games in here for a while.

So I downloaded it and everything was perfect and I even overcomed the Story Mode and got Dallas *__*

But now, I'm trying to open it again and it says that the file cannot be recognized or that it is broken and I wonder if there is any way of fixing it without losing all my info because I really was looking forward to play Open Ended Mode u_u

Developer

Re-downloading the game should still keep your information. There's also a save folder you can copy to your new version if not.

In Open Mode, it seems that there are numerous characters whose routes should be implemented, who don't seem to be working in my game. Collin, Rose and Emma are working, while Joel, Natasha and Faust aren't (I've yet to try Alessandro). By 'not working' I mean that, while the characters can be used in the band, there is no way to increase relationship with them or trigger scenes from their route.

I have tried to update the game, though this results in:

'An error has occured: Value Error: no JSON object has been decoded'

My game version is 0.60. I've also tried deleting and reinstalling the game, though this doesn't seem to have helped any

Developer

Re-download the game. 0.60 is an old version that I deprecated to force you to re-download the game, which is why the newer characters don't work for you. :)

When I try to record the first album in story mode, I get an exception screen with the following traceback:

[code]
I'm sorry, but an uncaught exception occurred.

While running game code:
File "game/code/gigs.rpy", line 563, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/gigs.rpy", line 1290, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/gigs.rpy", line 1290, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 231, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/talk.rpy", line 929, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/recordingstudio.rpy", line 1713, in script
File "game/code/recordingstudio.rpy", line 2261, in <module>
NameError: name 'overalquality' is not defined

-- Full Traceback ------------------------------------------------------------

Full traceback:
File "game/code/gigs.rpy", line 563, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/gigs.rpy", line 1290, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/gigs.rpy", line 1290, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/talk.rpy", line 546, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 231, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/shop.rpy", line 913, in script call
File "game/code/shop.rpy", line 905, in script call
File "game/code/shop.rpy", line 886, in script call
File "game/code/talk.rpy", line 929, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/planner.rpy", line 580, in script call
File "game/code/misc/event_dispatcher.rpy", line 308, in script call
File "game/code/recordingstudio.rpy", line 1713, in script
File "D:\Media\gamez\agth\RockRobin_Beta-all\renpy\ast.py", line 806, in execute
renpy.python.py_exec_bytecode(self.code.bytecode, self.hide, store=self.store)
File "D:\Media\gamez\agth\RockRobin_Beta-all\renpy\python.py", line 1577, in py_exec_bytecode
exec bytecode in globals, locals
File "game/code/recordingstudio.rpy", line 2261, in <module>
NameError: name 'overalquality' is not defined

Windows-8-6.2.9200
Ren'Py 6.99.10.1227

[/code]


Ignore option doesn't help, unfortunately, there is another exception and the game keeps cycling between those 2.

I have tried recording the album on different week of the game and changing the tracklist, but that didn't help either.

Developer

Thank you, I'll update the game here shortly.