Posts made by jiminy-billy-bob

jiminy-billy-bob

@kwistenbiebel said:

@jarynzlesa said:

new icons . why?

...cause the old ones were sooooooo 2012 .

So, back to 1999 ?

jiminy-billy-bob

@gareth said:

Jeff, that's the minimalistic look...!

Haha ! I laughed hard

jiminy-billy-bob

@cuttingedge said:

I think my trouble is more with sketchup 2013 than vray. the rendering part is smooth but I had bugsplat after bugsplat in the modeling part. which I think has nothing to do with vray.

It's a gamble for you to install Vray 1.6 on SU 2013. YOu may acquire a license for SU 2013, but keep the vRAY 1.6 beta on your more stable SU like v8.

In my experience, it's the opposite...
I first installed Vray 1.6 on SU8, and got bugsplats over bugsplats while modeling (I guess due to Observers used by RT). So I loaded it only when needed.
Then I moved on to SU2013 and have much less bugsplats.

jiminy-billy-bob

FYI the frame buffer on 3ds max with Vray 2.40.03 (the latest) tells me its core is 2.00.01

jiminy-billy-bob

2.00.02 according to the frame buffer.

jiminy-billy-bob

I think there are also numerous students using Sketchup, or schools, or...

jiminy-billy-bob

It surely depends on the artist. Some say it's not the tool, it's how you use it.
But even with proxies, VfS stays limited by SU for polycount. There aren't (yet) powerfull plugins like Multiscatter or Forest Pack. Dkendig said that over 400k proxies, Vray starts to chuckle. So there is still progress possible in that matter.
Besides, VfS still lacks some great features, like fog etc.

But yeah, now with proxies and dome light, we should see a significant improvement in image quality done in VfS !

jiminy-billy-bob

@rich o brien said:

Just like most companies, we’re not legally permitted to interpret our terms of use.

Why is that ?

jiminy-billy-bob

Wait a second... SU can benefit from SLI ?
Well, if true this is great news !

jiminy-billy-bob

Don't mean to interupt, but why is this in "SketchUp Discussions" and not the Corner bar ?

jiminy-billy-bob

@thomthom said:

Layer.visible, Layer.visible=, Layer.name, Layer.name= is there.

I know, I use them already. I was talking about change for these, in the LayersObserver.

@thomthom said:

(From what I understand, Adam has found a way to do this vis the C++ API.)

Hmm, would love to hear about this !

jiminy-billy-bob

@adamb said:

The litmus test for me is that I can walk the entire DOM and do.. whatever. Whether its in Ruby or C++. Yes, there are a small number of missing getter methods - Layer Color, Scene ordering - but the amount of gnashing of teeth I've seen posted the last couple of days around SU2013 seems totally out of proportion.

Yeah, well... I've not been around the SU-dev world for long, but even for the small things I've been doing, I miss a number of things : Layers being hidden/visible, layers being renamed, layers color get/set, layer delete, etc... There are some workaround for some of them (not all), but I feel like it should be native in the API.
You're talking about stability. Aren't native methods more stable than workarounds ?

@adamb said:

SketchUp is still a great, low-barrier-to-entry platform for modelling.

I totally agree ! But that's not the point

jiminy-billy-bob

@adamb said:

Dramatic changes/additions in APIs are generally a 'Bad Thing' in realworld software engineering. What you want is incremental (ideally backwardly compatible) progression. Think of it from the POV of the developers: having a new API for the latest version fo SketchUp is all fine and dandy, but you have N thousands of people out there on SketchUp 7 and 8 using your stuff. Having to develop multiple execution paths for different versions is a PITA and adds to instability.

I think most people are not complaining about the lack of "dramatic changes", but about basic methods still missing.

jiminy-billy-bob

By the way, will there be multiple beta releases during these three months, or do you plan to adress all the bugs for the future proper release ?

jiminy-billy-bob

@tig said:

I did write a whole raft of 'missing' layer methods...
I just thought I'd let you learn by doing...

I learn by looking at what you wrote !

jiminy-billy-bob

TIG is being modest, but he actually wrote a snippet for it : http://sketchucation.com/forums/viewtopic.php?t=20086

But don't use it as is, you need to modify it to use the method in your own namespace.
Here is how I did it (There may be some mistakes, I'm just starting ruby ! So check it, but it works fine for me) :

### LAYER DELETE METHOD ### ------------------------------------------------------
	#Simple modification of TIG's snippet delete-layer.rb
	#Basically, move or delete layer content, then creates an entry for every layer except one to delete, then purge layers, then delete entries
	
	def self.deleteLayer(layer, delete_geometry=false)
		model=Sketchup.active_model
		ents=model.entities; defs=model.definitions; layers=model.layers
		model.start_operation ("Delete layer")
		if delete_geometry
			allents=[]
			ents.each{|e|allents<<e if e.valid? and e.respond_to?(;layer)and e.layer==layer}
			defs.each{|d|d.entities.each{|e|allents<<e if e.valid? and e.respond_to?(;layer)and e.layer==layer}}
			allents.each{|e|e.erase! if e.valid?}
		else ### move geom to Layer0 etc
			ents.each{|e|e.layer=nil if e.respond_to?(;layer)and e.layer==layer}
			defs.each{|d|d.entities.each{|e|e.layer=nil if e.respond_to?(;layer)and e.layer==layer}}
		end#if
		group=ents.add_group();gents=group.entities ### temporarily use other layers
		temp=gents.add_group()
		temp.layer=nil
		(layers.to_a-[layer]).each{|layer|tc=temp.copy;tc.layer=layer}
		model.active_layer=nil if model.active_layer==layer ### ensure layer is not current layer
		layers.purge_unused ### purge layer from browser
		group.erase! ### erase! the temporary layer user, use set as was.
		model.commit_operation 
	end#def

Call it with something like self.deleteLayer(layers[layerName])