Sylvain Pepoli

Hello, In the next version (6.61), you will be able to select one or more materials from the imported scene (DAE and 3DS) in order to automatically convert the faces to PV fields. This way you can paint the modules with a material and they will be imported as PV fields in your scene ! This should save up a lot of time. The next version should be published next monday. There's currently a display issue not showing the string partition for polygonal fields which will be fixed too.

Thank you for reporting this, we will fix it for the next version.

Hello, We have identified the problem and fixed it, we will release a new version fixing it really soon. This doesn't happen to everyone though. Until then you can select objects in the right panel list and set coordinates in the "Move and rotate" panel at the right too.

Hello, For now you can switch to realistic view and click on the faces you want to define as PV modules to select them. In order to select multiple faces you need to hold SHIFT pressed. If you have many similar modules, you may want to select only one module (be careful to select both triangle faces to make one rectangle) and then click on the "Select -> Select similar faces" menu. Selected faces are drawn in a lighter red. Once you have selected your faces you can click on the "Create -> Transform to PV faces" menu and it should create the corresponding PV fields. In the next version of PVsyst, you will be able to select one or more materials used in the imported model in order to automatically transform faces which have this material.

Dear MicheleANE, Does it happen in the report itself or when printing it only ? Have you tried saving a new view for the report in the shading scene ? If no, please try it and tell me if it fixes it.

The shed to shed slope should be automatically set by the zone when it is filled, and tables will have an automatic baseline slope too. When using zones, we should not talk about sheds actually because it is generating single independent tables.

Hello unilhexio, I just tested it in version 6.53 and it seems to work. Are you sure that you leave the scene dialog by using the "File > Close" menu and not the "Cancel" one after saving the view ? Same question for the next dialog, make sure you use the "OK" button and not the "Cancel" one.

Hello davidv86, I would suggest that you use the "Zones of tables" tool in the shading scene. Please refer to the PVsyst help section called "Project design > Shadings > Near Shadings: 3D construction > Construction tools > Zones of tables". This way you will be able to fill any area with PV tables, and if you imported ground data the generated tables will land on it automatically.

Dear AlexMR, There is currently no support for importing tracking systems from Helios3D into PVsyst. Several users asked for this compatibility, so we are aware that this would be great. But this requires us to work with Helios3D to update the H2P file format to support it, and this takes time. We have no plans to develop it really soon, but this is something we consider on a mid-term basis.

Thank you SE2015 for your answer, as it is the only way to do it right now in PVsyst. But we implemented a new feature for the next major version (6.60) : it will allow users to fill a zone with tables which will automatically fill their row. This means that each row will only contain one table which will be stretched. Attached is a screenshot of the result. PVsyst zone filled with auto-length

Hello, We have implemented the possibility to import files from Sketchup using the open DAE (Collada) file format, and therefore from AutoCAD (using FBXConverter). This will be available in version 6.60 which should be published soon. You can already import a CSV topography in the shading scene using the menu "File > Import > CSV ground data". But this is intended to import topography, not 3D objects.

Dear chrisholcomb, Have you tried it with the latest version of PVsyst ? Can you please send us this project by email at support@pvsyst.com ?

Dear user, You can currently only generate simple PV tables when using zones of modules. If you create the trackers yourself and want to place them automatically on the ground, then you can use "Tools > Position & tilt tables on scene" but this will only be relevant if you have one tracker per field. If you have more than one tracker in a field, the result will not be correct as only the first one will be placed correctly. NB: when using trackers at different altitudes, it will not be possible to define a backtracking strategy. In PVsyst, this is only possible with regular arrays of trackers. The Backtracking strategy cannot be applied in a simple way in not-regular arrays of trackers, as the orientation of each tracker would be different (according to the neighbours), and should be calculated independently.

Dear jfish, Once you selected "Tools > Use partial shadings calculation" there will be a new group appearing in the "Groups and zones" located in the right panel (green folder icon). You have to insert the PV fields which you want to use for calculation into that group. You can do so by right-clicking it and selecting "Insert objects ..." and then select the fields in the list that pops up. After that, the active fields (the ones used for calculation) will be drawn in dark blue while the ones not included will be drawn in light blue.

Some companies use a network environment to install software on end-user computers. The basic command line to install PVsyst using msiexec is the following one : msiexec.exe /i "PVsyst6_3_4_setup.msi" /qn This command will perform a silent installation of PVsyst, upgrading any other previous version automatically. But you might also want to perform a parallel install, which you can do by adding the following parameter to the command line : msiexec.exe /i "PVsyst6_3_4_setup.msi"/qn UPGRADE=NO This will perform a silent parallel installation ! NB : The /i parameter is used when the command is executed on the computer where PVsyst will be installed, depending on the environment you may have to use /a, please refer to the Microsoft documentation for further information.

Dear customer, I sent you an e-mail to give your more details, but I will also put some useful information here. PVsyst version 6.31 is known to include a bug which may create some licence problems, switching the software into DEMO mode. To fix this issue, you just need to upgrade PVsyst to version 6.32 (or newer if your licence allows it) and everything should be fine again. We provide an online tool to download older versions which are included in your licence, here : https://www.pvsyst.com/previous-versions If your licence says that you can only use PVsyst until version 6.31, you must go to "Licence > Status & activation" and then click on "Synchronize...". After synchronization, you can restart PVsyst and download version 6.32 from the "Last available licenced version" panel.

Actually this error message and more generally file read errors at startup may happen when the situation meets the following criteria : - You are running PVsyst from a non-administrator session - UAC (User Access Control of Windows) has been completely disabled by the administrator OR only the VirtualStore has been disabled You have two solutions 1. - Either add write permissions for simple users to the PVsyst install folder (quicker but less secure). 2. - Or you can enable UAC or VirtualStore back (slower but more secure) by doing one of the following actions as an administrator : - enable UAC again in Control Panel -> User Accounts -> Change User Account Control settings, - only enable VirtualStore in Local Security Policy -> Local Policies -> Security Options and enabling User Account Control: Virtualize file and registry write failures to per-user locations Although, a fix will be included in PVsyst 6.3.5 (release date to be defined) which will allow you to keep your current configuration.

Thank you for reporting this bug. As I informed you by email, the fix to this issue will be implemented in PVsyst 6.20.

Thank you for reporting this bug. As I informed you by email, the fix to this issue will be implemented in PVsyst 6.20.