Sylvain Pepoli

Hello Debbie, For now PVsyst handles orientations in two ways (in the shadings part) : - it either tries to group fields into several orientations given a tolerance parameter - or it uses a single global average when you have imported a scene from an H2P file This leads to confusing situations when : - the imported H2P file defines several orientations (like domes, or multiple zones with different azimuths ...) and PVsyst makes its calculations with a single average - grouping the fields could be a lot more accurate if done manually, which can't be done yet Also, there is currently no tool to display the current orientations in the shading scene while building it. We are currently working seriously on this and hope to release it in the next few months, as this is something many users are often asking for. This new tool we will also display the orientations previously defined in the Project part to make sure both match.

Hello Thomas, It is currently not possible to apply textures to the PV panels. But this is something we will consider. In the future we would like to split to realistic view into two rendering modes : one to help building the scene and one to render it to look as good as possible. So rendering realistic textures on fields would be available in the second mode.

Hello, Don't you have a warning in the top-left panel saying you must adjust tables ?

Dear dmerlin, Please make sure your display drivers are up-to-date, you can find a tutorial detailing how to update them right there :

Since version 6.60, PVsyst uses hardware acceleration in the shadings dialogs. This increases display performance and allows drawing big scenes but it also requires that the display drivers are up-to-date. For Microsoft Surface devices, you can find updates for the system along with display drivers here : https://docs.microsoft.com/en-us/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices Find the version of your device and download the latest update from the above link.

Hello, This is strange indeed, can you send us the project on which this happens to support@pvsyst.com ?

Okay I understand and I managed to reproduce it. We'll make sure it is back like before in the next version.

Hello, Please update to version 6.62 as there was an issue in 6.61 when filling trackers with modules.

Hello Abdulrahman, Can you please tell us which version of PVsyst you are using, and also attach a screenshot of the error you get ?

Hello, We don't officially support the import from Skelion. However, you can import H2P files directly in the shading scene using the menu called "File -> Import -> Import a Helios3D file (H2P). What you can also do if you are using Sketchup is to export your scene from Sketchup as a DAE (Collada) file and then import it in PVsyst 6.62 with the menu "File -> Import -> Import a 3D scene (3DS, DAE)". If you want to keep your PV fields after the import, go to the "PV objects" tab in the next dialog and select the materials which define the PV faces.

Hello again, we've been able to identify and fix the crash in the zone sample field dialog. It will be included with PVsyst 6.62.

Okay, this is not possible yet in PVsyst. The only things you can change for multiple fields at the same time are width and length.

Hello, 1. We have identified an issue about real-time shadows in big scenes which will be fixed in the next version, please confirm that it doesn't happen anymore when it is released 2. We'll investigate this more in-depth About the scene not being saved, please make sure that you exit the dialog using the "Close" button or menu. Also make sure that you exit the next dialog by clicking on "OK", if you click "Cancel" here it will not save your changes in the scene.

Hello, Only a few windows in PVsyst are non-modal (independent from others), I am very curious to know how you managed to close the other ones independently in the past. We didn't change anything about that recently.

You're right I didn't read that the space is 10 cm, sorry. Can you please send me the scene to support@pvsyst.com ? I'll have a look why this happens.

Hello, You can disable the interpenetration check by clicking on "Tools -> Disable fields interpenetration check".

Hello, Yes there is an issue with objects not being imported from the H2P file. It will be fixed in version 6.62 to be released soon. Here's a workaround : import the H2P file in a previous version and save the scene to an SHD file, then read it from 6.60+.

Are you talking about the module in the select box of the "By modules" tab ? If yes, then you can't and it doesn't make much sense as I explained it here : http://forum.pvsyst.com/viewtopic.php?f=24&t=2878

Hello, You're right the module is not correctly reselected in the list. The other information is correctly kept though which should not cause issues. Please keep in mind that this "By modules" tab is here to help you setup your fields with the correct width and height. It is a design-only tool, it can also speed up filling subfields in the module layout but the modules defined here in the shadings have no direct impact on calculations.

Hello, If Module Layout is disabled then you have to make sure that your shadings match your system definition (PV area and orientations). If Orientation, System and Near shadings are OK, then you should be able to define the Module Layout. About the distance check between fields and objects, you can disable it by clicking on "Tools -> Disable field interpenetration check". Shadow losses only take bypass diodes into account when using the Module Layout definition in the simulation. Maybe you can't fill the fields with modules because of the margins ? If your fields have the exact same size as a module then try to set the module spacings to 0.00 and try to click on "Set modules" again.

Hello, There is an issue in the algorithm filling trackers with modules in the Module Layout part. It will be fixed in version 6.62 which should be released soon.

Hello there, It would be technically possible to make a 64 bits version of PVsyst, but it would currently take too much time for low gain, here's why : Before version 6.60, there was a known limitation when calculating shadings for big scenes which had many string partitions. The shading calculations have been refactored since in order to use less memory and be faster. So if you still have this kind of issues in version 6.60, can you please send us the project which crashes because of memory limitation ?

Hello, Could you please attach the image you are trying to load ?

Hello, Okay it's good to read that it was just a unit problem. About the other point : I think you're getting confused between the Material name (the one you check to transform objects to PV objects) and the Object name. In a scene you can have many objects which all have the same material. If objects have no name in the DAE or 3DS, we just call them "Object #...", if you checked a material to transform some objects to PV fields, then objects keep their name.

Hello Jose, About the DAE, have you tried to change the unit in the dialog which appears after the import ? If it is not found in the file, you can set it here and hopefully get the scene with the correct size. If not, please send me the file to support@pvsyst.com and I will have a look. The import may take a bit more time now, because the objects are being simplified when imported, which requires calculations.