Peet wrote:Obnoxious? I thought the 360 was much louder.
And temperamental too
LOL probably because people aren't sticking griddle plates to the heatsink on the 360 and cooking steaks instead of cooking it's GPU!
No, the ADSR on the SID only affects the volume and is easily to emulate on an Amiga as it's a DAC with volume control. Now you're saying something totally different, you're now bemoaning that lack of a programmable synthesiser. Say the wrong thing, pretend you said something else. I'm seeing a pattern.silent_unicorn wrote:Amiga is basically a sample playback 4 channel DAC. ADSR = Attack Decay Sustain Release controls for the waveforms. awell as volume (all be it universal) on the C64. Pro's and con's to both but wanted effects aswell as waveform/sample definition and channel volume.
Anyone who's written any significant amount of assembler will still be slapping their forehead at this statement. And again, you're commenting on something you have no direct knowledge of. Honestly, if having an credible opinion about this is important to you go and write some assembler rather than wasting everyone's time pontificating about it it on here.silent_unicorn wrote:Writing and reading memory locations via c64 basic as the only way to control the chipset functions is hardly a structured language. In machine code you do exactly the same operation, only the syntax is different. Without understanding what memory locations do or why there is no way to do sprites/sound/char maps on the c64.
Please read what other people have said. The code is about 95% machine independent C with a few line scaling routines in asm and the game exists on the Jag, a machine with a slow CPU and custom hardware. A 68k in fact. http://www.youtube.com/watch?v=cOehRSrxexksilent_unicorn wrote:Re:Doom quotes can see the confusion, it does what it does very well on simple fast CPU designs with no custom assistance, the game design is definately NOT geared to slow CPU+custom 2d hardware design. PC specific because of the way Doom isn't proper 3D (as opposed to polygonal Quake) in x86 assembler etc.
What the suffering fuck are you banging on about? Doom supported a fuck load of custom hardware. At that time there was no single PC architecture, at least 3 different audio chips and it ran brilliantly on 386 and 486 chips using VGA cards in modes that were almost universally misunderstood. Purely for idiotic example, the audio was fucking excellent on both SoundBlaster and Ultrasound - which were entirely different and custom. Then Abrash got involved for Quake and did it all again, out of which came some of the most influential architectural techniques we've seen and that are still in use today.silent_unicorn wrote:Re:Doom quotes can see the confusion, it does what it does very well on simple fast CPU designs with no custom assistance, the game design is definately NOT geared to slow CPU+custom 2d hardware design. PC specific because of the way Doom isn't proper 3D (as opposed to polygonal Quake) in x86 assembler etc.

If it's anything like the PS2 one, bloody awful. The PS2 had no cache-coherancy, so you had to manually flush it once per frame. And the version of gcc you used to compile the code would do helpful stuff like unroll a loop giving a 10% speedup, but er, would completely trash the instruction cache and thus shafting the next bit of code.Bubba wrote: Intel make lovely compilersClosely followed by MS and IBM. I wonder what the Sony cell compiler is like in comparison to the IBM one?
silent_unicorn wrote: It's hard to say for certain whether Doom was badly coded or not, the tools and techniques now probably weren't around then.
Did the graphics need to be tightened up as well?silent_unicorn wrote: The guys who did ST port of wolfenstein and the Adoom team obviously would have tightened up the code as much as possible
Not sure. It's probably not the CPU time but the memory requirements that are the problem. Generally, to do fast sprites on the ST you used prerotation. IIRC Gauntlet used 24-pixel sprite blocks and so had probably two prerotated instances at 0 and 8 pixels offset for the background tiles; that's about 768 bytes per tile. To go to 2 pixel offsets would therefore have cost more than 4x the memory (there's three cases that need 48 pixels). That only leaves space for about 100 tiles in a 520ST, and that's just for the background tiles...silent_unicorn wrote:out of interest presumably there would be sufficient available CPU time on Gauntlet 1 on the ST to improve the horizontal scrolling significantly? That's one thing I always wondered, still a fantastic early release of the arcade game mind and one of my all time ST faves as it was pretty spot on (much better than Gauntlet 2 on either machine IMO).
Well, you can download the code and take a look if you want. I haven't looked at the Doom source myself except for the asm in the Jag version, but I've worked with the source of Q2, Q3 and Doom3, and from my experience on those I'll pretty much guarantee you that Doom will be good code.It's hard to say for certain whether Doom was badly coded or not, the tools and techniques now probably weren't around then.
Surprisingly despite having a hairdressers car I have a really terrible haircutRoobarb wrote:Can we get back to insulting Gravy's car now?