Parsing a few strings separated by an equal sign once at the top of the application isn't going to cause the app to get flaky. In 12 mil lines of code, that's not where the complexity is. Anyway, that file is ASCII, you can diff it, delete part of it until you find the offending issue, etc. There shouldn't be a cargo cult around this file. Now deleting the whole user folder.. that does clears a few more complicated things, including perhaps some plug-ins, perhaps image proxies and a spdl cache.
On Wed, Apr 17, 2013 at 2:39 PM, Matt Lind <[email protected]> wrote: > I don't buy that. > > I've had to clear out my preferences folder 4 times just in the past 6 weeks > for various issues in 2013 SP1. I set very few preferences, and once they're > set I don't touch them anymore. Yet weeks later performing this or that > Softimage suddenly gets very flakey. Clearing out the preference folder > seems to be the only workaround. This issue has been getting worse with each > release. Most noticeably starting with 2010. We rarely had to do this in > 7.5. > > There is something wrong with how tools are reading/writing that file. I > have noticed it's organized as <category.preference> = <value>, but the > preference and '=' are separated by a tab instead of space. Is it possible > there is code assuming it should be a space? > > > Matt > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Luc-Eric > Rousseau > Sent: Wednesday, April 17, 2013 11:34 AM > To: [email protected] > Subject: Re: unresponsive under win7 > > the preferences file do not get corrupted, ever. It's just an ascii file of > values. The problem is people forgot what they have changed and installed > and that's a quick way to rule everything out. > > On Wed, Apr 17, 2013 at 1:41 PM, Matt Lind <[email protected]> wrote: >> Something really needs to be done about that clearing XSI preference folder >> workaround. We should never have to do that, yet it's the first suggestion >> for just about everything when something goes wrong. If defaults.xsipref is >> that fragile, then perhaps it should be redesigned to be less corruptible. >> >> >> Matt > >
