Login [Register]
Don't have an account? Register now to chat, post, use our tools, and much more.

Are you excited?
Yes!
 80%  [ 12 ]
No.
 0%  [ 0 ]
I don't care.
 20%  [ 3 ]
Total Votes : 15

Hey, I just want you guys to know that there is a VERY large possibility that I will not to be able to submit this entry in time for CC22. I've spent the last week or so trying to fix a bug in my code that I have literally no idea how to repair. I've tried all kinds of things, but nothing seems to be working. Meanwhile, everyone else is gaining ground and my development of new features has stalled. Also, I'm getting really frustrated with this and the end of month deadline is intimidating, to say the least. Development will continue, and I want to get this game out eventually, but most likely it won't be for CC22. So, kind of informally dropping out. If I somehow do manage to finish, I will be sure to submit it, however. Sorry, but I think that this is the best choice to bring you guys the best program I am able to. I apologize again. Now, time to look through my code for the problem for the 400th time. I think it's a problem with the appvar code, but I'm not at all sure.
According to the contest rules, it's fine for other people to help as long as it's done publicly. You could post your code, including the convpng input and output, here and we could try to help you find the bug in it. Both Michael and I (and probably more people) have shared our code publicly on GitHub so that others can see it and help debug.
Yeah definitely share your code and get help from the people here! Sometimes you look at the same code so many times that you just lose the capability of spotting the errors.
Alright thanks guys. The problem isn’t with the sprites as I had originally thought (I’m pretty sure, since I don’t have any real proof of that, and there’s far less than 64k of sprites in the program). I’ve been taking blocks of code and seeing if they work to try to narrow down the cause of the problem. When I took the save/ load code and tested it, I got similar errors to the ones I was experiencing when running the whole program. May upload on GitHub later, I guess. Thanks a lot for your support, too.
In case anyone wants to take a look, here is the save/ load code, which I believe is causing the problem.

Loading (should be fairly self explanatory, but CARIDEN is the car last viewed in the dealership, CARIDENA-E are the identification numbers of each car you own in the garage, and ACCA-E and TOPSPA-E are their stats; CURRCASH and CURREXP are your current cash and EXP levels):

Code:
sum(0)
sum(1,"DEALCAR","r"→A
If A=0
999999→CURRCASH
0→CARIDEN→CURREXP→CARIDENA→CARIDENB→CARIDENC→CARIDEND→CARIDENE→ACCA→TOPSPA→ACCB→TOPSPB→ACCC→TOPSPC→ACCD→TOPSPD→ACCE→TOPSPE
Else
sum(5,°CARIDEN,3,1,A)
sum(5,°CURRCASH,3,1,A)
sum(5,°CURREXP,3,1,A)
sum(5,°CARIDENA,3,1,A)
sum(5,°CARIDENB,3,1,A)
sum(5,°CARIDENC,3,1,A)
sum(5,°CARIDEND,3,1,A)
sum(5,°CARIDENE,3,1,A)
sum(5,°ACCA,3,1,A)
sum(5,°TOPSPA,3,1,A)
sum(5,°ACCB,3,1,A)
sum(5,°TOPSPB,3,1,A)
sum(5,°ACCC,3,1,A)
sum(5,°TOPSPC,3,1,A)
sum(5,°ACCD,3,1,A)
sum(5,°TOPSPD,3,1,A)
sum(5,°ACCE,3,1,A)
sum(5,°TOPSPE,3,1,A)
End
sum(0)


Saving (same things apply here):

Code:
sum(0)
sum(1,"DEALCAR","w+"→A
If A≠0
sum(4,°CARIDEN,3,1,A)
sum(4,°CURRCASH,3,1,A)
sum(4,°CURREXP,3,1,A)
sum(4,°CARIDENA,3,1,A)
sum(4,°CARIDENB,3,1,A)
sum(4,°CARIDENC,3,1,A)
sum(4,°CARIDEND,3,1,A)
sum(4,°CARIDENE,3,1,A)
sum(4,°ACCA,3,1,A)
sum(4,°TOPSPA,3,1,A)
sum(4,°ACCB,3,1,A)
sum(4,°TOPSPB,3,1,A)
sum(4,°ACCC,3,1,A)
sum(4,°TOPSPC,3,1,A)
sum(4,°ACCD,3,1,A)
sum(4,°TOPSPD,3,1,A)
sum(4,°ACCE,3,1,A)
sum(4,°TOPSPE,3,1,A)
End


If anyone could help it would be much appreciated. The glitch is probably just something I overlooked. Thanks in advance.

EDIT- Now that I have some more time to work on this (assuming I don't submit it for CC22), maybe I'll just start over (keeping some stuff, though). The program in its current state has an infestation of bugs and takes up far too much space. So, I think that it might be time to start fresh, keeping clear goals in mind. What do you guys think?
I haven't messed around with your code yet, but just looking at it: Have you allocated bytes for each of the variables that you are reading the save into?

For instance,

Code:
sum(1,"DEALCAR","r"→A
Alloc(3)->CARIDEN
Read(CARIDEN, 3, 1, A)
***{CARIDEN}->CARIDEN
Concept: DR0VE

New idea. How would you guys feel about me releasing a small drag racing game for CC22, then releasing the full-featured DR1VE later? DR0VE would include the full quick race system, a few cars, and maybe some options to change their performance to get the best time. It would be an arcade game of sorts. What do you think? Post your thoughts here.
epsilon5 wrote:
How would you guys feel about me releasing a small drag racing game for CC22, then releasing the full-featured DR1VE later? DR0VE would include the full quick race system, a few cars, and maybe some options to change their performance to get the best time.


Sounds great! Very Happy
epsilon5 wrote:
Concept: DR0VE

New idea. How would you guys feel about me releasing a small drag racing game for CC22, then releasing the full-featured DR1VE later? DR0VE would include the full quick race system, a few cars, and maybe some options to change their performance to get the best time. It would be an arcade game of sorts. What do you think? Post your thoughts here.


1) Clever naming. Smile 2) Yeah, that sounds great!
NoaxPrime wrote:


1) Clever naming. Smile 2) Yeah, that sounds great!


My idea from the start of this was to make the game a series for TI 84 Plus CE calculators. First would be DR1VE, then DR2VE, then DRIV3, and so on. Since DR1VE is coming later now, DR0VE is first. Not very inspired, I know, but I don't care that much, because it sounds (and looks) good.
DR0VE progress update:

So right now, the program can take an acceleration and top speed value and calculate the shift locations based on the number of gears. It will also calculate the current RPM of the engine and stop acceleration once you reach 8000 RPM (until you shift), at which point the RPM will drop. Downshifting is working as well. Finally, it will penalize you for trying to shift too early. And in its current state, all this code (compiled) is only about 850 bytes. I'm working on calculating distance traveled and setting up timers now, which shouldn't take too long.

Plans:

Soon, you will be able to configure a car to your liking, then race it. You will have to find the optimal balance of acceleration and top speed to get the best time. Your opponent's acceleration and top speed will be tuned so it will always give you a challenge. More to come! If you have any feedback, be sure to put it here.
epsilon5 wrote:
DR0VE progress update:

So right now, the program can take an acceleration and top speed value and calculate the shift locations based on the number of gears. It will also calculate the current RPM of the engine and stop acceleration once you reach 8000 RPM (until you shift), at which point the RPM will drop. Downshifting is working as well. Finally, it will penalize you for trying to shift too early. And in its current state, all this code (compiled) is only about 850 bytes. I'm working on calculating distance traveled and setting up timers now, which shouldn't take too long.

Plans:

Soon, you will be able to configure a car to your liking, then race it. You will have to find the optimal balance of acceleration and top speed to get the best time. Your opponent's acceleration and top speed will be tuned so it will always give you a challenge. More to come! If you have any feedback, be sure to put it here.


MAN I CAN"T WAIT!!! I really love the progress and I'd love to see how it turns out!
Feedback? There will be a scrolling background soon (if you have any tips on how to implement that, it would be appreciated, but probably not required).

EDIT- Oh yeah, the number in the top left corner is the current time in seconds.

It would be neat if the cars had shadows under them - you could probably use the same shadow for all the cars. It would help trick the eyes into seeing the cars one closer than the other in 3D space rather than one on top of the other in 2D space.
  
Register to Join the Conversation
Have your own thoughts to add to this or any other topic? Want to ask a question, offer a suggestion, share your own programs and projects, upload a file to the file archives, get help with calculator and computer programming, or simply chat with like-minded coders and tech and calculator enthusiasts via the site-wide AJAX SAX widget? Registration for a free Cemetech account only takes a minute.

» Go to Registration page
Page 3 of 3
» All times are GMT - 5 Hours
 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

 

Advertisement