Keyshot Save As Older Version
Leda Billock
The easiest and fastest way to recover previous versions is to simply backup your data to the cloud. In fact, using an online backup solution is actually the only foolproof way to make sure that previous versions of your files are safe and easily available to you.
Files of any kind can fall victim overwrites, corruption, infection, accidental deletion and so many other threats. If you want to be able to retrieve older versions of your files immediately, then you need to consider online backups.
Update 3: If geo is sent to keyshot and assigned materials and saved within keyshot. Then Keyshot can be shut down. reopened, have the geo (that has been altered in the meantime) sent over again at which point loading the bip-file will restore the original geo with materials. sending the geo AGAIN from zbrush at this point will result in the re-shaped geo appearing in keyshot WITH the materials assigned. If zbrush has been closed this will NOT happen and the connection seems to be forever broken.
Newer versions of substance are not creating the .sp folder and the ts folders inside of it anymore, so I am not able to use the material importer option in keyshot it just creates the textures on the root folder , tried deleting my settings , uninstalling and different substance versions: 8.1 , 8.2 and 8.3 . with both keyshot 9+ and the keyshot output templates, people are even commenting about this on the official susbtance to keyshot tutorial ( =oUZxkS6Y9A4) and no one has posted a solution. I usually have to render things with may parts, so is a pain to manually input every single texture node for all the parts.
From your screenshots, we can see that the maps exported aren't the ones from the Keyshot preset, but the native Document channels + Normal + AO and we can also see the preset setup here.
thanks for your assistance, sadly the problem still persist , tried the export preset and stills just gives me just the textures . tried also opening substance painter as administrator but it seems substance is just not creating the folders .
Thanks! this worked perfectly. This is on me, i was choosing my output on the output templates tab, thinking that it was the way to set my configuration. As the old version on the tutorial did not have this tab.
When installing KeyShot "Just for me" your KeyShot Programs folder is saved to your personal Users folder (under AppData, a hidden folder). The KeyShot Resources folder will be saved to your local Documents folder.
At the end of the day you still need to save a version to the cloud or use the solution from @dsouzasujay to create a "file" you can open in some way without using the recovery tools, if that's what you are ultimately after.
Another downside of the version history is that I have a lot of derived models, including derived flat patterns for nesting. Every time I save the original model all of my derived models want to be updated, even though my save didn't change any geometry associated with them. The updating process is very time consuming. At least with Inventor it will only prompt you to update a derived part if the relevant geometry in the source model has been altered.
For Saving File without New version, You just need to Click on Offline Button While before saving the File and your file saving in the offline cache without create a new version. Also, this will not Lose any design data, and when you online your Fusion360 it automatically update your file on the cloud without creating a new version.
The thing you are looking for are Milestones. These are special version markers you create when you save a design as a milestone. In your case the original model would be marked as a milestone. Your derived flat pattern nest files would not need updating when the original model changes.
Do you think that milestones will help cut down on your version churn? It should be a little like deferring updates for Inventor assemblies in that you would need to take action to keep everything up to date when necessary, but can enjoy less disruption as a result.
@dsouzasujayYou wrote "As of today there is no a way to avoid versioning in fusion 360."
Will this ever change? People already complained about this 4 years ago. Why is this still a thing?
There is a checkbox in the preferences to avoid creating a new version on closing but it looks like this checkbox does absolutely nothing at the moment. Either you just don't save while closing and lose your work, then a new version won't get created anyway, no matter what the state of that checkbox is, or you save while closing, then still a new version gets created, no matter what the state of that checkbox is. Since there is this checkbox, even if it doesn't have any effect right now, I don't believe this is how you originally intended this to work.
Of course, you decide what to do with your software and we just have to deal with it, but I think we still deserve to know how Autodesk thinks about this. Do you think there are other problems with a higher priority that have to be solved first, even if this is an issue for years, or is Autodesk not planning to address this issue at all?
I did. But that would basically mean "sacrificing" the milestone feature for the basic versions. I think the original intent of having version numbers and also milestones, is to have some sort of hierarchy in the versioning system and you would lose that with this workaround.
Yes, there probably are a lot of other things that are more important to solve. But how important to how many people an issue is, isn't the only factor. An issue that is hard to solve and important to many people could have the same priority as an issue that is easy to solve and only important to a few people. If developers don't approach it this way, minor issues would pile up in their software over the years.
And I'm pretty sure this issue isn't that hard to solve. It looks like they're calling a function where they shouldn't call it or they just forgot to add an if condition to check if that function should be called.
But no matter if they want to deal with it or not, it still would be nice to know.
In all honesty, no. Versioning is built into the very basis of Fusion, and is unlikely to ever change. What is likely to change, however, is better out of date processing. So, if you change, say, just a component appearance, there is no need to update toolpaths or SIM results. But, basic versioning is here to stay. And Milestones are a way for you to say "some versions are more important than others".
And, it is important for everyone to understand: Length of time that a request is out there has nothing to do with its priority for being implemented. People have been asking for a purely local (no cloud storage) version of Fusion since its inception. It is not ever going to happen. So, just because someone asked for this 4 years ago has no bearing on whether it ever gets implemented.
"But, basic versioning is here to stay."
Just so you don't misunderstand me, this wasn't about versioning as a whole. I don't want it to go anywhere.
This was about the problem that a new version gets created every single time you save and you have absolutely no control over it and you can't choose just to overwrite the last version.
What really makes me thinking is this checkbox in the preferences that says no new version gets created on closing when it's activated. Right now, that checkbox does nothing but just the fact that it exists tells me that Autodesk decided at some point to give us some control over when new versions get created and when not.
I also remember watching a tutorial where someone explains how to save your work without creating a new version and he also talked about that checkbox. But when I did exactly what was explained in the video, it didn't work. So perhaps that tutorial was made with an earlier version of Fusion 360 where it still worked that way. But since that checkbox is still there, it looks like Autodesk did not remove that feature on purpose and it looks more like a bug.
I personally have that check box disabled. What I noticed is that it automatically saves a version, without prompting the user. I'd rather be prompted and then can make a decision. Often enough I don't want the changes to be saved.
Saving is versioning. Other than the Milestones, which Phil mentioned, this is the basic versioning model. Milestones do, in a way, address some of your concerns - updating referencing models or drawings or manufacturing designs only happens when you declare a version is a Milestone. But, still, every save generates a new version. Milestones are just a way to say "some versions are more important than others".
as its name implies, this applies only to when a document is closed. If there are changes, and this setting is on, a save (and therefore a version) is automatically created when the document is closed. It was a (lame, IMO) attempt to get "Google Docs" type behavior of never having to save. As you can tell, I have it turned off. If off, Fusion will prompt on close as to whether you want to save or not. Many times I want to close without saving, so I would find this option to be annoying.
Then it looks like the reason I understood it wrong was that the tutorial I watched was just wrong in the first place. The tutor clearly said that you can choose if saving creates a new version or not. Turns out, that's not just the case right now, it never was.
Hey guys, you can just use the command "close" . It will close the file without saving and thus not clutter up your server space with unnecessary version (imagine you just hide some elements when having a look at a file and this counts as a modification)
so there you go, like in any other piece of software