You are not logged in.

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

  • "wannabeartist" started this thread

Posts: 20

Location: Finland

Occupation: 3D Artist

  • Send private message

1

Friday, March 19th 2010, 11:06am

Beginner needs advice for making first pano

Hi!

I'm just trying out krpano tools for the first time and despite reading the documentation, I'm afraid I'm still a bit lost.

I'm trying to make an indoor panorama, from 3d renderings - should I render out the 6 images for cubic panorama or what is the best way for this sort of thing?

I already tried this by myself, following the kmakemultires tutorial (is that what I should be using?), but with default settings the walls of the room get "pushed" into the distance a great deal. I made a very simple test scene with a camera inside a 5m x 5m cube. The sides of the cube all have separate colors and the camera is set to have a fov of 90 degrees (correct?). The resulting pano gets really stretched as you can see from the screenshot - what am I doing wrong?

Thanks!
wannabeartist has attached the following images:
  • Clipboard01.jpg
  • Clipboard02.jpg

  • "wannabeartist" started this thread

Posts: 20

Location: Finland

Occupation: 3D Artist

  • Send private message

2

Friday, March 19th 2010, 12:54pm

I found that the fisheye setting gives much better results, but it's still quite distorted. Yet I have seen such fantastic looking interior panos made with krpano - what's the secret?
Anyt tips most welcome! *g*

3

Friday, March 19th 2010, 12:58pm

RE: Beginner needs advice for making first pano

should I render out the 6 images for cubic panorama or what is the best way for this sort of thing?
I think this is the best way, as cubic panoramas feature the best viewing quality and the panotools use them anyway. Make sure you name them by this scheme, so the tools know how to align the cubefaces:
"pano_l" - left
"pano_f" - front
"pano_r" - right
"pano_b" - back
"pano_u" - up
"pano_d" - down

I already tried this by myself, following the kmakemultires tutorial (is that what I should be using?)
If you want. :) It depends on what you want to do, but it's no mistake. Keep on practicing with it.

The sides of the cube all have separate colors and the camera is set to have a fov of 90 degrees (correct?).
Use a (much) lower fov value and try some fisheye settings. That should fix it.
0100011101101100011001010110100101100011 0110100000100000011010110110110001100001 0111010001110011011000110110100001110100 0110010101110100001011000010000001001010 0111010101101110011001110110010100101110 0010000001000101011000110110100001110100 0010000001101010011001010111010001111010 0111010000101110

This post has been edited 1 times, last edit by "Dr. Schneckem" (Mar 19th 2010, 1:14pm)


  • "wannabeartist" started this thread

Posts: 20

Location: Finland

Occupation: 3D Artist

  • Send private message

4

Friday, March 19th 2010, 1:06pm

Hey, thanks for the tips!

Just to clarify the fov - do you mean I should render the images with a smaller fov?
Then I would need to have several pictures for each side of the cube and stitch them together before giving the 6 pictures for kmakemultires, right?

Sorry for the n00b-questions :D

5

Friday, March 19th 2010, 1:13pm

Ah, you were talking about the fov of your 3D software, right? I meant the fov in the pano xml. The distortion of your pano is founded in a small resolution of your cubefaces, I guess.
0100011101101100011001010110100101100011 0110100000100000011010110110110001100001 0111010001110011011000110110100001110100 0110010101110100001011000010000001001010 0111010101101110011001110110010100101110 0010000001000101011000110110100001110100 0010000001101010011001010111010001111010 0111010000101110

  • "wannabeartist" started this thread

Posts: 20

Location: Finland

Occupation: 3D Artist

  • Send private message

6

Friday, March 19th 2010, 1:19pm

Ok, thanks! I will try this again with a much higher resolution...

7

Friday, March 19th 2010, 1:25pm

That's not necessary for your example, your future panos will have a higher resolution anyway. So just use a smaller fov value in your pano.xml. The fov is in the <view>-tag:

Source code

1
2
3
4
5
6
7
<view stereographic="true"
		  fisheye="1.0"
		  fov="150"
		  fovmax="150"
		  hlookat="0"
		  vlookat="90"
		  />
0100011101101100011001010110100101100011 0110100000100000011010110110110001100001 0111010001110011011000110110100001110100 0110010101110100001011000010000001001010 0111010101101110011001110110010100101110 0010000001000101011000110110100001110100 0010000001101010011001010111010001111010 0111010000101110

  • "wannabeartist" started this thread

Posts: 20

Location: Finland

Occupation: 3D Artist

  • Send private message

8

Friday, March 19th 2010, 1:47pm

Thanks!

I messed with the fovmax of the fisheye-action in default skin.xml (because it seems to override the settings in the xml as it's included).
With fovmax of 75 degrees my actual room render started to look really nice - gotta dive deeper into tweaking this next, thanks again :)

9

Friday, March 19th 2010, 2:27pm

Hi,

was a - maxpixelzoom="1.0" - setting (in the xml) and low resolution pano used in the first try?

this would explain the large fov, because the zooming/fov was limited to avoid zooming the source pixels,
just remove the - maxpixelzoom - setting and replace it with - fovmin="10", then the zooming/fov
limit is independent of the screen and pano resolution,

btw - yes, a fov of 90x90 degree is correct for cube faces,

best regards,
Klaus

  • "wannabeartist" started this thread

Posts: 20

Location: Finland

Occupation: 3D Artist

  • Send private message

10

Friday, March 19th 2010, 7:00pm

Thanks for the tip!

Yes it was on and the resolution was of course insufficient - I'm really happy with the results now :)