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


Forums > CSDb Discussions > Fix / improve ancient releases?
2006-11-25 21:15
Master of Chaos

Registered: Apr 2002
Posts: 25
Fix / improve ancient releases?

Hello .

There are some ouf our releases from 86/87 which eiher containes bugs or are worth to be improved a little bit.

Not that many that there are great differences , but, for example more userfriendly ( level and traiber chioce has to be improved) or fixing the speed of a sound routine.

In fact, they are still as there were programmed in that days, but i am thinking of doing some minor updates befor uploading the stuff.

What do you think, leave the stuff as it was done years ago or better implement some modified code?

greetz

Master of Chaos

2006-11-25 21:29
Danzig

Registered: Jun 2002
Posts: 440
hands OFF!
2006-11-25 22:27
null
Account closed

Registered: Jun 2006
Posts: 645
If you'd change it a bit, ok, but also upload the original stuff, else it's kinda like changing history...
2006-11-25 22:45
Zyron

Registered: Jan 2002
Posts: 2381
Just let it be.
2006-11-25 22:54
Radiant

Registered: Sep 2004
Posts: 639
I agree, a release is a release and should be preserved like it was when first released.

Making new releases out of bugfixes of old stuff is fine with me, though, if anyone gives a fuck about my opinion on these matters. :-)
2006-11-26 08:58
A3

Registered: Dec 2005
Posts: 362
I agree if you want to fix someting in a release first upload the old version and then do a seperate release for the new version.
2006-11-26 12:11
Tao

Registered: Aug 2002
Posts: 115
The only type of fixes I see as acceptable is fixing issues that prevent demos/games from running on certain hardware. Such as people messing with $D030 (fucking things up if you have a C=128), things that crash when you have a cartridge connected, loaders that only work on some drives, invalid assumptions about ROM content, how RAM is initialised, etc.
That is, things that are TOTALLY broken.

Going through old stuff to fix raster timing, sprite flickering, ugly graphics, etc would be history falsification. I want my memories to be real; I don't want to discover that the otherwise perfect Digital Delight suddenly has had the slight flickering in the right sideborder fixed.

I don't want Red Storm to be "re_made [...] with a little help from some harder code and a PC", as Wile Coyote puts it. In fact, I think it would kill the magic of the demo.

Sure, some demos haven't rooted themselves in my memory to the point where I remember and love the flaws just as much as the brilliance, but then again, those demos would probably not suddenly turn great just because they are fixed either...
2006-11-26 12:21
tlr

Registered: Sep 2003
Posts: 1787
Quote:
The only type of fixes I see as acceptable is fixing issues that prevent demos/games from running on certain hardware. Such as people messing with $D030 (fucking things up if you have a C=128), things that crash when you have a cartridge connected, loaders that only work on some drives, invalid assumptions about ROM content, how RAM is initialised, etc.
That is, things that are TOTALLY broken.

In my opinion it is a _must_ that the original unmodified release is added.
A fixed version must be clearly flagged as fixed, and preferably by whom.

There is no easy way to determine what was intended with the original code. Even though it looks broken on current emulatiors/hardware it might have an intention.
If the original release is manipulated, that intention is lost.
2006-11-26 12:38
Mace

Registered: May 2002
Posts: 1799
I agree that it should be clear that one is dealing with a fixed version. Also, when publishing the fixed version, also make the original unfixed version available at the same time and place.

That said, I really wouldn't mind if someone felt the need to flicker-fix something or whatever else. Everybody should do as he or she sees fit.
2006-11-27 10:22
ChristopherJam

Registered: Aug 2004
Posts: 1408
Yup, I think upload as it originally was as a minimum, then add a clearly labled 'fixed' version as a separate entity if you really want.
2006-11-27 15:45
Graham
Account closed

Registered: Dec 2002
Posts: 990
Don't fix the old stuff. History is as it is, and if you want to release better stuff, just do new releases instead of fixing old stuff.
 
... 2 posts hidden. Click here to view all posts....
 
Previous - 1 | 2 - 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
Shogoon/Elysium/MSL
Paul Bearer
Frostbyte/Artline De..
Barfly/Extend
Brittle/Dentifrice^(?)
lotus_skylight
ccr/TNSP
Perff/No Name
MAT64
katon/Lepsi De
E$G/HF ⭐ 7
Peacemaker/CENSOR/Hi..
Hairdog/BOOM!^Dream
.jetan/AI-supported ..
Digger/Elysium
Jetboy/Elysium
dstar/Fairlight
saimo/RETREAM
Conjuror
mutetus/Ald ^ Ons
Guests online: 146
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 Uncensored  (9.6)
8 Wonderland XIV  (9.6)
9 Comaland 100%  (9.6)
10 No Bounds  (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 Censor Design  (9.3)
Top Crackers
1 Mr. Z  (9.9)
2 Antitrack  (9.8)
3 OTD  (9.8)
4 Fungus  (9.8)
5 S!R  (9.8)

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