Bugs and suggestions to make the workflow even better

Get Help
1

Hello D5 Team,

I have been working with D5 for a few years now and have followed several updates. Thank you for the current update as well. As always, it brings new, very practical features.

Unfortunately, I am also a bit disappointed, as clear bugs in the software that I have reported multiple times here in the forum have still not been fixed.

I would like to post a list of bugs and suggestions for improvement here, with the hope that it will be seen and implemented.

  1. The reflection of the “Rect Light” is visible through objects. I have already reported this bug several times. reported here
  2. If you create a kind of photo studio (a white, closed room with lights), the display automatically gets brighter and brighter. If I render right at the beginning, it is quite dark. If I wait 2-3 minutes without doing anything and then start the rendering again, it turns out significantly brighter. reported here
  3. Some objects that are located behind others are not displayed in the Top View and Wireframe Mode.
  4. A simple feature like snapping is missing.
  5. The file names of textures that I have imported myself are not displayed. The tiny preview under “Base Color Map” is way too small. At the very least, the file name should appear on “mouse over”.
  6. Zooming with the scroll wheel (in the Top, Front, Left, Bottom, Back, Right views) is not good. At first, you zoom in normally, and then the zoom suddenly jumps way too much. This is very annoying.
  7. Copying in the object list (bottom left) is not possible using Ctrl+C, Ctrl+V. Ctrl+D doesn’t work here either. To copy, I always have to move the object in the editor.
  8. Groups (in the object window) automatically expand when moving objects. This is very annoying. In large projects, this creates super long lists. Cinema 4D has an option to “close all groups” for this.
  9. In all settings, only the period (dot) is accepted for numerical inputs. It would be really good if commas could also be accepted.
  10. A grid/step function when copying or moving would be very practical. This way, objects could always be moved or copied by a specific value.
  11. The AI often over-processes the renderings. It would be nice to have an option that, for example, only automatically adds signs of wear and tear, like scratches and fingerprints.
  12. When loading an fbx file, the position of the axes should be applied automatically. Why does this always have to be done manually via “Sync Pivot”?
  13. All new materials that come with importing an fbx file have “Normal” set to 1. Personally, I have to manually set it back to 0 in 90% of cases. Perhaps this value could automatically be left at 0 upon import?
  14. The “Invisible in raytracing” option does not work correctly. The object with this material is still illuminated, and it casts and receives shadows.

Thank you and regards

1 Like
2

Hi @Albareus

Thank you for your continued feedback. We would like to assure you that the issues you reported have already been forwarded to our development team and are currently under investigation.

While we understand your urgency, bug fixes cannot be implemented immediately. Each reported issue must go through a thorough process of analysis, development, and testing to ensure that the fix is effective and does not introduce new problems or regressions.

Please rest assured that if an issue can be resolved quickly and safely, we do not intentionally delay its release. However, for more complex issues, our priority is to deliver a stable and reliable fix rather than a rushed one that may create additional complications.

We appreciate your patience and understanding as our team works to address these issues.

I would just like to clarify regarding item number 14 that you have pointed out. I tested it on my end using the 3.1 hotfix version, and toggling “Invisible in Raytracing” works normally.

Do they not always work on your end? Is it in specific files? Can you show us a sample?

3

Hi @Clov

Thanks for your reply. I fully understand that it’s impossible to fix everything at once, and I don’t expect that, either. I just want to point out that I have definitely reported the bug in the program (at least the one from the first point) about 4-5 times already (the first time on January 2024). Since then, there have been several D5 updates, yet this specific bug still exists. The other points are merely suggestions that would certainly improve working in D5. I think some of them would be easy to implement.

As for point 14, it actually works exactly as it does for you. The object stops casting a shadow. However, it still receives shadows and can still be illuminated by light sources. In my opinion, it shouldn’t. In my case, I use this option for the background behind windows. After activating “invisible in raytracing”, the object (or rather the texture) should be displayed exactly as it is, without shadows or lighting.

regards