When multiple members of a design team are working on the same project, versions quickly multiply. And without a standardized process for design version control, you can quickly find yourself with five files that look like this:
Setting up naming conventions is the first and most important step in solving your version control woes. This simply means coming up with a consistent format for naming your designs and their various versions. And making sure the entire team (and new team members, as they join) knows the new format!
Use branches to experiment with different design ideas or work on specific features independently. That way, you can isolate changes and avoid disrupting the main design project until changes are ready to be merged.
Design versioning tools, like the three we saw earlier, are specifically designed to help you manage multiple copies of the same file. They improve creative collaboration, prevent major disasters, and make your job much easier.
To overcome this, Git and some other version control systems offer large file storage (LFS), which stores large files outside the repository. Other steps you can take to overcome this challenge include optimizing file formats, compressing design assets, and regularly cleaning up your folders to reduce clutter and improve performance.
Collaboration is a fundamental part of any design project. But the more people involved, the harder it becomes to communicate clearly, juggle conflicting ideas and modifications, and keep everyone on the same page.
when I uprevise the schematic the process starts, I see two blobs text flash by the Details (presumably one for each page processed) window and it silently crashes on the third when calling van.exe. The last blob of text is as follows and is truncated:
My feeling is that this is due to non-Synchronized Design rules between the Schematic and PCB, which are normally resolved by using Tools -> Constraints -> Synchronize inside the old version of Cadence.
How can i successfully update the schematics to the current version of Allegro? If it means throwing away all Constraints Manager information in the Schematic or the Design Environment, i'm happy with that and call it a win.
you should contact your cadnec provider (mayube a channel partner): he will be able provide you old vesion of cadence tool. i uprev recently a database from 97A (aka v12, pre windows version.... with scald scheatic (pre hdl...) up to 17..2. Fortuntly, schematic and brd were in sync so i could uprev without major problem.
This is commonly reported as an error due to using the wrong version of SSMS(Sql Server Management Studio). Use the version designed for your database version. You can use the command select @@version to check which version of sql server you are actually using. This version is reported in a way that is easier to interpret than that shown in the Help About in SSMS.
Just a heads up, Got the same message when I installed SQL Express 2022... Literally Installed SSMS (v18) by clicking the link after Express finished installing. I deleted V18 and downloaded V19, which is still in beta, and it fixed the problem.
I ran into this problem when SQL Server 2014 standard was installed on a server where SQL Server Express was also installed. I had opened SSMS from a desktop shortcut, not realizing right away that it was SSMS for SQL Server Express, not for 2014. SSMS for Express returned the error, but SQL Server 2014 did not.
I am a private user of Fusion 360, and would like to clean up my workspace before the 10-document limitation is activated. I have dozens of old versions lying around, most of them I cannot delete because it is used in some old revision I do not care about.
Is there a way to download or keep only the last version of a project? I know this question has been asked before, but that was some time ago (about 2017), so I hope things have changed. Can't I download my current version with all active dependencies, close down my account and start from scratch after re-uploading it?
While most items cannot be deleted, I also successfully have deleted elements that really were required and never understood this. And why is "used in" only displayed in the web view, not in the desktop version?
If you download the top level design you will get an f3z file containing the assembly file and all the designs it's linked too. You could then delete the top level design on the cloud and all it's linked designs the upload your f3z to a new project.
Another option that should work is use Save Copy As to create a new top level design and delete the old one, this should free up and old unused linked designs no longer in the latest assembly. It gets a bit more complicated if you've created 2d drawings. You can download the 2d drawing as an f3z and it'll bring all dependent designs with it, then upload to a new project and delete the old. This will not work if you've created several 2d drawings linked to one design.
The design I've been working on for a while just used an offline update as it's current file save and now I cannot get back to the work I had done for almost an entire day since that offline save.
The time and date of a save should be considered when an offline save was made to when the "save" actually occurred. I'm going to have to download the old .stp file and get the dimensions off of what I have added to my design because the .stp files don't bring in the links associated with my designs. This seems like a bit of an oversight...
Here is what happened. I opened the design on another computer to do some machining on a component, that machine has Fusion360 on it and we run keyways on it; so it doesn't have to be connected to the internet all the time since wifi is spotty back in the shop. The operator must have saved it after he used the file and then closed it. The next day after working on the design for a few hours; I saved it and left for the weekend (I did not close the design). Come Monday morning, I get a little yellow triangle saying my design is out of date and I cannot save over it and I cannot open the older design.
This will take me about an hour to get back to where it was; not the end of the world but a pretty incontinent use of time since I've already done this once.
Last year it was mentioned in the forum that LightBurn was considering releasing a a design-only version of LightBurn which will not communicate with a laser, but would let you load / import / save LightBurn files. This would allow elimination of discount codes and enforce the intention of the discounted version.
Discount version??? Lightburn only has one version. Trial and Activated are the same program with all features enabled. If not Activated, the program is only enabled for 30 days, allowing plenty of time to determine if you like it, it works with your laser, you can see if you can bake a cake with it, etc.
We are considering based on feedback we have received. We have not finalized this, so much of what is being asked has not been resolved if we proceed at all. We want to, but this has not been our current highest priority.
Opinion of one: Without Gcode and communications, LB will be competing with 3-axis designers, many of which are free. DXF and SVG output will only be a minor inconvience to laser users. I wonder how many lasers are sold and operated without using Lightburn. Schools and makerspaces can buy a copy and train from that. LB would be moving away from the core purpose of the product, being design and operational software for lasers. Effort and resources will be pulled away from the maintenance and support of the current product.
We are not moving or pulling away, we are discussing ways we can provide additional options for those that have specific needs, not currently available. If we advance with these ideas, they will be in addition to our correct product offerings.
In a separate Twinmotion thread, there was a question touching on version control / display of design iterations within TwinMotion. Figured I would start a thread for those who would like to specifically discuss this topic.
1 hour ago, line-weight said:
And I assume that for each version of my model, I'd have to export that as a different file to TM? For example, if I have two versions of a design for part of the ground floor of a multi-storey building, in VW have duplicate ground floor layers, version A and version B and so on, with the appropriate ground floor layers turned on or off in my RW viewports. I think to see this in TM I'd have to export two copies of the whole model, one for each version. Is that right?
@line-weight Yes, you create different c4D export files for each version you want to display.
In your example, you would turn the design layer for version B off and export only the visible design layers to C4D.
You would then turn version A off / B on and export again, creating another file you name accordingly. Anything common to both versions would be left on during this process. Now you have two c4d files and a folder of textures
Now in TwinMotion, you just have to import one of those versions, let's say A. When you want to display B, you reload the c4D file using the three dots above the file icon and simply point the file to version B. This whole process takes like 20-30 seconds total. I toggled between 3 different design iterations (reloading models) and two view points (switching views) within TM in roughly 90 seconds.
Yes, you do this in the media center when creating your images. Each image you create can have different environmental settings, etc which you can export as images. Similarly, you can do the same thing with video.
I've developed several VWX/TM workflows to deal with all kinds of special requirements of my B2B clients, one of whom went from never using the software to creating a nicely textured and planted model with a 20+ image presentation within a single day...including purchasing and installing the software!
There are things it could do better. However, for the price, included libraries, available online assets and tutorials, and quick onboarding, I know of nothing comparable.