N64brew Wiki

Code segmentation guide: Difference between revisions

Page Discussion

Code segmentation guide (view source)

Revision as of 16:34, 6 August 2021

17 bytes added ,  2 years ago
m
Minor sentence fixes
VisualWikitext
(Split filesystems / data compression into separate topics, use consistent case (title case) for all subtopic titles)
m (Minor sentence fixes)
Line 1:
[[File:So_your_code_segment_is_over_1MB.png]]
 
You've been working hard on your Homebrew title, slowly adding in more content, when suddenly you realize that the game's having weird hanging issues related to any new assets that you've just added to your ROM. What gives?
 
== Why does the Code segment size matter? ==
Line 7:
When the console boots, the [[Initial Program Load]] which is contained in every ROM '''copies the first megabyte (1,048,576 bytes) of code to RAM and executes it'''. This means that if you've been linking your assets directly into your code segment, you can very quickly go past this 1MB limit.
 
Code by itself usually has a very small memory footprint (Butbut not negligible footprint, as we'll see later!), therefore, depending on how your engine is set up, you might only be required to split your assets from the main code and not have to worry about anything else.
 
== Where to go from here? ==
Line 17:
* [[Data Compression]]
 
Once you have read through those twothree pages, it is also recommended you look into techniques to split your code. It is preferable that you write your game to support at least one of these methods '''before''' you start adding too much to it, as it might become more challenging to modify such an intricate part of your engine after the fact:
 
* [[Overlays]]
Retrieved from "https://n64brew.dev/wiki/Special:MobileDiff/4184"