Caradavin on 9/1/2010 at 05:07
It seems to be working now. Please let me know, everyone, if anyone else has ever had this blasted permissions solution with Vista before. It's a brand new laptop, the OS came with it, and I'm the owner/admin. Thanks!
Ziemanskye on 9/1/2010 at 19:50
Quote Posted by d'Spair
Could you be a littlt bit more specific on this? What are the problems on Vista concerning gamesys and objectives?
I thought my comment pretty much covered it, but in more words, and this may just be me showing how out-of-touch I am with such things, but on my Vista laptop(s), I can create mission objectives ONCE. Trying to delete objectives will crash the editor (without deleting the objective). Trying to change the objectives will similarly crash the editor. Trying to update them (even just to correct typos) will crash the editor.
You can however delete the entire mission's worth of objectives (though it tends to crash the editor as well, they aren't there when you get back into it)
Similarly, it hasn't let me update the gamesys. Trying to create a new thing, locked the whole system up, forcing a hard reset.
I have occasional access to a windows XP machine, which I use for converting static meshes, and I had to build the objectives for my Cabal mission, and make the few adjustments I needed to the gamesys on that machine because it just got too frustrating and too annoying to keep trying to do so on my own machine.
As for your issue Caradavin, I can't comment: I only have one user account on this laptop, so while it sometimes asks for permission, there's no complications with it for me.
d'Spair on 9/1/2010 at 22:55
Wow, that's weird.
I've just installed T3Ed on my Vista to see how it works (I launched T3Ed on XP last time), and it definintely let me update my gamesys. I didn't bother with objectives, though.
Ziemanskye on 9/1/2010 at 23:34
It could just be this laptop, or it was me trying to do something odd (deliberately invert a static mesh, rotate it as needed, and attach a copy of it to the original, so there'd be an inside face as well - or it could well have been the attachment in the gamesys that it threw a fit at: that was a while back I was doing whatever was causing the problem)