Re: [hugin-ptx] Re: Hugin for games

2010-07-12 Thread Bruno Postle
On 12 July 2010 16:24, Tom Sharpless tksharpl...@gmail.com wrote:

 Does anyone here have, or have the ability to make, super-wide screen
 video from a favorite game?  I would like to convert some of that to
 Panini, as a demonstration of what is possible.

Many years ago there was a fisheye version of Quake. If you can find
some in-game footage then this would be easy to convert.

-- 
Bruno

-- 
You received this message because you are subscribed to the Google Groups 
Hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx


Re: [hugin-ptx] Re: Hugin for games

2010-07-08 Thread Hal V. Engel
On Thursday 08 July 2010 12:13:34 pm cri wrote:
 On 5 Lug, 08:52, David Haberthür david.haberth...@gmail.com wrote:
  Hey Christian
 
   I've used Hugin to make some equirectangular 360x180 panorama from
   within some videogames (most racing and flight simulators, my
   favourite kind of videogames). Just would like to share them if you
   are
   interested:http://www.flickr.com/search/?q=panogamew=39174608%40N04
 
  They look very interesting, great idea. Did you take the screenshots by
  hand while looking in the different directions or did you automate the
  process?
 
 I thought of automating the process (in particular for Flightgear that
 is very customizable with xml) but I've almost zero knowledge on
 programming so they were taken by hand

In FlightGear you can pause the simulation (use the p key) but you can still 
do things like pan or zoom your view or change the view position.  So taking a 
set of screen shots for a panorama by hand is a fairly simple process.  But 
automating it should be fairly simple as well at least for someone with some 
programming experience.  But I think this would require using nasal rather 
than XML although you would use XML to map a key or button to the nasal 
script.

 
   From a technical point of view, I noticed that autopano-sift-C had a
   lot of problem getting the control points right so I ended up by
   identifying them manually most of the time.
 
  This might be because there's no real lens information from your
  screenshots. Did you play around with the Lens Type to see what
  difference that makes? Greetings, Habi
 
 No, I've just inserted, when requested from Hugin, a FOV that was
 reasonable. In a couple of cases was only needed the assistant tab.
 
 Regards
 Cristian
 

-- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx