Jump to content

Recommended Posts

Posted

I have the same exact shading scene one with 30m and 10 m tall trees and one without trees, why: 

iso-shading diagram has loss line in both variant and they are very similar ?

image.thumb.png.7426656e4e10bf5de8cbe1e97fc765fa.png

image.thumb.png.f48ba290a9bca89850551625a91bded3.png

 

 

why the avg axis tilt is different between two variant?

 

 

image.thumb.png.2e22963ff2d966a3daf5bebea186f10c.png

Posted

I ran a similar scene (the only difference is that Tracking plane, horizontal N-S axis instead of Tilted Axis) and no iso shading diagram is generated: 

But I don't understand how one has tracking plane as horizontal N-S axis and the otehr one has tilted axis? 

image.png.f6fbd42986f2da7a7a551997b5abf491.png

Posted

Dear User,

It is kind of hard to analyse why your scenes yield different shading tables based on screenshots. 

For questions specific to your projects, please contact PVsyst support directly with your project : support@pvsyst.com.

Regarding your first question, the iso-shadings diagrams are not identical (clearly visible on the "40%" line at the bottom which is higher on the left graph). That seems consistent with the shadings losses being higher on the left too.

 

I won't be able to answer the second question without the actual project. Have you tried it with PVsyst 8? 

 

For the 3rd question, if the backtracking is enabled it might be possible you don't have mutual shadings at all. 

 

Posted

I haven't chosen a good word. Instead of "similar" I should have said why there are still shading when there is no tree. From your answer I realized that's might be the effect of backtracking. Although I am surprised because backtracking is activated in both runs and I have checked it few times. Could it be a glitch?

Posted

I guess, based on your scene the trees are not the major contributors to the shadings.

It could be that all your rows don't have the same height, which is not taken into account in the backtracking algorithm. It could also be a bug. At the very least you should try it with the latest PVsyst version to see if you get your expected outcome or is the shadings are still looking similar.

But again for this kind of questions you should contact PVsyst support instead of using the forum. There is only so much we can say based on a few screenshots.

Posted (edited)

 

- You are right, the terrain has been included in the scene and that's what is causing the issue. 

- PVsyst 8 crashes every time I want to import the scene and that's why I am using PVsyst 7.4 

-I have shared the project and log with the support team 4 days ago, before writing here but it seems this chat was more helpful and thank you! 

Edited by PVsystUser
Posted

Dear PVsyst User,

If you can reproduce these PVsyst crashes again, please press the <Send bug report> button of PVsyst error dialog

 

    image.png.259d91a25ce44656ee2c5713849237b9.png

 

and send us the prepared email (including the attached files) so we receive all the information needed to analyse the crash.

 

A description with the list of actions you performed to reproduce it is also very useful.

 

Best regards.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...