-d5 2.10
-NVIDIA GeForce RTX 4090
-AMD Ryzen 9 9950X 16-Core Processor 126G memory
-driver version 32.0.11024.2
-every scene I have created in 2.9 now has massive frame rate issues just navigating the scene. In short, the frame rate never goes about 9-10fps, and any movement in navigation creates a “jittery” effect, whereby the camera will orbit/rotate/zoom but it jumps one frame back before moving ahead 2 frames for the entire duration (so it looks like it’s wiggling is the best I can describe). It also loses resolution at the edges of the frame, whereby it looks like a melting watercolor painting.
1 Like
Hi there @mcdermoa
I apologize for the inconvenience.
- Can you perhaps send us a screenshot or video recording of this issue that you are currently experiencing?
- Have you tried updating your NVIDIA Driver Version to the latest one?
We would also want to test your file (Scene File and Log file) on our end and compare the issue that was evident on your end.
- You may send it to support@d5techs.com and have it titled ‘Clov - Forum 2.10 Massive Frame Rate Drop’
- How to Generate Log Files? https://docs.d5render.com/user-guide/hardware/how-to-use-support-tool
I have the same problem on 4090, latest version of d5 and Nvidia drivers installed. Speed drop does not happen immediately, but after several moves. This is very bad for my work deadlines.
Hi @tamara2507
I apologize for the inconvenience. I have a few questions for troubleshooting:
- Is this issue file-specific?
- Have you tried running Smooth Display instead of Precise?
- Did you enable FPS Booster?
Additionally, were there any Procedurally Generated Vine Assets in these files? And were they created in the 2.9.1 Version? If so,
-
To get the best results with the new version, we recommend adjusting the length, width, and density of your plants slightly down (since the old version had errors with the quantity of plants, while now, the fix will make the plants more, and the fps will be increased)
-
Enable “FPS Booster for Complex Geometry”; FPS will increase a lot
2 Likes
@Clov, thank you for the reply
-I cannot send mp4 files via this forum (or so it says), and a still image will not show the effect. I will try emailing it to you though, along with the log file. The scene folder is 9.5gb though, so let me know if you have a secure ftp site or something.
-yes, driver is up to date.
-the issue is not file specific, but perhaps size specific. I have fairly large scenes (100 mi sq), but again there was ZERO issue in 2.9. I have tried several times creating brand new scenes natively in 2.10, and the same issue occurs, including loading nothing but terrain or a segment of cityscape from the new feature.
-yes, have tried precise/smooth, disabling any/all beta widgets, super resolution, FPS booster and frame generation. None of them change the results whether they are on, or off.
-there are no procedurally generated assets in any of my scenes.
Hi @mcdermoa
You can send the video via generating a wetransfer link or you can send it together with the zip file.
- You may send it to support@d5techs.com and have it titled Clov - Forum 2.10 Massive Frame Rate Drop (mcdermoa)
- How to Generate Log Files? https://docs.d5render.com/user-guide/hardware/how-to-use-support-tool
Can you also send us the following images? The VRAM Info should be opened together with the D5 Render File. Thank you
is there a way to set up a call to go over this? Or the other thread I have going with you specifically about how the tail light streak feature is supposed to work? The turnaround time to trouble shoot these issues is sometimes 48+ hours just to have someone ask for another screen grab. I don’t mean to sound impatient, but this is an excruciatingly slow process to trouble shoot something that could probably be fixed in 20 minutes.
Hi @mcdermoa
I have sent you an email regarding the problem that you are experiencing with the massive frame drop:
Our team has received your log files, and while they provide some information, we also need the D5 Render Scene File for us to further investigate this issue.Your D5 Render scene file is absolutely essential for us to continue troubleshooting. You may send it via Google Drive Link and have it zipped, and please ensure that the permission settings are set correctly to avoid further delay.
The turnaround time to troubleshoot these issues is sometimes 48+ hours just to have someone ask for another screen grab. I don’t mean to sound impatient, but this is an excruciatingly slow process to troubleshoot something that could probably be fixed in 20 minutes.
I apologize for the delay. I believe that you made this post around Saturday or Sunday, which explains why there was no immediate response until yesterday. We operate Monday to Friday following HKT (Hong Kong Time) UTC/GMT +8 hours
zipped project folder sent, and you should see an invitation with permissions to access it. thanks!
1 Like
Hi, I am experiencing the same issue since the update, to the point where I can barely work.
is there something I can do?
I have fps booster on.
it worked great until the update even with relatively complex files.
Hi @neumannshea
Can you also send us the following images? The VRAM Info should be opened together with the D5 Render File. Thank you
-
Can you share to us your D5 Render File? You may send it to support@d5techs.com and have it titled ‘Clov-Forum 2.10 Massive Frame Rate Drop’
-
It’s also important to note that enabling Path Tracing will likely cause the Scene file to be heavier compared to the previous versions.
Hi @mcdermoa
Hi Adrian M Mcdermott,
Is this the same file as the video that you have provided? We would like to test the file that you were talking about in the video you have provided.
Additionally, the file you have sent (ANDURIL 1) is an heavy file amounting to 20GB in file size. D5 Render files with this size is expected to massively drop in FPS considering that:
- D5 Render Assets most especially vegetation are mostly used and are not organize properly. We suggest hiding these assets in scenes where they are not visible.
- Precise mode is enabled, we suggest switching to Smooth if you are editing.
I cannot share that file, unless you are willing to sign an NDA, so no.
I mentioned that the files are quite large as well, several times. I also mentioned that prior to v2.10, there was zero issue navigating these files. Yes, they are large, they need to be large, and the worked fine until this latest release. If you are suggesting that with the added new features, it is no longer viable to work in large environments, should I be reverting back to v2.09? That would extremely unfortunate, and was a major reason I migrated to your platform in the first place from other rendering softwares. I truly hope that is not what you are recommending.
can you elaborate on what a “proper” organization for vegetation would be?
Precise mode is necessary to show this to clients, and navigate around the environment in real time. Are you suggesting that this is no longer viable with the latest release?
Again, I cannot emphasize enough how great your software is, or at least was, at v2.09. It is a little perplexing that with this much hardware, the answer is to essentially not use the software the way we were able to one release generation back.
I guess I should also point out that the file I did send experiences the identical problem. So if you are asking for them to be coordinated, it would be more viable to send you a video of the scene I sent, rather than send you the scene from the older video.
Hi there @mcdermoa
My apologies for the accidental inclusion of the screen capture from your video recording. I have removed it immediately.
We’ve forwarded your files to our testing team for a thorough investigation. You’ve noted that this specific file performs as expected in version 2.9, but exhibits different behavior in 2.10, despite no intentional changes on your part.
If you’re facing a tight deadline and encountering issues in 2.10 that weren’t present in 2.9, we strongly recommend reverting to version 2.9 for the time being. This will allow you to continue your work while we address the underlying problem.
We understand how frustrating this issue is. Version 2.9.1 had a known problem with high GPU consumption related to vegetation and PCG assets. This was resolved in 2.10, and many users have confirmed the improvement. Your experience with this particular file, however, contradicts this. Therefore, we’re committed to a detailed investigation to understand the discrepancy.
Furthermore, we strongly recommend maintaining organized asset management, regardless of your system’s capabilities. Grouping assets into layers and hiding those not in use within specific scenes can significantly improve performance and workflow.