It's only 1,000 bucks...nope its free!! Check it out.
Showing posts with label Solutions. Show all posts
Showing posts with label Solutions. Show all posts
Monday, December 23, 2019
Revit 2020.2 Internal Origin Part Three
John Pierson and Parallax Team Apps recently shared a solution at the Autodesk App Store called Internal Origin Hide-ifier. I thought mine was cool but it doesn't install itself or come with a Doge.
It's only 1,000 bucks...nope its free!! Check it out.
It's only 1,000 bucks...nope its free!! Check it out.
Thursday, November 10, 2011
File Saving Issues
There have been a few threads at AUGI and Revitforum.org alike that discuss an error like this one.
The folks at Autodesk support have apparently pinned the cause down and are now offering a solution via a post at The Revit Clinic yesterday morning. Here's the text of their post.
____ ____ ____ ____ ____ ____ ____
This post is contributed by Niranjan Kamath who supports Revit on our team in India.
While working with a workshared file, Revit will report an error whereby the central file is not accessible.This issue occurs only when the clients had a different OS version. We could not recreate the file access issue if the clients were both W7, or both XP for example.
The reason this happens: Windows 7 client communicates with the server using SMB2, while the Windows XP client uses SMB. This difference in version may cause some file handling issues.
To resolve this issue disable SMB2 from Server and Win 7 users.
To disable SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems, run the following commands:
To restore SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems, run the following commands:
In order to disable SMB 2.0 on the server-side computer, follow these steps:
Warning!
This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, do not attempt these instructions. Instead, seek the help of a trained computer specialist.
The folks at Autodesk support have apparently pinned the cause down and are now offering a solution via a post at The Revit Clinic yesterday morning. Here's the text of their post.
____ ____ ____ ____ ____ ____ ____
This post is contributed by Niranjan Kamath who supports Revit on our team in India.
While working with a workshared file, Revit will report an error whereby the central file is not accessible.This issue occurs only when the clients had a different OS version. We could not recreate the file access issue if the clients were both W7, or both XP for example.
The reason this happens: Windows 7 client communicates with the server using SMB2, while the Windows XP client uses SMB. This difference in version may cause some file handling issues.
To resolve this issue disable SMB2 from Server and Win 7 users.
To disable SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems, run the following commands:
- sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
- sc config mrxsmb20 start= disabled
- Note there's an extra " " (space) after the "=" sign.
To restore SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems, run the following commands:
- sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
- sc config mrxsmb20 start= auto
- Again, there's an extra " " (space) after the "=" sign.
In order to disable SMB 2.0 on the server-side computer, follow these steps:
Warning!
This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, do not attempt these instructions. Instead, seek the help of a trained computer specialist.
- Run "regedit" on Windows Server 2008 based computer.
- Expand and locate the sub tree as follows.
- HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters
- Add a new REG_DWORD key with the name of "Smb2" (without quotation mark)
- Value name: Smb2
- Value type: REG_DWORD
- 0 = disabled
- 1 = enabled
- Set the value to 0 to disable SMB 2.0, or set it to 1 to re-enable SMB 2.0.
- Reboot the server.
Tuesday, May 03, 2011
Family Puzzler - Beam and Family Type Parameter
I'm opening up this issue to my clever readers out there to either enlighten me or corroborate my situation. Imagine a structural support that we'll refer to as a pipe support. If it helps, something like this:
I'm referring to the green "column" and "beam" with the tabs at the ends of the beam to counter potential "roll-off" in a seismic situation. The obvious way to make a family for this is to nest a column and beam family, use a Family Type parameter to swap between sizes when they are placed in the project. I write obvious because it would be nice to be able to use the standard framing families and types to choose the relevant form and configuration.
Everything is pretty straightforward until I attempt to change the type. The length of the Beam resists being constrained if I change the Type. I've managed to get it to work but it tends to break as soon as the beam size is changed.
The puzzler is... has anyone been able to get nested beams to behave when managing the "in-use" type with a Family Type parameter?
Working around the issue, a couple solutions come to mind.
If the Structural Framing beams are not used I can get it to work easily so that suggests a conflict with the category behavior (the structural framing template). If I build my own beams and columns using the same profiles and type catalogs it will work. Unfortunately that means we'd end up with "different" beams/columns than the other "real" beams and columns when we think of schedules.
The other solution might be to use the API to get the information that the user needs to supply and let the API create a custom family from the parts and build/insert on-the-fly. Like the Frame Generator extension does for Revit Structure.
Comments?
I'm referring to the green "column" and "beam" with the tabs at the ends of the beam to counter potential "roll-off" in a seismic situation. The obvious way to make a family for this is to nest a column and beam family, use a Family Type parameter to swap between sizes when they are placed in the project. I write obvious because it would be nice to be able to use the standard framing families and types to choose the relevant form and configuration.
Everything is pretty straightforward until I attempt to change the type. The length of the Beam resists being constrained if I change the Type. I've managed to get it to work but it tends to break as soon as the beam size is changed.
The puzzler is... has anyone been able to get nested beams to behave when managing the "in-use" type with a Family Type parameter?
Working around the issue, a couple solutions come to mind.
If the Structural Framing beams are not used I can get it to work easily so that suggests a conflict with the category behavior (the structural framing template). If I build my own beams and columns using the same profiles and type catalogs it will work. Unfortunately that means we'd end up with "different" beams/columns than the other "real" beams and columns when we think of schedules.
The other solution might be to use the API to get the information that the user needs to supply and let the API create a custom family from the parts and build/insert on-the-fly. Like the Frame Generator extension does for Revit Structure.
Comments?
Subscribe to:
Posts (Atom)