An error occurred whilst running SunCast. (-2)

[L Headley]

I've got a model that throws this error at me when I'm running suncast, after I click ok to this message I get an option to look at the error log which just shows me this:

[0] GSK[1217]: Invalid number of vertices (0)
[0] Failed to read GSK file!
[2] GSK[1217]: Invalid number of vertices (0)
[1] GSK[1217]: Invalid number of vertices (0)
[2] Failed to read GSK file!
[1] Failed to read GSK file!
[3] GSK[1217]: Invalid number of vertices (0)
[3] Failed to read GSK file!

The order of these changes every time I make changes and retry.

I'm guessing it thinks there is some incorrect geometry somewhere but this model used to work and I've only added a couple of simple rectangle blocks which even if I remove the error still occurs.

Some help on this would be much appreciated.

Luke

[L Headley]

*Update*

I have since found out that suncast works without the faster calculations option.

But obviously this isn't ideal as the shading we have slows the calculation down a lot.

Luke

[Tanith]

I got the same error when trying to run suncast on a model that has some complex external shading and also found that suncast would only run when the 'enable faster calculations' option is switched off (so takes much longer to run).
Is this a known issue or something that can be fixed for future versions?

[JohnM]

The number in the second set of square brackets (i.e. 1217) refers to the line number in the GSK fike.

If you navigate to this line, the line above it (that begins with IES), gives you the name and id of the offending room.

With this information you can hopefully fix/remove the room in ModelIT.

Rooms with no geometry (i.e. zero vertices) usually come from imported models.

FYI - The number in the first set of square brackets tells you the id of the process that output the error message. You can ignore it.

[PCully]

Just to confirm that we're looking to implement some changes in the next version that will feed back more information on these problems.

There's two parts to this don't let invalid geometry get created (or more likely imported) but when it does then the VE will feed back information regarding the problematic geometry so you can identify and resolve the problem.

Either way we can't ignore invalid geometry but we will treat it properly to minimise disruption to modelling

Phil

[stephentlloyd]

Thank you for posting/answering this thread. Could someone tell me how I 'navigate to this line' though?

Thanks,
Steve

[PCully]

Hi,

open the file in an application such as Notepad++ then you will get the line numbers displayed and option to jump to a line number
or copy into something like excel and it should be reflected in the row numbers

Phil