GRENDEL1 opened this issue on Apr 16, 2023 Β· 6 posts
GRENDEL1 posted Sun, 16 April 2023 at 6:41 AM
Here's a question... Can I move my Runtime to a different Drive and not have Poser freak out every time I try and open an older file that was created when the Runtime was on the previous drive? My Runtime is 932GB's, I need to move it to a larger Drive as the one it's on is almost full. Thanks in advance for any insights!
Y-Phil posted Sun, 16 April 2023 at 7:05 AM
Everything that is related to a file in a runtime structure is saved using a relative, specific notation, it is not saved using an absolute path, so that yes, given the fact that you've instructed Poser where the runtimes lies now, there should not be any problem.
Just keep the runtime's structure intact.
π«π½ππ
(γ£ββ‘β)γ£
πΏ Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gaming, Asus Tuf Gaming RTX 4070 OC Edition, 1+2 TB SSD's, 6+4TB HD
πΏ Mac Mini M2, Sequoia 15.2, 16GB, 500GB SSD
πΏ Nas 10TB
πΏ Poser 13 and soon 14 β€οΈ
GRENDEL1 posted Sun, 16 April 2023 at 7:08 AM
Thanks Phil!
NikKelly posted Mon, 24 April 2023 at 12:29 PM
Does this still apply using external libraries ?
I've remarkably little in P_11.3 'base' library on C:, but ~ 4 TB of assorted 'import' formats and external library runtimes on E: and G:
I link them in / out as needed. ( F: is mostly my non-CGI material.)
Saving a nice scene and render(s) with their makings makes it hard to re-arrange folders...
Y-Phil posted Mon, 24 April 2023 at 1:20 PM
as long as you respect the path that's written in Poser's LibraryPrefs.xml file. If you are unsure to edit this text file, just remove the runtime reference from Poser's library manager and add it back by pointing it in its new location.
π«π½ππ
(γ£ββ‘β)γ£
πΏ Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gaming, Asus Tuf Gaming RTX 4070 OC Edition, 1+2 TB SSD's, 6+4TB HD
πΏ Mac Mini M2, Sequoia 15.2, 16GB, 500GB SSD
πΏ Nas 10TB
πΏ Poser 13 and soon 14 β€οΈ
NikKelly posted Sat, 29 April 2023 at 6:11 AM
Thank you.