Ultra Engine -The program crashes while creating global illumination(beta version)

[vinurd2]

21 minutes ago, Josh said:

No, we use a combination of precomputed and dynamic lighting, along with optional screen-space reflections. We do not use ray tracing because the performance cost is too high on most hardware today.

there may be a conflict with this one. The card checks for re-reflections, sees your method, and since it's Nvidia and their new reflection algorithms, they don't match, it immediately turns off.

[Josh]

Just now, vinurd2 said:

there may be a conflict with this one. The card checks for re-reflections, sees your method, and since it's Nvidia and their new reflection algorithms, they don't match, it immediately turns off.

No, this is definitely not the case. I just need to get my hands on a 3000 series card and test it myself.

[Josh]

Can you guys confirm that this simple scene will cause the editor to crash when you open it and select the Tools > Build Global Illumination menu item?

probetest.zip

[WuotanStudios]

yep, i can confirm, it crashes also with your simple scene.

[vinurd2]

Yes, the scene crashed

[Josh]

When you guys say it "crashes", what actually happens? Does the window just stop responding, or is there some error message?

[Josh]

Another person with a 3070 on Discord says the same thing: https://discord.com/channels/1175951843118031049/1175951843612954786/1400943755070017566

[WuotanStudios]

In my case, as soon as i click "bake" the whole software shuts down, without any error or any pop up.

[vinurd2]

10 hours ago, Josh said:

Another person with a 3070 on Discord says the same thing: https://discord.com/channels/1175951843118031049/1175951843612954786/1400943755070017566

the program just closes instantly.

[Josh]

I just paid for a 3060 and I will go pick it up today.

[Josh]

GPU: Gigabyte Nvidia 3060
Driver: 580.88
OS: Windows 10

I created a box, created a probe, selected Tools > Build Global Illumination, and it worked correctly with no problem.

I also tried loading the scene I posted here and building global illumination, and had no problem.

@vinurd @WuotanStudios Please ensure your driver is version 580.88, which was released a few days ago. Driver is located here:
https://www.nvidia.com/en-us/drivers/details/251255/

[WuotanStudios]

Hmmm.... i already had the driver version 580.88 installed.
I reinstalled it, reboot computer, tried again -> still same issue.

My OS: Win 11 Pro, 64-Bit
Graphic: NVIDIA 3060 12 GB
RAM: 64 GB
Processor: AMD Ryzen 5 7600X 6-Core a' 4.70 GHz

 

[vinurd2]

13 hours ago, Josh said:

GPU: Gigabyte Nvidia 3060
Driver: 580.88
OS: Windows 10

I created a box, created a probe, selected Tools > Build Global Illumination, and it worked correctly with no problem.

I also tried loading the scene I posted here and building global illumination, and had no problem.

@vinurd @WuotanStudios Please ensure your driver is version 580.88, which was released a few days ago. Driver is located here:
https://www.nvidia.com/en-us/drivers/details/251255/

It worked for me.I thought I was updating, but it turned out that the C drive was full and the driver just wouldn't install. I launched it from the site, deleted the excess, and everything worked.

[Josh]

@WuotanStudios I recommend performing a clean install of the driver.

[WuotanStudios]

Thanks Josh, i made a clean re-install, but in my case, it still doesn't help.
The only difference is now, that the window freezes for a half minute until it shuts down.

I might try to uninstall the whole nvidia app and all drivers, and make another clean install ....

 

[Josh]

34 minutes ago, WuotanStudios said:

Thanks Josh, i made a clean re-install, but in my case, it still doesn't help.
The only difference is now, that the window freezes for a half minute until it shuts down.

I might try to uninstall the whole nvidia app and all drivers, and make another clean install ....

Thank you for trying this. Please let me know the result if you find anything else.

[Bruddwerks]

Hi, i performed all the above steps and I have still the same issue. The engine instantly closes itself when i build GI 

System Information:

OS Name: Microsoft Windows 11 Home
Processor: Intel(R) Core(TM) i9-10850K CPU @ 3.60GHz, 3600 Mhz, 10 Core(s), 20 Logical Processor(s)
BaseBoard Product: ASUS PRIME Z490-P
DedicatedGPU: NVIDIA MSI GeForce RTX 3070 GAMING X TRIO
Installed Physical Memory (RAM): Corsair Vengeance LPX 128GB DDR4 3200Mhz

 

[vinurd2]

As I understand it, Nvidia drivers should have space on the C drive for such actions. More than 7GB. For some reason, the textures are preserved   ProgramData folder on disk C 

[Bruddwerks]

22 minutes ago, vinurd2 said:

As I understand it, Nvidia drivers should have space on the C drive for such actions. More than 7GB. For some reason, the textures are preserved   ProgramData folder on disk C 

you mean that if there is no space on c:drive the program crash?  
because i have more than 400GB of free space but still instantly close as soon as i press build.

bugs me how a 3070 is so different from a 3060 or 3080  worries me to think that this is a problem with nvidia because i dont plan to change my card anytime soon. I'm just hoping Josh can work his magic here because i know NVIDIA will not for sure! 

 

[Josh]

1 hour ago, vinurd2 said:

As I understand it, Nvidia drivers should have space on the C drive for such actions. More than 7GB. For some reason, the textures are preserved   ProgramData folder on disk C 

These are just some temporary files the routine creates.

@BruddwerksThere is one last thing you can do. In Tools > Options there is a setting like "Flush log after write". This will ensure that the file is completely written after each new line of text is added to it, so it will be done writing if a crash occurs, If you enable this, and then produce the crash again, a file will be found at C:/ProgramData/Leadwerks/Leadwerks.log that might give a little more information about what the program did before it crashed, or at least what the last thing it wrote to the log file was.

[Bruddwerks]

4 minutes ago, Josh said:

These are just some temporary files the routine creates.

@BruddwerksThere is one last thing you can do. In Tools > Options there is a setting like "Flush log after write". This will ensure that the file is completely written after each new line of text is added to it, so it will be done writing if a crash occurs, If you enable this, and then produce the crash again, a file will be found at C:/ProgramData/Leadwerks/Leadwerks.log that might give a little more information about what the program did before it crashed, or at least what the last thing it wrote to the log file was.

log.txtok tested and the last thing it wrote was the failure of saving textures. Mmm user error? 

 

[Josh]

That is interesting. I wonder what would happen if you created a folder called "C:\ProgramData\Ultra Engine"?

[Bruddwerks]

6 minutes ago, Josh said:

That is interesting. I wonder what would happen if you created a folder called "C:\ProgramData\Ultra Engine"?

THAT SOLVES IT damn ! issue is now fixed! holy smoke.... 
i just wonder... it is my system that didnt create the folder? my graphic card requires it? i did uninstalled everything and reinstalled, steam included but still was crashing.

[Josh]

I think it's probably that older versions of the program were creating that, and you probably started using it more recently, so you didn't get the folder.

I am recompiling the editor now to fix this.

[Bruddwerks]

10 minutes ago, Josh said:

I think it's probably that older versions of the program were creating that, and you probably started using it more recently, so you didn't get the folder.

I am recompiling the editor now to fix this.

thanks Josh, so cool to be part of this community