Sidebar
Table of Contents
Corning Community College
CSCS2650 Computer Organization
PROJECT: Move The Block (MTB0)
OBJECTIVE
Using the Vircon32 Development Tools, write a C program, compile, assemble, and pack a cartridge that uses a custom texture to display a block that moves around the screen (block changes in some attribute) as a result of directional keypresses.
EDIT
You will want to go here to edit and fill in the various sections of the document:
MTB0
NOTE: this is a collaborative document between a couple of my classes this semester. That means more people editing. Be mindful that only one person can edit the document at a time.
Only task headings have been provided. You are not expected to know how to do the task given by just that description (although in some cases it can be adequately figured out). Instead, if no further information is yet present, ASK FOR DETAILS on the discord, then contribute that clarity here.
If something is present but needs polish: spruce it up.
If something is present but is incorrect: please fix it.
This is intended to be an informative, useful document that all can benefit from.
Those with prior experience, please be mindful not to gobble up all the low-hanging fruit from the newcomers.
Design your sprites / custom texture
Specifying Texture in XML
Selecting Texture
Just like in C, selecting a texture is simple
In C to select a texture we can use:
select_texture( int texture_id );
In Assembly the process is similar, as the command is simply:
out GPU_SelectedTexture #
Where the # is either the immediate value of the texture id, or a register containing the texture id
Defining Region
Defining a region is where assembly becomes much less simple, as in C one can use a variety of built in functions that handle everything, whereas in assembly we have to send the GPU every value ourselves
This looks like:
out GPU_SelectedRegion # out GPU_RegionMinX # out GPU_RegionMinY # out GPU_RegionMaxX # out GPU_RegionMaxY # out GPU_RegionHotspotX # out GPU_RegionHotspotY #
Once again with # corresponding to an immediate value or register containing the values we want to input
Selecting Region
Check for keypresses
Selecting joystick
Reading joystick value
translating read joystick value into X and Y
Playfield bounds checking
Vircon32 screen resolution
How to check if our sprite has reached a bound
How to limit our sprite from leaving the playfield
How to cause our sprite to wrap-around on the playfield
SUBMISSION
To be successful in this project, the following criteria (or their equivalent) must be met:
- Project must be submit on time, by the deadline.
- Late submissions will lose 33% credit per day, with the submission window closing on the 3rd day following the deadline.
- Executed programs must display in a manner similar to provided output
- output formatted, where applicable, must match that of project requirements
- Processing must be correct based on input given and output requested
- Output, if applicable, must be correct based on values input
- Code must be nicely and consistently indented
- Code must be consistently written, to strive for readability from having a consistent style throughout
- Code must be commented
- Any “to be implemented” comments MUST be removed
- these “to be implemented” comments, if still present at evaluation time, will result in points being deducted.
- Sufficient comments explaining the point of provided logic MUST be present
- No global variables (without instructor approval), no goto statements, no calling of main()!
- Track/version the source code in your lab46 semester repository
- Submit a copy of your source code to me using the submit tool by the deadline.
Submit Tool Usage
Let's say you have completed work on the project, and are ready to submit, you would do the following:
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.
RUBRIC
I'll be evaluating the project based on the following criteria:
78:mtb0:final tally of results (78/78) *:mtb0:submitted Vircon32 cartridge [13/13] *:mtb0:submitted XML and build script [13/13] *:mtb0:displays unique block that moves based on direction [13/13] *:mtb0:cartridge is NOT added to repository [13/13] *:mtb0:an attempt at bounds check and block adjustment [13/13] *:mtb0:committed project related changes to semester repo [13/13]
Pertaining to the collaborative authoring of project documentation
- each class member is to participate in the contribution of relevant information and formatting of the documentation
- minimal member contributions consist of:
- near the class average edits (a value of at least four productive edits)
- near the average class content change average (a value of at least 1024 bytes (absolute value of data content change))
- no zero-sum commits (adding in one commit then later removing in its entirety for the sake of satisfying edit requirements)
- adding and formatting data in an organized fashion, aiming to create an informative and readable document that anyone in the class can reference
- content contributions will be factored into a documentation coefficient, a value multiplied against your actual project submission to influence the end result:
- no contributions, co-efficient is 0.50
- less than minimum contributions is 0.75
- met minimum contribution threshold is 1.00
Additionally
- Solutions not abiding by spirit of project will be subject to a 50% overall deduction
- Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
- Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
- Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction
- Individuals who have not participated at least 50% will be subject to a 50% overall deduction.
