Posts made by jgb

I figured as much. thanks.

It is a minor annoyance to be sure, but is there any way to by-pass the SU/Trimbel Welcome screen and open directly into SU?

Like SU 8 used to do?

@jql said:

My wish for 2016 would be that Trimble would hire someone just to try every button and function Sketchup has and find things like:

• Wrong or unexpected behaviours;
• Inconsistent UI;
• Recurrent feature requests;
• Standardization of usual processes;
• Etc...

No need for Trimble to test every button and function. They will not learn much from doing that. SU needs to be worked to discover "bugs" and inconsistencies.

All Trimble and the SU development team needs to do is READ the past posts here and in other SU forums to learn what goes wrong and needs fixing.

I have bitched (and others too) about these problems for years, and they are still with us.

• Near field clipping
• Hyper zoom (click on empty space when panning...)
• Z fighting
• "constrained by..."
  There is a lot more, but only silence from the SU team.

I'm not talking about enhancements and new stuff.
This is OLD stuff that still doesn't work right.

But SU dev has always been far more interested in new bells and whistles for next years SU than in fixing past problems.

@unknownuser said:

I think all we need to resolve this is a modifier key, which if you hold down turns off axis/perpendicular constraints, on move, line and circle tools. I think "Ctrl" is the only obvious key that isn't taken by all those tools. If I understood you correctly....

Seeing as "CTRL" has no effect when drawing a line, I would agree to using it as a modifier key to override the "Constrained" feature.

The "ALT" key could also be used, but in limited testing, I noticed a strange effect of placing a line temporarily in position, sort of.... no time to follow up on this.

And to JQL.....

The "SHIFT" key modifies a line draw to maintain a set vector/direction. It does nothing to prevent "constrained".

@desertraven said:

Okay here it is,

5. !!!!! Give us an override for that obnoxious constraint engine and give us object-snap options already!!!!!!! Try tracing something that's not supposed to be square????? :berserk: :berserk:

Yeah!!!!

Drawing a line from endpoint A to endpoint B should NOT be a crapshoot because B is not exactly on an axis projection. I know that if A to B is "constrained"; ESC then going from B to A works. But that is double work and often the "constrained" message is not forthcoming. So that blows a solid up, and Curviloft goes nuts, followed by a 1/2 hr to sleuth out the error.

Thank you. I can sleep now.

MS is going to really push Win-10 real soon now.
I have signed up for an early (free) copy.
But how well will SU-2015 work with it?
Has anybody tested it, or is SU-2016 going to be the Win-10 version?

I just noticed something; whenever I import an SU-8 model into SU-2015 and make edits to some faces (in what was a perfect solid in SU-8 or SU-15) I often end up with multiple faces off single lines that SI-2 does not see, and SU says it is no longer solid.

It has happened in 3 models so far, and I quite often get 3 faces on a single lined perimeter. When I delete just the extraneous faces, it regains solidity.

It does not happen when the solid originates in SU-15.

Betchya nobody else sees this.

While I really appreciate TT's SI2's ability to fix problems, (for me it works well about 90%++ of the time) it would be better if it could simply highlight an "unfixable" problem, now indicated as "info" and maintain that highlight when exiting the tool, so I can find it fast and fix it manually.

Perhaps, by creating a group on its own temporary layer that traces/duplicates the unfixable errors and renders them in red lines/faces, as is done now to identify those errors. That way I can see and fix any problem outside SI2, then simply delete the highlight layer/group.

Just a thought.....

I found it impossible to fix. The bottom face was 3 faces bounded by a single line rectangle. I could not delete a face, it kept coming back if I tried to fix something on an adjoining face. Then when I thought it was almost OK, I did another SI which found many problems. So I said let SI fix it. Ended up with about 8 valid lines and faces. SI "fixed" it by blowing most of it away.
I blew the rest away, started fresh, and that turned out OK.

So, anybody, I don't need it fixed. I posted it for ThomThom to ferret out the why.

Another "shiny" but flawed non-solid. Multiple errors not detected; open faces, multiple faces (the bottom has 3 faces).

I was adding corner cubes and did an interim solid check

There were other errors it fixed, but somehow not these.

SI2 reports "shiny" but it is not.

Now that I knew where to look, I copied the comp to 1 side and saw the white face.
Gone in 5 seconds and fixed! Thanks again Dave.

In its original location those gear teeth in that area were visually covered by another gear (comp) so I could not see it. It was also the same area that SI2 found numerous non-fixable errors, and in my manual search and cleanup, missed that one. I never looked at the isolated comp I sent to this thread.

ThomThom: Is this sort of error findable or fixable in SI2?
I don't recall having this sort of error undetected in earlier SU-8 versions of SI.

Thank you. That is in the very same small area that I had a lot of SI2 found errors (most it could not fix) that took a while for me to find (no circles!!) and manually fix.

How did you find it so fast???

Another problem.....

Inspector says "all Shiny" but SU-15 says not solid.

Why??

SI2 says Shiny, but it is not solid.

That would be great.

Thank you.

I do not recall seeing anything other than the warnings box.

I will try to set up a "fail" and see if I get that same error message, or see a viewport.

Stay tuned......

10 min later ====================

Well I did not get the same error msg with this test, but I got an error msg without a circle or a "viewport" pointing me to where the error was, in this case an external face.
It is at the top center of the comp.

Unless I zoomed in, I would not see where it was, especially if it were much smaller.

The error is hard to find without a red circle.

I don't know if something ain't right or what....

I really like the improved SI over what I had been using in SU 8 for years.

I'm now on SU-15.

But I just noticed that the found errors are not highlighted with big red/yellow circles. Up until yesterday, that was not a problem, as SI fixed 100% of my errors.

But then there was a new error (can't remember exactly what) that only offered info and no fix. The problem was the line was so tiny, even in red, that it took me about an hour to find it in an object with over 4,000 lines. Only by zooming in and going over the whole thing twice (2 separate but identical errors) did I find the tiny red lines, deleting them, and all was OK.

No red circle to guide me to the errors. Why?

Kris

I mainly agree with you when in development stages of an SU model.

But not all of your concerns apply to presentation and just looking at a result.

First off you would not have to be on your feet all day, most VR can be effective sitting down. You would spin the model around rather than simulate by actually walking around, much like the SU native walk-around. Take Gravol before doing this.

Also, what grabbed my attention is for visualizing curved surfaces, such as airplane fairings, and trying to smooth them out to conform to various intersecting surfaces. Can be tedious in current SU, but using VR you can simply tilt your head to see irregularities and fix them. At least I think that would be true.

It's a start.... I remember way back in the late 60's the corporate IBM mainframe got a new "high tech" 14 inch video monitor (black and green, 24 lines by 80 char wide text only running at 300 char/sec.) for the system console monitor to replace the slow console line printer. Gee Whiz Batman, that was cool!! My very learned and tech savvy boss stated to the IBM rep that "he could see its use for the computer console operator, but not at all useful for a programmer who needed to see his work on paper". I kid you not!

Juju

There is a whole lot more to Hololens than its ability to run on Win xx. There has to be an interaction from SU to the HL display and an interaction from the HL to SU (ie: pan, zoom, tool use, etc).

SU computes an object in 3D but it natively displays in 2D.
And the HL takes its vue cues from hand motions as well as motions of the headpiece itself.

None of this is native to either Win XX or SU 20xx. (yet!!)

Probably too much to do for SU-2016....

Incorporate Microsoft's HoloLens.

That would sure beat a mouse and a 32in screen.