Cannot open Siemens JT file

Aspose.3D Product Family
1

I can’t open a jt file. I always get a Cannot open this file exception. It makes no difference if I try to open the file directly or from a stream with the specified SemensJT version file format enum.

Here is the code I tried:

var inputPath = @"...\V_11_38N435789_00_20241003.jt";
using var stream = File.OpenRead(inputPath);
var outputPath = @"...\V_11_38N435789_00_20241003.pdf";
var scene = Scene.FromFile(inputPath);
scene.Save(outputPath);

I have tried the attached files, both exit with the same exception.

jt-files.zip (1.2 MB)

2

Hi @Jan_Schlacher
These files are 10.6 and 10.5 JT files, which are not supported yet, we’ll ping you back once we have major progress on JT 10 version support immediately.

3

Hi, thanks for the fast reply! Any news on how long it will take? Is it this year, or next year? (or maybe next week? :smile: )

4

@Jan_Schlacher
We have an open ticket for JT 10 support and have already implemented most of the data structure parsing. However, we are currently blocked on some core data types due to critical errors in the official specifications, making it difficult to proceed. As a result, we’ve shifted our focus to other tasks for now, but we will revisit JT 10 periodically, and with some luck, we may be able to resolve the issues as early as next week, or it could take longer—perhaps later this year or even next year.

5

@Jan_Schlacher
JT 10 is a crucial format in the industry, and we are committed to supporting it. Despite the challenges and delays, we will continue our efforts and won’t give up until the issues are resolved.

6

Hi! Are there any updates regarding JT 10 support? I still cannot open a JT 10.3 file with the latest version (25.7).

7

Hello @Jan_Schlacher

Thank you for following up on this feature. One of the main challenges we’ve encountered is that the publicly available specification contains inconsistencies, which led to some incorrect assumptions early in the design phase. This slowed our progress as we worked to verify the correct requirements.

We’re now clarifying these details to ensure the implementation is accurate and compatible, and once this review is complete, I’ll be able to give you a more precise delivery timeline.

I appreciate your patience, and I’ll keep you updated as soon as we have firm progress to share.

Best regards.

8

Alright, thanks @lex.chou for bringing this to our attention. I really appreciate your time.