Bug direct Game Over?

dantedevil

dantedevil

Well-known member
Recently I found a bug I had not seen before. I do not know if it's the build, since I recently changed it to a newer one.
About the bug:
When I play a game and lose my lives, the Game Over screen comes out directly and it does not let me continue, even though I have more credits left.

I use the OpenBOR.v3.0.Build.6315

Here my set in levels.txt:
Code: 
set	NORMAL
typemp 0
custfade 100
lives   3
credits 99
nosame    1
cansave	2
completebg    1
 
Sort by date Sort by votes
dantedevil said:
pudu said:
Your levels.txt has noshare 2/1/0 set (no bugs after deleting this code)
Click to expand...

Not my friend, my levels.txt don't have noshare 2/1/0 set.
Click to expand...
I have encountered this problem before. No matter in any mode, "noshare" will cause all modes to lose all life after reading the file. There are still many "credits" but the picture ends directly and cannot be resumed.
 
Upvote 0 Downvote
Bloodbane said:
dante, does this happen all the time or just in certain conditions?
Click to expand...

After a lot of test, I can confirm the bug come with the build OpenBOR.v3.0.Build.6315
I also found another bug with this build, "nokill 1" does not work in the animations.

I try with the build OpenBOR_v3.0_Build_4432 and everything works ok again, It is the one I always use before changing and that has never given me problems. Without a doubt it is the most stable one that I have used.

I change to this build to use the script to brach in a specific hole:
http://www.chronocrash.com/forum/index.php?topic=3910.msg54872#msg54872

Now I have a big problem here.
 
Upvote 0 Downvote
O Ilusionista said:
Thanks for your effort in tracking which version originated the bug.
Click to expand...
No problem my friend, it is important for everyone to find the solution.
I am also happy to contribute in some way to help those who are really responsible for this.  ;)
 
Upvote 0 Downvote
Thank you.

Finding the exact version is a HUGE help... it lets us compare code changes from the previous version and possibly see where the problem is.

Otherwise we're just poking around blind in ~400k lines of code.

DC
 
Upvote 0 Downvote
Damon Caskey said:
Thank you.

Finding the exact version is a HUGE help... it lets us compare code changes from the previous version and possibly see where the problem is.

Otherwise we're just poking around blind in ~400k lines of code.

DC
Click to expand...

Happy to help my friend!
;D
 
Upvote 0 Downvote
After some testing on this bug, i found out what actually specificaly is happening and it may help you guys fix this.

Normally when loosing all lives the engine was giving the player about 10sec or something to press continue. Now after my testing it seems like you can still continue but only if you press continue very fast after loosing all lives.
So it's not like you can't continue anymore, but what actually happening is that the engine does not giving you the 10sec time to think about it anymore. So, if you are not fast = Game Over.
 
Upvote 0 Downvote
That does help, but please please it in the github bug reports. I have stepped back from engine coding to work on my personal projects a bit, but I'll be back soon and it will help no to have reports lost in threads.

DC
 
Upvote 0 Downvote
Damon Caskey said:
That does help, but please please it in the github bug reports. I have stepped back from engine coding to work on my personal projects a bit, but I'll be back soon and it will help no to have reports lost in threads.

DC
Click to expand...

I just reported the bug on github in a new thread, with all the information we have all contributed.
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top Bottom