Hmm, I switched to Vista and ended up going back to XP. Too many bugs in Vista. Still getting the error?
|
Hmm, I switched to Vista and ended up going back to XP. Too many bugs in Vista. Still getting the error?
I'm not too sure David, I have Vista x64 as well and it works fine. You should file a support request.
Funny girl.
Alas, shouldn't the 64 bit DWG Reader version install and work in the Vista 64 bit OS?
Thank you kindly, whist I do go download 32 bitDWG Reader.
It should David, mine works fine. Teresa is referring to 64 bit Revit
has anyone had any problems with this on a networked license server? We have quite a few computers with NW-Review each with their own license but it is obtained from a license server. We recently upgraded to 64-bit machines and have been unable to open navisworks review 2009 since this patch was installed.
Any suggestions would be appreciated because the ability to refresh is of great importance, and having to nwdout all the time makes a very strong argument for 32-bit work stations that require navisworks on a day to day basis.
R. Robert Bell
Design Technology Manager
Stantec
Opinions expressed are mine alone and do not reflect the views of Stantec.
we are using 2009.1, but getting a license is not a problem. The problem is that navisworks won't load after the patch was applied. It isn't throwing up missing license errors. I was just hoping to justify trying to bypass the network. Mostly because it is hard for me to fathom how one of the more critical features(for me) of extremely expensive software is released broken, and the patch to fix it just makes things worse.
If the 64-bit AutoCAD 2010 is released without the ability to make any polylines I'd expect it would get fixed rather than having to wait for the 2011 release and pay for the upgrade.... Sorry, now I am just complaining. I'll stay in my CadCave....
My method for bringing back refresh in 64-bit navis since the Autodesk fix seems to only make things worse. Please note this is only effective if everyone in the office adopts it:
Step1
Open navisworks and goto TOOLS->GLOBAL OPTIONS->MODAL->PERFORMANCE
and make sure that "Close NWC/NWD files on load" is checked
Step2
Open AutoCAD and type "NWOPT" which will bring up the internal Navis Options Editor.
goto FILE READERS->DWG
and make sure that "Convert XRefs" is unchecked
Step3
Now that we are all setup to export small navis files that only pertain to our current objects we can setup AutoCAD to do an auto-nwcout command every time qsave is run.
this is my acaddoc.lsp
Before we continue:Code:(setq error_backup *error*) (command "undefine" "qsave") (defun C:QSAVE (/ name) (defun *error* (msg) (setq *error* error_backup) (setvar "filedia" 1) (princ msg) ) (setq name (getvar "savename")) (if (= name "") (if (wcmatch (strcase(getvar "dwgname")) "~*DRAWING*") (setq name (strcat (getvar "dwgprefix") (getvar "dwgname"))) (progn (initdia) (command ".saveas" pause) (exit) ) ) ) (command ".save" name) (setq name (strcat(substr name 1 (-(strlen name)4)) ".nwc")) (setvar "filedia" 0) (command "nwcout" name) (setvar "filedia" 1) (setq *error* error_backup) (princ) );end defun
WARNING: if for some reason the error handling isn't bulletproof filedia set to 0 will disable most dialog boxes. There is an error in the nwcout/nwdout command that sometimes leaves the command open and will not allow a qsave/saveas to take place. Which is why ".Save" was used instead (it doesn't suffer from this problem). This must remain or you will get some error asking if you want to "retry" the command. Last thing that can be a real draw back is you are essentially doubling the time it takes to do a qsave, but setup in this fashion does make it more than reasonable.
Ok so we have redefined the built in AutoCAD Qsave to use our own custom one, setup navis to do an occational nwcout to update the files in the server. Last we need to use those NWC's.
Essentially you need to make an NWF file that is just a reference to all those nwc's. Lets call it a Master NWF. Note that this saves the nwc's to the same location as your dwg's so hunting them down to bring into navis should already be painless. If the need arises that you need to save a moment in time or keep/send an nwd of the projects current state..... just open the master nwf you've made and do a saveas to NWD Any other time you would need only open that nwf(s) to view the current state of the project.
Last edited by howardjosh; 2009-03-31 at 05:34 AM. Reason: I found some time to be more specific
Has this been resolved in Navis 2010?????