as on the screen - I've tested with different apps and different nvidia settings. it does not appear in other apps, so it's not an nvidia panel preset issue.

the bug appears on win10 with RTX 2070/2080 and GTX 970 series. that applies to most rendering functions except cell shading. how to fix ?

the screen is full of black dots patterns that are moving around the texture.

and please, make posting screens easier, we are 2020 not 1992.

   

https://esenthel.com/forum/showthread.php?tid=9978
https://esenthel.com/forum/showthread.ph...4#pid57254

I have updated the latest drivers and physx, and the issue still appears.
... aaaand it's months already

I was searching for the strings mentioned in the threads that you send me to, but these are probably very outdated as I could not find none.

I know some devs that abandoned the idea of using Esenthel just because of this issue. All of them had the same problem with rendering in the very beginning, tested with very different hardware. Tested both binary, github, rebuilded etc itp

Don't get me wrong, but you cannot expect anybody to take months to get that single issue solved. This is critical and urgent - the very basic functionality.

I see that this forum is barely alive and I found Esenthel very promisive in the beginning but c'mon... fix this thing. I expect engine to work as default, not to dig some forums and find half a year later that the issue still exist.

So, again - how to fix the rendering issue ?
None of your solutions worked so far.

https://github.com/Esenthel/EsenthelEngine/issues/21
This is a bug in GeForce driver, not Esenthel
the workaround is to change Editor Video Options \ Advanced \ Diffuse Mode to Lambert (instead of Burley/Disney)
in code it's: D.diffuseMode(..);
Feel free to contact Nvidia for resolving this problem.

How do you imagine developers using your engine ?

Do you expect all the steam players that would buy a game and return back after first run to contact nvidia too ?

You are ridiculus, just convinced us not to take Esenthel siriously.

(11-13-2020 09:01 AM)jinx Wrote:  How do you imagine developers using your engine ?

Do you expect all the steam players that would buy a game and return back after first run to contact nvidia too ?

You are ridiculus, just convinced us not to take Esenthel siriously.

I have the same hardware configuration and have the same issue. By using the steps Esenthel provided you do have a workaround. If you are unable to develop a game with just this issue at hand, a big surprise is coming your way.

I personally find your language quite rude and not professional. The bug is in the driver and I expect the card's manufacturer to fix this issue.

Dwight is on point.

Use lambert difuse for now, i dont see what the big deal is. All esenthel could do right now is disable disney until the issue is fixed in the driver.

As if all other engines are perfect and rock solid...
+1 to Dwight

Esenthel replied to your original post, just a day after, with suggestions that worked for other people.
It is _you_ who waited 4 months to reply with a statement of: "It doesn't work. Slow developer. Terrible engine."

Regardless of who should be fixing it (Esenthel or NVidia), I do not think you can call Esenthel unreasonable here.

(11-13-2020 09:01 AM)jinx Wrote:  How do you imagine developers using your engine ?

Do you expect all the steam players that would buy a game and return back after first run to contact nvidia too ?

You are ridiculus, just convinced us not to take Esenthel siriously.

You are not the steam players though, you are supposedly a developer. one part of being developer even if you are not an engine developer is to contact NVidia or AMD when there are bugs outside your capability to fix(in this case a driver problem)

Also, there is heaps of people who contact AMD or NVidia daily when there is issues with a specific game or engine, how else do you think you have driver updates that give game specific fixes and how priorities are sorted? if there is a specific bug in the NVidia driver pertaining to one method of rendering then it is indeed NVidia's fault. Esenthel has given you workarounds but you've decided to not do anything about it.

the "I know developers" tells me you do not know actual developers.

"You are ridiculus, just convinced us not to take Esenthel siriously."

Ah, yes, tell me how much you paid for Esenthel and ontop of that expecting Unreal Engine level of an engine from a single engine developer? and please tell me how people are to take you as a serious developer with such an attitude? how much leeway do you think a single developers gets in getting companies like NVidia to do anything?