[BUG] Precomputed Visibility Warning [4.5 Preview]

Development Platform & Builds
, , , ,
1

The engine crashes and the project no longer opens when “Show No Precomputed Visibility Warning”

The solution is to find DefaultEngine.ini and set this to FALSE

2

Hello, Kenomica.

I’m not seeing a crash in my project when I have ‘Show No Precomputed Visibility Warning’ checked on. I’m in 4.4.3 on a Rolling Ball template project. Can you help me reproduce the crash?

3

This is using the 4.5 preview build through the launcher.

It appears I had “Precompute Visibility” unchecked, but had “Show No Precomputed Visibility Warning” checked - maybe this was a clash

4

It doesn’t seem as though those two interfere; I have Precompute Visibility checked off and Show No Precomputed Visibility Warning checked on. They don’t seem to cause a crash on my end.

Do you have any other ideas what might be causing the crash?

5

None at all - all I know is that by turning off “Show No Precomputed Visibility Warning” int INI file allowed me to open my project without issue - but having it set to true, I could not open the project.

6

Can you send me your crash logs and dmp files, then? As a reminder, this post explains how/where to get them.

That should let us figure out why Show No Precomputed Visibility Warning would change anything.

7

Hi Kenomica,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.

8

Hi all,

I have the similar problem, when i select “Warn about No precomputed visibility” ( It’s been two years and current version 4.12.5 so “Show No Precomputed Visibility Warning” might be changed to “Warn about No precomputed visibility”) I get a red warning in my viewport as “No Precomputed Visibility” even after i add the precomputed visiblity volumes. Any ideas how to solve this ?

9

Hello,

Due to the age of this post, we’d like to investigate this issue in a separate thread. Could you please create a new post in the Bug Reports section?

Thanks, and have a great day