Hey lightstar,

                 What happens when you try to go up with programing in version. Usually it goes that way right?... or is it the other way around? Do this and see if it helps a bit do your win7 first up, then the vista and xp substyles. I'm not sure but I bet it is more than what you really see it doing now for some reason than before.

I do not think Stardock or anyone at this problem is responsible for such. OK I agree it is very frustrating to have this happen. But it does and did and so forth. It never works at blaming someone else for a problem that can be corrected. Lets try and work together. Not against things...

Here is another thing to consider with your problem - dual or triple booting an OS on the same Hard drive? There is an issue I'm still working on with this where some regs are still written wrong for the other OS by WIN7. Not Vista but WIN7 only. Not sure completely why yet. But it does it and there may be why your problem is happening for sks.

I stopped using dual boot system with win7 because of this. Plus it is a release canidate not the final RTM. I know everyone is ready to start making win7 skins and so forth. But I still remember when we first started doing the samething with Vista s it came out. Everything was changing - there where all kinds of problems that the math did not fit well with. We worked with it and finally got things in place. Now win7 and we have more and/or diffrent problems. Yes it is frustating as hell to see work go out the window.

One word - stop deleting stuff and move it to a backup area for safe keeping!

Anyway try going down not up in windows version to skin. Save things correctly and even do one for each version and then import the substyles as such need be. If there is a will there is a way to do it. Believe me!

figure fps and what graphics a base system will use! some will use 5 to 20 fps. So what would be good for that system?

same answer but for what system we ask again... vista maybe and depending on which system we say 20 to 50 fps. 60fps is perfect for most good graphics systems. But how does that figure with a system which graphics only allowing 20 fps total.

So there it figures to the system not the program. Here you make something in hi graphics speed and composite... then even if the program presents it; the system jerks along to run it.

So look at what would run on most any system and say this is what to use for the overall frame count. No more than 20 frames for most any animations. This is for xp and/or vista. Windows7 will be different and those can have a higher count.

There is ya like you say why did they not tell use this info question. But figure if you want something with a hi-end machine and can run 100fps. Thus you would make a skin for that machine and with that machine. Thus I would think sks would allow those frames to be populated into the skin as such.

Ok Lightstar but what I'm saying is there is more going on here with what you are doing than what is suppose to be. It does not matter how or to what drive you use for what OS. It only use's one drive for the boot file and regs!

You will have to do a wb for each windows version and then merge them into one skin with 3 substyles to get what you are trying to do.

These things will be sorted as best they can with the new win7 wb7 and sks7 once it is ready. I never blame a dev for something they miss or did not think of. I always try to suggest things and sort problems to the correct manner. Not point the finger and say you did it and it is no good. Those guys work as hard as they can to figure every problem. If we are gona get the e=best of the best for these new programs to work we have to work with them to correct or show what we see and input what we think correctly. Making someone mad about their hard work never brings a good result.

I am sorry you have lost your work, but I don't think the problem you had was a SkinStudio one.

Skinstudio isn't capable of removing all your work like that.  Even if it somehow forgot the substyle entry in the .SSD file, the newer graphics etc you did would still be in the folder (how would it know what to remove?)

The most logical explanation is the .WBA you used was in fact older and so you reverted to an older version of the skin.  In which case on your other OS the files should still be there unless the wrong WBA was used one OS switch before and you didn't notice it at the time.

that sounds wikked niel...but, i have encounted with vista in the userpane area for animations, that if i go over a certain amount of frames, i get white pixelations on the outside of the animation....to fix that, i reduced the frame number and it vanished....

Now thats the math I was looking for in that question.  Thanks Neil and thanks for the other answer as to why this missing data was lost or misplaced.

Then the only thing I can think of is the .SSD and .SSS files were somehow locked by something when the .WBA was built and so were missing from the WBA.  If you still have the WBA file that was created I can take a look to see if there is any evidence of what happened contained within it.

Were the substyles still listed or were they totally missing?

The substyles were still listed Neil, but I have since worked on the .wba and it is not the same as it was when the problem occured.  Thanks for the offer though.

I.R.  -  Thanks for the info, I appreciate it.

Hi Neil, can you explain what that means? I'm not sure....thanks.

They are settings in SKS on the page where you set the image.  Also ensure you do not tick premultiplied alpha as that can produce some unusual results with transparency unless the image really has multiplied alpha.

oh i get you now, just didnt know what flagged meant, actually, i did have the correct png boxes checked, i only use the premultiplied alpha on logg off glyphes and the navigational arrows............so im not sure now why the white pixelation happens when i go over a certain number in animated frames.

it was evil Block files...