| |
Raistlin
Registered: Mar 2007 Posts: 680 |
100% versions..? Party versions..? etc..?
So, I was wondering ...
Both "Delirious 11" and "X Marks the Spot" have the RESTORE key crash... and "X Marks" has a last minute glitch that crept in...
For myself I'd love to release a 100% version ... but I also kinda wouldn't - because doing so "dirties" the CSDB releases somewhat ... there'd then be something like an "X Marks Party Version" and "X Marks 100% Version" sullying the charts ........
I know Comaland had a 100% version, I can see it right now sat nicely at #2 in the charts ... but that version has more changed since the party version than what I'd likely do...
What do others think? Leave the demos alone and move on .. or go back and fix them. |
|
... 48 posts hidden. Click here to view all posts.... |
| |
Compyx
Registered: Jan 2005 Posts: 631 |
Quoting Oswaldmisc small shit, we need +h2k19 :)
Yeah, anyone can write that loader in about a week ;) |
| |
Peiselulli
Registered: Oct 2006 Posts: 81 |
@Krill : still the problem is not solved of writing values to $d011 at the wrong time (without extras checks this will happen), which results in shifting bad lines all over your screen layout. Also a problem is running into unintended VSP problems. |
| |
ChristopherJam
Registered: Aug 2004 Posts: 1409 |
Quoting MagerValpI've never understood the restore protection fetish. It's the system soft reset key, of course it causes a crash if you press it at the wrong moment. Heck, make it cleanly exit to basic if you feel the need to handle it somehow.
And if you're watching a demo, why the hell would you be pressing restore?
Hard this ^
I mean, ok, if you're not using NMI at all you can trivially disable it, but any time it's enabled you're at risk of being interrupted when you're doing something potentially time critical.. and, as the only reason to enable it is to do time critical things, you're pretty much guaranteed to be vulnerable to the restore key the moment you make anything dependent on the relevant timer interrupt. |
| |
Krill
Registered: Apr 2002 Posts: 2980 |
Quoting Peiselulli@Krill : still the problem is not solved of writing values to $d011 at the wrong time (without extras checks this will happen), which results in shifting bad lines all over your screen layout. Also a problem is running into unintended VSP problems. As i said, glitches aren't avoidable. But they are temporary. (And before you say VSP crash, okay, but that's a pretty low probability to begin with, given that VSPs don't happen in the normal case. So low this would probably only happen after frantically hitting restore repeatedly for quite some time. And then yes, the hitter really deserves a crash.) |
| |
chatGPZ
Registered: Dec 2001 Posts: 11386 |
Quote:frantically hitting restore repeatedly
<mrsid> cjam: It's the only fun I get in life! :) |
| |
Oswald
Registered: Apr 2002 Posts: 5094 |
why to do it ?
'disabling' restore was cool and secret knowledge, when we were kids, but those times are over. |
| |
Dano
Registered: Jul 2004 Posts: 234 |
Does anyone care for more than one drive on the bus in a democontext? I guess this happens far more often than anyone really pressing Restore in a demo.. ^^ |
| |
chatGPZ
Registered: Dec 2001 Posts: 11386 |
most of the time these days there are zero (real) drives on the bus :D |
| |
Raistlin
Registered: Mar 2007 Posts: 680 |
@Burglar (and other compo organisers): since it's you guys we mostly need to worry about with compos... can you guarantee no RESTORE key pressing? It might make sense to add into the notes/rules that "RESTORE key won't be pressed" ;-)
And... I'll not bother fixing the RESTORE key thing since it sounds like it's a nightmare. I -did- notice that even with what I thought should be a fix, I was getting issues on one part of the demo regardless. The part where I was doing lots of NMIs etc. So it did seem like it wouldn't be so trivial to 100% fix anyway... |
| |
Frantic
Registered: Mar 2003 Posts: 1648 |
If I will ever organize a LCP or BFP party again, I'll borrow Goto80's one fingered robot and have that press the restore key at random points in time during the compo. |
Previous - 1 | 2 | 3 | 4 | 5 | 6 - Next |