Likewise... plugged in and ready to go....getting ready for tomorrow
![]()
Likewise... plugged in and ready to go....getting ready for tomorrow
![]()
I remember coding in assembler with so strict timing that you were literally counting processor "ticks" needed to execute your code to make specific instructions run in exact moment when CRTube in monitor was pointed at exact dot/line on the screen, to switch color bank content / graphical mode / sprites bank to effectively work around hardware limits and display more colors / resolution / number of sprites on screen then it was theoretically possible by hardware specs.My first one was an Apple IIe with an extra Z80 card and USCD Pascal - at that time it was double as old than me, but I learned so much from this quite old computer, which I just wouldn't have learned, if my parents would have given me a brand new machine first. One of the positives of that was that I learned how to use assembler (6502, 8080/Z80) and modular software design (due to how UCSD Pascal was structured) - these were my first 2 years owning a computer, then my parents bought me a brand new machine - what a difference, but I would have never appreciated it that much without the experience with the Apple IIe. One of the things remaining from that time - i write compact code with a low memory footprint and I'm still writing some code segments in assembler.
Optimistic in the way, that I think FDev isn't in suicide mode - so they will deliver something.Is that the forum survival kit(ten) or are you really pessimistic optimistic?
If this didn't make you cry back in the 80's you never loved Star Trek!Oh - you want space explosions!
Got it!
Stupid Klingons!
Ah, zx spectrum days!I remember coding in assembler with so strict timing that you were literally counting processor "ticks" needed to execute your code to make specific instructions run in exact moment when CRTube in monitor was pointed at exact dot/line on the screen, to switch color bank content / graphical mode / sprites bank to effectively work around hardware limits and display more colors / resolution / number of sprites on screen then it was theoretically possible by hardware specs.
Stupid Klingons!
Messing with the timelines!You see in the Wrath of Khan it was Spock who went into the core but when Khan had his JJ revenge, it was Kirk!
Genius really.
Yeah you basically waited for some memory addresses to change value (those where bound to certain hardware states), and when this signal came, you had to execute what was required within a strict time frame to not cause flickering on screen (because writing into display memory had it's time constraints). This was all long before hardware accelerated graphics. But on the other side, this experience with how graphics were done in the early 80s showed me as well, that Mr. Braben was actually really good at that time - it wasn't that easy to make 3d graphics that fluent at that time.I remember coding in assembler with so strict timing that you were literally counting processor "ticks" needed to execute your code to make specific instructions run in exact moment when CRTube in monitor was pointed at exact dot/line on the screen, to switch color bank content / graphical mode / sprites bank to effectively work around hardware limits and display more colors / resolution / number of sprites on screen then it was theoretically possible by hardware specs.
I wish they actually embraced the absolute dystopian silliness of their universe. And enshrined that yes, your own ship/suit are snitching on you, and THAT'S HOW IT IS because the Pilot Federation is a bunch of lulz merchant who have struck gold in the past, say they got lucky with their F2P BR shooter going viral, and they used their money to build up a complete monopoly on high-tech devices that enabled them to setup a giant galaxy-scale shooter game using ships/suits as their admin tools.Exactly, that's why we also have a silencer which is an anti suit snitching. Everytime you fire, the silencer tell all the suits around to stop snitching about you.
Messing with the timelines!
Then Spock goes all Terminator on Khan... Well if you could do that in the first place, buddy, why did you wait until the end of the film???
Not wanting Star Wars folks to feel ignored...
Oh I would...It was probably all that 'special time' he was spending with Uhura ...
Almost...Ah, zx spectrum days!
we actually have the predecessor of it in our collection - a ZX81 with 16kB memory extension and a thermo printer - we cannot use it anymore though, it used cassette recorder storage and we have none of these devices anymore.Ah, zx spectrum days!
Absolutely.Yeah you basically waited for some memory addresses to change value (those where bound to certain hardware states), and when this signal came, you had to execute what was required within a strict time frame to not cause flickering on screen (because writing into display memory had it's time constraints). This was all long before hardware accelerated graphics. But on the other side, this experience with how graphics were done in the early 80s showed me as well, that Mr. Braben was actually really good at that time - it wasn't that easy to make 3d graphics that fluent at that time.
There are pretty good emulators of most of "prehistoric" computers running on Android.we actually have the predecessor of it in our collection - and ZX81 with 16kB memory extension and a thermo printer - we cannot use it anymore though, it used cassette recorder storage and we have none of these devices anymore.
Framerate was... fractional![]()