Revit Launcher

[michaeld.183023]

ok. i figured why is wasn't working...RTFM. at least i don't get that error message anymore.

but now, after it starts revit, it causes the following windows crash;

Problem signature:
Problem Event Name: APPCRASH
Application Name: ad32lw_m.exe
Application Version: 2.1.0.0
Application Timestamp: 47ae8a98
Fault Module Name: MSVCR80.DLL
Fault Module Version: 8.0.50727.1434
Fault Module Timestamp: 4757746d
Exception Code: c0000005
Exception Offset: 000505a9
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: ab0e
Additional Information 2: 66b3b9f94ba4d274188850b0316d94c1
Additional Information 3: 173a
Additional Information 4: 3aaa3013d86aab16060fdfdd59efeec2

[david.kingham]

I'm not sure what to tell you about the crash, have never seen it before, sorry.

[michaeld.183023]

hmm...i get the same crash on my xp pro mahcine, with MEP 09 on it.

launcher does makes the local folder and copies the .rvt file, with the correct users file name, but still crashes on the 'open revit' option.

we're running distributed license installs for revit. does launcher care about that when starting the revit executable?

[michaeld.183023]

this is one of the errors logged from openstart.txt after initiating the "only open revit" option;

'
Set Jrn = CrsJournalScript
Jrn.Command "Menu" , "Close the active project , ID_REVIT_FILE_CLOSE"
Jrn.Command "ToolBar" , "Create a new project , ID_REVIT_FILE_NEW"

...does launcher look for the revit executable in a particular directory, other than the default install?

thank you.
-michael

[david.kingham]

It looks in the default location...C:\Program Files\Revit MEP 2009\Program\Revit.exe, that journal file you're seeing is created by the script, not an error from Revit. I assume you have your file named correctly now? the end of it should look like this M09_Central.rvt anything can be in front of that and the M could be and E or P or it could be MEP

[William Troeak]

David,

Great tool!

I have a quick question, Do you instruct your team members to delete there local files each night?

Or does the archive automaticly delete files when they get to a set age limit?

I am worried that the folder may get to big.

Thank you,

[peter.wood82285434]

I am really impressed with the effort of the Revit Make Local, and the collaboration. I really enjoy the automatic launch of worksharing monitor. I wonder if someone could add the SMP Seesaw Pro that will separate the Revit Program to a particular cpu on a dual core machine to give Revit more processor, or atleast bring up the program to remind us to separate the programs to CPUs.

With select worksets, I figured out that we need to select Yes for the worksets we want to see. Is there a way to select the active workset while in that dialog? Sorry if I'm beeing too picky.

When the option asks to select the workset, and I do so....the default workset that was last saved seems to be active. Am I not understanding this properly? I have reviewed many posts and it still is not working properly. I have reviewed the select_ws.txt file and really do not understand this one...also, our worksets are (not editable)Ductwork, etc. Is there anyhting I have missed?

Lastly, my machine is Vista Business, Intel (R) Core (TM)2 Duo CPU 2.66 GHz, 4 Gig Ram 32 Bit OS.

Any help is appreciated.
Thanks

[truevis]

.. I wonder if someone could add the SMP Seesaw Pro that will separate the Revit Program to a particular cpu on a dual core machine to give Revit more processor...

Should be easy enough to implement.

Have you actually found speed improvements by using SMP Seesaw on Revit?

[dbaldacchino]

I couldn't find anything significant and quantifiable. Plus the fact that it has to be done every time you restart is very annoying!

[peter.wood82285434]

The team members and I did a project with an MEP file at 45 meg, and with the hardware system peices I mentioned, it seemd to be better.

Now that I realized that we can open Revit model, and only bring some of the worksets to the local file towork with, I'm sure this will be more significant process enhancment.

Before, we were brining all of the worksets to the local file.

I guess we learned something here. Thanks