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.
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!
6 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
When publishing Revit projects containing curtain wall elements the progress stays at “Starting to send” forever.
I also tried to send model groups containing stair families which managed to send but neither stairs or the model groups are visible in the viewer.
Hey Eugen,
This is using the latest version of the next-gen connectors right?
Could you send us a drive/dropbox link with a sample model to test?
I have used 3.0.0-beta.216.
On the modell groups I get the publish warning “Category Modellgruppen is not supported”. I’m using Revit in German. Maybe it ist a language problem.
When ungrouping all groups except the groups containing adaptiv curtain wall elements everything looks the publish succeed including the stairs.
But when ungrouping the adaptive curtain wall elements I couldn’t publish the project.
I have PM send two files to test.
I’m having the same problem after recently pulling the latest “dev” branch from the speckle-connectors repo. I now cant push anything to the server from Civil 3D, and it appears to stall at the serialization task.
Because I’m attached to the debugger in visual studio, if i pause the code during this period of inactivity, it tells me that no code is running. Ill rase an issue in GitHub with more details and test files…
Hi @jhdempsey86
We’re stabilizing a few things and have just fixed a few other issues. What you’re describing shouldn’t be happening but still can under a few scenarios depending on whether the thread is controlled by us or the host application. I can try to help on Github but the beta is still WIP.
Thanks,
Adam
Happy to say we’ve fixed this - both template 1a and template 2b pass through nicely. We’re imminently pushing out a new beta release, and we will ping.
I’d share screenshots and model links as proof for you to check but that might be a private project 
@clrkng this question might be best suited for you to answer…
We have pushed a Civil 3D corridor onto speckle, and we are trying to use SpecklePy to grab one of the featurelines, using its “id”
But when we provide that ID into the SpecklePy function it returns a 404 not found error:
We can see in the underlying code that the URL its generating is
https://ldd-emea.dev.jacobs.com/objects/f0447c2f94/6eeb5837fe108d5b5d427660a21b4eb7/single
In the speckle viewer, i can see the featureline is an object nested under the baseline object, and I can select it and see the “Id” in the properties on the right hand side
But if i click the button to open up this object in a new window, the new window what opens up is an empty model with nothing to show
Do you know what’s going on here? Is this by design? How can we use SpecklePy to get the featureline by its ID?
PS - there is no issue in getting the baseline object through its “id”
While many objects will have an ID, they will only be separately accessible if detached.
I’ll cede to @clrkng if the featurelines all are - but if they are not detached objects you can query the parent element and programmatically extract the featureline.
In next gen, featurelines are currently sent as type Dictionary<string,object?> under the properties > general properties > feature lines field of a Corridor object. See:
These aren’t queryable as objects, because they do not inherit from Base and will have no id.
Featurelines are also sent as Base under the BaselineFeaturelines list: if you are trying to retrieve these, they are not detached (unlike baselines), which is perhaps why your query isn’t working. This is a good reminder for me to detach them: fix(civil): detaches featurelines so they are queryable by clairekuang · Pull Request #627 · specklesystems/speckle-sharp-connectors · GitHub
Since the properties dictionary and featureline objects are a bit redundant (I wasn’t sure which form is more useful), is there one you’d prefer?