[closed] Castle Game Engine Editor haging when using Viewport

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!

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!

1 Like

bro come on, upgrade to 11, you wont miss any feature win7 is a depricated shithole by now, dont hang up on your nostalgia because I know even with win7 what a freaking nuisance it was to install updates and their damn service packs always missing or incomplete… I find win 11 (when you do a full debloat atleast via ntlite or similar tools) way way better

also I would mark this as [closed] due to it being most likely buggy due to windows 7 depricated stuff. Just saying?

Hi,

I’m marking it closed.

Reason: As I described in my answer, I’m happy to investigate / diagnose, but we need more information exactly how it appears. I’m also interested in information does it appear once upgraded to a supported system (for Windows, this means now Windows >= 10). It’s been 2 months since the original post, so I’m unsure if this is still interesting to the OP :slight_smile:

To be clear, as I mentioned, the fact that you’re using an unsupported system doesn’t mean we will not help. But, we need more information, and ideally → also information does it still occur once you upgrade to newer system.

Feel welcome to respond to this thread with more information to reopen it :slight_smile:

I found some inexplicable cge problems I had that nobody could reproduce came from the video drivers. Make sure you have the lastest available drivers that work with win7.
ps…
Not all machines can update and the nice thing about pascal that I have found is that it is good at running on older windows. I am not going to throw away my toughbook because it won’t upgrade from win7. Same will happen soon with 11 and machines that won’t update… like my dev machine says it can’t.

You do not need to throw away old machines, but beware of using systems without security support. There are real, known, exploitable vulnerabilities in operating systems whose lifetime expired. Using system without security support → it means that each time you connect to the Internet / USB / Bluetooth, download anything, or just consume any other potentially untrusted input → you’re at risk.

And personally, I found “this machine is too old to be upgraded” to be somewhat a myth. I have in garage 2 old laptops, over 15-years old, that were upgraded to Windows 10 (they serve as GitHub Actions agents now :), also for CGE purposes). Note that this is about Windows 10, which has still security support and is supported on a wider hardware range than Windows 11. (Windows 11 has higher requirements, though also they can be lifted). So you don’t need Windows 11, you only need 10. And if even Windows 10 cannot run on your machine, install Linux. 90% of Castle Game Engine has been developed on Linux, so I assure you it’s a fully-capable desktop OS :slight_smile:

Aside from security reasons, the practical thing is also that we have to “cut” support at some point to just conserve our resources in CGE. We support a lot of OS/CPUs already, and every combination implies we need access to the given machine, because eventually there will be a bug related to it. So, we need some reasonable rule to “cut off” too old systems. Cutting off systems that have been dropped by vendor (Microsoft in case of Windows) makes sense :slight_smile:

And if CGE doesn’t persuade you to upgrade, note that this decision follows almost all other software. Google Chrome, Firefox, Steam, GPU (NVidia) drivers… you will find all of them are not supported on older systems.

I hope I did persuade you to not throw the old machines, but at the same time upgrade them :slight_smile:

1 Like

My old machine is used to watch free tubi and goog check things. It doesn’t log into anywhere. have tried to upgrade it. Its twin upgrade to 10 fine, but this one won’t. It runs tubi great as is. Ain’t broke, don’t fix.

I am not saying that you should support win7. Just pointing out that they do exist for the shpend, and thinking win7 is less likely the culprit than the video drivers.

From my security background, the “ain’t broke, don’t fix” is not a good rule when it comes to security :slight_smile: You really should apply security fixes, even if things seem to work. And if you’re on system that doesn’t get security fixes, you should switch to system that does, whether it means Windows >= 10 or Linux. You connect to the Internet → that’s a security risk.

The GPU drivers may indeed be a fault here. ( Though it may still be connected to Windows version in this case — GPU vendors also “cut off” older systems and it’s possible that some bugfix just didn’t land in a the driver for older Windows. ) Input from OP is welcome here :slight_smile:

1 Like