Recent Posts

21

Support - How to ... ? / Re: Is it possible to flush cached nodes? Running out of memory.

« Last post by Alexis Vaisse on January 07, 2021, 05:21:52 PM »

No there is no way to tell Instant Terra to discard the cached nodes.

Instant Terra uses an automatic discard system. For instance, it's possible to compute the three Vector Warp Blur nodes of your project with 4K terrains and masks with a computer with 16 GB of RAM, even if the total amount of memory required to store the terrains and masks of all nodes is greater than 16 GB.

To get a quick visual feedback, Instant Terra doesn't compute nodes one by one, but all nodes at the same time (kind of). That's why it requires quite a lot of RAM to run.

If the amount of available RAM is too low, Instant Terra may not be able to compute a node (you will see the waiting animation forever), but it's not supposed to crash. If it crashes, it's a bug that we have to fix.

For your specific project, you can use Multi blend nodes. For instance, you can replace 4 Blend nodes by a single Multi Blend node. The number of nodes will be reduced and the project will require less memory.

BTW congratulations for your component, the results are awesome!

22

Support - How to ... ? / Is it possible to flush cached nodes? Running out of memory.

« Last post by Flint Stryker on January 07, 2021, 03:39:09 PM »

I have a component I'm working on. It's pretty cool I think. But it uses a minimum of 126 mask or terrain nodes, including a lot of blend nodes that combine everything, and when working with a 4K terrain this causes an out of memory crash. I assume this is because my component is caching 126 4K masks/terrains, which by my calculations adds up to..... a lot of bytes. This seems unnecessary, since all of those nodes are blended in pairs, and then those pairs are blended, and so on until there is only 1 blend of all 126 nodes. Is there any way to discard the cached nodes after the blend step?

Edit: attached the terrain file in case anyone's interested.

23

Support - How to ... ? / World browser results - Wrong aspect ratio

« Last post by Marianne Calva on January 06, 2021, 04:27:47 PM »

Hi all,
this is a remark that comes back frequently about the World Browser:

"I purposefully download only square regions. However, as soon as the terrain is created, it's not square anymore."
This is because Google Maps (used for the display in the World Browser) and Open Topography (used to download the data) don’t use the same projection.
Google Maps projection respects the aspect ratio, Open Topography projection doesn’t.
The aspect ratio will be the same near the Equator but will diverge more and more when the latitude increases.

To fix this, you can add a “Change terrain size” node after your Import terrain node, to get a square terrain.
For instant, this is what you get after downloading a 100km x 100km from the World Browser:



As it’s a part of Norway, the latitude is high and the terrain is highly deformed because of the projection.
The size of the terrain is 2123 x 1082 pixels.

Then I use a “Change terrain size” node to retrieve the good aspect ratio:




You need to:
-   Uncheck the “Keep aspect ratio” check box
-   Set the same value for width and height
-   Set the same value for the quad size (30.86 meters for the “Precise” resolution (default value) and 92.59 meters for “Coarse” resolution).
-   Select “Leave heights unchanged”

  Here is the result:



Et voilà!

24

Feature requests / Re: Zoom extents option to move camera above terrain

« Last post by Alexis Vaisse on January 05, 2021, 02:02:04 PM »

Hi,

Thanks a lot for your feedback.

Your suggestion has ben validated and will be implemented in the next release of Instant Terra.

25

Support - How to ... ? / Re: Kaspersky antivirus reveals virus

« Last post by Samusam on January 05, 2021, 12:36:10 PM »

Ok i updated database Antivirus and now work. Tnks

26

Support - How to ... ? / Re: Kaspersky antivirus reveals virus

« Last post by Alexis Vaisse on January 05, 2021, 10:34:52 AM »

Kaspersky has just confirmed this is a false positive:

Sorry, it was a false detection. It will be fixed.
Thank you for your help.

I guess they now need to update their database and release a new version of it.

27

Support - How to ... ? / Re: Kaspersky antivirus reveals virus

« Last post by Alexis Vaisse on January 05, 2021, 09:03:38 AM »

Hi,

Thanks for reporting this issue.

According to Kaspersky website, it's possible to get a false detection or a false positive (as it's possible for any antivirus software).

We've just submitted a "reanalyze" request by following the instructions of this page: https://support.kaspersky.com/1870.

The request has been registered:

Hello,
Thank you for contacting Antivirus Lab.
Your request #976... has been registered and will be processed by virus analyst soon.
This is an automatically generated message. If you have additional information about this request, please reply to this e-mail.

Hopefully they will fix the issue quickly.

28

Support - How to ... ? / Kaspersky antivirus reveals virus

« Last post by Samusam on January 04, 2021, 09:04:37 PM »

The antivirus reveals a virus when I start the program.
How can I solve the problem?

29

Feature requests / Zoom extents option to move camera above terrain

« Last post by Flint Stryker on January 04, 2021, 05:01:10 PM »

I use the zoom extents feature often, usually because after switching to a different terrain node, the terrain is outside the current camera view. When this happens, it is usually because the terrain is above the camera position, and so zoom extents will fill the viewport with the underside of the current terrain, and then I have to rotate the camera to a new position to see the top side of the terrain. It would be very convenient to automatically reset the camera above the terrain when using the zoom extents feature.

30

Crash and bug reports / Re: Crash when setting component to "Internal" category.

« Last post by Flint Stryker on December 29, 2020, 06:19:05 PM »

Thanks! Unfortunate that all components are part of the main graph. Some of my components were created just to repeat processes within a component, and make no sense on their own. No harm there, of course, but it feels messy.