User Forum of Software BASEMENT

ako

User

Registered: 2020-05-29

Posts: 2

BASEMENT v2.8.1 -BASEviz Error on Windows 10

Hi,
BASEMENT v2.8.1 doesn't start when the BASEviz output is activated and I get the following message:
"Error: no override found for 'vtkTexture'. "

I use BASEMENT v2.8.1 on windows 10. Is it an issue with windows 10? I installed the version 2.8.1 again as well as the Microsoft Visual C++. But I couldn't solve the problem. The simulation works good without the BASEviz output. Thank you for your help.

Best regards
Aurélie

Marulke

User

Registered: 2015-11-14

Posts: 24

Re: BASEMENT v2.8.1 -BASEviz Error on Windows 10

Hi,
I just experienced the same problem.

I installed Basement 2.8 on a new computer running Windows 10 Enterprise version 20H2. Basement crashes at startup as ako describes, but not if I disable BASEviz.

I was previously using Windows 10 Enterprise version 1909 and did not experience this problem.

Regards
Marulke

Marulke

User

Registered: 2015-11-14

Posts: 24

Re: BASEMENT v2.8.1 -BASEviz Error on Windows 10

Hi,
after some more testing I found that this problem is not related to the version of Windows 10, but to the version of Basement. The problems I had with Basement crashing when Basewiz output was activated, was with the newest version of Basement, version 2.8.1 

I installed the previous version of Basement, version 2.8, and the problem disappeared.

So this is probably due to a bug in the latest release of Basement.

Regards,
Marulke

davidz

User

Registered: 2016-02-01

Posts: 16

Re: BASEMENT v2.8.1 -BASEviz Error on Windows 10

Hi everyone.
The original post is quite old, but as my computer was updated to Windows 11, the same problem appeared again.
I use Basement Version 2.8.1 on Windows 11 Pro 21H2.

How has this problem been solved two years ago, except downgrade to an older Basement version??

Thanks and regards,
David

Matthias Bürgler

Developer

From: Zürich

Registered: 2019-04-04

Posts: 175

Re: BASEMENT v2.8.1 -BASEviz Error on Windows 10

Hi everyone,

This was a bug of version 2.8.1, but problem was fixed with the new version 2.8.2.

Best regards
Matthias