3D Scene Orientation and Parameters Reset After Reopening Project (Versions 8.0.6 and 8.0.7)

[Niken13]

Dear PVSyst Support Team,

I am facing an issue in PVSyst versions 8.0.6 and 8.0.7 where certain 3D scene parameters reset after saving and reopening a project. This issue was not present in version 7.4.8.

Issue Description while working with PVsyst version 8.0.6 ND 8.0.7:

I import the 3D scene using a .DAE file, setting the module orientation to portrait and the X-distance between modules to 0.01.

After saving and closing the project, when I reopen it, the orientation changes to landscape, and the X-distance resets to 0.02.

As a result, the number of modules in the 3D scene changes, and I am forced to re-import the 3D scene every time I open the project to restore the correct layout.

Additionally, after reopening the project, I receive a warning saying "671 tables not defined by modules"—even though all tables were correctly defined with modules when I initially imported the 3D scene. The module count in the 3D scene and in the System definitions matched perfectly before saving.
This issue only appears after reopening the project.

Please have  a look to the attachments.

Environment:
PVSyst Versions: 8.0.6 and 8.0.7 (issue present)
PVSyst Version 7.4.8: Works correctly, no reset of orientation or spacing
Import Format: .DAE file

Request:
Could you please investigate this behavior or advise on a workaround? It seems like the 3D scene parameters are not being retained properly in the newer versions, and this is disrupting the workflow.
Thank you for your assistance.

Regards,
Niken

[Jéremie Bernier]

Hello Niken. Thank you for submitting this observation. We're going to investigate this and if we can confirm the issue, we will fix it as soon as possible. Don't hesitate to request update directly at support@pvsyst.com. Regards

UPDATE: please send both projects PVsyst 7.4 and 8.0.6 since we need the definition of the subarrays to have modules dimensions

[Niken13]

2 hours ago, Jéremie Bernier said:

Hello Niken. Thank you for submitting this observation. We're going to investigate this and if we can confirm the issue, we will fix it as soon as possible. Don't hesitate to request update directly at support@pvsyst.com. Regards

UPDATE: please send both projects PVsyst 7.4 and 8.0.6 since we need the definition of the subarrays to have modules dimensions

Hi I will update directly at support@pvsyst.com.
Thank you for consideration.

[Niken13]

4 hours ago, Jéremie Bernier said:

Hello Niken. Thank you for submitting this observation. We're going to investigate this and if we can confirm the issue, we will fix it as soon as possible. Don't hesitate to request update directly at support@pvsyst.com. Regards

UPDATE: please send both projects PVsyst 7.4 and 8.0.6 since we need the definition of the subarrays to have modules dimensions

and also please let me know is it ok to import 3D scene as a .DAE file in Pvsyst version 8.0.7?

[dtarin]

While that is being investigated, in the past, these types of issues were caused by the default program assumptions overriding the project settings. The default value is 0.02. In the main PVsyst menu under advanced settings, set the default to 0.00 or 0.01. Import your shade scene where things are showing up correct, save, and reopen to check. The warning about tables not defined by modules is not material in most cases.