Skip to content

renderer: build_room_kit r3 — wall/pillar mass, baked lighting, brazier shape (#83)#1683

Merged
100yenadmin merged 1 commit into
mainfrom
kit-room-r3
Jul 22, 2026
Merged

renderer: build_room_kit r3 — wall/pillar mass, baked lighting, brazier shape (#83)#1683
100yenadmin merged 1 commit into
mainfrom
kit-room-r3

Conversation

@100yenadmin

Copy link
Copy Markdown
Member

Round-3 beauty pass on extensions/renderers/unity/scripts/build_room_kit.cs (on main since #1682) for the #83 3D-first crypt. All fixes are in the C# build script; C# is uncompilable on the authoring Mac, so this is authored to mirror the proven sibling idioms and is compiled + run on the GEX44 Unity box.

Evidence. Defects measured from kit_crypt_r1.png / kit_crypt_r2.png against the target read of the painted crypt extensions/renderers/unity/plates/crypt_v36_registered.png (massive stone walls, fat carved pillars, warm fire pools on cool stone, high contrast).

Per-defect changes

  1. Walls were paper-thin planes barely taller than a person (r1/r2: knee-to-shoulder panels). PlaceWall rewritten for MASS: detect which local axis is the length (was hardcoded to local-x), fit length → one CELL edge, then scale height up to ~3.6u (WALL_H, Mathf.Max(1f, …) so a natively-taller wall is never shrunk) and thicken the short horizontal axis to ~0.8u (WALL_T; a thin panel bulks ≈3–4×, a natively-thick wall is left alone). Base re-seated on the floor as before.

  2. Pillars were toothpicks (r1/r2: slender posts). New PlacePillar replaces the native-scale Place call: widens the horizontal footprint to ~0.9 cell (PILLAR_FOOT=1.8u, keeping the round X/Z proportion) and lands height in a 3.5–5u band (PILLAR_H_MIN/MAX, clamped) → fat carved columns. Primitive fallback height bumped 3.0→4.2u.

  3. Lighting too dark both rounds (r1/r2: near-black floor, no ambient fill). Baked into the build: flat ambient (0.20,0.22,0.30); cool directional key intensity 0.7, tint (0.65,0.72,0.9), Euler(55,30,0); fire point lights range 10, intensity 3.2, color (1.0,0.62,0.28); + a low warm point light (intensity 1.4) over the sarcophagus for the painted crypt's centre glow. PurgeStrayKitLights sweeps any orphaned prior-build KitRoom_* lights so a re-run never doubles the rig (root is also destroyed+rebuilt each run → idempotent).

  4. Braziers read as glowing mushroom orbs (r1/r2: emissive sphere on a fat pedestal). BuildBrazier reshaped brazier-like: narrow dark stem cylinder + wide shallow dark bowl cylinder + a flat ember-orange emissive DISC on top (fresh Standard material instance with _EmissionColor + RealtimeEmissive), replacing the sphere. FireAnchor empty preserved.

  5. Sarcophagus read as a flat slab. If the fitted tomb is under 1.2u tall, its vertical scale is raised to ~1.3u (footprint unchanged) and re-seated on the floor — done before the lid pass so the closed lid seats on the raised top. Its warm rim comes from the sarcophagus glow light in (3).

  6. Deterministic (no RNG), material-defensive rule, summary log line + SaveScene — all preserved. // r3 round note added to the header + inline.

Diff: 1 file, +131/−28. Brace-balanced; not locally compilable (Unity Editor script) — runtime verification is on the GEX44 box.

@100yenadmin
100yenadmin enabled auto-merge (squash) July 22, 2026 14:57
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 34 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 97c05b25-3bae-4ba4-8409-eeb3b60e527f

📥 Commits

Reviewing files that changed from the base of the PR and between b56bb99 and 862c99d.

📒 Files selected for processing (1)
  • extensions/renderers/unity/scripts/build_room_kit.cs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch kit-room-r3

Comment @coderabbitai help to get the list of available commands.

@evaos-code-review-bot

evaos-code-review-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown

evaOS review status: closed or merged before review

PR: #1683 - renderer: build_room_kit r3 — wall/pillar mass, baked lighting, brazier shape (#83)
Head: 862c99d190625b7289e968e1d69e74ee5ec39d57
Updated: 2026-07-22T15:33:07.773Z

evaOS review stopped because the PR closed or merged before this queued head could be reviewed.

Automation note: agents should wait for this comment to reach completed, stale_head, closed_or_merged_before_review, skipped, or failed before treating evaOS review as settled for this head. provider_deferred means evaOS still intends to retry.

PR URL: #1683

Details: state=closed

@100yenadmin
100yenadmin merged commit 7299f05 into main Jul 22, 2026
29 of 30 checks passed
@100yenadmin
100yenadmin deleted the kit-room-r3 branch July 22, 2026 15:04

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 862c99d190

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +238 to +239
Vector3 tOff = tomb.transform.position - tbR.center;
tomb.transform.position = new Vector3(tbR.center.x + tOff.x, tOff.y - tbR.min.y, tbR.center.z + tOff.z);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Re-seat the raised sarcophagus against the floor

When a fitted tomb is shorter than 1.2u, this re-seat formula uses the post-scale world-space center/min as if they were origin-relative bounds. That moves the tomb by -tbR.center.y too far, so a base-seated tomb with a bottom at 0 ends up sunk below the floor after the vertical scale bump; the lid and glow are then placed from those lowered bounds, undermining the intended waist-high sarcophagus pass. Re-seat by applying the delta from the current world min instead of recomputing from tOff.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant