Hi,
I am a pro user and i work with very very large file sizes and large spans. Which means atleast 50acres of planting and landscape design works…
I am very lucky that d5 atleast gives me the viability to work at such scale and no other software does. Lumion runs at 1FPS with the same file.
And if i work in layers such as trees/shrubs/people/cars/fountains/site context. and switch them on and off as per the resources i need as per my work to commence the software is more forgivable in its FPS. There is another way to go about this. Which means to break the project into smaller part and put them as well into layers and switch off the parts not needed. Which might also increase the resources needed. But im used to working with low FPS whenever i can to get my work out and then rendering the final with all of them on.
You needed to hear that backstory for me understand my biggest pet Pieve i have with the topic subject of TOO MANY SAVES.
- Timer on the save which i have set to 60mins which occasionally comes on and D5 hangs and i dont realise that its hung becos its saving. There is a small …saving info on the top with the filename that occurs which makes me realise oh its not a crash and its just saving. My recommendation: Please be bolder and let it say in the middle of the screen like anyother save that it does with a proper progress bar in the middle and call it “INCREMENTAL SAVE”. Atleast we know we arn’t just panicking and the software is unresponsive becos of it.
- The software ever since its opened runs its incremental save each hour from the time its opened even thou i have just saved the file manually myself via the hamburger menu or an cnt+s function. It still does it incremental saving without regards to my already saved file. Which means im stuck for 2mins then and again after each hour like clockwork after the file has opened.
- Biggest one of them all: Each time before i click the render button it save the file again. It doesn’t at all take in regard to if i saved the file previously manually and as standard just saves the file again so time loss there again. becos invariably i have saved twice. I can undestand that it does so in videos. Its so frustrating to wait that 2mins-5mins for the save to happen when im taking rough low quality renders of the scenes to show client the work completed/number of views achieved.
The system just doesn’t take any regard of the users saves and invariably just saves over an already saved file 2seconds prior. I appreciate that its a safety feature but maybe there may be a better way to handle saving & incremental saves.
Maybe rethinking on how the saves are done as well, as per the changes i have made rather than saving and overwriting the whole file with all textures and assets in its co-ordinate axis information etc. (Just thinking out loud not really sure how the backend system of saving really works). There could definitely be a more user efficient and user-end based process on how saves work in the software to enable faster useability and function while using the software.
Thanks
Monks.