Any one else had the delights of trying to develop an oxp whilst using vista 64? Its proving to be "interesting" vista seems to be putting copies of files in something called "virtual storeage" and then cleverly not updating them when the "real" copy gets altered about 2 hours of my time was spent trying to trace why one of my ships was using an outdated texture ...
Since then Ive found this virtual storeage thing seems to be doing all sorts of interesting things...
Ive deinstalled oolite and reinstalled it to c:\oolite instead of in program files doesnt half make life easier without all those lovely vista security pop ups becauuse you are working in a program files directory...
I do most of my stuff under windows xp from my work pc, but like to do little bits at home where I run vista.
Also managed to lose my save game, fortunately I had an old copy backed up on a memory stick, lost a few days work though...
Any one else had the delights of trying to develop an oxp whilst using vista 64? Its proving to be "interesting" vista seems to be putting copies of files in something called "virtual storeage" and then cleverly not updating them when the "real" copy gets altered about 2 hours of my time was spent trying to trace why one of my ships was using an outdated texture ...
Since then Ive found this virtual storeage thing seems to be doing all sorts of interesting things...
Ive deinstalled oolite and reinstalled it to c:\oolite instead of in program files doesnt half make life easier without all those lovely vista security pop ups becauuse you are working in a program files directory...
Just out of curiosity... are you remembering to hold down shift, while starting Oolite.. the shift key flushes the Cache that oolite will build the first time it meets a new OXP, it checks this by the date of the files, rather than time and date... if you dont, it will not update cache if the files are from the same date...
I´m on Vista 32 bit... yeah the UAC is a pain in the but... but for security better.. you just have to make sure your files inherit the security settings of the directory... ofcourse you also has to make sure the the active user has the apropiate permissions...
Explaining all this here is out of scope, since MS has allready done it here
Ive not managed to get the shift key to work for that purpose for some reason...
What Ive been doing instead is moving the whole oxp from addons to the desktop starting oolite without it then moving the oxp back to addons then restarting it to force updating. Ive been doing this under xp at work as well.
Vista though was doing this additional thing with the virtual storeage. Only way I figured out in the end was doing advanced file search for the texture name and found out that there was a vistual storeafe \oolite\addons\ version of the texture that was out of date, as soon as I deleted that it managed to grab the current one from the program files \ oolite\ addons folder...
Working from c:\oolite seems to be a bit more friendly. Now I just need to figure out how to assign standard equipment to my new ships properly
I think my mistake with the shift key was trying random pressings and holdings of the shift key instead of just holding it from start to finish? had a couple of confirmed sucess with updating the oxp like that, Still wouldnt get round the nasty vista issues but they are taken care of running it from the c:\oolite
I have Vista, albeit not 64. You have to press the Shift key continously from before you start up Oolite until you see the "Load a Commander (Y/N)" screen for this to work in my experience.
To get around Vista`s hilarious "security", I installed Oolite into Vista`s "virtual" regions ... thereby circumventing any and all "doesn`t edit files if it has to due to ... security ..." crap.
...
... thereby circumventing any and all "doesn`t edit files if it has to due to ... security ..." crap.