No STL Support #141

Open
opened 2026-04-12 15:38:13 +00:00 by Triager-bot · 7 comments
Owner

Original bug report: https://projects.blender.org/blender/blender/issues/157235

System Information
Operating system: Windows-10-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 5060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 577.09 Opengl Backend

Blender Version
Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash: a37564c4df7a
Worked: (newest version of Blender that worked as expected)

Short description of error
There is no STL option. Have tried looking for it under preferences/Add-Ons

Exact steps for others to reproduce the error
[I have opened Edit-Preferences-Add on. It is not listed as an option.

Original bug report: https://projects.blender.org/blender/blender/issues/157235 **System Information** Operating system: Windows-10-10.0.26200-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 5060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 577.09 Opengl Backend **Blender Version** Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash: `a37564c4df7a` Worked: (newest version of Blender that worked as expected) **Short description of error** There is no STL option. Have tried looking for it under preferences/Add-Ons **Exact steps for others to reproduce the error** [I have opened Edit-Preferences-Add on. It is not listed as an option.
Triager-bot added the Status/Needs review label 2026-04-12 15:38:13 +00:00
Author
Owner

Report is clear

LLM Reasoning

Got it, let's see. The bug report title is "No STL Support". The body says there's no STL option and they checked Add-ons in preferences. The steps are opening Edit-Preferences-Add on and it's not listed. So the description is clear about what the issue is (no STL support) and how to reproduce (check add-ons). Even though system info is there, we ignore that. The steps are present and clear. So the answer should be Yes? Wait, wait. Wait, the user wants a single word: Yes or No. Let me check again. The bug report's text description: "There is no STL option. Have tried looking for it under preferences/Add-Ons" – that's clear. Steps to reproduce: [I have opened Edit-Preferences-Add on. It is not listed as an option.] So the steps are there, and the issue is clearly described. So yes, it does clearly describe the issue.

JSON Data

{
"llm_judgement": true,
"processing_time": 11.132347
}

<!-- ID: CLARITY_CHECK --> ### Report is clear <details> <summary>LLM Reasoning</summary> Got it, let's see. The bug report title is "No STL Support". The body says there's no STL option and they checked Add-ons in preferences. The steps are opening Edit-Preferences-Add on and it's not listed. So the description is clear about what the issue is (no STL support) and how to reproduce (check add-ons). Even though system info is there, we ignore that. The steps are present and clear. So the answer should be Yes? Wait, wait. Wait, the user wants a single word: Yes or No. Let me check again. The bug report's text description: "There is no STL option. Have tried looking for it under preferences/Add-Ons" – that's clear. Steps to reproduce: [I have opened Edit-Preferences-Add on. It is not listed as an option.] So the steps are there, and the issue is clearly described. So yes, it does clearly describe the issue. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 11.132347 } </details>
Author
Owner

Report is specific

LLM Reasoning

Got it, let's analyze this bug report. The title is "No STL Support" and the body says there's no STL option, tried looking in preferences/Add-Ons. The steps are specific: opening Edit-Preferences-Add on and not finding it. So it's about a specific issue where the STL option isn't present. Wait, but let's check the definitions. Specific is about a specific feature or step, like crashing while using a specific feature. Here, the user is reporting that a specific option (STL) is missing in a specific place (Add-Ons under preferences). So it's a specific issue because it's about a particular feature not being available where expected. Wait, but maybe "generic" would be if it's vague like "crashing while rendering". But here, the report is about a specific missing option. Let me confirm: the user tried looking in a specific location (Add-Ons under preferences) and didn't find STL. So that's a specific issue. So the answer should be 'Specific'? Wait, but let's check the example. The example for specific is "Crashing while using a specific feature while rendering" — here, it's about a specific option not being present in a specific menu. So yes, specific. Wait, but maybe I'm overcomplicating. Let's see: the bug report is about a specific issue (no STL support) with exact steps (looking in Add-Ons). So the answer is Specific.

JSON Data

{
"llm_judgement": true,
"processing_time": 16.224248
}

<!-- ID: SPECIFIC_REPORT --> ### Report is specific <details> <summary>LLM Reasoning</summary> Got it, let's analyze this bug report. The title is "No STL Support" and the body says there's no STL option, tried looking in preferences/Add-Ons. The steps are specific: opening Edit-Preferences-Add on and not finding it. So it's about a specific issue where the STL option isn't present. Wait, but let's check the definitions. Specific is about a specific feature or step, like crashing while using a specific feature. Here, the user is reporting that a specific option (STL) is missing in a specific place (Add-Ons under preferences). So it's a specific issue because it's about a particular feature not being available where expected. Wait, but maybe "generic" would be if it's vague like "crashing while rendering". But here, the report is about a specific missing option. Let me confirm: the user tried looking in a specific location (Add-Ons under preferences) and didn't find STL. So that's a specific issue. So the answer should be 'Specific'? Wait, but let's check the example. The example for specific is "Crashing while using a specific feature while rendering" — here, it's about a specific option not being present in a specific menu. So yes, specific. Wait, but maybe I'm overcomplicating. Let's see: the bug report is about a specific issue (no STL support) with exact steps (looking in Add-Ons). So the answer is Specific. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 16.224248 } </details>
Author
Owner

Report flagged as NOT a duplicate by LLM

no stl support

https://projects.blender.org/blender/blender/issues/157232

System Information
Operating system: Windows-10-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 5060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 577.09 Opengl Backend

Blender Version
Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash: a37564c4df7a
Worked: (newest version of Blender that worked as expected)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the key sections: Description and Steps to Reproduce.

Bug Report 1:

  • Short description: "There is no STL option. Have tried looking for it under preferences/Add-Ons"
  • Exact steps: "I have opened Edit-Preferences-Add on. It is not listed as an option."

Bug Report 2:

  • Short description: The user left it blank, but the title is "no stl support".
  • Exact steps: Also blank, but the title suggests the same issue.

Wait, but Bug Report 2's body has placeholders (like [Please fill out...]) which means the actual details might be missing. But the title of both is about no STL support. However, Bug Report 1 has specific steps and description, while Bug Report 2 is incomplete. But the question is if they are the same issue based on the provided text.

Wait, the user's focus is on Description and Steps to Reproduce. Bug Report 1 has a clear description (no STL option) and steps (looking in preferences/add-ons). Bug Report 2's description is empty, but the title is "no stl support". But since the body of Bug Report 2 is mostly placeholders, maybe it's incomplete. However, the question is whether they are duplicates based on the given text.

Wait, let's check: Bug Report 1 says they looked for STL in preferences/add-ons and didn't find it. Bug Report 2's title is "no stl support" but the body has no steps or description filled. But maybe the user intended them to be the same? Wait, no—because Bug Report 2's steps are not provided (they have placeholders), so we can't confirm if they are the same. But wait, the problem says "based on the text description of these two bug reports". So Bug Report 1 has a clear issue: missing STL option in add-ons. Bug Report 2's title is similar but the body is incomplete. However, maybe the user made a mistake and Bug Report 2 is a duplicate but with incomplete info. But according to the instructions, if unsure, respond 'No'. Wait, but let's think again.

Wait, Bug Report 1 has specific steps: opened Edit-Preferences-Add on, not listed. Bug Report 2's steps are placeholders, so we don't know what steps they took. So even though the title is similar, the actual description and steps (which are key) in Bug Report 2 are missing. Therefore, we can't confirm they are the same. So the answer should be 'No'? Wait, no—wait, maybe the user intended Bug Report 2 to be a duplicate but forgot to fill it. But according to the given text, Bug Report 2's description and steps are not filled, so we can't say they are the same. Therefore, the answer is 'No'? Wait, but let's check again.

Wait, the first bug report has a clear issue: no STL option in add-ons. The second one has title "no stl support" but no details. So based on the provided text, we can't confirm they are duplicates because Bug Report 2 lacks the necessary details (description and steps). Therefore, the answer is 'No'.

JSON Data

{
"llm_judgement": false,
"processing_time": 34.688717,
"duplicate_report_number": "157232"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>no stl support</summary> https://projects.blender.org/blender/blender/issues/157232 **System Information** Operating system: Windows-10-10.0.26200-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 5060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 577.09 Opengl Backend **Blender Version** Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash: `a37564c4df7a` Worked: (newest version of Blender that worked as expected) **Short description of error** [Please fill out a short description of the error here] **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)] </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the key sections: Description and Steps to Reproduce. Bug Report 1: - Short description: "There is no STL option. Have tried looking for it under preferences/Add-Ons" - Exact steps: "I have opened Edit-Preferences-Add on. It is not listed as an option." Bug Report 2: - Short description: The user left it blank, but the title is "no stl support". - Exact steps: Also blank, but the title suggests the same issue. Wait, but Bug Report 2's body has placeholders (like [Please fill out...]) which means the actual details might be missing. But the title of both is about no STL support. However, Bug Report 1 has specific steps and description, while Bug Report 2 is incomplete. But the question is if they are the same issue based on the provided text. Wait, the user's focus is on Description and Steps to Reproduce. Bug Report 1 has a clear description (no STL option) and steps (looking in preferences/add-ons). Bug Report 2's description is empty, but the title is "no stl support". But since the body of Bug Report 2 is mostly placeholders, maybe it's incomplete. However, the question is whether they are duplicates based on the given text. Wait, let's check: Bug Report 1 says they looked for STL in preferences/add-ons and didn't find it. Bug Report 2's title is "no stl support" but the body has no steps or description filled. But maybe the user intended them to be the same? Wait, no—because Bug Report 2's steps are not provided (they have placeholders), so we can't confirm if they are the same. But wait, the problem says "based on the text description of these two bug reports". So Bug Report 1 has a clear issue: missing STL option in add-ons. Bug Report 2's title is similar but the body is incomplete. However, maybe the user made a mistake and Bug Report 2 is a duplicate but with incomplete info. But according to the instructions, if unsure, respond 'No'. Wait, but let's think again. Wait, Bug Report 1 has specific steps: opened Edit-Preferences-Add on, not listed. Bug Report 2's steps are placeholders, so we don't know what steps they took. So even though the title is similar, the actual description and steps (which are key) in Bug Report 2 are missing. Therefore, we can't confirm they are the same. So the answer should be 'No'? Wait, no—wait, maybe the user intended Bug Report 2 to be a duplicate but forgot to fill it. But according to the given text, Bug Report 2's description and steps are not filled, so we can't say they are the same. Therefore, the answer is 'No'? Wait, but let's check again. Wait, the first bug report has a clear issue: no STL option in add-ons. The second one has title "no stl support" but no details. So based on the provided text, we can't confirm they are duplicates because Bug Report 2 lacks the necessary details (description and steps). Therefore, the answer is 'No'. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 34.688717, "duplicate_report_number": "157232" } </details>
Author
Owner

Report flagged as NOT a duplicate by LLM

5.0 倒角找边 崩溃

https://projects.blender.org/blender/blender/issues/151130

System Information
Operating system: Windows-10-10.0.26100-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 581.80 Opengl Backend

Blender Version
Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash: a37564c4df7a
Worked: (newest version of Blender that worked as expected)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the description and steps for each.

Bug report 1 is about "No STL Support"—the user can't find the STL option in preferences/Add-Ons. The steps are opening Edit-Preferences-Add on and not finding it listed.

Bug report 2 has a title that translates to something like "5.0 Bevel edge crash" (since "倒角找边" is beveling edges, maybe). But the description and steps sections are empty or placeholder text: "[Please fill out...]" and "[Please describe...]". So there's no actual issue described here—just placeholders.

Since bug report 2 doesn't have a clear description or steps (they're just placeholders), we can't say they're the same. Bug report 1 is about missing STL support, while bug report 2 has no concrete info. So they aren't duplicates.

JSON Data

{
"llm_judgement": false,
"processing_time": 11.603299,
"duplicate_report_number": "151130"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>5.0 倒角找边 崩溃</summary> https://projects.blender.org/blender/blender/issues/151130 **System Information** Operating system: Windows-10-10.0.26100-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 581.80 Opengl Backend **Blender Version** Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash: `a37564c4df7a` Worked: (newest version of Blender that worked as expected) **Short description of error** [Please fill out a short description of the error here] **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)] </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the description and steps for each. Bug report 1 is about "No STL Support"—the user can't find the STL option in preferences/Add-Ons. The steps are opening Edit-Preferences-Add on and not finding it listed. Bug report 2 has a title that translates to something like "5.0 Bevel edge crash" (since "倒角找边" is beveling edges, maybe). But the description and steps sections are empty or placeholder text: "[Please fill out...]" and "[Please describe...]". So there's no actual issue described here—just placeholders. Since bug report 2 doesn't have a clear description or steps (they're just placeholders), we can't say they're the same. Bug report 1 is about missing STL support, while bug report 2 has no concrete info. So they aren't duplicates. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 11.603299, "duplicate_report_number": "151130" } </details>
Author
Owner

Report flagged as NOT a duplicate by LLM

Blender 5.0 beta is not bundled with GPU kernels

https://projects.blender.org/blender/blender/issues/147772

System Information
Operating system: Windows-10-10.0.26100-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090 NVIDIA Corporation NVIDIA 581.29 Vulkan Backend

Blender Version
Broken: version: 5.0.0 Beta, branch: blender-v5.0-release, commit date: 2025-10-10 00:59, hash: f4152fa946a3
Worked: 4.5

Short description of error
[No compatible GUPs found for Cycles] found in 5.0 beta, but I has no such error in 5.0 Alpha, as the screen shots show below. Thank you.

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.

Bug report 1 is about "No STL Support"—the user can't find the STL option in Add-Ons. The steps are checking Edit-Preferences-Add on, not finding it.

Bug report 2 is about "Blender 5.0 beta not bundled with GPU kernels"—the error is [No compatible GPUs found for Cycles], which is a different issue related to GPU support in Cycles rendering, not STL import/export.

The descriptions and steps are completely different: one is about missing STL add-on, the other about GPU compatibility for Cycles. So they're not the same issue. Therefore, the answer is No.

JSON Data

{
"llm_judgement": false,
"processing_time": 9.808286,
"duplicate_report_number": "147772"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Blender 5.0 beta is not bundled with GPU kernels</summary> https://projects.blender.org/blender/blender/issues/147772 **System Information** Operating system: Windows-10-10.0.26100-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090 NVIDIA Corporation NVIDIA 581.29 Vulkan Backend **Blender Version** Broken: version: 5.0.0 Beta, branch: blender-v5.0-release, commit date: 2025-10-10 00:59, hash: `f4152fa946a3` Worked: 4.5 **Short description of error** [No compatible GUPs found for Cycles] found in 5.0 beta, but I has no such error in 5.0 Alpha, as the screen shots show below. Thank you. </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce. Bug report 1 is about "No STL Support"—the user can't find the STL option in Add-Ons. The steps are checking Edit-Preferences-Add on, not finding it. Bug report 2 is about "Blender 5.0 beta not bundled with GPU kernels"—the error is [No compatible GPUs found for Cycles], which is a different issue related to GPU support in Cycles rendering, not STL import/export. The descriptions and steps are completely different: one is about missing STL add-on, the other about GPU compatibility for Cycles. So they're not the same issue. Therefore, the answer is No. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 9.808286, "duplicate_report_number": "147772" } </details>
Author
Owner

Report flagged as NOT a duplicate by LLM

Dear Blender

https://projects.blender.org/blender/blender/issues/154496

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 581.80 Opengl Backend

Blender Version
Broken: version: 5.0.1, branch: blender-v5.0-release, commit date: 2025-12-15 16:36, hash: a3db93c5b259
Worked: (newest version of Blender that worked as expected)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the key sections: Description and Steps to Reproduce.

Bug Report 1: The description is "There is no STL option. Have tried looking for it under preferences/Add-Ons" and steps are opening Edit-Preferences-Add on, not finding STL listed.

Bug Report 2: The description is empty (just "[Please fill out...]") and steps are also empty ("[Please describe...]"). So Bug Report 2 doesn't provide any details about the issue. Since we need to compare based on Description and Steps, but Bug 2 has no content there, they can't be the same. Because Bug 1 is about missing STL option in add-ons, while Bug 2 has no info. So they aren't duplicates.

JSON Data

{
"llm_judgement": false,
"processing_time": 10.348897999999998,
"duplicate_report_number": "154496"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Dear Blender</summary> https://projects.blender.org/blender/blender/issues/154496 **System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 581.80 Opengl Backend **Blender Version** Broken: version: 5.0.1, branch: blender-v5.0-release, commit date: 2025-12-15 16:36, hash: `a3db93c5b259` Worked: (newest version of Blender that worked as expected) **Short description of error** [Please fill out a short description of the error here] **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)] </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the key sections: Description and Steps to Reproduce. Bug Report 1: The description is "There is no STL option. Have tried looking for it under preferences/Add-Ons" and steps are opening Edit-Preferences-Add on, not finding STL listed. Bug Report 2: The description is empty (just "[Please fill out...]") and steps are also empty ("[Please describe...]"). So Bug Report 2 doesn't provide any details about the issue. Since we need to compare based on Description and Steps, but Bug 2 has no content there, they can't be the same. Because Bug 1 is about missing STL option in add-ons, while Bug 2 has no info. So they aren't duplicates. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 10.348897999999998, "duplicate_report_number": "154496" } </details>
Author
Owner

Report flagged as NOT a duplicate by LLM

No Navigation Bar on some UserPref editors

https://projects.blender.org/blender/blender/issues/146284

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 NVIDIA Corporation NVIDIA 580.97 Vulkan Backend

Blender Version
Broken: version: 5.0.0 Alpha, branch: main, commit date: 2025-09-14 16:58, hash: edd298105793
Worked: 4.5, 5.0 (build before few days ago)

Short description of error
There's no navigation bar on some user_preference editors in a file from just a few days ago.

I do believe that this the culprit: blender/blender#146169 but no confirmation.

Exact steps for others to reproduce the error
You can open the given file to reproduce the issue.
user_pref_bug.blend

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.

Bug report 1 is about "No STL Support"—the user can't find the STL option in preferences/Add-Ons. The steps are opening Edit-Preferences-Add on and not finding it listed.

Bug report 2 is about "No Navigation Bar on some UserPref editors"—the issue is missing navigation bar in user preference editors, with a video demo and a .blend file to reproduce.

The issues are completely different: one is about STL support (a file format import/export), the other is about UI elements (navigation bar) in user preferences. So they're not the same. Therefore, the answer is No.

JSON Data

{
"llm_judgement": false,
"processing_time": 11.084885,
"duplicate_report_number": "146284"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>No Navigation Bar on some UserPref editors</summary> https://projects.blender.org/blender/blender/issues/146284 **System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070 NVIDIA Corporation NVIDIA 580.97 Vulkan Backend **Blender Version** Broken: version: 5.0.0 Alpha, branch: main, commit date: 2025-09-14 16:58, hash: `edd298105793` Worked: 4.5, 5.0 (build before few days ago) **Short description of error** There's no navigation bar on some user_preference editors in a file from just a few days ago. I do believe that this the culprit: blender/blender#146169 but no confirmation. <video src="attachments/e6b41bfc-19af-4782-8713-d8a55acdda94" title="bug_demo.mp4" controls></video> **Exact steps for others to reproduce the error** You can open the given file to reproduce the issue. [user_pref_bug.blend](/attachments/63e4be8c-b86a-4330-b958-d9ac209f9b5f) </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce. Bug report 1 is about "No STL Support"—the user can't find the STL option in preferences/Add-Ons. The steps are opening Edit-Preferences-Add on and not finding it listed. Bug report 2 is about "No Navigation Bar on some UserPref editors"—the issue is missing navigation bar in user preference editors, with a video demo and a .blend file to reproduce. The issues are completely different: one is about STL support (a file format import/export), the other is about UI elements (navigation bar) in user preferences. So they're not the same. Therefore, the answer is No. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 11.084885, "duplicate_report_number": "146284" } </details>
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Triager-bot/test#141