Jéremie Bernier

Hello, the irregularities of the terrain makes it difficult to adjust exactly the fields on it. Please increase 'Distance to ground' progressively untill the result is satisfactory.

Hello. It means that in your scene, 179 tables have their dimensions defined 'By the sentitive sizes' instead of 'By modules'. Please refer to the following help page: https://www.pvsyst.com/help/project-design/shadings/near-shadings-3d-construction/object-types/pv-fields.html#table-size-page

Hello Irakli. You have to set orientation in 'Basic parameters' tab of your shed fields. Or you can use the 'List and management of objects' tool, select the fields and change value in orientation column.

Hello. For some reason no PV field is attached to your system orientation. If you need help to fix that, please send your 3d file and your exported project as zip to support@pvsyst.com

Hello Alexander. To better assist you, could you please send us (support@pvsyst.com) your project containing your intial dome configuration. Then we will try converting them to fixed tables and figure out what's the problem. Thanks

Hi. Please consider following pages that may help you in understanding how to match your design with the system layout: https://www.pvsyst.com/help/project-design/shadings/near-shadings-3d-construction/object-types/pv-fields.html https://www.pvsyst.com/help/project-design/orientations-in-v8/system-and-3D-attributions.html?h=definition

Hello, can you please confirm if you started by setting up the system part and you want now to design the scene with PV modules and shading objects? Or if it's the other way arround? That is, you have already your scene (either manually created or imported from a 3d file) and need guidance so as to define the system part? If you want, you can send the exported zip file of your project (Project / Export the project) and send it to support@pvsyst.com so we can have a look at it

Hello Alexander, Since version 8.05 of PVsyst, you can convert your domes and array of domes to fixed tables. As a result, you will end up with 2 orientations matching your previous dome orientation. You can achieve this by right-clicking on your dome and select 'Convert domes to fixed tables' After this you will be able to link your last 'half dome' to the relevant orientation, and have your 2 orientations mixed together on an inverter (or not) in the system.

Hello. Did you use the automatic altitude feature? Right-click on the PV fields you want to adjust at the level of the ground and select 'Automatic altitude'. Does it fit on your ground?

Hello NGD. The parameter is a positive value. The absolute value of the angles difference is checked against this parameter. My guess is that in the first case (15 - 12.6) you set a value that was sufficient to accept this difference, but not in the second case (109.9 - 93.6 = 16.3) Please check again Edit: Your error actually refer to parameter 'Tilt Spread Max'

Hello. To better assist you with your issue, please send your V7 project to support@pvsyst.com

Hello. This is a 'Portion of Cylinder' The Height of this object is editable in 'List and management of objects' This object is 'House + 2-sided roof' It's height is NOT editable. So if you have already an object in the list thas editable height (like the portion of cylinder), the height for this object will be visible but 'N/A' As for the reason why height for 'House + 2-sided roof' is not editable, I'm not sure if it's by design or if it can be changed to editable. I will inquire and will request enhancement if it's possible. Regards

Hello, some object fields apply only to certain types of objects. In this case, if you have objects of different types you may have a non editable N/A value for a given object. For instance, heigh for object house is not editable in this tool, hence the N/A. It is editable for 'Portion of cylinder', and this is why the column is present.

Hello. When you change a parameter value, just click in another field so the new value is taken into account right away. Also, I did the test - changed the Heigh above ground value - and it's been reflected after a few fractions of second in the graph. Please try again. Do you observe same behavior with other parameter - for example Pitch?

Hello, this question is already answered on multiple topics in this forum. Consider for example this one: Regards