I have a fairly complex model which I’ve not had problems with until today, I’ve worked on far bigger ones with no issues. Any idea why when I start the render it goes to a really weird looking kind of image, almost like it’s one of the render passes, but missing other. It then freezer and won’t let me export it.
Any thoughts welcome as I’m stuck and have a deadline next week.
@hbc_visual , I’m sorry to hear about that and thank you for these example screenshots.
Right away, I reckon you’ve also reset your Visual Settings already to its default settings just to check if that makes a difference? It shouldn’t be related to that as you mentioned this occurs during rendering itself and not during the live preview, though please try that briefly if not done so.
Furthermore, please make sure you’re using the latest available drivers for your graphics card and if possible re-install Enscape. Alongside definitely also submit a feedback report kindly so that we can check your log files for any hints.
Once submitted please let me know too. I’d appreciate it!
I’m just out at meetings, once back at my desk I will do as requested and send the feedback as well. I have a feeling that it might be a component that might be causing it to happen. But I have tried putting it into a new drawing file, and importing item by item.
Hi @Demian_Gutberlet & @Clemens_Musterle I’ve just sent over some log files for this one. I’m currnetly trying different way of opening the files and loading them in, I think that it could be a currupt file that is causing the issues but it’s hard to know as they seem to work fine indipendately.
I’ve now been able to work in the model, although increadibly slow at times. I have had this come up now as well, I’m on the latest NVIDIA driver so not sure what it’s wanted me to do. I’ve sent fresh log files as well.
My issue is that I’m going to need to do walkthrough videos from this project, but I’m struggling to even get the model to render at present. I had turned the quality slidder down to draft to see if it helped, but I didn’t realise when you render, it comes out as draft, (I thought it would come out at normal quality defined in the output tab) hence why the quality doens’t look great in the image.
I can’t remember the name but there’s a plugin that lists all the textures and importantly their pixel sizes in the model.
To my thinking you’re running out of mem on the gpu and there’s a good chance it’s caused by excessive textures, it might just be 1 that’s tripping things up.
@Paul_Russam Legend for dropping me this message, I hadn’t thought about the texture impact, I was looking at it from a component point of view, however it might be that it’s a component with a texture that’s tripping this bad boy out. Sometimes I wish things didn’t have a limit and could just work, day and half of work time wasted, live and learn! Will let you know if I fix it and what was causing it when I do for good old learning!
Hi Paul, yer I did some digging as I couldn’t get the materials tool to show the textures, but the material resizer is a game changes, I will be using this on all projects going forward as I have some really high res textures, but don’t need them for most jobs! So far the model is working, but I still think there are some gremlins inside it. Thanks for you help on this
Watchout! It WILL resize the texture(s) but NOT the associated bump/displacement etc.
What I’d do is use it to ‘show you’ the large stuff and then resize their respective jpg’s manually in the likes of Photoshop (I use XNConvert for batch resizing)
Oh wow, ok that’s a massive red flag to know about, god dam it! Ok back to the drawing board for creating batch resizing textures, this would have been a nice little disastor if you’d not flagged it!
As an update. Last night I was able to bit by bit get the model all in place, and it was working (slowly). Now I’ve just fired up the file that was working fine last night and it’s gone straight to this weird draft setting looking live preview. I can’t reload bit by bit each time as I need to continue to develop the model, I need to know what I can do now to fix this.
Have just sent fresh log files, can you please get back to me today with thoughts or any questions etc.
@Paul_Russam if you have any ideas always welcome to hear as well
@hbc_visual , thank you for the feedback reports as requested.
I wasn’t too sure if any of those file names might be confidential, so please check your e-mails for a further reply from myself. There is a specific texture file which cannot be properly accessed by Enscape, identified via a main error message inside of your log files.
If that doesn’t seem to do the trick and you still experience further problems, please kindly proceed as advised via the report itself, and thanks a lot in advance for your efforts Henry.
Is that just a photo in the background or is it an HDRI? If it’s an HDRI try removing it/replacing it with another as a test.
Toggling between the 2 images you posted I can’t see anything missing but all the shadows are burnt out making me think it’s some damaged exposure thing
Hi Paul, no the background is just an image, no HDRI.
It’s just odd as last night it was working fine, reload this morning goes to this draft settting and not working. Demain has identified a random file name which isn’t loading but I can’t trace it on my system so it’s still a mystery! I tihnk I’m going to remove texture from the whole bar section and see if I can rebuild it from there.
Are you monitoring your GPU performance? I’d check if you are maxing out GPU memory when using Enscape with that model. How much GPU memory do you have?
It doens’t look to be making out the GPU memory when loading up the model. To be honest, I never really look at this when I’m working as 99% of the time, things work smooth as butter. So I don’t have a reference on how it works on other large models.
It would be the “Dedicated GPU memory usage.” Maxing that out would be an issue but looks like you’re well under max utilization. (When I had only 8GB memory this ended up a regular occurrence and would show weird things in the Enscape viewport & crash.)
@hbc_visual , I’ve went into further detail in the e-mail I’ve sent you which you likely already read.
Speaking from the experience of a colleague of mine, she also ran into problems like these (slowdowns and crashes especially) using an external USB drive, in your case (E:), for around half of the linked materials.
This should in theory not be a problem especially when using either USB 3 or thunderbolt for connection, but just perchance you may be using USB 2 and/or an external HDD instead of an SSD then I’d especially advice moving your files to either internal SSD.
As per my e-mail, if that really is not possible at all, could you let me know a bit more about the external drive? Is it connected via USB 2 or 3? Maybe there is a model name or similar for me to look up that specific device/drive?