Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > CSDb Entries > Release id #112378 : Coma Light 13
2012-11-06 21:59
Nightlord

Registered: Jan 2003
Posts: 131
Release id #112378 : Coma Light 13

now that we all had watched this many times, I wanted to ask if the authors can give a bit more info on the technical side of things. The demo has a really entertaining notefile but coders want more detail, so that we know what exactly we need to beat :)

For instance is the shadow casting vector realtime, or the dualpyramid with the 4 circles attached to its vertices. is that realtime?

Thanks again for a great demo.
 
... 24 posts hidden. Click here to view all posts....
 
2022-02-25 23:50
chatGPZ

Registered: Dec 2001
Posts: 11154
How though? Whatever isnt needed, gets deleted. And "loader identification string" qualifies for this for sure :)
2022-02-25 23:53
Krill

Registered: Apr 2002
Posts: 2856
Oh well, i did hide some version numbers in the code at some point, precisely because of this lame thinking. =)

(And yes, it is needed once in a while (re: forensics), just not for the demo to run.)
2022-02-26 00:01
chatGPZ

Registered: Dec 2001
Posts: 11154
> Oh well, i did hide some version numbers in the code at some point, precisely because of this lame thinking. =)

So basically disassembling the binary blob and then kill what shouldnt be there is still needed - thanks for the hint :)
2022-02-26 00:22
Krill

Registered: Apr 2002
Posts: 2856
You're obviously trolling, and the source is still open, but setting a few single bytes here and there to... something else will most likely not provide any crunching gain to speak of. =) (If that's what you're after.)
2022-02-26 00:31
chatGPZ

Registered: Dec 2001
Posts: 11154
Not trolling at all - disassembling the binary blob and then optimizing it for my needs is what i do, i am faster at that than what it would take to understand the macromessoverkill to do the same with the original source (and AFAIK its also what bitbreaker did before he made his own thing). Its also easier to integrate that way (because i am not using ca65 for anything demoish)
2022-02-26 00:41
Krill

Registered: Apr 2002
Posts: 2856
You failed so far to show me a better way of achieving the multi-platform/multi-drive support without macros, and they're generally not used just for the sake of using them.

Also you don't assemble SID tunes for your demos yourself, do you?
The loader is just another library, like SID tunes are, and is supposed to be linked as binaries anyways when you're not using ca65.
2022-02-26 00:57
chatGPZ

Registered: Dec 2001
Posts: 11154
Quote:
You failed so far to show me a better way of achieving the multi-platform/multi-drive support without macros

why would i? demo is runnung on c64, with 1541.
2022-02-26 01:24
Krill

Registered: Apr 2002
Posts: 2856
I was referring to the loader code with its "macromessoverkill". C-64 and 1541 are not its only targets.
2022-02-26 15:45
Bitbreaker

Registered: Oct 2002
Posts: 501
Back then even more memory got wasted, like with a script that was resident and loading the respective parts. $200 bytes are enough for everyone and i still stick to it. As for assembling SID tunes, there's SDI with TASS-source if you need to relocate /o\ I don't see any problem in nulling out the version number, nor would i waste any byte for it, nor did i wipe it out :-D Afaik it was a ported version that was working with acme back then, and i guess anything that was not needed was simply thrown out. Because one could as the main reason :-D
2022-02-27 12:45
Krill

Registered: Apr 2002
Posts: 2856
Quoting Bitbreaker
$200 bytes are enough for everyone and i still stick to it.
Sure, $0200 bytes for the resident loader portion is just perfect to stick it at $0200-$0400 in memory. :)

Quoting Bitbreaker
Afaik it was a ported version that was working with acme back then, and i guess anything that was not needed was simply thrown out. Because one could as the main reason :-D
I have seen "Krill's loader, version acme" elsewhere, and this explains. :D

I can see why you'd reverse-assemble the resident loader binary and port it to the assembler of your choice for some dabbling, but i don't quite see the point for the install code. (Except forking, ofc. =D)

In this case, that somebody wasn't quite thorough, though. Pointer to version string is still set up and returned by the install routine, just that it points to zeroes. :)
Previous - 1 | 2 | 3 | 4 - 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
t0m3000/HF^BOOM!^IBX
Clayboy
Mr. SID
Acidchild/Padua
zscs
Steveboy
iAN CooG/HVSC
Sixx
Guests online: 95
Top Demos
1 Next Level  (9.7)
2 Mojo  (9.7)
3 13:37  (9.7)
4 Coma Light 13  (9.7)
5 Edge of Disgrace  (9.7)
6 Aliens in Wonderland  (9.6)
7 Comaland 100%  (9.6)
8 Uncensored  (9.6)
9 No Bounds  (9.6)
10 Wonderland XIV  (9.6)
Top onefile Demos
1 Layers  (9.6)
2 Cubic Dream  (9.6)
3 Party Elk 2  (9.6)
4 Copper Booze  (9.6)
5 Rainbow Connection  (9.5)
6 It's More Fun to Com..  (9.5)
7 Dawnfall V1.1  (9.5)
8 Daah, Those Acid Pil..  (9.5)
9 Birth of a Flower  (9.5)
10 Quadrants  (9.5)
Top Groups
1 Nostalgia  (9.4)
2 Oxyron  (9.3)
3 Booze Design  (9.3)
4 Censor Design  (9.3)
5 SHAPE  (9.3)
Top Fullscreen Graphicians
1 Joe  (9.7)
2 Veto  (9.6)
3 Facet  (9.6)
4 The Sarge  (9.6)
5 Carrion  (9.5)

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