Sylvain Pepoli

Hello Jose, Do you confirm that it's okay now in version 6.66 ?

Hello, As solarguru suggested you can indeed delete the unwanted tables afterwards. We are aware that an "excluded-parts" feature would be a great enhancement for the tool though !

Hello Hennie, Please try to open the shadings scene and click on "Tools -> Edit orientations", and then click on "Identify orientations". This should fix the identification in the shadings. This kind of situations should not happen anymore with version 6.65 to be released soon, as this is something we have fixed already.

Hello Bris, Can you send us the files you are trying to import (CSV and DAE) to support at pvsyst.com ? We'll have a look and try to help you.

Hello, Are you talking about the modules layout you see when going to the "By modules" tab of the fields editing dialog ? If yes, then this is an information we don't import from Helios3D, that would be interesting to import it though.

@solarguru Yes, you can select your objects and then click on the menu "Edit -> Set auto. altitude", this will show a panel at the right with a few options for it.

Hello, If one module is one 3D PV field, then you will need to use the Module Layout part in order to simulate the electrical effects. You will also get the bypass diodes calculations if you do so. What was not working when you didn't separate them in Sketchup ? Could you provide us with some DAE files by mail ?

Hello, Please make sure that you have enabled 3D acceleration for the virtual machine. Also make sure that the host graphics drivers are up-to-date, more info here :

Hello there, We have identified and fixed an issue happening when loading shading scenes, modules layout parameters were not read properly and therefore PVsyst was getting an automatic layout everytime. This will be fixed in version 6.65.

Hello there, This is something which should have been fixed in version 6.64. There was indeed an issue with the displayed value of the orientation when a baseslope was defined, it was also fixed automatically after saving/reopening the variant.

Hello, The new shading scene has been tested on VMWare and VirtualBox environments without issues, we didn't test it on Hyper-V. You need to make sure that you enabled 2D/3D acceleration for the guest and that the display drivers are up-to-date and support OpenGL 2.1 on the host. With the recent improvements in the scene this is now a requirement.

Hello, Have a look at the PVsyst help. There are new sections about the new tool and three use cases detailing when and how to use it.

Hello Debbie, There have been many improvements and fixes in the shadings algorithm since version 6.60, so you should rely on the latest versions. There is indeed a lower diffuse factor in your project.

Thanks for the suggestion, The grouped modification is currently basic, on only a few parameters. But I agree that this would be helpful to have all common parameters available given the current selection.

You should be able to select the source unit in the dialog opening after the import, isn't this working ?

Hello, Well the one on top should be the latest added to the scene. There's currently no way to switch it in PVsyst but you should try to manually edit the variant file (.VCx) : look for the two "pvShdGroundImage" blocks and switch them, then save the file and close it.

Make sure you click on "Apply" after you defined the X1 and X2 points or else nothing will happen.

Hello, You can import ground data as ASCII XYZ, using the menu "File -> Import -> Import ground data (CSV)". About shading objects and PV tables, you can import scenes from Sketchup or AutoCAD in the latest version of PVsyst. You can check out the PVsyst help (F1) to get more details about these two imports.

Hello, Are you trying to use the "Module layout" part on a 60MW plant ? If yes, then you should avoid to do so as it has not been designed to handle such big installations. You can use string partitions calculations instead to be able to simulate the electrical effect on module strings.

Hello, Could you please export the shading scene (.SHD) and send it to us at support@pvsyst.com ? I just tried to fill some polygonal zones with automatic length and didn't get this kind of behaviour, so maybe there's something special in your scene.

Hello, Thanks for reporting this, the image base width is indeed reset after being read. We have fixed it for the next version.

Thank you for reporting this and for sending the file, there is indeed an issue with the baseslope being negative when it should be positive, during the conversion of objects to PV fields. We've fixed it and we'll try to release a new version soon.

My bad, it was not so obvious with the two first pictures :) Could you please send us the DAE file you used here ? (to support@pvsyst.com) We'll have a look as soon as possible once we get it.

Hello, Can you please make sure that your display drivers are up-to-date ? Here's a how-to : The fact that it's not displayed in technical mode seems to be linked with your hardware drivers.

Hello, This just looks like you switched to perspective view in 6.63, so just switch back to orthogonal view and it should look like in 6.62