Looking for:
Localappdata autodesk revit autodesk revit 2017 journals free |
- Phil-osophy in BIM:
Revit Journal Files: They Aren’t Just for Autodesk Support | Autodesk University.
Nauman Mysorewala. This is an abstract from a presentation at Autodesk University Many operating systems and software applications have a method of logging messages, errors, output, etc.
These files are used to diagnose issues or making sure that the program is working correctly. Revit is no different in logging various information about the current Revit session and refers to these logs as Journals. Journals contain valuable information that can be used to help in troubleshooting various issues encountered with Revit performance, stability or Revit file health.
However not officially supported anymore, these can also be used to perform automated scripting in Revit, especially in older version when there was no programming interface API was available. Journals provide insights into:. This folder also contains backups of families edited, non-workshared networked project backup file and other diagnostic files.
A Journal file is created for each session of Revit, and number increments i. The highest numbered file, is for the last session loaded on the computer. Each version has its own Journal folder. This will list all the variables and its assigned values. I use this trick to find out the current setting for Revit Server Accelerator settings, without opening up Revit, or if I wanted to check while Revit is busy with a Sync.
Skip to main content. Knowledge Network. To translate this article, select a language. View Original Translate. English Original X. View Original X. Products and versions covered Revit Products. Journal Content Reading between the lines. Commands and Actions are preceded by the Jrn. The underscore represents continuation of the command on the next line. As mentioned before that Journal files can be used to script Revit. Though not in the standard Journal file except the variable definition Jrn , you can use VBA like script in Journal files as well.
There is an example of a Journal script included in the class dataset. The script allows you to mass upgrade families to the current version. This script was hidden away in the previous versions, but deprecated in onwards.
Revit constantly logs this data as you use the program throughout the Journal file. Many times, lack of these resources will cause performance issues, crashes, or data corruption. There is more detailed information available later in the file. Each Revit release and updates have a Build number associated. This is the first thing to check when diagnosing any issues. If the software is not up-to-date, it is recommended to update the to the latest release and see if the problem is resolved. In a work-shared environment, it is important to make sure all users accessing a central file s are on the same Build.
If you are experiencing these symptoms, review whether there was a recent Windows update. This usually happens on a Tuesday or Wednesday based on the Microsoft update release cycle. Hardware Acceleration turned on or not. For a weaker graphics card, turning off Hardware Acceleration can sometimes prevent Revit from crashing, or leaving artifacts on the screen. Various Add-ins installed. Refer to Assess the Basics for verifying the graphics drivers. Shows the Name and other various metrics regarding the installed processor.
journal |
Revit copies the central file to the local drive and appends the user name. Depending on the activity of the user how many projects are being worked on, and how often , the sizes of the projects, and the size of the local drive, keep only the last 3 months, 6 months, or 1 year of files and their corresponding folders.
It might be desirable to keep files for a longer period than folders. These are copies of files on the Vault server that are created by "get" or "check out" read-only reference or read-write working copies. You should be able to safely delete older ones.
You should only delete files from the cache for projects that are no longer being worked on , otherwise the files will simply be downloaded again and cause a slowdown the next time the project is opened with no permanent space savings. It's expected to have 3x the file size of the models being worked on not sure if it's 1x or 2x for links that aren't being edited , see Collaboration for Revit Cache File Quantity and Size Excessive.
You may be interested in this Autodesk support link: Location of journal files. Who moved my Cheese Files? Thanks to The Revit Clinic for this information. Jose Guia has also responded to the challenge. Here is a direct link to the program he created: RevitUsageAnalyzer. He includes a few more statistics, and the folders are already setup for RAC.
It also links into the Revit Forum thread. Rather than just uninstall Revit, you need to uninstall Revit and a whole host of other applications. A while ago, I posted a solution for how to uninstall the Building Design Suite with PowerShell , the problem is however that this solution no longer works with the current Powershell; it was written for v2. To get the job done in Windows 10, first we want to get a list of all the installed applications on the machine, I just want the name of each package so we need to type the following at the PowerShell prompt.
Before you run any of these scripts though, you will need to change your execution policy. You can do this just for the current PowerShell instance rather than permanently allow scripts to be run on the system. To do this, it is as simple as. To run the script you need to include the full location of the script, even if you are running it from the current folder.
For example. If you are specifically dealing with Revit software, you can take your uninstall a step further and clean out the associated files along with it. To do this, just add the following to the end of your script.
Recently for me it was a line pattern that had been transferred across from an old template. One by one, I check each line pattern I had imported and discovered there was just one causing the problem. No matter what I did, Revit would crash. So what do you do in this situation?
I ended up turning to the API to obliterate the pesky line pattern. As you can probably tell, this is quite a simple macro and the API is capable of doing much more. I recorded a video on how to create the FWG a long time ago, but after a bit of back and forth discussion on Youtube, I have decided to pull that old video out and record some voice annotation so you can follow along.
A quick follow up to my previous post on titleblock integers with a little more in depth explanation for new users to Revit. The first thing you do is pull out your trusty SP. Writer only to find that when you create a new parameter you get a run-time error Once enabled, select Visual Basic from the developer tab on the ribbon. On the left hand side of your screen, you will see a window titled Project — VBA Project , scroll down until you find Modules.
Right click on modules and from the contextual menu select Insert.. The final step is to make a small change to the UserParameter form. You can now start creating shared parameters again. This time around, you need to review the journal file and look for the error specifically related to missing elements.
If there error has just occured, it will be recorded in your most recent journal file. The easiest way to find the most recent file is to change your file sorting by date modified with the newest files at the top. From the Collaborate tab of the ribbon, select Restore Backup. Browse to where you have saved your backup file and then open the file with the audit box checked. Once you have successfully opened the model, using the Select by ID tool, search for the elements in your backup model.
The audited model becomes your new central model. You need to run through the process of loading the model onto C4R. If anyone else is working on the project, their local cache will no longer synchronise with the newly created cloud model. Others in the team will need to rename or delete the folders in both their CollaborationCache and PacCache folders. When speaking with Autodesk, they advised that the best way to prevent this missing elements error is to always open your C4R models with the audit check box ticked.
In addition to the above, both Revit and have had updates released since I originally wrote this post. The patches for both fix the problems that cause these errors.
Usually Revit will synchronise the changes with your local and the endless grind of office life moves on. First, we need to clear the C4R local cache on your machine. The second level of folders are the projects. The files within the folders are the models related to the project. The PacCache is where all the delta file transfer information is cached for all the C4R models that you have worked on. Everything is lumped in the same folder. This should actually be the last method you try for clearing out your cache.
The easy way is to just wipe out everything in both the CollaborationCache and PacCache folders. With Revit closed, just browse to the folders in your favourite file explorer you can delete the contents of the PacCache folder and then move everything inside the CollaborationCache folder to another location.
No comments:
Post a Comment