PLEASE PLEASE 2014 PLEASE FIX THE ZOOM

pbacot · 3 Mar 2014, 19:06

I wonder how prevalent is the view this is a big problem. I use SU a lot, and though it can come up, there are known ways to avoid it, and it rarely occurs for me.

I can see it would be good to fix this and some other issues that must be explained to every user. Low on my list anyway.

mitcorb · 3 Mar 2014, 19:21

Hi, Gerald:
Understanding the conditions that cause this phenomenon to occur helps a great deal in avoiding it. Maybe you could post a .skp file or an image that describes your issues. That way, the responders can provide some guidance.

What would be ideal in at least one case is if you could "press a button" for automatic scale up of the workspace such that while you input a value of say 1" the program is operating at maybe a scale of 10x or 100x scale, but reports it at 1" or whatever, to avoid the tiny open faces problem. And the zoom function would be adjusted likewise. Until that happens, one method is to use components and make a scaled up copy/instance on which you do your operations. The originating component at 1x scale will follow along with whatever you do on the large version. When finished, delete the large copy. This is a technique that Dave R uses regularly in his work.

There are other conditions that cause the camera clipping, but this is just one.

JGA · 3 Mar 2014, 20:27

I have to admit agreeing with Gerald, the clipping has been a "feature" with SKUP for as long as I can remember. While there are workarounds (the explode & regroup imported items is a new one for me), it's still a nuisance while modelling.
Anyway, I've yet to install 2014, so I'm hoping for the best with it in other ways, as 2013 turned out to feel more responsive than v8.

GMthompson · 4 Mar 2014, 00:29

i was starting to think i was out of line, the thing is SU is not the only 3D software we use, and i don't have those problems with say turbocad

i know how to work around it, but it can become a real frustrating thing when trying to create faces by zooming in to correct a small error, my favorite workaround is the rotated rectangle ....kind like a fix pasting over the whole area, i find myself getting to picky trying make everything perfect

to the people that posted in effort to offer suggestions thank you, i kind of got the impression i was stepping on toes, if so my appologies

GMthompson · 4 Mar 2014, 00:36

another workaround i use is to create a 2 sided box with faces around where you are trying to zoom in, the closed in faces at times help if you eliminate background, "if that makes sense to anybody"

mitcorb · 4 Mar 2014, 00:59

"if that makes sense to anybody"

Yep.

mac1 · 4 Mar 2014, 07:10

In stead of calling this a bug maybe sould be design deficiency.
Clipping planes are used in 3D program to limit the amount of rendering that is required. Otherwise the app will process ( render) to infinity. The are 6 planes top, bottom, left, right and z far and and z near. OpenGL has the extension to allow the user to control the clipping.
I think its stable release is 4.0 but Trimble ( Google) continues to state the min system requirement spec is >=1.4. OpenGL was backward compatible but that has now changed and in fact most have deprecated at ?? with the MAC's out front. In some posting bloggers are stating the DirectX vs OpenGL competition is over basically at DirectX 10 or 11.

For some reason SU designers aka Bacus (sci) never seem to discuss this issue and what plans are going forward. If this was a big issue with the paying base it would have been fixed some time ago so you are stuck with learning the work arounds. IMHO the help manuals are not good in this area.

mitcorb · 5 Mar 2014, 13:36

Haven't read the manuals, but, due to some display issues (invisible selection box). I updated the driver for my GTS450, and since then (coincidental?) I have been getting blue screens, but not so far in Sketchup. Only while browsing.
The adjustments for display within Sketchup seem inadequate, but I don't really understand those settings.
I do appreciate the purpose of, and the reason for, the clipping thing, however.

mac1 · 5 Mar 2014, 16:21

With todays design of windows I would guess this is a xxx.dll problem associated with the graphics driver. Usually you get a error report to go along and if want to go to the trouble of laoding the reader of those from MS you can open and see what it states.( Think it is in binary)
FYI from the windows OCA ( Online crash analysis)
70% caused by third party code => dll's
15% unknow ( memory too corrupt)
10% hardware issues
5% by MS code
Try graphics driver update or debugging tool at http://www.microsoft.com/ support;
Event logs look at for kernel memory dump
debug tools Win debug, Not my fault tool, drievr verffies, run verfiver .exe

mitcorb · 5 Mar 2014, 20:01

Thanks mac1.
I will have a look into this. Including, talking to a local service.
I have a text file grab of the data in the little details expansion area of the dinky little report box.

mac1 · 5 Mar 2014, 22:00

fyi;
Think you will have to look at % systemroot%\memory dump. If not getting dump paging file maybe set too low;
c:\windows\mini dump look at with debugger.
If memory not failing me the little box is set to allow ok to send data to MS OCA?? Service will need the dump files