Author Topic: Crash when specifics nodes are selected(v 1.10.2)  (Read 501 times)

altostratus

  • Jr. Member
  • **
  • Posts: 5
Hello,

When selecting specific nodes such as "ridged node" from "terrain generation" the "node properties" window seems to go in an endless loop (the node properties windows is flickering) crashing the software (CPU is going skyrocket from 32 % use to 100 % use). Same with the "stamping node" from "mask composition" or other "terrain generation" nodes

S1.png : Before selecting the "ridged node"
S2.png : After selecting the "ridged node"   ---> the node properties window is flickering

Windows 10 / Version : 1909 - 18363.720
Microsoft Visual C++ 2015-2019 Redistributable (x64) 14.25.28508.3
Embedded graphic card : Intel graphics HD 4600
Aditionnal graphic card : NVIDIA GeForce GTX 850M
Intel Core i5-4200H CPU @ 2.80 GHz
RAM : 10 Go DDR3

No difference between embedded or additional graphic card on that problem.

Any hints would be greatly appreciated, thanks ! ;)
« Last Edit: March 27, 2020, 05:36:56 PM by altostratus »

Danilo Nishimura

  • Sr. Member
  • ****
  • Posts: 64
  • INSANE Games Lead Technical Artist
Hi, just noticed something.
IF the dev above didn't change anything in the startup project, we're having different information on the tooltip:

Marianne Calva

  • Administrator
  • *****
  • Posts: 58
Hi Altostratus,
Indeed this is the first time we hear about such a behavior.
Some questions: have you noticed if this is specific to some nodes apart the Ridged noise? Is that 100% repro with the default project?
Do you have the same behavior when the window is maximized or not?
Can you check that the size of the text is 100% (window display settings). Should not be a trouble, but just checking.


  Marianne
« Last Edit: March 27, 2020, 07:10:49 PM by Marianne Calva »

altostratus

  • Jr. Member
  • **
  • Posts: 5
Hi Marianne,

Thank you for your prompt response!
My answers to your questions (in bold) :

Have you noticed if this is specific to some nodes apart the Ridged noise?
After some tests I have found that the following nodes are crashing the soft :
  • Terrain generation (Perlin, Billowy, Ridged & Cellular noise)
  • Terrain composition (Stamping)
  • Mask composition (Stamping)
All the other nodes don't crash the software.

Is that 100% repro with the default project?
Yes, just selecting the ridged noise node without touching anything else crash the software.

Do you have the same behavior when the window is maximized or not?
Yes

Can you check that the size of the text is 100% (window display settings).
Yes set to 100 %

I am using the last Microsoft Visual C++ redistributable available from Microsoft :  14.25.28508.3
I will run some tests using different Microsoft Visual C++ 2015-2019 Redistributable (x64) versions. I'll keep you informed.

Thanks!
« Last Edit: March 28, 2020, 02:36:31 PM by altostratus »

altostratus

  • Jr. Member
  • **
  • Posts: 5
After some tests :

  • Microsoft Visual C++ redistributable 2017 14.11.25325.0  --> crash
  • Microsoft Visual C++ redistributable 2015 14.0.23026   --> crash

Did one test changing display resolution from 1366*768 to 1280*720 --> crash

So this is not a compatibilty problem with the Microsoft Visual C++ redistributable...
And not a display resolution problem...

UPDATE :
Just found on the download page that "Microsoft .NET framework 4.7.2 must be installed before you start installing Instant Terra."
Checking my registry keys with the following command :
Code: [Select]
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP"gives me :
Code: [Select]
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\CDF
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4.0

and then the following cmd to get the version of the v4 .NET :
Code: [Select]
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full" /v versiongives me :
Code: [Select]
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full
    version    REG_SZ    4.8.03752

So with 4.8.03752, I am above your 4.7.2 requirement. Maybe that's the beginning of an answer? More tests tomorrow...

Thanks!


« Last Edit: March 29, 2020, 12:33:00 AM by altostratus »

Alexis Vaisse

  • Administrator
  • *****
  • Posts: 138
Hi,

It's really hard to see what's happening here.

We've just released a patch (Instant Terra 1.10.3) with additional checks for the Properties window.

You can download it from www.wysilab.com, install it and see if it works better on your computer.

altostratus

  • Jr. Member
  • **
  • Posts: 5
Hi Alexis!

Thank you very much for the patch!

It is a great progress, it's working way better with 1.10.3 : no more endless loop, still a loop but with a stop at the end! Almost top-notch ! ;)
I recorded my screen to show you the effect of 1.10.3 --> see attachment file.

Do you think it could come from my Microsoft .NET framework 4.8 ? Very hard to try 4.7.2 because 4.8 is embedded in Windows 10 1909 (last available) and downgrade the .NET is not possible anymore (thanks Microsoft). One solution would be to test in a virtual machine on older Windows 10 with 4.7.2 embedded.

Altostratus


Alexis Vaisse

  • Administrator
  • *****
  • Posts: 138
Hi,

Thanks a lot for the video.

Unfortunately there is little chance that the problem comes from your version of Microsoft .NET Framework.

We have no idea why the problem happens on your computer and not on other computers.

With Instant Terra 1.10.3, you should be able to work, event if it's not very convenient.
We'll try to improve the behavior of the Properties window in the next release of Instant Terra (the problem seems to come from the vertical scroll bar and we know this scroll bar sometimes doesn't behave correctly ; for instance it can be incorrectly shown or hidden).