Castle Game Engine Editor haging when using Viewport

Bugs
1

Hi all,

I am experiencing crashes from Castle Game Engine Editor when using Viewports, both 2D and 3D
It is more a “not responding” loop than a real goodbye crash.
It occurs when inserting a viewport, but also when inserted and handling it sometimes.
It seemed to be solved when the project was freshly saved before inserting, but the problem reappeared even in unchanged projects.
(Sometimes it works, I followed the 3D Tutorial (“sorry we cant post links in your post”) it’s runnable and the transformations work, however it also crashed when interacting with the viewport by mouse…)

Not sure if system problem or bug, anyone can relate or any ideas why and where from?
what information would you need?

MS Win7 64bit, Nvidia GeForce GT 630…
Thank you!

2

Thank you for the report!

Hm, I don’t experience this naturally, so we’ll need more information to debug it.

  • I have edited the thread title – as I understand, the editor hangs for you at certain moments, so that’s something quite different than what we usually call “crash” :slight_smile:

  • “Sorry we cant post links in your post” – I bumped your trust on this forum, you can post now anything.

  • Can you record a video what happens, when do you experience the hanging?

  • Please upgrade the GPU drivers, there may be newer versions on https://www.nvidia.com/ .

  • Please note that we officially support only operating systems that have security support. This means Windows >= 10 now. And I see you have Windows 7. The same applies actually to other software, including WWW browsers like Firefox/Chrome, including Steam, and including NVidia drivers – you really should upgrade to a supported Windows version, 10 or 11 at this point (or some other OS naturally :slight_smile: ).

    This doesn’t mean I will not help just because you have Windows 7, but it means that it may be a difficult problem to reproduce / debug if you use an outdated software. If you can upgrade everything, it will make sure you experience the same thing as me when testing, and there’s a big chance that the issue will also disappear at this point :slight_smile: Thank you!