Papers › LSceneLLM: Enhancing Large 3D Scene Understanding Using Adaptive Visual Preferences

LSceneLLM: Enhancing Large 3D Scene Understanding Using Adaptive Visual Preferences

2 Dec 2024CVPR 2025 1arXiv:2412.01292archive 2025-07-28

Hongyan Zhi, Peihao Chen, Junyan Li, Shuailei Ma, Xinyu Sun, Tianhang Xiang, Yinjie Lei, Mingkui Tan, Chuang Gan

Research on 3D Vision-Language Models (3D-VLMs) is gaining increasing attention, which is crucial for developing embodied AI within 3D scenes, such as visual navigation and embodied question answering. Due to the high density of visual features, especially in large 3D scenes, accurately locating task-relevant visual information is challenging. Existing works attempt to segment all objects and consider their features as scene representations. However, these task-agnostic object features include much redundant information and missing details for the task-relevant area. To tackle these problems, we propose LSceneLLM, an adaptive framework that automatically identifies task-relevant areas by leveraging LLM's visual preference for different tasks, followed by a plug-and-play scene magnifier module to capture fine-grained details in focused areas. Specifically, a dense token selector examines the attention map of LLM to identify visual preferences for the instruction input. It then magnifies fine-grained details of the focusing area. An adaptive self-attention module is leveraged to fuse the coarse-grained and selected fine-grained visual information. To comprehensively evaluate the large scene understanding ability of 3D-VLMs, we further introduce a cross-room understanding benchmark, XR-Scene, which contains a series of large scene understanding tasks including XR-QA, XR-EmbodiedPlanning, and XR-SceneCaption. Experiments show that our method surpasses existing methods on both large scene understanding and existing scene understanding benchmarks. Plunging our scene magnifier module into the existing 3D-VLMs also brings significant improvement.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2412.01292")

Code

Syntology Ran 6 of 11 code samples harvested from 1 repository linked to this paper; 5 have no recorded run. Of those that ran: 1 ran · our draft was wrong; 5 ran · fixture could not drive it.

By repository: official repository: 11 samples from 1 repository, 6 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Hoyyyaard/LSceneLLM officialmentioned in papermentioned on GitHubpytorch report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested; 6 ran; 0 honoured the contract we drafted; 5 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

1ran · our draft was wrong
5ran · fixture could not drive it
5unverified

Licence: 11 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from Hoyyyaard/LSceneLLM. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

repeat_kv Hoyyyaard/LSceneLLM/models/modeling_llama.py official repository ran · fixture could not drive it fingerprinted no licence file found · pointer only · 30d7eec482ebf6b1 · report
apply_rotary_pos_emb Hoyyyaard/LSceneLLM/models/modeling_llama.py official repository ran · fixture could not drive it no licence file found · pointer only · d61c483a3c2b3156 · report
knn_point Hoyyyaard/LSceneLLM/models/dvae.py official repository ran · fixture could not drive it no licence file found · pointer only · 3fc6f6b239b211f9 · report
rotate_half Hoyyyaard/LSceneLLM/models/modeling_llama.py official repository ran · our draft was wrong fingerprinted no licence file found · pointer only · b99eea6376d1e212 · report
shift_scale_points Hoyyyaard/LSceneLLM/datasets/SceneVerseDataset.py official repository ran · fixture could not drive it no licence file found · pointer only · 818099bdffc93897 · report
square_distance Hoyyyaard/LSceneLLM/models/dvae.py official repository ran · fixture could not drive it fingerprinted no licence file found · pointer only · 3bfe172e686075cd · report
concat_all_gather Hoyyyaard/LSceneLLM/models/Point_BERT.py official repository unverified no licence file found · pointer only · 73cecca9f3575f09 · report
down_sample Hoyyyaard/LSceneLLM/datasets/SceneVerseDataset.py official repository unverified no licence file found · pointer only · e8b06f96b26a076f · report
get_missing_parameters_message Hoyyyaard/LSceneLLM/utils/checkpoint.py official repository unverified no licence file found · pointer only · 79cfc5c7bcc39b7b · report
get_unexpected_parameters_message Hoyyyaard/LSceneLLM/utils/checkpoint.py official repository unverified no licence file found · pointer only · f45b84cf72162235 · report
pc_norm Hoyyyaard/LSceneLLM/datasets/SceneVerseDataset.py official repository unverified no licence file found · pointer only · ef3c7c47e4b19514 · report

Tasks

Embodied Question AnsweringQuestion AnsweringScene UnderstandingVisual Navigation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

AttentionSoftmax

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections