Simple Optimization Trick
-
I've never written a single line of code in assembly, and I'm now curious
A little late to this comment but there are some assembly videogames out! They are puzzles and gives you the gist of how assembly works.
I really enjoyed TIS-100. I just never got around to beating it.
-
Since it wasn't mentioned yet: https://openrct2.io/
Best way to play till this day
-
I learned z80 assembly back when the cutting edge of technology was a ZX Spectrum, and 68k assembly when I upgraded to an Amiga. That knowledge served me quite well for my early career in industrial automation - it was hard real-time coding on eZ80's and 65c02 processors, but the knowledge transfers.
Back in the day, when input got mapped straight into a memory location and the display output was another memory location, then assembly seems like magic. Read the byte they corresponds to the right-hand middle row of the keyboard, check if a certain bit is set in that byte, therefore a key is held down. Call your subroutine that copies a sequence of bytes into a known location. Boom, pressing a key updates the screen. Awesome.
Modern assembly (x64 and the like) has masses of rules about pointer alignment for the stacks, which you do so often you might as well write a macro for it. Since the OS doesn't let you write system memory any more (a good thing) then you need to make system calls and call library functions to do the same thing. You do that so often that you might as well write a macro for that as well. Boom, now your assembly looks almost exactly like C. Might as well learn that instead.
In fact, that's almost the purpose of C - a more readable, somewhat portable assembly language. Experienced C developers will know which sequence of opcodes they'd expect from any language construction. It's quite a simple mapping in that regard.
It's handy to know a little assembly occasionally, but unless you're writing eg. crypto implementations, which must take the exact same time and power to execute regardless of the input, then it's impractical for almost any purpose nowadays.
Very interesting. Thank you. I may start looking into C instead. I'll still watch a couple of videos on assembly, just for the hell of it.
-
Since it wasn't mentioned yet: https://openrct2.io/
Holy fucking shit this is the best motherfucking news this year
-
If you're curious, I recommend this channel. It often delves deep into the code to explain stuff, as well as how the hardware works. Really fascinating!
This is a very interesting channel. Thank you
-
This post did not contain any content.
Have you seen the insane complexity of modern CPUs? Ain't no one hand coding that like a 6502 in 1985.
-
A little late to this comment but there are some assembly videogames out! They are puzzles and gives you the gist of how assembly works.
I really enjoyed TIS-100. I just never got around to beating it.
Oh, that's pretty cool. Thank you
-
Have you seen the insane complexity of modern CPUs? Ain't no one hand coding that like a 6502 in 1985.
I wonder if there's anyone alive right now who would be capable of such a task.
-
Because it's true. Here's an article from Tim Sweeney from 2001:
https://web.archive.org/web/20010105180900/http://www.gamespy.com/legacy/articles/devweek_c.shtm
Mainstream application programmers switched to C in the early 80's. Game developers were slower to switch, because their small teams and focus on performance kept assembly language viable till the following decade. When id Software released DOOM, they surprised much of the industry by having no reliance on assembly code--despite excellent game performance, and by successfully cross-developing the game (in NeXTstep and DOS), then successfully porting it to an astounding variety of platforms.
having no reliance on assembly code
That's not true. The original Doom has assembly. They replaced it for the Linux source release. But by that time PC hardware was much faster ( remember back in the 90's performance doubled every 2 years) so it wasn't needed.
"Planar.asm"
-
Have you seen the insane complexity of modern CPUs? Ain't no one hand coding that like a 6502 in 1985.
Even if one did, say using x86, it would still just be interpreted by the CPU into the CPU's native opcodes, as the legacy instruction sets are interpreted/translated.
-
I wonder if there's anyone alive right now who would be capable of such a task.
If the hardware was fixed, I don't see why not.
Might not be as fast as the optimisations compilers do these days though.
If you have to support thousands of types of GPU and CPU and everything else, then fuck no.
-
Even if one did, say using x86, it would still just be interpreted by the CPU into the CPU's native opcodes, as the legacy instruction sets are interpreted/translated.
as the legacy instruction sets are interpreted/translated.
Wth? That's it, I'm sticking to the AVR then
-
Holy fucking shit this is the best motherfucking news this year
Wait, it looks like the only way to install OpenRC2 is to have already installed RC2?
Installing on my Linux machine:
OpenRC2 needs files from the original RollerCoaster Tycoon 2 or RollerCoaster Classic in order to work. Please select the directory where you installed RollerCoaster Tycoon 2 or RollerCoaster Classic.
(I haven't learned anything about how to live in the Linux environment, I barely use this machine) -
Wait, it looks like the only way to install OpenRC2 is to have already installed RC2?
Installing on my Linux machine:
OpenRC2 needs files from the original RollerCoaster Tycoon 2 or RollerCoaster Classic in order to work. Please select the directory where you installed RollerCoaster Tycoon 2 or RollerCoaster Classic.
(I haven't learned anything about how to live in the Linux environment, I barely use this machine)You just need the main game files. If you want to be legal, you can just buy RCT2 off of gog, and then just use wine to "install" the game, of which, you just copy the installed files into OpenRCT2. RCT1 is not needed, but adds more to the game.
-
You just need the main game files. If you want to be legal, you can just buy RCT2 off of gog, and then just use wine to "install" the game, of which, you just copy the installed files into OpenRCT2. RCT1 is not needed, but adds more to the game.
I guess I'll have to find a friend I can borrow from, does piratebay still have old PC games?
-
> almost
wrote on last edited by [email protected]I used those as examples but I claim that most everything was C by the early 90's. The statement that C compilers got fast which allowed it isn't true. When a new compiler came out it was always a couple of percentage points faster than the old version. Meanwhile hardware was doubling in performance every two years.
C compilers didn't need much optimization because there wasn't much performance that could be optimized into code on the simple CPUs of 1992 when Doom was being written. CPU's weren't the superscalar multi core monsters they are today. A compiler couldn't take advantage of reordering instructions to use multiple adders because there was only one.
-
I guess I'll have to find a friend I can borrow from, does piratebay still have old PC games?
wrote on last edited by [email protected]The internet archive probably has a copy. That's the way I usually go with old PC games.
I did find a site called gog-games.to , but I have never used the site, so be careful.
EDIT:
ripped.guide is a great website to find piratable stuff. Just make sure you use a VPN when doing this stuff (besides the Internet Archive, ofc) -
Wait, it looks like the only way to install OpenRC2 is to have already installed RC2?
Installing on my Linux machine:
OpenRC2 needs files from the original RollerCoaster Tycoon 2 or RollerCoaster Classic in order to work. Please select the directory where you installed RollerCoaster Tycoon 2 or RollerCoaster Classic.
(I haven't learned anything about how to live in the Linux environment, I barely use this machine)Yeah, it uses the original assets. Similiar to OpenRA for ... multiple games.
-
You couldn't pay me to write a game in C today. Our expectations of what games have to be are sky high today. You cant get away with the productivity lost writing in c, maybe c++ since its supported by a number of engines. But, im personally not aware of a single engine that uses C. I tried my hand at writing a game without an engine, and it was a hot mess. Writing low level code to make a button with text, no thanks...been there done that, in my game, you could bump into trees and get stuck...not very fun in my opinion, and thats after a few months of writing code.
Well, as a curious person myself, what programming language would you use to write a game engine in, or at least a game in?
-
Well, as a curious person myself, what programming language would you use to write a game engine in, or at least a game in?
wrote last edited by [email protected]I use Unreal Engine right now, but I've also used Godot and Unity in the past. I dont use Unity anymore, and probably won't ever bcz of some shenanigans they've pulled in the recent past. Also used pygame, and way back before I discovered game engines I tried using OpenGL and SDL directly. (Do not recommend going that route) They are way too low level for you to make any real progress, at least in a timely manner. They are what you'd want to use if you are trying to write your own game engine, but most people aren't trying to do that. Most people just want to make games.
