I’ve actually tested with our service account on your server, and things seem fine! @vwb do you think you can gimme more intel on what happened?
It magically worked now. Earlier in the morning I could not see any geometry (even thought the data seemed to be loaded by the frontend). Now its there. Will send some big boys
2 Likes
Missed the fact that this is for rhino 7. Works in rhino 8. managed to get 24000 balls to load. took a minute but once online works well.
https://app.speckle.systems/projects/1a169c644c/models/72ddb8cee0@3a8f8c4629
4 Likes
You’ve got… a lotta balls man 
Here’s the following challenge: in the same session, send those balls out, then move one and update.
Let me know how fast the update is 
1 Like
I just want to add to Chris point, because an app I develop had a similar feature and very we soon we realized how expensive is to “save” the model. Sync to central, etc, all that good stuff…
We had to fallback to save metadata on disk using a hash based on lots of info from that file. Sketchy but we haven’t heard. From 2024 there is actually a “Created Guid” to uniquely identify a Revit file that you can leverage.
2 Likes
Hi. Moved 1 ball and reloaded. Now I get a blank screen.
https://app.speckle.systems/projects/1a169c644c/models/72ddb8cee0
loads fine here:
This is unrelated to anything connector related - it’s probably down to the interaction between viewer, available resources, and browser.
We’ve heard you guys. I raised a ticket to get to this!
Thank you. Great that it works for you. I can not see the 24000. the 8000 works fine. I tried it with vivaldi browser and chrome.
Might be time for a fresh install of windows.
Hey there!
We’ve just released a new version of the beta, maybe you have already realized? Because we enabled “Update available” notification in our UI! 
Aside from all others, one of the biggest ones is support for receiving reference geometries in Revit!
You can create a new project in your workspace from now on!
Changelog
User Interface
- Projects can be created on selected workspaces.
- Notify the user when a new version is available.
- Send settings were in send filters before, they moved to model card actions to prevent confusion and misbehavior on changing things.
- Filters can be saved without sending the model.
Revit
- Receive models as reference geometry (direct shape).
- Performance improvements: 3x smaller sends.
- WIP: Simpler parameter extraction for all elements
- Fix missing support on sloped glazing.
- Fix receiving circles.
Autocad
- Fix receiving render materials from Rhino and Revit.
- Fix sending arcs.
Rhino
- Fix missing render material of layers on second send
.NET Connectors
- Simplify DI/assembly structure, and replace Autofac with Microsoft DI.
- Add model’s “units” information to the root object.
- Improve root and host object builders.
- Fix 3h session timeout on bridges.
Any feedback more than welcome! Looking forward to hearing from you to shape our next steps together!
5 Likes
Hey there,
New beta version has been released with new features, fixes, and enhancements!
Some outstanding items are as follows!
Brep support in Revit from Rhino! listen by @gokermu 
.NET Connectors
- Last selected account is persistent for later use.
- Improved async handing into communication between UI and Connectors
Rhino
- Fixed scaling issues when copy-pasting between documents
- Improved expiration checks for better robustness
Revit
- Corrected parameter integer values being sent as strings when non-integer
- Fixed issues with brep revamp
- Improved parameter export for Revit as more lightweight data
What’s Cookin’
We’ve started introducing Tekla Structures and Civil3D for Next-Gen Connectors, stay tuned!
Looking forward to your feedback!
5 Likes
Hey hey,
features and improvements have landed with the latest release!
Revit Views Send Filter
A searchable dropdown is added to select a view to send your data! Once the model card is clicked after sent is completed, Revit switches to the view that has been selected!
.NET Connectors 
Integration of multiplexing into our deserializer, we achieved a 3x increase in speed by dynamically managing data streams. Combined with our harmonized inner caching logic, this enhancement has led to faster access times and a more streamlined data processing workflow. Hats off to @adamhathcock and @Jedd 
Here you can find more details on the relevant pull request!
What’s coming on short notice
- Archicad and Civil3D will land soon.
- Revit categories filter on send.
Best!
6 Likes
Happy Monday with new features!
Revit Category Send Filter
A searchable list of items added under the Category filter that you can add/remove them. After your first send you can edit the filter whenever you want!
Tekla connector is on!
Tekla (2024) is now part of our send-only reference geometry workflow as a first pass! Kudos to @dogukan 
Click here to install, let us know what you think; it will help us shape its roadmap!
Rhino
- Rhino 8 crashing problems are resolved!
Best!
8 Likes
Hey, got some double precision meshes far from zero and they’re coming into Rhino with the telltale wiggle…
but only when the units are changed. The following works fine:
- Import DWG into Rhino, set meshes to double precision in import process, set units to mm
- Upload to Speckle
- Observe in Speckle viewer - meshes look good, no single-precision floating stuff
- Download into new document, units set to mm.
The above works all good. But downloading into a new document, with the units set to m, introduces the floating point issue.
Hey @chris.welch,
Thanks for the regression steps, will be helpful in tackling the issue. I’ll update you here when it is solved!
Hey @chris.welch ,
Can you please share the DWG file? I have tried reproducing but wasn’t able to reproduce.
Will send you the commit in a dm - can be reproduced (I hope!) simply by pulling down in both large-mm and large-m modes.
My hunch is that the meshes don’t have the MeshVertexList.UseDoublePrecisionVertices property enabled on import
1 Like
Is there a minimum version of the Speckle server that needs to be used to run the beta connector?
I’m testing out the Civil 3D connector, which works fine with app.speckle.systems, but on our own internally hosted speckle server, it gives me a 400 error
I think you’re quite behind possibly - which server version are y’all currently running on? To clarify: we’ve been operating under an “evergreen” assumption for next gen (ie, on the server we roll out to production on every successful push to main, and we assume a reasonably up to date version of the server).
i do believe a release from at least ~1mo ago should be valid. it looks like your server is the pre-workspace era from the response.
I shall go back to our IT team to find out. But if it as simple as updating our speckle server version, then fingers crossed that should solve it for us 
2 Likes