Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
 Welcome to our latest new user Harvey ! (Registered 2024-11-25) You are not logged in - nap
CSDb User Forums


Forums > C64 Coding > Pinball Dreams discussion forum
2003-02-13 19:16
WVL

Registered: Mar 2002
Posts: 898
Pinball Dreams discussion forum

Hey guys/girls,

instead of updating my homepage all the time, I though I could open a new thread here instead. This will also allow other ppl to comment on the development.

okay, so whassup at the moment?

Well, Last month I completely restarted from scratch on the code. Why? Well, first I wanted to concentrate more on getting the game to run in less memory, also I wanted to focus more on accurate simulation of the ball and some small other things...

What I have done till now :

1 - spawned the ball ;-)
2 - added gravity to the surroundings, the gravity data is now RLE encoded, so it doesn't take up much memory anymore. Used to eat 20 blocks of memory, now I think a map would use 3-4 blocks..
3 - I changed the gravity routine to use polar-based vectors instead of cartesean, much more accurate!
4 - added a debug mode to the movement routines, you're able to pick up the ball with the firebutton and move it around. Let go of the button and you drop it on the table again.
5 - Worked on an accurate (within 1 'bradian' degree) direction calculation routine. This routine will be used for both friction calculations and calculating new directions after collisions. So it needs to be
6 - added a (simple) friction routine.
7 - I put a small preview on the web ;-)

get it at http://www.interstyles.nl/pinball.rar

okay, what am I up to now?

1 - increase the speed accuracy to 24 bit, I need this because the friction only affects speed in the last 3 bits or so, so it's not accurate at all..
2 - add spin to the ball, so it is allowed to roll.. (also gives effect to the ball like top-spin and such)
3 - dunno yet, I'll see what is the next logical step after that.. probably the new method of collision detection, dunno..

I'm thinking of putting the sourcecode online as ascii file, so everyone can check it out...

Suggestions? Questions? other stuff?

greets, Werner
2003-02-13 22:52
cadaver

Registered: Feb 2002
Posts: 1160
Are there any keys (or something) to test scrolling yet?
2003-02-13 23:04
Pater Pi
Account closed

Registered: Jan 2002
Posts: 121
Nice ball-movement.
Anybody ever tried to place the ball far to the upper border? The result is kind of funny (unlimited ball-acceleration).
2003-02-14 07:14
Majikeyric

Registered: Sep 2002
Posts: 83
Great !!! I was thinking the project was aborted !!! :o)
2003-02-14 11:49
WVL

Registered: Mar 2002
Posts: 898
As for scrolling : It has been removed for now, but it's easy to add. All the necessary (REU) routines are ready, but as I was saying I'm trying to get it to run on a stock machine as well, so I'll have to add a linecrunch routine...

About the top border : the game only allows for a 64 char high table -> place the sprite in the upper border and it will read the gravity data from row 63,62.. etc, which are not defined yet :) only rows 0-24 (the top screen) is defined as to now... (IE - AFTER ADDING COLLISION DETECTION IT WILL BE IMPOSSIBLE TO GO IN THE TOP BORDER OFCOURSE :))

Werns
2003-02-14 14:55
WVL

Registered: Mar 2002
Posts: 898
oh, btw, please don't mind the background 'picture' in the preview ;-) it was only meant to visualise the resulting gravity-force... about one minute work in photoshop and then some on my converter...
2003-02-20 18:32
Nafcom

Registered: Apr 2002
Posts: 588
Hello there!

Okay, preview is great anyway, so thanks!

Great to see, that developing goes on! :)

One question: How about NTSC & PAL compatibility?!

Thanks in advance!

All the best!
Bye!
Joerg
2003-02-21 13:05
WVL

Registered: Mar 2002
Posts: 898
well, it will be PAL, dunno if ppl will want to convert to NTSC? also I don't know if NTSC has enough cycles/frame to do all necessary calculations, it might be necessary to drop some realism in a possible NTSC version..
2003-02-21 15:53
MagerValp

Registered: Dec 2001
Posts: 1074
I dare say that the majority of the active NTSC users today have SuperCPUs. Just enable 20 MHz mode in the border and switch back to 1 MHz mode in the first irq and NTSC users will have plenty of cycles to catch up.
2003-02-21 17:28
cadaver

Registered: Feb 2002
Posts: 1160
Also, if you do all critical (but fast) stuff in IRQs and heavy calculations in mainprogram, running out of time doesn't matter that much (just momentary slowdown)
2003-03-07 14:46
WVL

Registered: Mar 2002
Posts: 898
it runs either at 50fps or not at all.. I'll include a debug feature that will halt the game whenever all calcs cannot be done in one frame, and will write debug data to disk or something. This will allow me to see where speedups are in order.
 
... 163 posts hidden. Click here to view all posts....
 
Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | ... | 18 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Mike
Alakran_64
t0m3000/hf^boom!^ibx
A3/AFL
psych
swasti
Skate/Plush
WVL/Xenon
Airwolf/F4CG
pcollins/Quantum
Electric/Extend
Guests online: 87
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Coma Light 13  (9.7)
4 Edge of Disgrace  (9.6)
5 Mojo  (9.6)
6 The Demo Coder  (9.6)
7 What Is The Matrix 2  (9.6)
8 Uncensored  (9.6)
9 Wonderland XIV  (9.6)
10 Comaland 100%  (9.6)
Top onefile Demos
1 Layers  (9.6)
2 Party Elk 2  (9.6)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.6)
5 Libertongo  (9.5)
6 Rainbow Connection  (9.5)
7 Onscreen 5k  (9.5)
8 Morph  (9.5)
9 Dawnfall V1.1  (9.5)
10 It's More Fun to Com..  (9.5)
Top Groups
1 Performers  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Nostalgia  (9.3)
5 Triad  (9.2)
Top NTSC-Fixers
1 Pudwerx  (10)
2 Booze  (9.7)
3 Stormbringer  (9.7)
4 Fungus  (9.6)
5 Grim Reaper  (9.3)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.037 sec.