Відео

Howdy Roman. In theory, yes, it is supposed to take all of those elements (materiality) into consideration as long as your materials are set up with the correct parameters. However, this video is a bit older...so i am not 100 percent positive.

@@DavidRBeach thanks for reply :-)

Not 100 sure i understand...but, not seeing something is usually one of two reasons. It is hidden, or behind the view plane. To figure out if something is hidden click the light bulb at the bottom. You can find out if something is behind the view plane by clicking on your elevation tag in the plane view, and visually referencing that to what you WANT to see. Remember, in Revit, pretty much everything is actually a section, including elevations. If the cut line for the elevation (section) is not on the correct side of your object it will not show up.

@@DavidRBeach I forgot to add this, but the toposurface suddenly disappeared after finishing the conversion process. Even with unlimited view range, nothing is showing up in the plans.

@@drvlive2023 - oh! Wow...not sure on that one at all. You might try this: Take the base file that you are working with (the topography imported from sketchup or wherever) use Revit to export it as a *.dwg. Re-import that *.dwg file, and use that specific file to create your topography. Revit, in its newer releases, seems to have become very picky about what format it will create a topo file from. Formatting the file as a cadd file (*.dwg) from Revit has helped in many instances. The other thought i would have is to make sure you are looking in your site plan view. Topography objects do not, by default, show up in any of the plan views. Only the site plan view.

@@DavidRBeach edit: it is indeed in *dwg Another thing is that maybe I should just redo the whole document.

@@DavidRBeach update: I repeated eveything and these are what happened: Toposurface generated in 3d view, but the file is still in import symbol in all floor plan views. I don't know anymore.

Hey Regina! Off by how much?? If it is off by what would amount to around 10-20 feet at the edges, with a slight difference in rotation, i would say that is common. This is why i describe the method as being "accurate-ish" but not survey level quality. Good enough for early ideation and academic studies, not good enough for documentation.

I am buried in preps for a couple of talks i am giving at AU this fall - but if you have a drawing/image/etc. i would be happy to put something together as soon as i can get to it. -dave.

In Revit or SketchUp?? In Skup...it is probably an issue of deleting or doing a boolean on the geometry. In Revit you can use the topo tools (split surface) to keep only what you want. If this is an image issue (texture map) then you are using Photoshop and positioning processes of the image in Revit. Just make sure that any changes you make to the image allow for the scale of the image and the scale of the geometry to match. If the scales don't match, you end up with a fictional site. Cool??

Howdy Jason! Yes, exporting a 2d graphic and editing in Photoshop works great as well. When teaching college kids (my primary audience), i sometimes add extra steps to reduce variables that can go wrong (like forgetting to set the view to 2d). We have also started grabbing images from Google Earth, overlaying those on the 2d graphic from Skup, and essentially "uprezzing" the pretty terrible resolution on the imported image map - takes a bit of time, but worth it for much higher fidelity results. On the off axis issue...someone posted the reason why this happens on why of my videos a while back, it had something to do (if my shaky memory serves me correctly) with the way georeferencing happens in programs that use real-world values (Flux, Google Earth, etc.) vs programs like Revit and Skup. If i can put my hands on that answer again i will be happy to share it, but my initial search came up empty.

Thank you for this reply. Anxious to know more about the axis issue.. however, is there any way to counter it, or do we just assume minor editing and trust that errors are negligible? Thanks again

Hmm..i haven't had that problem, but the work around is kind of an old school one that we used to do with SketchUp: Select the mesh in Revit that is intended to be the topography and export it as a .dwg file. Delete the original import from Flux.IO. Import the .dwg file that you just exported (yes, it is a bit ridiculous, but it works) and use the "create from import" tool in the Toposurface toolset. That should do it...

Hmm..i haven't had that problem, but the work around is kind of an old school one that we used to do with SketchUp: Select the mesh in Revit that is intended to be the topography and export it as a .dwg file. Delete the original import from Flux.IO. Import the .dwg file that you just exported (yes, it is a bit ridiculous, but it works) and use the "create from import" tool in the Toposurface toolset. That should do it...

Under the Insert tab/ribbon top and leftish...select the .jpg file and place it inside of the relevant view.

You definitely have to establish the scale once you are in your slicer (the program that defines how your 3d model is going to be printed). Best practice is to know the math, and check the output dimensions (outside to outside dimensions) of your model prior to printing.

Yup. Check the following link - post me back if something isn't working correctly!! sites.google.com/site/duhsascalecalculator/home -dave.

Howdy kelleyscause - check your print settings (setup button in the Print dialogue box) and make sure that your scale is set to 100%. The default is "scale to fit" which will not maintain your scale into Photoshop. The exact same steps will work from Revit to InDesign...just make sure that you are printing from a page layout in Revit, make sure you are printing at 100%, and your PDF file should come in at the appropriate scale.

Not sure if this is exactly what you are looking for - but this is the process i used: ua-cam.com/video/ZSA6-ttf70Q/v-deo.html. Hope that helps - post back if you need additional help.