Hi everybody, we need help as we could not figure out why is the file keep crashing.
D5 project file
Hello, @meeting
Welcome to D5 forum and sorry for the inconvenience. I noticed an issue here. If you only move the .drs file to a specific location or storage path, the project may fail or become corrupted. It’s best to transfer the entire folder of your D5 scene along with the file. Please see the photo below for guidance.
Hi, attached is the project folder. could you help us check what is wrong? thank you
Hi meeting, I’m a colleague, I think the D5 team will have a problem opening it, the folder you posted is incomplete, I tried to open it but it doesn’t open, I get this message
Sorry D5 team if I butted in
1 Like
If you have noticed maslu from the D5 team I have also explained it well to you, if you notice on the image it shows you what should be included in the folder.
Instead you only have the DRS file in that folder, no reference to the other folders that are missing.
If you have moved the files, check if everything is OK as Maslu indicated
1 Like
Hello, @meeting
As I mentioned above, I already checked your file and found out that you have sent only the .drs file, as you can see on the attached photo.
Your file is lacking and can not be opened. To access your file, you will need to obtain the entire folder or the complete D5 scene file. The complete file includes the asset, backup, videoscreenshot, .drs file, etc. Please check below the sample of a full D5 folder.
I recommend that you obtain the entire folder or the complete file so that you can access it properly.
I hope you understand this better. Thank you
1 Like
Hi many apologies for the confusion on our end. i think this should be the full file
Hi, any luck with the files?
Hello, @meeting
Thanks for sending your files appreciate it. Upon checking the scene and reviewing it, the Vram usage went straight over 90%, and it’s hard to manage due to the large file size.
I recommend optimizing your files and following the steps below:
-
Start with your models by deleting unseen or unnecessary objects or unwanted faces or surfaces.
-
Be cautious when using foliage, lighting, and non-essential characters when syncing to D5.
-
Consider separating the interior and exterior scenes for better manageability.
-
Alternatively, consider using a more powerful device or PC capable of handling larger files.
-
It’s a good practice to activate the statistics feature, these can show you how much VRAM usage you are dealing with. Once it goes to over 90%, issues such as lagging, freezing, slow rendering, and shutting D5 render may occur, so it’s best to avoid this.
Please let me know if my suggestions work on your end.
Hi thank you for the response, i feel like these are a bit too generic solution. i did reduce our model assets in the project file but the vram usage are stil above 90% at all time.
In term of pc, i think we have a monster already.
may i know what else could i do to optimise the project file?
could this all be due to hardware issue that caausing to crash?
Hi,
Before I answer your last inquiries, I have a question. Does this issue occur with this specific file only, or does it affect all of your project files? I should have asked you this from the beginning, but we focused on trying to figure out the cause of the lag in one specific file only.
Thank you.
I wonder how was this situation resolved. What is the conclusion. I have been dealing with the same problem and this annoying situation does occur from asset-scene interaction. Especially the nature assets cause so much problems when added to the scene. We need deeper investigation and analysis and urgent advice when requesting help from d5 teams.
After reviewing the conversation in this thread, it appears that we were unable to reach a final conclusion on the issue, as we did not receive follow-up responses to our team’s earlier requests for additional information, which are necessary for deeper analysis. Considering that the last message dates back to 2024, it seems possible that the issue was resolved on the user’s end.
I also reviewed your previous posts and noticed that in your most recent one, you mentioned that removing certain assets resolved the problem. Could you please let me know which specific assets caused the issue? I’d be happy to test them on my end to further investigate.
As a temporary workaround, we recommend using similar alternative assets to minimize disruption to your workflow. Our team is continuously optimizing the software, and we hope to provide a more permanent solution in an upcoming update.
Thank you for your understanding and cooperation. 