tt-acm / spectacles.revitexporter Goto Github PK

from intro page and likely from github as well

Good suggestion from @mnaugle-tt . Push people to the viewer app from Revit. Include a good icon, tooltip, etc.

As discussed with @mnaugle-tt and @JonatanS, let's export .spect files containing json data.

Currently when exporting a Revit model we give the user a loooong list of pre-checked boxes regarding which parameters should be included in the Spectacles export, resulting in a overly long and confusing list in the Spectacles parameter panel once opening the model in a browser. We need to curate this list to a certain extent to ensure the Web version is 'usable'.

I'd suggest either:
a) Set a smaller # of relevant parameters via a "TT Struct Default" button and let users add to it if necessary or...
b) set up a means of storing previous parameter settings for re-use (similar to print setting re-use settings dropdown.)

Suggested 'Default' Spectacles Object Parameters:
Beams/ Braces = Section Size
Hosted Level (+ offsets if present)
Cross-Section Rotation

Columns = Section Size
Base + Top Level
Grid Location

Floors = Family + Type
Level
Thickness

Nick caught this one - for whatever reason I thought htis was working already :\

@anagpuyol - can you please have a look? I'm guessing this has something to do with the unit conversion issue you've been working through...

As described in that repo, I'd like to refactor all of the code that serializes geometry into Spectacles.json files.

Relates to this issue in the Spectacles.Net repo:
tt-acm/Spectacles.Net#1

When saving the json file, the window is full screen and you can not adjust its size.
Should be a more reasonable size.

• add a cancel button, either in the windows bar or the main UI
• lock form size; right now it is unrestricted
• make OK button (and entire orm) a bit smaller. Not all users are old men like me 👴

Phongs are a little tricky, and currently we are getting lots of weird normal behavior with meshes exported from Revit. Let's use Lambert materials for the sake of stability and consistency - hopefully the normal issue won't pop up there too. Come back and add phong support on a second pass if needed.

@anagpuyol - can you please have a look at parameter filtering? The UI is populated properly, but exported .json files still contain all parameters, even if none were checked in this UI.

Spruce this baby up!

Hello dea,
I had a problem when exporting file from revit addin spectacles!!
Reit tell me failure of the external command in revit! whats wrong? i have frllowed all structural set up

regards

Add the MIT license to the top of every source code file.

@bhowes-tt @anagpuyol --

BH and I looked at this last week, when trying to export from R15 I received the following error:

Our initial thought was it may have to do with not having cameras in the scene, however through further testing I couldn't replicate with 100% certainty.

I just received the same error after installing and attempting to export my first model in R16. This time I re-started R16 a few times, tried the process again, and continued to have the same issue. I finally tried adding a camera and received this notification:

Which then succeeded in exporting the model. Once that text file was created I am able to export models with or without cameras.

The issue appears that without a camera in your first export after install you don't get the text file created which kills all exports.

need to tell users where to put the .dll and .addin files

Interesting one! When I have multiple (only two in my case) revit files open and I export the active one, I get the views from both open files.

Project 1:

Project 2:

Add spectacles and CORE studio logos to UI layers. Spruce up the UI in general as needed.

When selectiong the "Check/Uncheck All" in filter by parameters, revit and the exporter crash.

also had weird categories such as multiple "this text" tabs and a "this long text that I am making up as I type" tab

I took a first pass at this in the Repo. We need to do the same thing in the code. The solution, the project, any namespaces and classes ... etc, everything should be renamed.