dlk30341 opened this issue on Mar 27, 2007 · 8 posts
dlk30341 posted Tue, 27 March 2007 at 1:19 PM
This a question on how Vue accesses available HD space. I had a weird anomaly & need a tech geek to tell my why this happened - if there is in fact a reason.
First off, I have 3 internal HD’s 120gb = C drive(main)…. 200GB = E……40G = F.
I have Vue loaded on C drive(66GB free) and the Atmos/Objects/Materials libraries loaded onto E(68GB free)
I moved the above libraries to drive F which after moving left only 1.2GB free.
I then tried to use Vue doing various things & it came to a grinding halt & even crashing when trying to load a PZ3.
So, I moved all the above mentioned libraries back to E drive & all was back to normal as it should be.
Now then, my question is why did this happen? Is it somehow that Vue was trying to do it’s thing on my F drive and was running out of space? Since there was only 1.2GB free?
This isn’t a bug – just more out of curiosity – since I thought Vue was executing and calculating on main drive C.
I hope this makes sense. Thanks :)