That should return Poser to its default state. (Taken from my post, here: )Īll of these will be regenerated once Poser starts up. PoserUI *x*.xml (custom resolution UI settings), LibraryState.xml (contains your library display prefs) and the RenderFirefly.cfg (or any other Render*.cfg currently generated) and the preferredstate.pz3 file, which is the customized prefered pz file scene loaded when you start Poser, if you've made one besides the default "Andy" scene. However, I would also recommend deleting (cut/paste somewhere) some others: The files Smith Micro recommends deleting to restore factory defaults, and clear up some issues, can be found here along with their locations: I will list them below: (I'd recommend just pasting them there and working from scratch if you get Poser up-and-running.) "Cut" them from their directories and "Paste" them into a directory were you can later copy them back over if you'd like to troubleshoot the issue and restore some of your settings. Here are all the "preferences" files that I would recommend removing. You'll lose any custom UI changes and will have to re-associate your content directory, but other than that it's fine. This will reset Poser back to its factory-installed default state. If it's not a brand new install, then I'd first suggest that you delete all of your preferences files. Is this a brand new install? If so, did you install everything? Check with the SM Installer app to be sure everything is installed and all patches are applied.
#POSER DEBUT CRASHES ON STARTUP WINDOWS 10 HOW TO#
To be safe, just do a clean reboot if you don't know how to check to be sure there aren't any orphaned processes running. Typically, "Poser.exe" but I think it also runs a couple of others. I don't have Win 10, so some suggestions may not apply and I may not be able to help you with certain OS tasks.įirst, make sure that no other executables of Poser are running.
0 kommentar(er)
