Krpano not automatically detecting view settings

It has always been to my understanding --and some of my old prototypes seem to show this behaviour as well-- that Krpano is perfectly capable of determing view settings itself. In particular the properties 'fov', 'fovmax', 'vlookatmax' and 'vlookatmin'.

My input image is a simple JPG of 1837x313 px. In those old prototypes Krpano is perfectly capable of initializing and limiting the view in such a way that one cannot look beyond the top or bottom edges of the image.

Unfortunately, now I cannot for the life of me get it to work anymore. Here's me hoping some of the Krpano veterans can shed some light on the possible causes. We're using version 1.0.8.11 in both the implementation and the prototypes.

The used XML is the following:

<?xml version="1.0" encoding="UTF-8" ?>
<krpano version="1.0.8">
	<!-- Include Global Settings -->
	<include url="/js/pano/global.xml" />
	
	<!-- Include Editor Settings -->
	<include url="/js/pano/editor.xml" />
	
	<!-- View Settings -->
	<view hlookat="28" vlookat="0" />
	
	<!-- Image Settings -->
	<image type="sphere">
		<sphere url="/_temp/360fotos/panoramas/temp/pano.jpg" />
	</image>
	
	<!-- Hotspots -->
	<hotspot	name="hotspot-1"
			style="hotspot"
			ath="199"
			atv="5"
			title="Keuken"
			href="080C5BC6-F95B-4D23-87D9-9A50227D0806"
	/>
</krpano>

Even when using the following barebones version it won't work. As such, I can't believe it's caused by anything in the global.xml or editor.xml files.

<?xml version="1.0" encoding="UTF-8" ?>
<krpano version="1.0.8">
	<!-- Image Settings -->
	<image type="sphere">
		<sphere url="/_temp/360fotos/panoramas/temp/pano.jpg" />
	</image>
</krpano>

The documentation as well as my prototype leads me to believe this should work. The default settings of view.hfov equals 360 which is correct for the input image. Since view.vfov is empty, this should be calculated based on the view.hfov and the input image's dimensions. Finally, automatic limiting for vlookatmin and vlookatmax should kick in.

I tried a lot of settings related to limitrange and whatnot, but to no avail. If anyone could give some ideas what could possibly cause Krpano not to figure it out on its own, it'd be much appreciated. I am completely clueless right now.

Unfortunately, I cannot provide much more code as we have a lot of code doing lots of things, nor can I give an online location as it is not released yet.

Thanks in advance.

michel, thanks for the quick reply, but I just solved it in 10 seconds.

Very embarassed to admit it was caused by a cached version of the input image. Google Chrome caches anything loaded through Flash ruthless and never seemed to pick up on the changed JPG. Moving on.

Edit: This does make me realize we'll have to seriously look at implementing proper expiration headers for the input images as well. Already doing this with the XML though.