Jump to content

Recommended Posts

Posted

I just updated to version 6.62 and now whenever I create any object (shading object, pv plane, ect) PVsyst crashes.

513239379_Capture1.thumb.PNG.852246426b191ba24200542971c7c9d2.PNG

 

The object never shows up in the perspective view although I can edit the parameters. As soon as I hit close or cancel, I get the error report.

313706614_Bugreport1.PNG.91c9bb5f37c9b9c777f38b74f68ce30d.PNG

 

I tried reinstalling the program already and I am still having the same problem.

Has anyone else ran into this error? Is there any way to fix it?

  • 8 months later...
Posted

Hello dear PVsyst.

I have the same problem with crash Shading Scene Construction.

My project is very big 361MW, it is about 600 hectares. 42 840 strings with 30 modules in one string

When I do Shadings Animation I get bug report:

date/time : 2018-01-11, 13:53:28, 662ms

computer name : W1041-CZC724BC6

user name : makarevichvm

registered owner : Пользователь Windows

operating system : Windows 10 x64 build 16299

system language : Ukrainian

system up time : 5 hours 14 minutes

program up time : 6 minutes 29 seconds

processors : 8x Intel® Core i7-7700 CPU @ 3.60GHz

physical memory : 26669/32647 MB (free/total)

free disk space : (C:) 178,93 GB

display mode : 1600x900, 32 bit

process id : $2128

allocated memory : 1,50 GB

largest free block : 3,25 MB

executable : Pvsyst6.exe

exec. date/time : 2017-11-16 16:45

version : 6.6.7.0

compiled with : Delphi 10.2 Tokyo

madExcept version : 4.0.18

activation key : c786b354f9244c38abede5b1a9accb25 (end of support: 09.01.2019)

release date : 16.11.2017

contact name : Makarevich Vladimir

contact email : makarevichvm@dtek.com

callstack crc : $0040ea9d, $08748426, $08748426

exception number : 3

exception class : EOutOfMemory

exception message : Mémoire insuffisante.

How to fix this bug?

scene1.thumb.PNG.594919535e09739a3f3556d22c256d07.PNG

scene2.PNG.3e0c30626c81c00ea35b4a76b6b93f96.PNG

  • 1 month later...
Posted

Hello,

Displaying the shadings animation over one day on very big scenes can cause these kind of crashes, especially when you define modules strings.

This is due to the fact that PVsyst remembers all shadows for each animation step, so you can use the scrollbar afterwards to set an hour without having to recompute it.

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...