Papers › 3D-VisTA: Pre-trained Transformer for 3D Vision and Text Alignment

3D-VisTA: Pre-trained Transformer for 3D Vision and Text Alignment

8 Aug 2023ICCV 2023 1arXiv:2308.04352archive 2025-07-28

Ziyu Zhu, Xiaojian Ma, Yixin Chen, Zhidong Deng, Siyuan Huang, Qing Li

3D vision-language grounding (3D-VL) is an emerging field that aims to connect the 3D physical world with natural language, which is crucial for achieving embodied intelligence. Current 3D-VL models rely heavily on sophisticated modules, auxiliary losses, and optimization tricks, which calls for a simple and unified model. In this paper, we propose 3D-VisTA, a pre-trained Transformer for 3D Vision and Text Alignment that can be easily adapted to various downstream tasks. 3D-VisTA simply utilizes self-attention layers for both single-modal modeling and multi-modal fusion without any sophisticated task-specific design. To further enhance its performance on 3D-VL tasks, we construct ScanScribe, the first large-scale 3D scene-text pairs dataset for 3D-VL pre-training. ScanScribe contains 2,995 RGB-D scans for 1,185 unique indoor scenes originating from ScanNet and 3R-Scan datasets, along with paired 278K scene descriptions generated from existing 3D-VL tasks, templates, and GPT-3. 3D-VisTA is pre-trained on ScanScribe via masked language/object modeling and scene-text matching. It achieves state-of-the-art results on various 3D-VL tasks, ranging from visual grounding and dense captioning to question answering and situated reasoning. Moreover, 3D-VisTA demonstrates superior data efficiency, obtaining strong performance even with limited annotations during downstream task fine-tuning.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

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

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 6 code samples harvested from 1 repository linked to this paper: 4 ran (of which 2 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 1 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 6 samples from 1 repository, 4 ran (4 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

3d-vista/3D-VisTA mentioned on GitHubpytorchSyntology: 6 samples, 4 ran (0 instrument-failed) · 2 unverified 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

6 samples harvested: 4 ran (of which 2 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 1 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
1ran · violated contract
2ran
2unverified

Licence: 0 of the 6 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 3d-vista/3D-VisTA. “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. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (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 are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. 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 six 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; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. 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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

3d-vista/3D-VisTA community (archive-listed) 6 samples, 4 ran (0 instrument-failed) · 2 unverified
Registry in 34 papers model/vision/unified_encoder.py ran MIT (permissive) · af392075ecc51271 · report fixture: returned Registry · level recorded 2026-09-22
TransformerEncoderLayer in 90 papers model/vision/unified_encoder.py ran · metamorphic tier: deterministic MIT (permissive) · 8f3dbe47a6eb7b40 · report fixture: returned TransformerEncoderLayer · level recorded 2026-09-22
generate_causal_mask in 6 papers model/vision/unified_encoder.py ran · violated contract MIT (permissive) · ef7878a2c111e5e2 · report fixture: signature length:int/0/int · returned Tensor · level recorded 2026-09-22
generate_mm_casual_mask model/vision/unified_encoder.py ran · honoured contract MIT (permissive) · e4b5ceca275ea601 · report fixture: signature txt_length:int/0/int, pc_length:int/0/int · returned Tensor · level recorded 2026-09-22
UnifiedSpatialCrossEncoderV2 model/vision/unified_encoder.py unverified MIT (permissive) · 5a6f1742cb13f1fc · report
init_weights in 109 papers model/vision/unified_encoder.py unverified MIT (permissive) · 6c816339122f69e9 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for 3D-VisTA (graph method: 3D-VisTA). 8 bricks; individually on a fixture: 6 ran (of which 2 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 1 violated, 2 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. UnifiedSpatialCrossEncoderV2 entry · level 0 · unverified · 5a6f1742cb13f1fc
  2. TransformerEncoderLayer helper · level 1 · ran · 8f3dbe47a6eb7b40
  3. _get_clones helper · level 1 · ran · our draft was wrong · a8f1bbeb369e1829
  4. generate_mm_casual_mask helper · level 1 · ran · honoured contract · e4b5ceca275ea601
  5. init_weights helper · level 0 · unverified · 6c816339122f69e9
  6. _get_activation_fn helper · level 1 · ran · our draft was wrong · 0bb264f52e707e08
  7. generate_causal_mask helper · level 1 · ran · violated contract · ef7878a2c111e5e2
  8. Registry helper · level 1 · ran · af392075ecc51271

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2308.04352") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

3D Question Answering (3D-QA)Dense CaptioningQuestion AnsweringText MatchingVisual GroundingVisual Reasoning

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Question Answering (3D-QA) SQA3D 3D-VisTA Exact Match 48.5 #8 of 13 Archive leaderboard report
3D Question Answering (3D-QA) ScanQA Test w/ objects 3D-VisTA BLEU-1 - #9 of 18 Archive leaderboard report
3D Question Answering (3D-QA) ScanQA Test w/ objects 3D-VisTA BLEU-4 10.4 #9 of 18 Archive leaderboard report
3D Question Answering (3D-QA) ScanQA Test w/ objects 3D-VisTA CIDEr 69.6 #9 of 18 Archive leaderboard report
3D Question Answering (3D-QA) ScanQA Test w/ objects 3D-VisTA Exact Match 22.4 #9 of 18 Archive leaderboard report
3D Question Answering (3D-QA) ScanQA Test w/ objects 3D-VisTA METEOR 13.9 #9 of 18 Archive leaderboard report
3D Question Answering (3D-QA) ScanQA Test w/ objects 3D-VisTA ROUGE 35.7 #9 of 18 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Absolute Position EncodingsAdamAttentionAttention DropoutBPECosine AnnealingDense ConnectionsDropoutGPT-3Label SmoothingLayer NormalizationLinear LayerLinear Warmup With Cosine AnnealingMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformerWeight Decay

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