The Lantern Room exhibition — Parallax Sketchbook

SKETCHBOOK / 08 The Lantern Room · 2-week chapter

Page 1 of 3: Close the feature list

Capstone / scope

Close the feature list

Choose one final composition and one transport question your renderer answers well. A diffuse room with one area light and an explained MIS comparison is a complete study. It is more useful than a large collection of half-tested materials and a new UI.

List implemented features, learner extensions, and known limitations separately. The supplied companion covers RNG, sampling, statistics, sphere queries and a bounded diffuse image renderer with emission and a constant environment. Your contribution is the original scene and its extensions: additional materials, direct-light sampling and MIS, progressive updates, tests and evidence. Keep that distinction visible in your portfolio.

Keep original work visible: your scene, integration choices, tests, debugging record, and explanatory diagrams. Credit the RNG and primary reading, and identify supplied source excerpts. A portfolio contribution statement should let another engineer distinguish what you built from what you studied.

TRY IT IN YOUR STUDIO

Write a five-line feature freeze: one visual goal, one remaining bug, one test, one limitation, and one item deliberately deferred.

From the page to your own work

Your studio assignment.

Exhibit your original Lantern Room as a reproducible engineering study.

A finish line you can see

A finished CPU renderer subset, original room image, tests, build notes, and a five-minute technical walkthrough.

Separate supplied experiments from your implementation.
Include a tiny reproducible smoke scene and a failure case.
Record one measured tradeoff with its environment.
Credit sources and list deferred features honestly.

Keep the evidence in your weekly notebook ↗

Explain it like an engineer

Try answering aloud before opening the review notes. Use your own implementation as evidence.

Walk me through a bright outlier in your final image.

Trace the event and its PDF/throughput.
Separate a valid rare contribution from a numerical or weighting bug.
Describe how you reproduced and tested the case.

These prompts support practice; they are not an automatic assessment of your work.

A tip for this exercise

Freeze one composition and one transport question for the exhibition. Keep a tiny smoke scene beside the final image so another person can verify your build and estimator choices without waiting for a long render.

Hints, when you need them.

Try a first step, then reveal as much help as you need. Each hint gets a little more specific.

1Hint 1 · Find a starting point

Pick one camera sample you can explain from launch through display. Mark which pieces came from the companion and which scene, integration, and tests you implemented yourself.

2Hint 2 · Choose an approach

Write the reproduction settings before the walkthrough: compiler, build mode, scene revision, seed policy, image size, sample budget, and path limit. Add one failure case and one measured tradeoff.

3Hint 3 · Check your reasoning

Follow your written commands from a fresh build directory, reproduce the smoke result, and trace its chosen sample aloud. Keep any unsupported material or platform claim out of the release scope.

A small creative variation ↗

Make a second room composition with the same implemented feature set; improve the explanation before adding a new subsystem.

Optional. Save it for later if this chapter already feels full.

Coming back after a break? ↩

Run the tiny smoke scene and choose one unfinished item that can be closed in one session.

Books & principles behind this study +

Original Parallax explanations and assignments, with these works for further reading.

YOUR MARGIN NOTES

Leave yourself a good question.

What changed your mind? What would you try next?

Notes for The Lantern Room exhibition

Notes are private to this browser and saved as you write.

A CHECKPOINT, NOT A SCORE

Can you explain the idea and try the exercise yourself?

Completion records your own assessment. It does not compile or test your C++.

Companion source 10 files