Stéphane

Did you have this issue on one particular file or on every files ? Did you need to this operation once and then it was fixed or did you need to do this operation after each release ?

I have got exactly the same error-message. Could you please develop on how did you solve the issue ?

Issue A Thank you for your input. So, that's it ? My model is now georeferenced ? Our partners ask us to have our geometry geo-referenced. Having the model far from User Origin is what they want. DWG exports have never been an issue, and they are happy with it. My initial question remains : What is the Document Georeferencing options window ? How does it impact the file ? Issue B solved What caused issue C was also what caused issue B. Since I deleted everything that was not in the safe area, they can read the IFC like before. Nice. Thank you ! Issue C solved Issue D I could live with that issue, but If you have an idea about it, I would be glad to read it.

Progress has been made. Issue C solved. Thousands of objects were at User Origin, and a 3'000 km line (dont ask me why) between it and Internal Origin. So, fuzzy walls are caused by scattered model I guess. Not only the Internal Origin needs to be next to the project, but also nothing should be out of the safe working area, 5000 m of the Internal Origin, according to @Tom W.. Big thank you @Tom W.. By the way, opening the IFC file with Solibri, I discovered some floating wall caps (without the walls) at User Origin. So, I deleted each single wall caps in VW (funnily enough there were all at Internal Origin). After re-exporting an IFC file, opening it in Solibri, no more floating wall caps. Feedbacks for issues/questions A, B and D welcomed !

The blue cross hairs is 180 m away of the fuzzy walls. Is it too far away ? Yes, indeed. Well to clarify to everyone : The blue thing is next to my project (180 m away), because I read somewhere that it should be next to it otherwise we get fuzzy walls. Red and green thing is far away because someone in Switzerland decided it would be cool to have the 0;0 somewhere in the middle of the Atlantic.

Since you were always super useful to me (also others of course but I dont know each ID by heart), I hope you won't mind that I summon you in this topic : @Christiaan @zoomer @Tom W.

Hello, Our engineers need to be able to import our exported DWG files and everything is placed at the right coordinates, without doing anything. I have several issues since I tried to georeference my project. This is how my file looks like : And this is how my document georeferencing options look like : My questions and issues, since the document is georeferenced : A. Is my file set properly ? Also, I am not sure on how the Documents Georeferencing options impact the file... And there is an option to georeference a layer in the layer manager, what does it do ? B. Engineers cannot use exported IFC file anymore using BIM Vision or Revit. However it works with Solibri with a mention "widely scattered models". After a check, some objects are somewhere next to the internal origin in the IFC but nothing in the VWX. -> What causes this issue ? Scattered models ? Project too far away of the internal origin ? C. Model in design space, openGL, looks like that. -> What causes this ? D. Hatches follow the rotation of the 2D rotated plan. Rotation in walls is unchecked in the hatch options. Hopefully, this doesn't occur in layout space. -> Bug or normal behavior ? A bit annoying when I do a quick and dirty print from design space.

Bumping in the thread 10 years later.. @PVA - Admin Has the feature – Rotate Page Print Boundary – been implemented ? Would still be useful. Yes it is definitely the way to go for common plans you want to publish weekly. However, sometimes you want to print something directly from the drawing space – quick and dirty – in order to solve a detail with a pen in you hand, old fashioned style. Create a viewport on a sheet layer : 5 min Print from drawing space : 5 sec

Hi, I have the same issue, but I couldn't solve it. My file structure : - Class for slab objects - Class for wall objects - Class for each component used in slabs and walls, sometimes I use the same class, for instance "Concrete". They are set so visible. Now, if I set the class "Concrete" to invisible, it removes the unwanted hatch of the slab objects in the exported DWG, but it also removes it from the walls. I want the components hatches removed from the slab objects but not from the wall objects. When I export the layout to PDF I don't have this issue : Slab objects don't generate their components hatches, because they are not cut. I would like my DWG to be exactly like my PDF.

@Tom W. Pretty nice solution, thank you ! I have tested it and it looks much more efficient than these wall features. @cberg Thank you for your honest answer. "If it sounds painful. It is. And we've all been there. " Somehow, that comforts me, thank you. I think I'm going to do a mix of your solutions : I will only split the insulation part as Tom W. suggested it and class it amongst everything that is under the slab and deactivate it in plan. Instead of duplicating the openings, maybe I could just split the wall above them and offset the bottom accordingly.... Need to test this.

Hello, I would be glad to get your precious hints on my issue. Since one drawing is better than one thousand words, please find my issue below 🙂. How would you draw such a wall ? I tried walls features but I have 2 problems with them : - difficult in the angles - somehow refuse to show the hatch I want, always shows the extrusion filling attributes in a hidden line section viewport (so it is always a solid color with no contour

@Tom Klaber You described exactly what I experience when I do OpenGL renderings in VW2021 SP5. What I observed : - Memory pressure stacks after each renders. When memory pressure reaches 34 GB, VW crashes. - Save, quit and restart VW release the memory. - My routine to prevent a crash when I do OpenGL renders : 1. No more than 5 renders. 2. Save, quit and restart. 3. Back to point 1. - I lost a keyboard last Friday because I did 7 renders before saving and had to redo everything 🙂

Still an issue in VW 2021. VW doesn't release memory after an openGL rendering. I have to save&restart after 10 pretty basic renderings.

Thank you very much for this, @Pat Stanford. I will share here the conclusions for other VW CH_FR users (Potentially 2.2 mio users 🙂) 1) My door is a 'Door CW' not a 'Porte' 2) The fields in the OIP are actually translated from German. So you need to call them in German. 3) The IFC fields are always in English. 4) If you click on the little arrow in a cell and select "Database" and the PIO you want ("Door" or "Window" or whatever) you will find a list of all parameters you can use. So what I was looking for was : ='Door CW'.'BaseQuantities_Height'/10 (/10 because BaseQuantities are in mm but I work in cm) ='Door CW'.'BaseQuantities_Width'/10 ='Door CW'.'Türhöhe' ='Door CW'.'Türbreite' ='Window CW'.'BaseQuantities_Height'/10 ='Window CW'.'BaseQuantities_Width'/10 ='Window CW'.'Fensterhöhe' ='Window CW'.'Fensterbreite'

Hello there, Awesome explanations, @Pat Stanford, thank you for that. My VW is set in French and =(Door.Width) doesn't seem to work. I use a PIO which is called Porte. In the OIP there is a field called "Largeur de la porte" =(Porte.'Largeur de la porte') doesn't work neither. Questions : Does your trick work for each PIO ? How do you get the name of a PIO ? Is it the one written at the top of the OIP ? Is there an official English name hidden somewhere ?