Posts made by rami_lpm

I use this.

def self.reload()
	Sketchup.send_action(CMD_RUBY_CONSOLE) 
	load __FILE__
	puts "reloaded #{__FILE__.to_s}\n"
end

Hello everyone. I've modified the plugin so it saves textures as png.
It will also respect(mostly) the names of already textured materials.

If 4088 works, so should 2044(or near). Actually, I'ts a miracle that some particular resolutions work at all.
The exported images FOV is 90.
The FOV you can modify is the viewer's FOV. You can change this in the javascript code as well.
You're welcome. I'ts good to see that this is useful.

AKHLPZ: I don't know how to solve that. I can suggest you generate the images with this plugin and then change the names.

brettsichellodesign: when you export with resolution 2040 it still shows the lines? what is your OS and sketchup version?

Sadly, this bug is related to the way Sketchup 2017 renders the bars when the image export ratio and the window ratio are different. It's not something I can fix at the moment.

Not yet.
Have you tried modifying the resolution to 1020,2040 or 4080?
What program are you using? this is for cubic panoramas, and the plugin generates the html needed to show the result.

the color can be adjusted? is there a command to do that? I can try and see.

I wrote the panorama plugin in 2014, and never had this problem.

Ok, I've just tested this.

model=Sketchup.active_model
view=model.active_view
cam=view.camera            
cam.aspect_ratio=1

Yes, in SU2016 the bars were transparent. in SU2017, the bars are black. That's a regression? I don't remember the bars ever being black.
I fail to see why this change would interfere with view.write_image
Has anyone else reported this problem when exporting images? maybe with other aspect ratio?

I've only encountered this in sketchup make 2017 on windows 10, Driven tested it on a mac, same issue.

I see. this happens in SU 2016 as well.
Apparently looking straight up renders the style background color, not the sky color.
To avoid this glitch, you should make them both the same color.

Hey pilou, is that on windows or mac? I've tested it on windows 10 and and the only problem was the border around images.

I've found a workaround, if you set the resolution to 1020 or 2036, the edges are gone.

Oh, that was a typo, I've corrected it.
Yes, this only happens in sketchup 2017.

Edit:
All right, there are 'magic' numbers at work here.
If you write the image with resolution up to 1020x1020, it comes out fine.
Above that the border starts showing, and as the resolution grows, it becomes thicker, and the gaps bigger.
At about 2000x2000, a square appears, as the lines are so thick and the gaps so wide that the lines meet in the center of the image.
At 2036x2036 the glitch is gone.
Aaaand its back at 2041x2041.

This is strange.

For the moment, I will advise the users of my plugin to use one of the 'safe' resolutions on their panoramas.

Hello everyone.
I've just noticed that when you export a square view with FOV 90, a dotted line border appears in the lower and bottom sides.
This breaks my Cubic panorama plugin.
Any ideas on how to fix it?

I've tried changing image size, aspect ratio, format, and setting view.line_width to 0, but the glitch appears anyway.

Here is my test code.

model=Sketchup.active_model
view=model.active_view
cam=view.camera				
pos=cam.eye

newFov=90
newAR=1.0
newIW=24

shadowinfo = Sketchup.active_model.shadow_info
shadowinfo["UseSunForAllShading"]=true

#face front
newTarget=[pos.x+1,pos.y,pos.z]
newUp=[0,0,1]
#set camera
cam.set pos, newTarget, newUp
cam.fov=newFov
cam.aspect_ratio=newAR
cam.image_width=newIW	

keys = {
 ;filename => "test2017a.jpg",
 ;width=>2048,
 ;height=>2048,
 ;antialias=>true,
 ;compression => 0.6,
}
model.active_view.camera=cam
#model.active_view.line_width = 0 #I don't think this does anything.
model.active_view.write_image keys 

I've attached the resulting image.

Thanks in advance for any tips.

Ok, I've tested it, it appears that the exported images have a black border (bottom and right).
Can anyone else confirm this?
I'll try and fix it.

I haven't tested it in SU 2017 yet. I'll see what I can do.
Thanks for the heads up.

Thanks.
Nice scene!
Yes, filenames are a little restricted because I wrote the plugin mostly for the web.
What filenames would you like to change?

Hi everyone.
I'm having trouble with UI.openpanel. It doesn't show the title when running in OS X, no problems in Win 10.
Also, UI.savepanel does show the title. Is this a bug or am I doing something wrong?

I tested it with this oneliner.
UI.openpanel("can you read this?", "~/","yes")

Thanks

Edit:
UI.savepanel does show the title.
According to Driven "the UI.savepanel and UI.openpanel use different nib files, so the behaviour is 'by design'..."

So strange.
Makes no sense that UI.openpanel has this bug and UI.savepanel doesn't.
I guess it's a problem with ruby and OS X. I'll see if there is a way around it.

Thanks for letting me know.

Looks great!
Doing this by hand is a real pain.

Thank you for the feedback.
That's a strange behavior. 'custom template' requests three template files: html, css and js in that order.
Can you try pasting this line in the ruby console and telling me if it shows the title?

UI.openpanel("can you read this?", "~/","yes")