archigraphica

I just realized I didn't have the most current version on this machine. I installed it, still has these issues.

Here is a list of things that are not working correctly on my 1080ti machine. When doing an extrusion, pnt extrusion or 3D extrusion by a specified distance (not dynamic) it offsets the view to the left. Here are 4 screenshots overlayed to show the movement. When moving/copying a circle (and some other objects) the preview is a scaled distance and not actually where the circle is moving. So if it looks like you're moving it 100' it's actually only moving it 50' Where as moving a line the preview is correct. If this doesn't make sense I can make a quick video.

"Probably because it has been around for at least 25 years in its current state" Great point! Anymore my work consists of fixing disastrous Revit models and building sites for those Revit models. The single most beneficial tool that I could use is something to make sites easier. Get rid of the guessing game that is fixing imported topo lines! Interpolate X feet beyond the generated site. Live boolean. Sculpting tools. A road/sidewalk tool that would fit the topography up to a constructed road. Curb generator. Random terrain function. Retaining wall generator..... now I'm just getting crazy! But it's nice to dream.

Thanks Justin. For what I'm doing it doesn't need to be perfect. That definitely works. I run into this situation every so often so I thought I would throw it out and see if I was missing something obvious. Doesn't sound like there is a specific way to accomplish this accurately. edit - hold on, I just figured it out. The stair tool set to ramp. Do one for each rail, pull off a spline and make surface. A few more options in the stair tool and it would accomplish all of it. thanks for all the comments!

I could even go and distribute crossing segments and use the terrain tool. That seems like more work than it needs to be. All these tools it seems like there should be an easy way to do this. thanks for the reply!

This is something that's probably easy to do but I've never been able to figure it out. I'm trying to model an offramp for a road. There is 30' of elevation change. The ramp has a multi-radius curve in it. I have composite curves for both sides of the ramp but they are only in 2D. How do I make one end of the composite curves slope up 30' so I can sweep a shape along them and build the ramp? The only thing I can figure out is make it a Nurbz curve and fake it but I'd like to figure out something more accurate. thanks temp.fmz

This has been happening ever since I first switched to V8.6. This is a dumb thing but it has annoyed me for years and I just figured out what causes it. Now to figure out how to fix it: I have the "fit all" icon in the upper horizontal tool bar assigned the "F" shortcut key. I've had this same shortcut from as far back as I remember. Sometimes when I hit "F" it works correctly by executing the "FIT ALL" command, other times it switches the view to Axonometric and "LEFT". I assumed this was random but today I noticed something: if I do anything in the "LAYERS" palette then hit "F" it switches to the Axonometric and "LEFT" view instead of executing the "FIT ALL" command. Any interaction with the other palettes and the "F" key works correctly. Here's what I know: - the "FIT ALL" icon works correctly. It's only the shortcut key that doesn't work when you interact with the layers palette first. - Changing the shortcut key to a key other than "F" doesn't seem to matter. - IT doesn't matter if the "LAYERS" palette is floating or docked in the "Palette Dock". - Same effect if you're in Iso, Axo or 3-pnt perspective to start. It always ends in Axonometric. After experimenting some more it looks like interaction with any palette that has the stripes causes the error. I just usually use the Layers palette. thoughts? FYI - I am using a dual monitor setup.

I just noticed that the Dropbox option is gone? Is that intentional? Also please add to the suggestion list: space those 3 icons out in the lower left corner. I keep hitting the wrong one with my fat fingers. thanks!

Gave up on these along time ago. (but at least there's a new render engine that I'm never going to use)

Here's an easy one. I'm working on a building with multiple components. Exterior, Interior, FFE, etc. I'm old school so I have things divided up by layers. The issue is going back and forth between different layer configurations. (In C4D I would use TAKES) I was trying to do this with the Scene's pallet which I haven't really used before, but that doesn't appear to do what I'm after. If I could suggest adding 3-4 configuration buttons to the top of the pallet. (see the attached image) It could be as simple as setting your layers like you want then CNTL-LMB to save the configuration to that button. That way you could always click the button and have bring the configuration back. Make sense? Easy to do? thanks.

yes. Drafting has always been a lost opportunity for ADS. Look at how many use Draftsight.

Thanks! One of those little settings I've never looked at. Not sure why it extruded like that but at least it's an easy fix.

Here's something I've been seeing in this latest version. Typically happens when an object is generated from imported geometry. Started as a closed spline that came in from a DWG. Extruded it up. Shows as a solid but looks hollow. Doc doesn't fix it. Tried reversing and converting it with no luck. Usually I can pull a face off and extrude it to make a new piece of geometry but no luck. I did export it as a 3DS and re-imported it into Z. That one looks fine. There's something here the doc isn't seeing. Any ideas? https://www.dropbox.com/s/ennn1b2o1quldlb/pond%20shape.fmz?dl=0

It's exactly for this reason that we need the OLD tool options that you could set the specific number of facets (like most other 3D programs) of a curved spline or surface. Percentages of 100 don't mean anything when you're exporting. All the faceting scheme options and there's on where to put in a simple number like "40" so I have 10 segments every 90 degrees. This has been very frustrating since 7.

Well, if it hasn't been fixed in multiple versions it does need reported again.