yep it would be great to have some meadow style grass like TwinMotion got ...
for now : try to buy some cool looking and quite low poly grass and with skatter you can make meadow like grass today ....
The crash happens indeed somewhere deep inside AMD driver in our lighting pass. We have seen it on a few feedback logs from other users with the new generation GPUs from AMD at least with Rhino and Revit. Unfortanutely we could not get any of those GPUs to have a deep look ourselves yet.
Do you have artificial lights in projects you work on?
well i am working on exteriors with daylight so dont think so / right now i am back with my old nvidia 1080ti so i just pushing my brain to remember /
btw : if you want i can help you with debugging , just send in PM
well this is enough evidence to ask enscape devs for a reaction ....
btw i am running skp 2018 pro version with preview version 3+35113 right now
hmm maybe you can make a video from that crash ? /not screen capture/
nothing happen when i just shoot randomly images in a row / 3 images /
but i am running only 432.00 drivers version on my 1080 ti
here it is image from your scene :
cau you pls save file in 2015 version ? i have 2018 version but maybe other may try it too ....
will check btw
what version of enscape you are running ?
hmm i overlooked one big detail 1080 is with or without Ti ?
because thats means how many V ram you have , i have 11 gb of ram and i never reach V ram limit with enscape / twinmotion is oppossite site of story - crashing all the time /
so can you pls check how many V ram /or system ram / it takes to enscape load your scene ? maybe this is a problem but still i dont get that whole "blackout" of your pc .
last what my thoughts are , check your system ram for errors . i think windows it self got some ram test buildin .
Thumbs UP on the Threadripper and 6800 (I'm thinking about a 5950x and 3090 along with 128Gigs ram and 4TB gen4 stuffs... but if problems with crashes continue with Enscape, I rather wait a bit on that purchase... or switch to Blender for a while and pause using Enscape while the issues are resolved... (but if tariffs make everything go up... yikes... can't win...)
[EDIT] Esncape3D runs fine while orbiting and navigating files, and using the Xbox controller to move about models in the Enscape Window, adding lights, Enscape Objects, and everything else. It only crashes when rendering when not using the FHD preset. for those of you coming into this post...[/endEdit]
On to the issue:
Yeah, I thought similar about power limits, but the Furmark stress test runs for several minutes no problems... whereas Enscape3D shows the progress bar after pressing the render button, then before it starts moving or fills up a little, bam!! Instant crashes (it takes seconds to crash from the time I click on render/export, not minutes)... so, not sure lack of power being the problem. If the forum thread I had posted here in Enscape3D forums is still available we could reference that... Just in case it is not, I am attaching the screenshots from Furmak before I did a fresh windows install back in December 2nd 2020 (and removed extra SSDs and one HD to reduce power consumption to see if that was the problem). Of of the screenshots shows the 1080 reaching 85 degrees C and it is fine and no crashes even after running for several minutes... the crashes with Enscape3D happen at around 61C with no particular number being the lucky number (not consistent temperature that would indicate it being a deciding factor).
But to be more specific, I have the Lenovo Cube Y710 that came with the upgraded PSU from Lenovo and has supported the GTX 1080 no problems... and has supported everything I've thrown at it for about 3 years... even previous versions of Enscape3D rendering at 4K...
I did some heavy rendering these past few weeks with Blender using both Eevee and Cycles renderers at 7000x3000 pixels 128 samples and some renders with 256 samples, and also thrown in some compositing to top it off on more recent renders (and as I learn how to use blender more I keep adding more objects and blender features to the renders) and no problems there. no crashes or reboots... There was one exception: I found a 3D model of mineral stones that when orbiting it once or twice rebooted the PC... I later found out more about that particular 3D model that it was made with lots of subdivisions (got it from CGTrader.com and the author gave me more info on it after I asked about that file) but that file does crash my PC all the time... I can navigate that file mostly OK...
Enscape3D now crashes in the neighborhood of 95+ % of the time when using anything other than preset FHD...
The BIOS settings do not have power limits that I can tell (see forum post below referring to a freeze rather than a reboot with the setting changed), but most Mobos will do a thermal shutdown to prevent burnouts... as it is a very simple MOBO. Nothing fancy, text based interface (nothing like the fancy interfaces with mouse and high quality graphics).
Reference Post in Lenovo forums stated compatibility of the 1080 card that came with the PC... the 1080 card in my PC is the one that came with the PC from Lenovo and the PSU as well and it designated as a Gamin PC (for resource intense software):
People who upgraded their GTX 1080 cards to 2080 TI ones had to upgrade the PSU, but otherwise... I am not finding definitive information to 100% point at lack of power as I would also be experiencing more crashes and restarts if that were the case... I mean... I really get my money's worth with this PC... I edit large photos... decompress very large 10 or 20 GB 7zip files... open very complex files with 100k + objects in CorelDraw...
I also found this post (an other similar ones) on the Lenovo Forums for this particular Model:
The error reads, vaguely (not power alone being the issue, so, thank you, Microsoft for the specificity):
"This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
So, I tried and tried to push the power on this PC to help ascertain the lack of power being the issue... no luck... it runs stable... even after plugging in several USB devices that draw power directly from the mobo... but lo-and-behold... Enscape can make it crash and restart consistently... so why not other programs like Furmark that are designed to push the system to it's limits, I wonder???
Been trying other resource intensive programs to try and force my PC to crash to see if I can collect more data on this and the only other way I found so far to make my PC crash and restart was the combination of Blender and that one particular blender file with that subdivision-heavy crystal models in it that does not make it crash consistently... So that don't help me much to collect more data.
I have been trying to open several Chrome tabs, multiple programs, CorelDraw files, Affinity Designer files, Blender rendering running of 7000x3000 files, and watching YouTube videos all at the same time, running backups and Dropbox, and encryption, etc, etc, etc... videos don't skip a beat, no dropped frames... several minutes... can't... make it... crash... It is almost becoming a hobby now.... nope, not really ;-).
I've seen other posts here in the Enscape forums indicating crashes with version 2.9x... not restarts though. All said and done, this leads me to believe my case not to be entirely unique and only isolated to my PC hardware AND may not be entirely all Enscape3D... Not sure if it is a combination of multiple factors being aligned in such a way that the result is crash and restart...
I suspect a combination of latest Windows versions (something inside Windows with its now-gazillion components that changed) AND/OR Graphics Drivers AND/OR recent versions of Enscape3D. I did not have problems a seral months ago (like six or eight months ago or along those lines) with this same PC when I was using SketchUp Make (2017) and Enscape demo version 2x and a previous version of Windows rendering at 4K no problems...
Core i7 6700 @ 3.4 GHz
nVidia GefoForce GTX 1080
Samsung EVO 860 1TB
Windows 10 Home 64bit version 20H2
I really hope it's something dumb and simple that I overlooked... I could live with that... As long as Enscape can work crash-free.
I can wait and try and troubleshoot this more as 3D modeling is not my main gig and I don't have major projects pending and no people that depend on them for anything mission-critical. Though... I do want to get to the bottom if this as... cause, you know... this is not gonna beat me :-D.
Any help appreciated. It may also help other Enscapers...
PSA: By the way, nVidia released new drivers to address security holes... upgrade as appropriate and not in the middle of projects that could break if upgrading the driver... Also, have a decent Antivirus that monitors programs all the time... not just on disk-write or only at launch... next-gen... next-gen.
well it points to power loose to me , what PSU are you use for your pc ?
for me i have x399 platform with amd threadripper 1920x cpu , 32 gb of ram and nvidia 1080ti /yes i got new amd rx 6800 too /
with two monitors and when i saving even FHD image res my powermeter from the wall peak around 450 watts but i have 750 watt seasonic PSU .
enscape can dig much performance from GPU in expenses of power , mine is from gigabyte and i can hear that coils squeaking ... /its normal /
or your MoBo have some power limit or power protection /maybe/ adjusted in bios ...
what is exactly your video card ? /brand name , number /
NVIDIA GeForce GTX 1080... crashes only happen when changing resolution from FHD to Ultra HD and also happen when using custom resolutions... anything that is not the preset "FHD"...
Side note, but related:
Been using Blender and did several renders with Eevee renderer and some with the slow Cycles rendered... made probably over 70 renders (3440x1440, 4k, 1920x1080, etc. with no problems. BUT Only once when loading a custom file uses converted materials from Cycles to Eevee rederer. In preview mode when trying to orbit the scene of that one file, it crashed my PC and restarted it.
So I am wondering now, if there are some settings in some renderers or programs that are trying to use some function or set of instructions, or loading something into parts of VRAM, that try to use something specific that is triggering a bug in the nVidia drivers or the combination of software with driver is causing the hardware to do something it is not supposed to and BAM!
So... a big puzzle, but not sure how to put it together, but there are some small clues. I had been using Enscape in trial mode months ago and an earlier version of Enscape... and earlier version of nVidia drivers and there were new Versions of Windows between then that everything worked, and now...
Additionally, I removed extra HDs and SSDs from my PC to make sure it was not a power issue. Installed Windows From scratch... looked at the temperature of the CPU, was playing graphics intensive games (Warzone and Doom at 3440x1440 settings at ultra), no problems. The recommended GPU tool to stress test it... Furmark, no problems...
So Enscape consistently crashes it with pretty much all files that are rendered at not FHD preset and that one complex blender file for Eevee... nothing else crashes the PC.
Temperature of the PGU reaches 61C or a bit higher when rendering in Blender... or playing video games, and the GPU goes 99% solid when using Eevee render in blender for several seconds.... even rendering with 256 samples and making it take longer to let the temperature go up... no crashes. I also kept the side panel open to ensure extra air flow of cool air...
I reset bios settings, did bios upgrade on the mother board... same results...
I am running out of ideas... and saving pennies to get a new system when GPUs come back down in price... in the rare case that it may be the hardware somehow degrading...
Transmutr's "GPU Info" has some interesting data, not sure if this is relevant or just too much extra (I do not have any custom settings on the nVidia Control Panel, al settings are stock config) There's tons more data, but these are the first three sections, the rest of the sections have file paths, dll paths, and tons of other info:
Graphics Feature Status
- Canvas: Hardware accelerated
- Flash: Hardware accelerated
- Flash Stage3D: Hardware accelerated
- Flash Stage3D Baseline profile: Hardware accelerated
- Compositing: Hardware accelerated
- Metal: Disabled
- Multiple Raster Threads: Enabled
- Out-of-process Rasterization: Disabled
- Hardware Protected Video Decode: Unavailable
- Rasterization: Hardware accelerated
- Skia Renderer: Disabled
- Surface Control: Disabled
- Surface Synchronization: Enabled
- Video Decode: Hardware accelerated
- Viz Service Display Compositor: Enabled
- Viz Hit-test Surface Layer: Disabled
- WebGL: Hardware accelerated
- WebGL2: Hardware accelerated
Driver Bug Workarounds
- Protected video decoding with swap chain is for Windows and Intel only
Disabled Features: protected_video_decode
- Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
- Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
- Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
- ANGLE crash on glReadPixels from incomplete cube map texture: 518889
Applied Workarounds: force_cube_complete
- Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
- Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
- Decode and Encode before generateMipmap for srgb format textures on Windows: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
- Delayed copy NV12 displays incorrect colors on NVIDIA drivers.: 728670
Applied Workarounds: disable_delayed_copy_nv12
- Hardware overlays result in black videos on non-Intel GPUs: 932879
Applied Workarounds: disable_direct_composition_layers
- Metal is only available on macOS.
Disabled Features: metal
- Viz hit-test surface layer version is not enabled by default.
Disabled Features: viz_hit_test_surface_layer
- Skia renderer is not used by default.
Disabled Features: skia_renderer
ok i found work around ,
i just switch normals to reverse and it will start casting shadows correctly ...
my background which is plane with PNG file cast shadows like whole rectangle
my background image is actually WITH alpha channel /with opacity /
!!!! from this momet i have to revert to last official version due to this bug ...
who argue against that ? /skatter strees are low poly /
high poly trees are made by maxtree for example , or other company .... but can handle that highpoly trees your video card ?
well i like that foliage , what is it ?
hmmm i got RX 6800 too
but i am using it with sketchup 2018 and no crashing when enscape starting ...
i am running 2.9.0+32504 version