polyxo

4.5.20 (without any changes on the computer) wasn't able to start today. Win64Cuda crashed at startup, both DX and GL. Installing over the existing installation seem to have fixed the issue for now. Something else: I think there's still something wrong with navigation and I believe I have found a possible reason. In earlier versions I can not remember that Zooming with RMB or Hover with Pen ever worked with both dragging horizontally and vertically. I think Zooming used to be mapped to just up and down. The new behaviour doesn't add anything useful but seems like a source of error for me – simply because that way it is possible to give 3DC ontradicting input. If drag to right is mapped to + and also drag up to + and the respective opposite directions to – one needs to drag in perfectly straight lines to give the program unambiguous input. As soon as one drags a little bit to the left while dragging up there should be also – which registers. I figure that there are some clever filtering mechanisms in place for such funcitons, but I indeed run into undesired spontaneous Zoom direction inversions. I'd like to turn zooming by dragging to the left and right of, I don't need it anyway.

No, I have this too (it started in versions after 4.5), without hardware changes or recent modification of Windows services. It is a very massive malfunction, one simply can't work without proper Zoom Funktion. I reported in the Beta thread.

This is a neat feature but the hotkeys are actually wrong, No geometry is getting copied here: Ctrl+X and Ctrl+V was better.

I frankly would need a bit of narration in this video to identify the details. For navigation I don't use the Icons but rather use the mouse but it seems that there's quite a bit of stuff to look into. I'm also pretty sure that with one of the 4.5 releases the default Zoom direction got inverted. I didn't have to dial in -1 in earlier releases.

In recent versions I have bad troubles with Zooming. Its actually a combination of behaviours I don't like. 1. Zoom often behaves sticky in a way that the function still gets executed when I let go RMB. Any further movement of the Mouse/Pen still keeps zooming the camera and I have no idea how to "drop the tool". Pretty terrible. 2. Zooming no more wraps around at Top-Bottom Screen borders. As soon as the screen border is reached, the mouse pointer sticks there and further dragging up or down doesn't do anything useful any more. I can only zoom with small movements, by making sure not to touch the screen margins. Does anyone know a cure for these behaviours? No hardware changes here. I should add that I have inverted the Zoom direction, so that dragging upwards zooms in.

You will not find these controls in Camera navigation. The default hotkeys were removed as one considered the Gizmo a good replacement. But luckily a setting in preferences was added which gives you back the old behavior (see screenshot).

Good! This old hotspot problem should at some point get fixed too. Check where my cursor is, I find myself checking and unchecking options when I drag up and down the page with the pen.

I actually fiund the direct action offered by the hotkeys better and had no problems - thus far rarely used the 2D gizmo. Hence my question if there was some way to restore these hotkeys on a per user basis, even if the default mapping is gone.

This is nothing at all critical... I see that you now have removed the default hotkey binding for interactive manipulation of stencils, materials etc. Is there some secreet way left to re-assign them? Pressing on the buttons in the Preview Options panel with the End-key pressed does nothing...

Andrew, Edit/Mesh and Texture resolution in 4.5 lets the the mesh explode. I used the sample model creature with default 1024px map and subd to 22912 faces and tried to increase to 2k. Do you see this too?

Oh, there it was! Thanks you Malo.

Could someone please give me a hint where to find the setting to invert the Zoom direction? I don't find that setting in the Camera customization but it must be somewhere – some of the presets do invert the direction. Thanks!

Thanks, unfortunately it will not work in R7 (the release which brought 64 bit). Those (probably few)who still use Zbrush 32 might be able to make the older applink work.

This Applink doesn't work any more. For Zbrush R7 64 it needs to be remade to support the 64bit version and also the 32 bit version needs a revision, so that it installs in the appropriate folder.

This actually shows a pretty unconventional and quite simplified approach to support structures. Usually things rather look like seen here. Cleverly constructed lightweight structures, often from another material than the actual printing material, which support the actual print – not on a few points only, but as a dense scaffold. They still can get easily broken away or washed away with suitable solvents. Here's some more images.

Whatever man...I also have better things to do. Your nickname at least is well chosen. PS: There was nothing wrong with the deleted statement you quoted, although you again want to appear clever. I deleted it because I didn't want to open up another can of worms in a nasty discussion I wanted to leave.

Alphagrunt, please refrain from assumptions about my background – let's instead stay by the facts. Dealing with support geometry properly certainly isn't something Andrew could code up within a few hours. Given the fact that finalizing physical output isn't 3DC's current focus I personally think that one should use existing solutions for that task. You may not agree, but that's no reason to get unfriendly.

My answer should have been specific enough to figure that a lengthy explanation on support material wasn't necessary. All I want to point out that one can build support structures inside software which ships with the printer or dedicated tools, such as Magics.

In my understanding the creation of support geometry falls into the realm of the software used to talk to the 3D printer. Support geometry also needed to get tagged in a specific way, so that the particular printer understands that it needs to lay out support material here and the actual model material elsewhere. How this works exactly will likely differ between printer brand and printing principle.

Hmm, I use two regular screens and a Cintiq and don't see problems with monitor switching on multimonitor enabled apps like Photoshop.One can declare several monitors to be logically just one for the Tablet or simply hop from one to the other without even moving the hand – faster than with the mouse.

Yes you can. File/Import/Mesh for Voxelization In the panel which comes up check "import w/o voxelization (then it comes in as the raw mesh) File/Export Object – in the Exporter you can dial in a value or drag the simplification value. Hope that helps.

I currently have not much time to test but the speedup in Undo makes editing a lot snappier. Nice!

How would you want your stylus to work then? Regardless how you set it up, you will have to press the Alt key for at least some camera actions when the object fills the screen entirely. Unless you prefer using the Navi-Zone around the viewport or or using the Navigation Icons at the top right margin of the vp.

You know that you can store app-specific settings for Wacom devices, right? Therefore you can use any config in 3DC without losing what you're used to in other apps. I find the LMB/RMB Combo most powerful in 3DC, AS it gives you the context menus too. Causes no issues with my Cintiq.

I don't think that removing the Bug report and feature request sub-forums was a helpful measure. The reasoning is understandable (streamlining feedback and having things neatly organized in one place, so that there's less work also for those who maintain this forum). That said, I think using three different formats, which even require separate logins simply expects way too much from normal customers. No other software I know has feedback rules that strict. Not everyone who has something helpful to contribute also brings along the dedication of a serious Beta Tester – and that's perfectly fine. Even those who are on the release version and don't use unstable tools could encounter critical bugs which are still there. I don't see why those users shouldn't be able to simply shout when something is wrong – without first digging through a non-trivial feedback system. What I now expect is regular calls for order by moderators, directed at people who in fact did a good thing: Reporting a bug or suggesting a feature.Those who received a reprimand for having spent time to describe what could make the software better might opt to rather post no more. The same is true for people who only read what happens when posting in the wrong place.