3D script error - pgon status

[Richard Molnar]

Hi All,

We recently switched from AC26 to AC28 and kept getting error messages in the Report window. We learnt that it was caused by the objects we created over the years in older versions, so we decided to resave the objects we are using. I thought that selecting the object's subtype or saving the raw model as a new object would solve the problem, but it did not.

For some unknown reason, AC28 finds an error in the 3D script. It is not an error that prevents it from creating the 3D model, but it annoys me regardless. Especially because this was not highlighted as an error in the previous (AC20-AC26) versions.

When a morph in the model turns into 3D scripts, the status number becomes big. Below you can find an example:

pgon       4,  136,   4098,                 !   #136 PolyId=0

        -373,       -374,       -395,       -394

material materialAttribute_3

At least that is the only thing that jumps out from the script's lines found as errors. I don't know the reason.

Is this a bug in AC28?
Any suggestions on how to fix this would be greatly appreciated.

I considered recreating the object using tools other than morph, but there are some parts of the object that are easier to make with morph tool.

Operating system used: Windows 10

[runxel]

I am not aware on any changes in AC28 here in this regard, but the status bit is indeed extraordinarily high.

If you save a Morph as an object in AC28, does this happen too?

Maybe it was a bug in former versions and only now the GDL interpreter has started to become a bit more tight in what it flags? 🤔

Also, can you share the exact error message?

[Richard Molnar]

Hi Runxel,

The original file was created in AC22, which I always reopened in the newer versions over the years. So I did the same and opened the file I was previously working on in AC26. The screenshot was made from an object created in AC28 from a morph. Strangely, not all morphs get this, but the more morphs are in an object's original form, the more of these are present in the 3D script. Couldn't find the reason why this is happening.

Regarding the error messages, this is from the Report window after opening an object in the 3D window:

Number of processor cores : 8
----------------------------------------------------------------------
Document name : Object creator AC28 (28-03-2025)
Processed : 0 walls 1 objects 0 columns 0 beams
Start time : 29/04/2025 09:11:00
End time : 29/04/2025 09:11:00
Elapsed time : 0 seconds
----------------------------------------------------------------------
at line 5462 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 5690 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 5736 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 5908 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 5952 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 7062 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 8380 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 8542 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 8565 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 8763 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 8781 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 8994 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 9012 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 9225 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 9243 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 9464 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 9488 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 10718 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 10810 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
at line 11261 in the 3D script of file DRIVE UNIT V2.0.gsm. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)
There are several problems with this file. You can cancel the operation with Ctrl/Command - period. (MC_OPERATIVE | 2DD44C07-7743-40DD-9ACB-7493DE86D3A2)

And this is the error message that appears when running the Check script command in the 3D script window:

And the line from the script that the first error message referred to:
pgon 4, 136, 4098, ! #136 PolyId=0

Strange. Maybe it is to do with the file origin being from AC22?
When I have time, I will test this theory.