Eric Poirrier

Hello Carlos, PVsyst simulations are limited to a maximum period of one year. Accordingly, the associated weather data file is also limited to one year, and any data beyond 365 days in a custom-imported file are ignored. If your dataset covers more than one year, you will need to run separate simulations, each using its own corresponding weather data file. Additionally, since your measurements contain missing data, I would recommend isolating the reliable and consistent measurement periods into separate files using a text editor. These cleaned files can then be reimported using the Import and Generate Custom File tool. Best regards, Eric

Dear LPeterson, Thanks for reporting the issue. We managed to reproduce it and we are working on a fix to address it. In the meantime I can only advise to roll back to a previous version of PVsyst to import weather data like you mentioned doing. Best regards, Eric

Dear Nicolas and Laura, Thank you for your post. We appreciate your feedback and your suggestions for improving PVsyst. Accessibility — including considerations for colour blindness and support for visually impaired users — is an important topic we are actively discussing, and we hope to bring improvements in this area in future versions of PVsyst. Regards, Eric

Hi Vamsee, Unfortunately, the issue with PV Fields not receiving shadow when they are set as non-casting object is still present in the latest version of PVsyst. For the PV fields to receive Shadow the PV itself need to cast Shadow (Shadow casting ON). Can you set your PVs to cast shadow? Regards, Eric

Hi Evan, Thanks for the project file. Indeed, PVsyst has a problem with the "Shadow Casting" setting on PV fields. According to the documentation (https://www.pvsyst.com/help/project-design/shadings/partial-shadings-and-calculations.html?h=casting#shadow-casting) this setting should not prevent PV fields to receive shadows from surrounding “shadow casting” objects. I have raised a software change request to address this issue. In the meantime, please turn the shadow casting for all your PV objects ON (setting by default). Cannot really think about a scenario requiring the shadow casting of PV trackers field tuned OFF anyway. As far as I can see non-PV Objects behave as expected, they cast shadow on PV fields according to their settings. Best regards, Eric

Hi Evan, Thanks for posting on the PVsyst forum. Can you check you don't have the "partial shading calculations" turned ON ? https://www.pvsyst.com/help/project-design/shadings/partial-shadings-and-calculations.html?h=partial#shadow-casting Alternatively, if you can export your project and send it to : support@pvsyst.com , I will be happy to take a look. Best regards, Eric

Dear Nikoloz, We recommend using a maximum of 50k polygons for the ground data. Exceeding this number will make PVsyst slower without significantly improving the accuracy of the simulation results. The import ground as CSV provided by PVsyst has an option to simply the geometry to meet with the 50K limit, you can either use this tool or find a way to reduce the number of polygons in your 3DS file. Regards

Hello Lois, Yes this is true, v8.0 applies the orientation selected to the PV tables created, so in your case azimuth = 23. Why don't you reset the azimuth to 0 for your orientation while you create the components of your scene, to work in an "easy" coordinate system and then use the rotate tool for the entire scene to the required azimuth ? like you use to do with v7 ? Regards, Eric