No Stupid Questions
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
You should go read up on the small optimizations that developers do to seemingly surpass the limits of earlier hardware. Stuff like swapping palettes in between scanlines to give the impression of more available colors, or reusing palette swapped cloud sprites in place of bushes to save on limited ram. Good engineers are really, really good. They seem to find a solution for everything.
When I was extracting sounds from the sound banks from the Nintendo 64 game F-Zero X I simply couldn't find certain sound effects. It turns out that some effects are created during runtime by taking a sound sample and applying certain effects or filters, for instance pitch shifting the sample and looping it in rapid succession.
It's a clever way to save on memory and the player doesn't notice if it's well done. The original Pokémon Red/Blue on the gameboy is an example where it's not so well done in some places. If you pay attention you'll notice that some Pokémon's battle cries are simple pitch shifts of other ones and they didn't apply any other effects to obfuscate this.
Shout out to Retro Video Game Mechanics Explained for his explanation of the entire construction of the cries.
I mean, pokemon needed 151 different battle cries. There is bound to be some overlap.
Pokemon is very optimised. In order to have the feature to give your pokemon nicknames, they had to scrap the other 105 pokemon just so they had enough space to write the code.
Need is such a strong word
I don't think they needed a single one.
The game would be equally popular with, and without the screeches.
That's exactly what I'm looking for ^^
I don't know if there are any for the switch specifically, but Modern Vintage Gamer on YouTube does a really good deep dive series he calls "impossible ports" where he covers the technicals of how a port of a game was made for a console and why it's crazy that it works at all. Portal on the N64 and halflife on the PS2 are the example that first come to mind.
Sorry, can't give you references, but the examples I used were from one of the early Mario games. I was around when the euro demo scene was still hot, so there were loads of tips and tricks they used to game the 8086-x386 hardware to create dazzling effects in real time, prior to the introduction of acceleration and dedicated graphics chipsets. It was a truly glorious time, and a great source of wonder growing up in the 90s watching the industry evolve around me.
Still blows my mind (though not in a good way) to hear a simple app or http framework nowadays needs several gigabytess just to install. Everything I mentioned used to happen in 32k-8mb of RAM.
The demo scene still exists and they still produce mind blowing stuff.
I still remember "playing"
.kkrieger, a 3d shooter fitting in a fucking 64kb exe. It did use quite a bit of RAM though.Ah yes! Projecktt or something like that. Procedurally generated models and textures, and caused some controversy due to heavy reliance on the directx API. But technically astounding, nonetheless!
Produkkt
Check out this rather extreme example: REVS on the BBC micro https://youtu.be/p5s-zbXtDoo?si=5UWDROP2HtGQSiut
Hell yeah. I think it was Spyro -- anyway, some psx game -- that had to literally go through the source code and declare integers like
ioutside of loops, so they could be reused. All so the game would fit on disc.